Bug 473766 - Anaconda throws exception during Fedora 9 --> 10 upgrade using preupgrade or preupgrade-cli
Summary: Anaconda throws exception during Fedora 9 --> 10 upgrade using preupgrade or ...
Keywords:
Status: CLOSED DUPLICATE of bug 473239
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 10
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-30 12:41 UTC by Muyi Taiwo
Modified: 2014-01-21 23:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-02 16:16:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Anaconda exception report: F9 --> F10 upgrade using preupgrade (128.46 KB, text/plain)
2008-11-30 12:43 UTC, Muyi Taiwo
no flags Details

Description Muyi Taiwo 2008-11-30 12:41:35 UTC
Description of problem:
When upgrading from Fedora 9 --> 10 using preupgrade and pre-upgrade-cli, upgrade proceeds fine until after reboot.  After reboot, about 27% - 30% into checking package dependencies, anaconda throws exception (exception report attached)

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


How reproducible:
Every time upgrade is attempted

Steps to Reproduce:
1. Run preupgrade
2. 
3.
  
Actual results:
-- Packages selected and downloaded
-- Prompted to reboot
-- Reboot
-- Anaconda checks package dependencies
-- Exception is thrown (see attached exception report)

Expected results:
-- Packages selected and downloaded
-- Prompted to reboot
-- Reboot
-- Anaconda checks package dependencies
-- Upgraded packages (Fedora 10) installed

Additional info:
-- See attached exception report

Comment 1 Muyi Taiwo 2008-11-30 12:43:17 UTC
Created attachment 325124 [details]
Anaconda exception report: F9 --> F10 upgrade using preupgrade

Comment 2 James Antill 2008-12-02 16:16:54 UTC

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


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