Bug 949300 - Error on upgrade process after Release Upgrade (F17 -> 18)
Summary: Error on upgrade process after Release Upgrade (F17 -> 18)
Keywords:
Status: CLOSED DUPLICATE of bug 912012
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 18
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-07 14:57 UTC by Keith Wilkinson
Modified: 2013-04-08 06:48 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-04-08 06:48:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Keith Wilkinson 2013-04-07 14:57:41 UTC
Description of problem:
Apper could not install critical updates for http and glibc

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


How reproducible:


Steps to Reproduce:
1. Use Apper to try to upgrade these components
2. Fails with error message
3.
  
Actual results: 
For http, got 
ERROR with transaction check vs depsolve: 
httpd-mmn = 20051115-x86-64 is needed by mod (and list of F17 modules like mod_fcgid-2.3.7-1.fc17.x86_64 and mod_log_post-0.1.0-4.fc17.x86_64) 
Apper "installed" screen showed F17 versions of modules were installed 
(after "version" and "architecture" columns were turned on by right click--this was discovered by accident as they seem to be turned off by default). 
The F17 modules needed to be manually removed/updated to F18 before http could be updated. 

For glibc, there were many dependencies. YUM CHECK and Apper "installed" screen showed that a wrong-architecture F17 version was installed in addition to the correct-architecture version. Think that I needed to manually remove it with YUM, YUMEX failed. 

Expected results:
Apper should be able to figure out such problems, or tell the user what to do (try YUMEX, also YUM CHECK, and how to display "version" and "architecture" columns on "installed" screen of Apper to help find the version or architecture conflicts that are causing the problem). 

Additional info: 
Described in "Actual results" above.

Comment 1 Jan Zeleny 2013-04-08 06:48:15 UTC

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


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