Couldn't help it but mention purge-kernels.service doesn't work on
it's own too because it has plain `zypper` in Exec stanza instead of
`zypper --non-interactive` per zypper's own error message in the
journal (see https://paste.opensuse.org/95163190).
On Fri, Jan 24, 2020 at 6:08 PM Dominique Leuenberger / DimStar
On Fri, 2020-01-24 at 16:00 +0100, Andreas Prittwitz wrote:
but is not mentioned in the zypper.spec here
https://build.opensuse.org/package/view_file/openSUSE:Factory/zypper/ zypper.spec?expand=1
Shouldn't the spec file contain a
Requires: /usr/lib/systemd/system/purge-kernels.service
or something similar like the package name?
No - zypper should not require that service. In fact, the plan is for the base pattern to recommend the service to be present (it's imho not a hard require on a system)
BUT: we faced a problem with the sequence things happen: during boot up, that service fires up at the same time the KDE session might start and the updater applet check for updates. And since PK and zypper never liked each other being run at the same time, PK will simply 'yell' with a big warning. The KDE Team is currently busy adjusting the notificiatin appled for KDE to be less intrusive in the case of the (expectable) database lock [0]
Once this fix is ready, the purge-kernels-service will be added as recommends to the base patterns.
Cheers, Dominique
-- Regards, Andrei Dziahel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org