public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Haelwenn Monnier" <contact@hacktivis.me>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: sec-keys/signify-keys-lanodan/
Date: Tue,  2 Apr 2024 13:11:40 +0000 (UTC)	[thread overview]
Message-ID: <1712063486.3521640e86009a7fde0b4cf24d9dda6ba3a4496f.lanodan@gentoo> (raw)

commit:     3521640e86009a7fde0b4cf24d9dda6ba3a4496f
Author:     Haelwenn (lanodan) Monnier <contact <AT> hacktivis <DOT> me>
AuthorDate: Tue Apr  2 13:10:55 2024 +0000
Commit:     Haelwenn Monnier <contact <AT> hacktivis <DOT> me>
CommitDate: Tue Apr  2 13:11:26 2024 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=3521640e

sec-keys/signify-keys-lanodan: Use verify-sig? in BDEPEND

Signed-off-by: Haelwenn (lanodan) Monnier <contact <AT> hacktivis.me>

 sec-keys/signify-keys-lanodan/signify-keys-lanodan-2023.ebuild | 2 +-
 sec-keys/signify-keys-lanodan/signify-keys-lanodan-2024.ebuild | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/sec-keys/signify-keys-lanodan/signify-keys-lanodan-2023.ebuild b/sec-keys/signify-keys-lanodan/signify-keys-lanodan-2023.ebuild
index f99506fa8f..321dda971d 100644
--- a/sec-keys/signify-keys-lanodan/signify-keys-lanodan-2023.ebuild
+++ b/sec-keys/signify-keys-lanodan/signify-keys-lanodan-2023.ebuild
@@ -19,7 +19,7 @@ LICENSE="public-domain"
 SLOT="${PV}"
 KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc ~x86"
 
-BDEPEND="sec-keys/signify-keys-lanodan:${MY_PREV_PV}"
+BDEPEND="verify-sig? ( sec-keys/signify-keys-lanodan:${MY_PREV_PV} )"
 
 VERIFY_SIG_OPENPGP_KEY_PATH="/usr/share/signify-keys/${PN}-${MY_PREV_PV//-/.}.pub"
 

diff --git a/sec-keys/signify-keys-lanodan/signify-keys-lanodan-2024.ebuild b/sec-keys/signify-keys-lanodan/signify-keys-lanodan-2024.ebuild
index 1a93567530..f41946bf96 100644
--- a/sec-keys/signify-keys-lanodan/signify-keys-lanodan-2024.ebuild
+++ b/sec-keys/signify-keys-lanodan/signify-keys-lanodan-2024.ebuild
@@ -19,7 +19,7 @@ LICENSE="public-domain"
 SLOT="${PV}"
 KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc ~x86"
 
-BDEPEND="sec-keys/signify-keys-lanodan:${MY_PREV_PV}"
+BDEPEND="verify-sig? ( sec-keys/signify-keys-lanodan:${MY_PREV_PV} )"
 
 VERIFY_SIG_OPENPGP_KEY_PATH="/usr/share/signify-keys/${PN}-${MY_PREV_PV}.pub"
 


             reply	other threads:[~2024-04-02 13:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 13:11 Haelwenn Monnier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-06 18:19 [gentoo-commits] repo/proj/guru:dev commit in: sec-keys/signify-keys-lanodan/ Haelwenn Monnier
2024-04-04 12:13 Haelwenn Monnier
2024-04-02 12:38 Haelwenn Monnier
2024-04-02 12:34 Haelwenn Monnier

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=1712063486.3521640e86009a7fde0b4cf24d9dda6ba3a4496f.lanodan@gentoo \
    --to=contact@hacktivis.me \
    --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