Didn't look through this all just now, but a couple of quick notes:
- The sysusers support is disabled in the Fedora package, you need to uncomment
%__systemd_sysusers in the main macros file
- The sysusers addition runs from *outside* a chroot, so the "host" provides
all the dependencies. That's basically the only way an empty chroot can be
bootstrapped with file ownerships from the first package. In other words,
you're overthinking it all by a mile. It's of course possible the main rpm is
missing some packages for the script-based sysusers.sh version (and should be
added explicitly), but grep, shadow-utils and all that are almost certainly
pulled in by something else that rpm depends on. That's a Fedora packaging
matter though.
- The dbus user vs group EVR thing is explained in
https://rpm-software-management.github.io/rpm/manual/users_and_groups.html the
technical details section but in short: sysusers creates implicit groups for
all users, so the group doesn't need any more info. The provides is there only
for dependency resolution.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2697#issuecomment-1750090967
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2697/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
http://lists.rpm.org/mailman/listinfo/rpm-maint
