From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/tmpfiles/
Date: Sun, 17 Apr 2022 12:48:48 +0000 (UTC) [thread overview]
Message-ID: <1650199720.ca1b03dcdafbbe4bb1bb5d096a67db79ee045be1.sam@gentoo> (raw)
commit: ca1b03dcdafbbe4bb1bb5d096a67db79ee045be1
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 17 12:45:14 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Apr 17 12:48:40 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ca1b03dc
virtual/tmpfiles: keep transitional sys-apps/systemd-tmpfiles
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 systemd-tmpfiles 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/tmpfiles/{tmpfiles-0-r2.ebuild => tmpfiles-0-r3.ebuild} | 1 +
1 file changed, 1 insertion(+)
diff --git a/virtual/tmpfiles/tmpfiles-0-r2.ebuild b/virtual/tmpfiles/tmpfiles-0-r3.ebuild
similarity index 94%
rename from virtual/tmpfiles/tmpfiles-0-r2.ebuild
rename to virtual/tmpfiles/tmpfiles-0-r3.ebuild
index 98146846fcc7..3b9e2b2f95f7 100644
--- a/virtual/tmpfiles/tmpfiles-0-r2.ebuild
+++ b/virtual/tmpfiles/tmpfiles-0-r3.ebuild
@@ -11,6 +11,7 @@ RDEPEND="
!prefix-guest? (
|| (
sys-apps/systemd-utils[tmpfiles]
+ sys-apps/systemd-tmpfiles
sys-apps/systemd
)
)"
next reply other threads:[~2022-04-17 12:48 UTC|newest]
Thread overview: 34+ 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-06-15 2:07 [gentoo-commits] repo/gentoo:master commit in: virtual/tmpfiles/ Sam James
2023-06-15 2:03 Sam James
2023-04-22 12:08 Sam James
2022-08-04 21:56 David Seifert
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-08-24 11:33 Fabian Groffen
2021-05-13 15:19 David Seifert
2021-01-06 12:42 Fabian Groffen
2020-12-03 11:32 Andreas K. Hüttel
2020-11-28 19:15 Georgy Yakovlev
2020-11-28 19:15 Georgy Yakovlev
2020-10-29 6:42 Georgy Yakovlev
2019-05-04 9:37 Mikle Kolyada
2018-12-07 9:01 Fabian Groffen
2018-07-04 14:08 Michael Haubenwallner
2018-02-22 20:49 Michał Górny
2017-04-08 8:58 Jeroen Roovers
2017-03-11 17:07 Agostino Sarubbo
2017-02-28 11:22 Tobias Klausmann
2017-02-25 10:03 Agostino Sarubbo
2017-02-24 8:30 Michael Weber
2017-02-24 5:45 Mike Frysinger
2017-02-22 16:08 Agostino Sarubbo
2017-02-22 15:06 Agostino Sarubbo
2016-12-01 22:18 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=1650199720.ca1b03dcdafbbe4bb1bb5d096a67db79ee045be1.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