From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-kernel/ugrd/
Date: Mon, 20 Jan 2025 23:49:56 +0000 (UTC) [thread overview]
Message-ID: <1737416905.e91ba92eda10d4711c183c2b5da97194a6b49b80.sam@gentoo> (raw)
commit: e91ba92eda10d4711c183c2b5da97194a6b49b80
Author: Zen <z <AT> pyl <DOT> onl>
AuthorDate: Mon Jan 20 22:34:55 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jan 20 23:48:25 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e91ba92e
sys-kernel/ugrd: revise 1.29.0, fix RDEPEND version for zenlib
3.0.2 is needed for colorize
Closes: https://bugs.gentoo.org/948464
Signed-off-by: Zen <z <AT> pyl.onl>
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-kernel/ugrd/{ugrd-1.29.0.ebuild => ugrd-1.29.0-r1.ebuild} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sys-kernel/ugrd/ugrd-1.29.0.ebuild b/sys-kernel/ugrd/ugrd-1.29.0-r1.ebuild
similarity index 95%
rename from sys-kernel/ugrd/ugrd-1.29.0.ebuild
rename to sys-kernel/ugrd/ugrd-1.29.0-r1.ebuild
index 21ddb7fb455a..c7003f024a64 100644
--- a/sys-kernel/ugrd/ugrd-1.29.0.ebuild
+++ b/sys-kernel/ugrd/ugrd-1.29.0-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 2023-2024 Gentoo Authors
+# Copyright 2023-2025 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
@@ -19,7 +19,7 @@ PROPERTIES="test_privileged"
RDEPEND="
app-misc/pax-utils
- >=dev-python/zenlib-2.3.2[${PYTHON_USEDEP}]
+ >=dev-python/zenlib-3.0.2[${PYTHON_USEDEP}]
>=dev-python/pycpio-1.4.0[${PYTHON_USEDEP}]
sys-apps/pciutils
"
next reply other threads:[~2025-01-20 23:50 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 23:49 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-21 21:13 [gentoo-commits] repo/gentoo:master commit in: sys-kernel/ugrd/ Nowa Ammerlaan
2025-01-25 19:25 Nowa Ammerlaan
2025-01-25 0:48 Sam James
2025-01-21 15:02 Nowa Ammerlaan
2025-01-21 15:02 Nowa Ammerlaan
2025-01-20 23:49 Sam James
2025-01-20 23:49 Sam James
2025-01-20 23:49 Sam James
2025-01-14 20:36 Nowa Ammerlaan
2025-01-14 20:36 Nowa Ammerlaan
2025-01-14 17:27 Sam James
2025-01-04 15:29 Nowa Ammerlaan
2025-01-04 15:29 Nowa Ammerlaan
2025-01-04 15:29 Nowa Ammerlaan
2024-12-03 8:08 Sam James
2024-11-20 9:37 Nowa Ammerlaan
2024-11-20 9:37 Nowa Ammerlaan
2024-11-09 10:03 Arthur Zamarin
2024-11-09 9:02 Arthur Zamarin
2024-11-01 17:10 Andrew Ammerlaan
2024-11-01 8:55 Andrew Ammerlaan
2024-11-01 8:55 Andrew Ammerlaan
2024-10-27 8:46 Andrew Ammerlaan
2024-10-27 8:46 Andrew Ammerlaan
2024-10-24 8:42 Arthur Zamarin
2024-10-23 7:53 Jakov Smolić
2024-10-14 7:21 Andrew Ammerlaan
2024-10-14 7:21 Andrew Ammerlaan
2024-10-12 16:33 Andrew Ammerlaan
2024-10-12 16:33 Andrew Ammerlaan
2024-10-10 16:54 Andrew Ammerlaan
2024-10-10 16:20 Arthur Zamarin
2024-10-08 10:22 Andrew Ammerlaan
2024-09-23 14:45 Andrew Ammerlaan
2024-09-14 12:26 Andrew Ammerlaan
2024-09-14 12:26 Andrew Ammerlaan
2024-09-03 7:37 Andrew Ammerlaan
2024-09-03 7:37 Andrew Ammerlaan
2024-08-31 18:51 Andrew Ammerlaan
2024-08-29 7:18 Andrew Ammerlaan
2024-08-10 8:45 Andrew Ammerlaan
2024-07-21 17:42 Andrew Ammerlaan
2024-07-21 17:42 Andrew Ammerlaan
2024-07-15 23:29 Sam James
2024-07-15 19:18 Andrew Ammerlaan
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=1737416905.e91ba92eda10d4711c183c2b5da97194a6b49b80.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