From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/qt:master commit in: x11-misc/sddm/
Date: Mon, 13 Feb 2023 07:53:41 +0000 (UTC) [thread overview]
Message-ID: <1676274804.89c3b54f581b42fbfab5e6f7c443255449f3a711.asturm@gentoo> (raw)
commit: 89c3b54f581b42fbfab5e6f7c443255449f3a711
Author: Robert Buhren <robert <AT> robertbuhren <DOT> de>
AuthorDate: Sun Feb 12 23:41:54 2023 +0000
Commit: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Mon Feb 13 07:53:24 2023 +0000
URL: https://gitweb.gentoo.org/proj/qt.git/commit/?id=89c3b54f
x11-misc/sddm: Change RUNTIME_DIR path to "/run/sddm"
The systemd tmpfiles config provided with sddm sets the permission for
RUNTIME_DIR to 0711. Setting RUNTIME_DIR to "/run" results in the
wrong permission set for this directory leading to bugs similar to:
"systemd-networkd fails to start before dbus.socket with selinux enabled"
Closes: https://github.com/gentoo/qt/pull/265
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>
x11-misc/sddm/sddm-9999.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x11-misc/sddm/sddm-9999.ebuild b/x11-misc/sddm/sddm-9999.ebuild
index b8117a94..d4499b5d 100644
--- a/x11-misc/sddm/sddm-9999.ebuild
+++ b/x11-misc/sddm/sddm-9999.ebuild
@@ -110,7 +110,7 @@ src_configure() {
local mycmakeargs=(
-DBUILD_MAN_PAGES=ON
-DDBUS_CONFIG_FILENAME="org.freedesktop.sddm.conf"
- -DRUNTIME_DIR=/run
+ -DRUNTIME_DIR=/run/sddm
-DSYSTEMD_TMPFILES_DIR="/usr/lib/tmpfiles.d"
-DENABLE_PAM=$(usex pam)
-DNO_SYSTEMD=$(usex !systemd)
next reply other threads:[~2023-02-13 7:53 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 7:53 Andreas Sturmlechner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-01 21:49 [gentoo-commits] proj/qt:master commit in: x11-misc/sddm/ Andreas Sturmlechner
2024-07-01 21:49 Andreas Sturmlechner
2024-07-01 21:49 Andreas Sturmlechner
2024-05-27 22:18 Andreas Sturmlechner
2024-03-08 23:03 Andreas Sturmlechner
2024-02-22 11:32 Andreas Sturmlechner
2023-11-27 10:51 Andreas Sturmlechner
2023-03-22 19:24 Andreas Sturmlechner
2023-03-10 22:08 Andreas Sturmlechner
2023-02-08 19:33 Andreas Sturmlechner
2023-02-05 16:24 Andreas Sturmlechner
2023-02-04 13:00 Andreas Sturmlechner
2023-02-04 13:00 Andreas Sturmlechner
2023-02-04 13:00 Andreas Sturmlechner
2022-10-08 10:52 Andreas Sturmlechner
2021-09-22 17:41 Andreas Sturmlechner
2021-08-13 15:13 Jimi Huotari
2019-12-31 16:44 Andreas Sturmlechner
2017-08-27 5:52 [gentoo-commits] proj/qt:qtbase59 " Michael Palimaka
2017-08-27 5:50 ` [gentoo-commits] proj/qt:master " Michael Palimaka
2015-10-01 14:27 Michael Palimaka
2014-09-22 0:08 Davide Pesavento
2014-08-04 12:47 Jauhien Piatlicki
2014-08-04 10:44 Jauhien Piatlicki
2014-07-26 9:03 Davide Pesavento
2014-07-24 17:01 Michael Palimaka
2014-06-18 13:00 Michael Palimaka
2014-06-04 13:41 Davide Pesavento
2014-05-31 16:02 Davide Pesavento
2014-02-14 19:48 Johannes Huber
2013-07-22 15:17 Ben de Groot
2013-04-29 9:09 Michael Palimaka
2013-03-24 6:58 Ben de Groot
2013-03-19 12:46 Ben de Groot
2013-03-18 14:32 Ben de Groot
2013-03-18 11:31 Ben de Groot
2013-03-18 11:04 Ben de Groot
2013-02-08 12:55 Michael Palimaka
2013-01-27 14:56 Ben de Groot
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=1676274804.89c3b54f581b42fbfab5e6f7c443255449f3a711.asturm@gentoo \
--to=asturm@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