-
Notifications
You must be signed in to change notification settings - Fork 210
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
Reload dbus in post install script #5419
Conversation
This is needed so that newly created users are taken into account for dbus permission handling.
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.
- Are you sure this actually works?
- Have you tried it out?
- Is there a macro to be used for systemd or should this be unconditionally included?
- Please add a ticket reference
- I suggest to rewrite the git commit message to make the effect clear in the subject line, i.e. turn around the subject and first line
- Isn't this about os-autoinst where script/os-autoinst-setup-multi-machine and systemd/os-autoinst-openvswitch.service.in live?
No
I tried but we seem to do too much black magic so I wasn't able to quickly build the rpm locally using
I don't know - if there is one, factory reviewers might tell us. Documentation in the wiki doesn't state that anything needs to be used.
https://progress.opensuse.org/issues/138302
I think it makes more sence like it is now.
The user is created in this spec file (actually in the %pre script - see https://en.opensuse.org/openSUSE:Packaging_guidelines#Users_and_Groups) - so it makes sence to reload dbus after the user got created. But you are right - maybe it is not about the user but about the dbus config:
|
Maybe we need to do it like some other packages do: https://build.opensuse.org/package/view_file/openSUSE:Factory/certmonger/certmonger.spec?expand=1 %post
if test $1 -eq 1 ; then
%{_bindir}/dbus-send --system --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig 2>&1 || :
fi This is essentially the same as
|
The OBS CI checks actually generate the packages so after fixing the OBS build failing you can install projects from those repos – maybe need to be set to published – and then try it out.
in the git commit message.
yes, so it looks better suited to do this in os-autoinst.
looks good. |
Good that we have CI checks for that. Unfortunately they failed before due to an unrelated problem. Make sure to be based on the current master because you might be missing #5418.
I think "Ensure D-Bus config is effective after installing package" would make sense. |
This is needed so that newly created users are taken into account
for dbus permission handling.