public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 1/2] dbus-broker: Do not longer create user/group
Date: Wed, 29 Mar 2023 16:35:21 +0200	[thread overview]
Message-ID: <20230329143522.2559935-1-stefan.schantl@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]

The dbus user and group will be created by the dbus-common packge
which is a dependency of dbus-brocker. So no need for trying to doubble
create them.
---
 dbus-broker/dbus-broker.nm | 12 +-----------
 1 file changed, 1 insertion(+), 11 deletions(-)

diff --git a/dbus-broker/dbus-broker.nm b/dbus-broker/dbus-broker.nm
index a65a1e0d6..5a33f4ad7 100644
--- a/dbus-broker/dbus-broker.nm
+++ b/dbus-broker/dbus-broker.nm
@@ -5,7 +5,7 @@
 
 name       = dbus-broker
 version    = 32
-release    = 1
+release    = 2
 
 maintainer = Stefan Schantl <stefan.schantl(a)ipfire.org>
 groups     = System/Daemons
@@ -58,16 +58,6 @@ packages
 			dbus-common
 		end
 
-		prerequires += shadow-utils
-
-		script prein
-			getent group dbus >/dev/null || groupadd -r dbus
-			getent passwd dbus >/dev/null || \
-				useradd -r -g dbus -d / -s /sbin/nologin \
-					-c "User for dbus service" dbus
-			exit  0
-		end
-
 		# Just search for new unit files that were just installed.
 		script postin
 			systemctl daemon-reload >/dev/null 2>&1 || :
-- 
2.30.2


             reply	other threads:[~2023-03-29 14:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 14:35 Stefan Schantl [this message]
2023-03-29 14:35 ` [PATCH 2/2] dbus: Ship our own sysusers file Stefan Schantl

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=20230329143522.2559935-1-stefan.schantl@ipfire.org \
    --to=stefan.schantl@ipfire.org \
    --cc=development@lists.ipfire.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