-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
systemd: Use systemd-sysusers to create cockpit-wsinstance user #20447
Merged
martinpitt
merged 3 commits into
cockpit-project:main
from
martinpitt:main-sysuserconfig
May 8, 2024
Merged
systemd: Use systemd-sysusers to create cockpit-wsinstance user #20447
martinpitt
merged 3 commits into
cockpit-project:main
from
martinpitt:main-sysuserconfig
May 8, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 tasks
martinpitt
force-pushed
the
main-sysuserconfig
branch
from
May 8, 2024 05:57
8438537
to
e5335a5
Compare
Let's clean up properly.
Even oldoldstable and the last two Ubuntu LTSes have never versions, this isn't necessary any more.
allisonkarlitskaya
previously approved these changes
May 8, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good except for one trivial nag. Please either merge as-is, do a force-push, or I'm also fine with a follow-up (ideally before release).
Thanks!
Add a sysusers config file for our remaining system user. Arch was already using sysusers, replace the packaging specific one with the upstream one. For Debian, run dh_installsysusers (compat level 14 will do that automatically in the future). RPM 4.19 has native support for sysusers in principle [1], but it's not currently enabled/working [2]. Fedora rather wants packages to do an overcomplicated process which keeps a downstream copy of the sysusers file in the packaging dist-git [3], which is error prone and ugly to automate. So keep the tried-and-tested current approach of creating the user directly in the spec's `%pre` script for the time being (which is necessary anyway for CentOS/RHEL 9). [1] https://rpm-software-management.github.io/rpm/manual/users_and_groups.html [2] rpm-software-management/rpm#3073 [3] https://docs.fedoraproject.org/en-US/packaging-guidelines/UsersAndGroups/#_dynamic_allocation
martinpitt
force-pushed
the
main-sysuserconfig
branch
from
May 8, 2024 14:43
e5335a5
to
3862deb
Compare
allisonkarlitskaya
approved these changes
May 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was originally proposed and discussed extensively in @travier 's PR #20365. However, all of a sudden I'm not allowed to push into @travier's branch any more:
So cloning the PR from my fork.