From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/libudev/
Date: Sun, 17 Apr 2022 12:48:48 +0000 (UTC) [thread overview]
Message-ID: <1650199722.32eec7440046151d9de01bee671186571f7cc32b.sam@gentoo> (raw)
commit: 32eec7440046151d9de01bee671186571f7cc32b
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 17 12:47:59 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Apr 17 12:48:42 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=32eec744
virtual/libudev: keep transitional sys-fs/udev
Portage may be inclined to try (and fail) to use systemd
here instead of the new (for non-systemd systems) systemd-utils
tools package, so let's include sys-fs/udev instead, which
is a transitional package, below systemd-utils.
Already seen one nasty such situation where Portage gets
confused & can't resolve w/o this, and this sorts it out.
Signed-off-by: Sam James <sam <AT> gentoo.org>
virtual/libudev/{libudev-232-r6.ebuild => libudev-232-r7.ebuild} | 1 +
1 file changed, 1 insertion(+)
diff --git a/virtual/libudev/libudev-232-r6.ebuild b/virtual/libudev/libudev-232-r7.ebuild
similarity index 93%
rename from virtual/libudev/libudev-232-r6.ebuild
rename to virtual/libudev/libudev-232-r7.ebuild
index aed453196d9b..60120fb8bbda 100644
--- a/virtual/libudev/libudev-232-r6.ebuild
+++ b/virtual/libudev/libudev-232-r7.ebuild
@@ -14,6 +14,7 @@ IUSE="systemd"
RDEPEND="
!systemd? ( || (
sys-apps/systemd-utils[udev,${MULTILIB_USEDEP}]
+ sys-fs/udev[${MULTILIB_USEDEP}]
>=sys-fs/eudev-3.2.9:0/0[${MULTILIB_USEDEP}]
) )
systemd? ( >=sys-apps/systemd-232:0/2[${MULTILIB_USEDEP}] )
next reply other threads:[~2022-04-17 12:48 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 12:48 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-12 14:27 [gentoo-commits] repo/gentoo:master commit in: virtual/libudev/ Mike Gilbert
2023-10-12 14:27 Mike Gilbert
2023-10-12 14:27 Mike Gilbert
2023-09-01 16:07 Arthur Zamarin
2023-08-29 18:02 Arthur Zamarin
2023-08-29 17:55 Arthur Zamarin
2023-08-29 17:49 Arthur Zamarin
2023-07-31 15:22 Mike Gilbert
2023-07-21 12:43 Sam James
2023-07-20 19:12 Matt Turner
2023-06-15 2:03 Sam James
2023-06-15 2:03 Sam James
2022-06-04 2:21 Sam James
2022-06-03 7:05 Sam James
2022-06-03 0:52 Sam James
2022-06-03 0:52 Sam James
2022-06-03 0:37 Sam James
2022-06-02 1:52 Sam James
2022-06-02 1:52 Sam James
2022-05-30 7:15 Sam James
2022-04-16 23:13 Mike Gilbert
2021-09-07 17:37 Mike Gilbert
2021-08-13 16:18 Mike Gilbert
2021-08-13 16:18 Mike Gilbert
2021-08-09 15:15 Mike Gilbert
2021-07-22 22:45 William Hubbs
2019-12-10 8:47 Agostino Sarubbo
2019-12-03 8:37 Agostino Sarubbo
2019-12-02 11:04 Mikle Kolyada
2019-12-02 11:04 Mikle Kolyada
2019-12-02 11:04 Mikle Kolyada
2019-11-30 21:45 Sergei Trofimovich
2019-11-21 22:20 Matt Turner
2019-11-11 18:09 Aaron Bauman
2019-11-08 3:23 Aaron Bauman
2019-11-04 20:06 Sergei Trofimovich
2019-11-04 20:06 Sergei Trofimovich
2019-11-02 0:42 Matt Turner
2019-11-02 0:42 Matt Turner
2019-11-01 20:09 Matt Turner
2019-11-01 20:09 Matt Turner
2019-11-01 19:30 Mike Gilbert
2019-11-01 10:51 Mikle Kolyada
2019-11-01 10:34 Mikle Kolyada
2019-10-31 23:50 Thomas Deutschmann
2019-10-28 17:12 Mike Gilbert
2019-10-28 17:10 Mike Gilbert
2019-10-28 12:07 Anthony G. Basile
2019-10-27 15:31 Michał Górny
2019-10-27 15:31 Michał Górny
2019-10-27 15:31 Michał Górny
2019-05-04 19:58 Andreas K. Hüttel
2018-04-18 5:54 Mart Raudsepp
2017-09-14 20:19 Sergei Trofimovich
2017-07-13 1:56 Markus Meier
2017-07-12 9:38 Sergei Trofimovich
2017-07-04 18:06 Mike Gilbert
2017-07-04 17:27 Mike Gilbert
2016-11-26 19:41 Mike Gilbert
2016-11-26 19:41 Mike Gilbert
2016-11-04 23:15 William Hubbs
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=1650199722.32eec7440046151d9de01bee671186571f7cc32b.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