public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "John Helmert III" <ajak@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-admin/gopass/
Date: Tue, 22 Jul 2025 00:44:16 +0000 (UTC)	[thread overview]
Message-ID: <1753144934.e82a1777ded753897dcea2aa83538d3d6d242f56.ajak@gentoo> (raw)

commit:     e82a1777ded753897dcea2aa83538d3d6d242f56
Author:     John Helmert III <ajak <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 22 00:17:23 2025 +0000
Commit:     John Helmert III <ajak <AT> gentoo <DOT> org>
CommitDate: Tue Jul 22 00:42:14 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e82a1777

app-admin/gopass: add which BDEPEND

Closes: https://bugs.gentoo.org/956840
Signed-off-by: John Helmert III <ajak <AT> gentoo.org>

 app-admin/gopass/gopass-1.15.15.ebuild | 1 +
 1 file changed, 1 insertion(+)

diff --git a/app-admin/gopass/gopass-1.15.15.ebuild b/app-admin/gopass/gopass-1.15.15.ebuild
index 911e39994059..eb96b9f61fc3 100644
--- a/app-admin/gopass/gopass-1.15.15.ebuild
+++ b/app-admin/gopass/gopass-1.15.15.ebuild
@@ -19,6 +19,7 @@ RDEPEND="
 	dev-vcs/git
 	>=app-crypt/gnupg-2
 "
+BDEPEND="sys-apps/which"
 
 PATCHES=(
 	"${FILESDIR}/${PN}-1.15.3-skip-tests.patch"


             reply	other threads:[~2025-07-22  0:44 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22  0:44 John Helmert III [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-22  0:44 [gentoo-commits] repo/gentoo:master commit in: app-admin/gopass/ John Helmert III
2025-01-21  0:05 John Helmert III
2024-12-02  0:47 John Helmert III
2024-12-02  0:47 John Helmert III
2024-12-02  0:47 John Helmert III
2024-08-31 21:28 John Helmert III
2024-08-31 21:28 John Helmert III
2024-05-18  9:09 Arthur Zamarin
2024-04-28  6:46 Arthur Zamarin
2024-04-08  4:10 John Helmert III
2024-01-08  3:24 John Helmert III
2024-01-08  3:24 John Helmert III
2023-12-03 21:41 John Helmert III
2023-12-03 21:41 John Helmert III
2023-11-25 17:56 John Helmert III
2023-11-21  4:27 John Helmert III
2023-11-21  4:27 John Helmert III
2023-11-21  4:27 John Helmert III
2023-09-14  4:47 John Helmert III
2023-04-16 20:43 John Helmert III
2023-04-16 20:43 John Helmert III
2023-04-16 20:43 John Helmert III
2023-02-26  1:10 John Helmert III
2023-02-25 17:54 Arthur Zamarin
2023-02-19 16:46 John Helmert III
2023-01-17 17:13 John Helmert III
2023-01-17 17:13 John Helmert III
2022-11-01 10:11 Yixun Lan
2022-08-26 14:37 Robin H. Johnson
2022-08-26 14:37 Robin H. Johnson
2022-05-17  5:08 Robin H. Johnson
2021-12-18 17:28 Mikle Kolyada
2021-07-02 17:45 Mikle Kolyada
2021-07-02 17:45 Mikle Kolyada
2021-07-02 17:45 Mikle Kolyada
2021-07-02 17:35 Mikle Kolyada
2021-05-12 19:30 Mikle Kolyada
2021-05-12 19:29 Mikle Kolyada
2021-03-28  7:42 Mikle Kolyada
2021-03-28  7:42 Mikle Kolyada
2021-03-21 18:11 Mikle Kolyada
2021-03-21 18:11 Mikle Kolyada
2021-03-13 19:48 Mikle Kolyada
2021-03-13 19:48 Mikle Kolyada
2021-03-10 10:09 Mikle Kolyada
2021-03-09 10:01 Mikle Kolyada
2021-02-22 23:21 Mikle Kolyada
2021-01-20 10:26 Mikle Kolyada
2020-11-13 17:32 Mikle Kolyada
2020-11-13 17:32 Mikle Kolyada
2020-08-30 22:09 Georgy Yakovlev
2020-08-28  7:03 Mikle Kolyada
2020-06-19  9:06 Mikle Kolyada
2020-06-19  9:06 Mikle Kolyada
2020-05-19 20:35 Georgy Yakovlev
2020-05-14 11:18 Mikle Kolyada
2020-05-10 14:30 Mikle Kolyada
2020-05-04 19:34 Mikle Kolyada
2019-11-22 15:48 Mikle Kolyada
2019-11-19 17:59 Mikle Kolyada
2019-11-18 22:21 Tim Harder
2019-11-18 22:21 Tim Harder
2019-08-21 11:58 Tim Harder
2019-08-21 11:58 Tim Harder
2019-03-28  7:03 Tim Harder
2019-02-05 11:29 Tim Harder
2018-12-12  8:25 Tim Harder

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=1753144934.e82a1777ded753897dcea2aa83538d3d6d242f56.ajak@gentoo \
    --to=ajak@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