Bug 473169 - F9 -> F10 upgrade failure
Summary: F9 -> F10 upgrade failure
Keywords:
Status: CLOSED DUPLICATE of bug 473239
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 10
Hardware: x86_64
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-26 21:44 UTC by lf010
Modified: 2014-01-21 23:07 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-12-02 16:13:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
exception report (193.40 KB, text/plain)
2008-11-26 21:44 UTC, lf010
no flags Details
Anaconda exception report during preupgrade Fedora 9 --> 10 upgrade (128.46 KB, text/plain)
2008-11-30 12:32 UTC, Muyi Taiwo
no flags Details

Description lf010 2008-11-26 21:44:46 UTC
Created attachment 324804 [details]
exception report

Description of problem:

F9 -> F10 upgrade failed after checking package dependency.

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


How reproducible:

always. I've tried three methods of upgrading.
(1) from DVD
(2) from DVD image on HD
(3) using preupgrade

In all cases, after reboot, upgrading proceeded until checking package dependency, then threw an exception. Attached is the exception report.

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


Expected results:


Additional info:
Attached is the exception report.

Comment 1 Muyi Taiwo 2008-11-30 12:32:19 UTC
Created attachment 325123 [details]
Anaconda exception report during preupgrade Fedora 9 --> 10 upgrade

Comment 2 James Antill 2008-12-02 16:04:37 UTC
Traceback (most recent call first):
  File "/usr/lib/python2.5/site-packages/yum/packages.py", line 981, in __init__
    self.summary = misc.share_data(self.hdr['summary'].replace('\n', ''))

...interesting that's the second report we've seen of that.

Comment 3 James Antill 2008-12-02 16:13:24 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.