http://bugzilla.suse.com/show_bug.cgi?id=1035286 http://bugzilla.suse.com/show_bug.cgi?id=1035286#c4 Thorsten Kukuk changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dleuenberger@suse.com Flags|needinfo?(kukuk@suse.com) | --- Comment #4 from Thorsten Kukuk --- (In reply to Franck Bui from comment #0)

Hi,

When setting up a new root filesystem based on the latest snapshot of TW I got the following errors:

(147/170) Installing: dbus-1-1.10.16-1.1.x86_64 ....................................................[done] Additional rpm output: groupadd: Cannot determine your user name. useradd: group '100' does not exist

group user (100) is still part of aaa_base, nothing has changed here. Why is it not there? Both errors mean: aaa_base is not yet installed. For some reasons it will be installed too late now.

useradd: the GROUP= configuration in /etc/default/useradd will be ignored useradd: group 'messagebus' does not exist /var/tmp/rpm-tmp.vAtfeB: line 40: dbus-daemon: command not found

Ok, you cannot call binaries in %pre section from the current, to be installed package. Bug in dbus-1 %pre section. (In reply to Simon Lees from comment #3)

Thorsten, is this a case where I should be using your new system user setup or should dbus create the "messagebus" user itself?

This has nothing to do with the new system user design or not. There are two bugs: 1. aaa_base will now be installed too late 2. dbus-1 %pre section is buggy calling tools not yet installed. If only dbus-1 uses this accounts, you can stay with useradd. Else you can move this into a system-user-messagebus RPM. But be carefull: if systemd has a requires to dbus and dbus will now get an requires to systemd, you will create an unsolveable dependency cycle. -- You are receiving this mail because: You are on the CC list for the bug.