Red Hat Bugzilla – Bug 449783
PackageKit with rollback causing invalid updates
Last modified: 2008-06-06 03:58:37 EDT
Description of problem:
I'm running Fedora 9 with the Livna repository added, all packages up to date. I
have also enabled auto-repackage to yum and RPM for easy rollbacks. Whenever
PackageKit automatically updates my software, a popup claims there was a system
error. I was once able to generate a full stack trace that said something about
rollback in it, but I can't figure out how to do that again. Where can I find
more in-depth logs or error messages to post?
Additionally, (though not positive its connected) I have noticed several of my
installs getting invalidated after updates (usually missing library files).
Using yum I have either uninstalled and reinstalled the damaged package or
installed the missing dependency, and the program works fine afterwards.
However, it is a hassle to have programs randomly fail.
Please let me know where I can find more verbose and specific error messages.
Can you try "pkcon update-system" and try to get a backtrace please. Thanks.
Created attachment 308443 [details]
pkcon update-system output
Right, the constants that yum supplies us with are:
TS_UPDATE = 10
TS_INSTALL = 20
TS_TRUEINSTALL = 30
TS_ERASE = 40
TS_OBSOLETED = 50
TS_OBSOLETING = 60
TS_AVAILABLE = 70
TS_UPDATED = 90
It appears the rollback source uses constants not here. Have you got a link to
the rollback source code? Do you know what constants the rollback script uses?
We will need to add localised descriptions for them too.
If you edit: /usr/share/PackageKit/helpers/yum/yumBackend.py and change:
self.message(MESSAGE_WARNING,"The constant '%s' was unknown,
please report" % action)
Do you get a warning with the constant name?
Created attachment 308463 [details]
IRC log of solution
Solved via IRC
I've merged a more complete patch into git master, thanks. It'll be in the 0.2.3
release which should be in a couple of weeks. Cheers for your help.