Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 442832 - anaconda should nuke preupgrade cache after preupgrade-upgrade finishes
Summary: anaconda should nuke preupgrade cache after preupgrade-upgrade finishes
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F9Target
TreeView+ depends on / blocked
 
Reported: 2008-04-17 04:30 UTC by seth vidal
Modified: 2013-07-29 01:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-16 20:32:08 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description seth vidal 2008-04-17 04:30:09 UTC 
Description of problem:
user preupgrades their box
they boot up into the new release
a bunch of disk space is sucked up in /var/cache/yum/anaconda-upgrade
that space will not be cleaned up by commands like 'yum clean packages' b/c that
repo is not enabled anywhere.

it would great if anaconda could nuke that cache if the install completes
successfully.
Comment 1 Jeremy Katz 2008-04-17 06:42:06 UTC 
Handled in git
Comment 2 Bug Zapper 2008-05-14 09:34:00 UTC 
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 3 stanl 2008-05-18 13:09:35 UTC 
I think this should be a choice presented to the user.  If I want to upgrade
many other installs, I can then use the existing packages instead of having to
download them.  In that case, I am responsible for cleanup but I have chosen to be.
Note You need to log in before you can comment on or make changes to this bug.