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
Offline updates broken with PackageKit 1.2.0 due to service enablement being lost in Meson conversion #401
Comments
Keep https://bugzilla.redhat.com/show_bug.cgi?id=988235 in mind; the solution implemented was option b as suggested by Lennart |
I don't have time this week to look at the issue, but I'm happy to review patches. Sorry that's not more helpful. |
I'm going to just fix it in our downstream spec for now, by creating the symlink at the end of |
Much appreciated dude. |
You should use meson.add_install_script() with something like this: https://github.com/systemd/systemd/blob/master/tools/meson-make-symlink.sh |
Could you do a PR please? I always get the systemd stuff wrong. Thanks! |
This is an upstream report for downstream bug https://bugzilla.redhat.com/show_bug.cgi?id=1833176 . To summarize, the autotools -> Meson conversion inadvertently left out enablement of the
packagekit-offline-update.service
service insystemd-update.target
, so now when we do the offline update boot, PackageKit just doesn't do anything at all. This block from the oldMakefile.am
simply has no equivalent in the newmeson.build
.It's not clear what the best way to fix this would be, though. Creating symlinks in meson doesn't seem to be a really supported thing, and arguably we shouldn't really be doing it here; another option would be to revert this commit from 2014 and make the service a more "normal" one again, as systemd now cleans up the
/system-update
trigger file which was the justification for that change.The text was updated successfully, but these errors were encountered: