Bug 558808 - Fedora 11 to 12 Upgrade Failure
Summary: Fedora 11 to 12 Upgrade Failure
Keywords:
Status: CLOSED DUPLICATE of bug 472958
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-26 13:48 UTC by Wayne Carruthers
Modified: 2010-03-16 18:09 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-16 18:09:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Wayne Carruthers 2010-01-26 13:48:09 UTC
Description of problem:

Upgrade of Fedora 11 to Fedora 12 failed with transaction error (file conflicts) on compiz libwall.so, wall.xml, compiz-wall.schemas, as well as kde.csh, kde-settings, kde.sh

System was onto CD 2 when error occurred, then hung on boot thereafter

Unable to run upgrade a second time as installer skips straight to new install & gives no option to upgrade existing system

Able to boot to single & running a yum clean & update now

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

Release 12 CD set


How reproducible:

Cant tell as no other system to destroy

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

As above

Expected results:

A clean upgrade

Additional info:

Will file a feature request as it seems odd (silly) that when an error like this occurs there are no other options in the error dialog box but to exit install/upgrade. Surely we need something the following options

1/ Submit Bug or save error message to a file
2/ Replace the conflicting files or skip & continue install/upgrade

Completely failing an upgrade which is 2/3rds done & not being able to recommence from where the error occurred or switch to another screen & remove the offending files as happened here is counter productive to say the least

Comment 1 Chris Lumens 2010-03-16 18:09:14 UTC

*** This bug has been marked as a duplicate of bug 472958 ***


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