Bug 731052 - Preupgrade doses not clean up /var/cache/yum preupgrade metadata
Summary: Preupgrade doses not clean up /var/cache/yum preupgrade metadata
Alias: None
Product: Fedora
Classification: Fedora
Component: preupgrade
Version: 19
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-08-16 15:22 UTC by Shawn Starr
Modified: 2013-04-09 08:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-04-09 08:31:06 UTC

Attachments (Terms of Use)

Description Shawn Starr 2011-08-16 15:22:53 UTC
Description of problem:
If you attempt to do an preupgrade, but are unable to upgrade to a specific version, trying a different version fails as it retries the existing yum metadata found.

Version-Release number of selected component (if applicable):
Any version of preupgrade.

How reproducible:

Steps to Reproduce:
1. From Fedora 12, try to upgrade to Fedora 15, which isn't supported it downloads successfully, aborts in anaconda correctly.
2. From Fedora 12, try to upgrade to Fedora 14, fails, preupgrade continues to try Fedora 15 metadata found in /var/cache/yum/preupgrade-fedora directory.
Actual results:
Fails to download correct Fedora metadata

Expected results:
Deletes metadata then fetches correct metadata for right version of Fedora.

Additional info: It seems to be in all preupgrade versions released.

Comment 1 Fedora End Of Life 2013-04-03 17:20:52 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:

Comment 2 Shawn Starr 2013-04-09 08:31:06 UTC
Close it, preupgrade is obsoleted fedup is new kid in town

Note You need to log in before you can comment on or make changes to this bug.