Description of problem: Currently, packages that need to create uid/gid are supposed to run useradd/groupadd manually, and for pre-allocated uids/gids even with a bit more complex logic: https://fedoraproject.org/wiki/Packaging:UsersAndGroups#Soft_static_allocation (The version as of the time of filing this bugzilla is https://fedoraproject.org/w/index.php?title=Packaging:UsersAndGroups&oldid=331685#Soft_static_allocation). It would be good to provide utility which would do this automatically, using values from /usr/share/doc/setup/uidgid (that probably should no longer be %doc but real data file), avoiding the need of hardcoding the uid/gid in all packages that feel they need the user. Or it could be an rpm macro. Then the guidelines could be changed to recommend to just call this one utility / macro -- something like %pre ensure-user-exists apache or %pre %ensure-user-exists apache and packages changed to just do this. Even better, rpm could this automatically when it would detect files owned by user that does not exist but is defined in uidgid. Additional benefit would be should the local users start to live somewhere else than in /etc/passwd one day -- possibly in local sssd database. Then this single utility would need to be changed to add the feature or enhance it, rather than multiple .spec files. Version-Release number of selected component (if applicable): shadow-utils-4.1.5.1-8.fc20.x86_64 and Packaging:UsersAndGroups as of today How reproducible: Deterministic. Steps to Reproduce: 1. Try to ensure user exists for your packages (bug 1143067 or bug 1143067). 2. Read the Packaging:UsersAndGroups. 3. Wonder if this is the easiest way to do it. Actual results: It's not that easy. Expected results: It's very easy. Additional info:
A good partial step could be for useradd/groupadd with -r and without -u/-g to observe uidgid and use those values if no clashing record yet exists, instead of going down from 999. That would also lead to gradual consolidation of installations to use the pre-allocated uids/gids.
(In reply to Jan Pazdziora from comment #0) > 1. Try to ensure user exists for your packages (bug 1143067 or bug 1143067). I meant to write bug 1143066 or bug 1143067 here.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I am sorry, we are not going to pursue this RFE at this point. Pagure PRs are always welcome.