Red Hat Bugzilla – Bug 509592
Preupgrade lacks a means to clear out its cache, and yum won't remove it either (after failure or interruption)
Last modified: 2014-01-21 18:10:16 EST
Description of problem:
Cause preupgrade to fail, either by not having enough space in /boot and having to install from a CD to get around it, or otherwise interrupting the install.
Thereafter there does not appear to be a means to clear the preupgrade cache equivalent to 'yum clean all', and 'yum clean all' won't do it either (presumably because there is no repo configuration for it).
Version-Release number of selected component (if applicable):
This happens when upgrading from FC10 to FC11 with preupgrade fails. The package ends up as version preupgrade-1.1.0-1.fc11.noarch.
I don't want to try it again to prove it, but I imagine that it is easily reproducable by rebooting mid upgrade and the like.
Steps to Reproduce:
1. See "Description of problem:".
See "Description of problem:".
"preupgrade --clean" or "preupgrade clean all" existing and cleaning out the cache.
I reckon nobody thought of this yet is all.
If you get left with a mangled RPM database, "package-cleanup --dupes" coupled with clever shell scripting is VERY VERY much your friend in that situation. I do wish you'd finally get everything tagged as "fc$releasever.$arch" though, as it would make that shell scripting work in full rather than requiring manual intervention for the packages that aren't tagged in such a way.
Apologies for mis-tagging this bug, but FF3.5b4 from FC11 has taken a considerable dislike to your AJAX package/component selector, and would not allow me to select 'preupgrade' as the package.
Actually there is a preupgrade --clean command already. The README says:
If you want to clean up manually, you can do:
Or, if you really want to be sure, do it by hand:
rm -rf /var/cache/yum/preupgrade* /boot/upgrade