From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/patch/
Date: Sun, 09 Feb 2025 04:32:36 +0000 (UTC) [thread overview]
Message-ID: <1739074484.93c764bb648eebcb1c878f4019b33ebdadc2233b.sam@gentoo> (raw)
commit: 93c764bb648eebcb1c878f4019b33ebdadc2233b
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 9 04:14:44 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Feb 9 04:14:44 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=93c764bb
sys-devel/patch: sync live, fix verify-sig dep
See aea62d8988f0c4da2d9d522046ccad12e51edd32.
Fixes: f1a47f75b7d37843cb73d8a060e15afa9c626f23
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-devel/patch/patch-2.7.6_p20250206.ebuild | 2 +-
sys-devel/patch/patch-9999.ebuild | 11 +++++++++--
2 files changed, 10 insertions(+), 3 deletions(-)
diff --git a/sys-devel/patch/patch-2.7.6_p20250206.ebuild b/sys-devel/patch/patch-2.7.6_p20250206.ebuild
index 15df468ab034..c410f22ffd4f 100644
--- a/sys-devel/patch/patch-2.7.6_p20250206.ebuild
+++ b/sys-devel/patch/patch-2.7.6_p20250206.ebuild
@@ -34,7 +34,7 @@ RDEPEND="xattr? ( sys-apps/attr )"
DEPEND="${RDEPEND}"
BDEPEND="
test? ( sys-apps/ed )
- verify-sig? ( sec-keys/openpgp-keys-patch )
+ verify-sig? ( >=sec-keys/openpgp-keys-patch-20250206 )
"
src_unpack() {
diff --git a/sys-devel/patch/patch-9999.ebuild b/sys-devel/patch/patch-9999.ebuild
index df6c6cec8db2..c410f22ffd4f 100644
--- a/sys-devel/patch/patch-9999.ebuild
+++ b/sys-devel/patch/patch-9999.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2024 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
@@ -11,6 +11,13 @@ HOMEPAGE="https://www.gnu.org/software/patch/patch.html"
if [[ ${PV} == 9999 ]] ; then
EGIT_REPO_URI="https://git.savannah.gnu.org/git/patch.git"
inherit git-r3
+elif [[ ${PV} = *_p* ]] ; then
+ # Note: could put this in devspace, but if it's gone, we don't want
+ # it in tree anyway. It's just for testing.
+ MY_SNAPSHOT="$(ver_cut 1-3).211-86ac"
+ SRC_URI="https://alpha.gnu.org/gnu/patch/patch-${MY_SNAPSHOT}.tar.xz -> ${P}.tar.xz"
+ SRC_URI+=" verify-sig? ( https://alpha.gnu.org/gnu/patch/patch-${MY_SNAPSHOT}.tar.xz.sig -> ${P}.tar.xz.sig )"
+ S="${WORKDIR}"/${PN}-${MY_SNAPSHOT}
else
SRC_URI="mirror://gnu/patch/${P}.tar.xz"
SRC_URI+=" verify-sig? ( mirror://gnu/patch/${P}.tar.xz.sig )"
@@ -27,7 +34,7 @@ RDEPEND="xattr? ( sys-apps/attr )"
DEPEND="${RDEPEND}"
BDEPEND="
test? ( sys-apps/ed )
- verify-sig? ( sec-keys/openpgp-keys-patch )
+ verify-sig? ( >=sec-keys/openpgp-keys-patch-20250206 )
"
src_unpack() {
next reply other threads:[~2025-02-09 4:32 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 4:32 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-05 23:09 [gentoo-commits] repo/gentoo:master commit in: sys-devel/patch/ Sam James
2025-05-01 20:04 Arthur Zamarin
2025-05-01 6:10 Sam James
2025-05-01 6:07 Sam James
2025-05-01 6:01 Sam James
2025-05-01 5:59 Sam James
2025-05-01 5:59 Sam James
2025-04-13 21:22 Sam James
2025-03-13 1:21 Sam James
2025-03-13 1:11 Sam James
2025-03-13 1:11 Sam James
2025-03-13 1:09 Sam James
2025-03-13 0:53 Sam James
2025-03-13 0:45 Sam James
2025-02-27 7:04 Eli Schwartz
2025-02-14 8:22 Eli Schwartz
2025-02-06 23:31 Eli Schwartz
2025-01-21 3:41 Sam James
2024-11-03 20:47 Eli Schwartz
2024-09-01 1:37 Sam James
2023-03-31 12:08 Arthur Zamarin
2023-02-24 18:36 Sam James
2023-01-29 0:59 Sam James
2023-01-27 8:05 Sam James
2023-01-27 8:05 Sam James
2023-01-27 8:05 Sam James
2023-01-27 8:05 Sam James
2023-01-27 6:31 Sam James
2023-01-27 6:31 Sam James
2022-10-30 15:51 Sam James
2022-04-07 3:57 Sam James
2022-01-06 9:07 David Seifert
2021-01-06 15:32 Fabian Groffen
2020-12-27 18:18 Fabian Groffen
2020-05-04 17:36 Thomas Deutschmann
2019-08-23 10:26 Mikle Kolyada
2019-08-23 10:26 Mikle Kolyada
2019-08-23 10:26 Mikle Kolyada
2019-08-23 10:26 Mikle Kolyada
2019-08-23 10:26 Mikle Kolyada
2019-08-23 10:00 Agostino Sarubbo
2019-08-19 6:57 Sergei Trofimovich
2019-08-18 10:12 Sergei Trofimovich
2019-08-18 10:10 Sergei Trofimovich
2019-08-18 10:08 Sergei Trofimovich
2019-08-18 8:29 Sergei Trofimovich
2019-08-16 22:38 Thomas Deutschmann
2019-08-16 21:53 Aaron Bauman
2019-08-16 21:50 Mikle Kolyada
2019-05-03 23:38 Mikle Kolyada
2019-04-11 9:49 Mikle Kolyada
2019-04-11 9:49 Mikle Kolyada
2019-04-11 9:49 Mikle Kolyada
2019-04-10 22:03 Sergei Trofimovich
2019-04-08 8:39 Mart Raudsepp
2019-04-08 6:42 Mikle Kolyada
2019-04-07 21:53 Mikle Kolyada
2019-04-07 21:41 Mikle Kolyada
2019-04-07 20:52 Sergei Trofimovich
2019-04-05 20:47 Agostino Sarubbo
2018-08-31 3:26 Thomas Deutschmann
2018-08-31 3:26 Thomas Deutschmann
2018-05-27 14:53 Mikle Kolyada
2018-04-24 15:14 Mart Raudsepp
2018-03-22 16:37 Mikle Kolyada
2018-03-18 1:02 Matt Turner
2018-03-18 1:02 Matt Turner
2018-03-15 14:14 Mikle Kolyada
2018-03-05 13:57 Tobias Klausmann
2018-02-17 22:12 Sergei Trofimovich
2018-02-14 13:29 Jason Zaman
2018-02-13 7:54 Sergei Trofimovich
2018-02-12 21:36 Thomas Deutschmann
2018-02-07 11:35 Lars Wendler
2018-02-07 9:51 Lars Wendler
2017-02-20 14:11 Michael Haubenwallner
2017-01-29 20:14 Fabian Groffen
2016-12-07 8:40 Mike Frysinger
2016-12-01 21:59 Lars Wendler
2016-02-29 8:46 Stephen Klimaszewski
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=1739074484.93c764bb648eebcb1c878f4019b33ebdadc2233b.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