Bug 294961 - Cleanup after failed upgrade
Summary: Cleanup after failed upgrade
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda   
(Show other bugs)
Version: 7
Hardware: All Linux
low
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-09-18 15:46 UTC by Gary Thomas
Modified: 2008-04-22 15:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-04-22 15:53:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Package list after failed upgrade (36.96 KB, text/plain)
2007-09-18 15:46 UTC, Gary Thomas
no flags Details

Description Gary Thomas 2007-09-18 15:46:20 UTC
Description of problem:

I tried to upgrade from FC5 -> FC7.  The process continued through
some 600 of 995 packages, then crashed (solid).  Now I have tons of
multiply installed packages, many causing conflicts when I try to
update using 'yum'

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Looking for help and guidance on how to clean up the install.
List of installed RPM packages is attached.

Comment 1 Gary Thomas 2007-09-18 15:46:20 UTC
Created attachment 198501 [details]
Package list after failed upgrade

Comment 2 Chris Lumens 2008-04-22 15:53:06 UTC
Certainly the best thing to do here is to just reinstall the latest stuff and
keep going.  Barring that, the best way in my opinion is to remove the new
versions of the duplicate packages and try again with the upgrade.  Anyway,
probably the fastest way to get a response on things like this in the future is
to try one of the user mailing lists.


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