You are not logged in.
I've just updated my filesystem package and {group,passwd,gshadow,shadow}.pacnew popped up.
A quick look on package commit shows that uuidd and dbus system users are being moved to systemd-sysusers.
( https://git.archlinux.org/svntogit/pack … 12bd55b0db , https://bugs.archlinux.org/task/45196 )
But `man sysusers.d` says that the sysuser may be created at install time or boot time. So I wonder the current dbus and uuidd entries in my files are whether:
1) Just the same as the configuration that would be if I did a fresh install of filesystem, libutil-linux and dbus, which would do this at intall time; or
2) Is better to be removed, since they are to be created dynamically evert time the system boots up.
Last edited by Dreaming in Code (2017-04-01 06:01:35)
Offline
Standard answer: Ignore group/passwd pacnew files.
Offline
Standard answer: Ignore group/passwd pacnew files.
I'd gladly ignore changes introduced by modification from other packages; however I'm asking about this specific change about moving to systemd-sysusers.
Last edited by Dreaming in Code (2017-04-01 03:38:55)
Offline
And the answer doesn't change.
Offline
Yes, indeed. Did a fresh installation in virtualbox and the entries are there. Marking as solved.
Last edited by Dreaming in Code (2017-04-01 06:02:25)
Offline
Just out of interest, are there anything I actually need from those pacnew files? I just assume delete the pacnew files for the most part. I'm guessing if we need to edit existing group, gshadow, shadow, and passwd files there'd be an arch announce on which variable to rename.
Offline
Just out of interest, are there anything I actually need from those pacnew files? I just assume delete the pacnew files for the most part. I'm guessing if we need to edit existing group, gshadow, shadow, and passwd files there'd be an arch announce on which variable to rename.
No; the only changes shown in git is removal of hard-coded uuidd and dbus users, and they are added back once you install dbus and libutil-linux.
Offline