public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-irc/ngircd/
Date: Wed, 11 Dec 2024 06:01:14 +0000 (UTC)	[thread overview]
Message-ID: <1733896803.0e87697f7b0156ed13ea2fda04667711fefb0817.sam@gentoo> (raw)

commit:     0e87697f7b0156ed13ea2fda04667711fefb0817
Author:     Z. Liu <zhixu.liu <AT> gmail <DOT> com>
AuthorDate: Wed Dec 11 05:43:55 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Dec 11 06:00:03 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0e87697f

net-irc/ngircd: verify-sig depend on newer pgp key

Bug: https://bugs.gentoo.org/901975
Signed-off-by: Z. Liu <zhixu.liu <AT> gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/39674
Signed-off-by: Sam James <sam <AT> gentoo.org>

 net-irc/ngircd/ngircd-26.1-r5.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-irc/ngircd/ngircd-26.1-r5.ebuild b/net-irc/ngircd/ngircd-26.1-r5.ebuild
index edb828a920e5..867467ff64ce 100644
--- a/net-irc/ngircd/ngircd-26.1-r5.ebuild
+++ b/net-irc/ngircd/ngircd-26.1-r5.ebuild
@@ -39,7 +39,7 @@ BDEPEND="
 		dev-tcltk/expect
 		net-misc/netkit-telnetd
 	)
-	verify-sig? ( sec-keys/openpgp-keys-alexbarton )
+	verify-sig? ( >=sec-keys/openpgp-keys-alexbarton-20241211 )
 "
 
 PATCHES=(


             reply	other threads:[~2024-12-11  6:01 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11  6:01 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-22 15:29 [gentoo-commits] repo/gentoo:master commit in: net-irc/ngircd/ Sam James
2025-04-28 14:01 Sam James
2025-04-28  4:39 Sam James
2025-04-28  4:32 Sam James
2025-04-28  4:21 Sam James
2024-12-27  8:13 Sam James
2024-12-11  6:12 Sam James
2022-10-04  9:09 Sam James
2022-08-15  7:42 Agostino Sarubbo
2022-08-15  7:41 Agostino Sarubbo
2022-08-15  7:40 Agostino Sarubbo
2022-04-15  6:36 Arthur Zamarin
2022-04-14  8:12 Agostino Sarubbo
2022-04-14  8:08 Agostino Sarubbo
2022-04-13  9:32 Jakov Smolić
2022-04-12 21:04 Sam James
2022-03-12 12:33 Arthur Zamarin
2021-08-05  1:56 Sam James
2021-07-31 13:40 Michał Górny
2021-07-09 15:04 Sam James
2021-05-02 19:47 Mikle Kolyada
2021-04-20 21:04 Sam James
2021-04-16  3:58 Sam James
2021-04-16  3:58 Sam James
2021-03-23  4:53 Sam James
2021-02-14 19:59 Sam James
2021-02-13 19:18 Sam James
2021-02-03  0:01 Sam James
2021-02-02 21:00 Sam James
2021-01-02 21:08 Sam James
2020-08-19 14:33 Sam James
2020-07-25 13:09 Sam James
2020-07-24 23:53 Sam James
2020-07-24 15:09 Agostino Sarubbo
2020-07-08 20:50 Sam James
2020-06-20 20:31 Thomas Deutschmann
2020-06-20 20:31 Thomas Deutschmann
2020-06-08 16:34 Mart Raudsepp
2020-06-08  6:41 Michał Górny
2020-06-03 15:10 Agostino Sarubbo
2020-06-03 10:27 Agostino Sarubbo
2020-05-08  6:25 Mart Raudsepp
2020-04-26 13:37 Joonas Niilola
2020-04-26 13:37 Joonas Niilola
2019-10-12 21:00 Mikle Kolyada
2017-04-27 10:36 Agostino Sarubbo
2017-02-23  8:41 Michael Palimaka
2017-02-23  8:39 Michael Palimaka
2016-05-13  8:41 Agostino Sarubbo
2015-12-29 15:49 Ian Delaney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1733896803.0e87697f7b0156ed13ea2fda04667711fefb0817.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox