Bug 651419

Summary: F12->F14 upgrade misses some packages, breaks dependencies
Product: [Fedora] Fedora Reporter: Jan "Yenya" Kasprzak <kas>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 15:15:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Output of "rpm -qa|fgrep .fc12.|sort" after the upgrade of F12 to F14 none

Description Jan "Yenya" Kasprzak 2010-11-09 14:59:43 UTC 
Created attachment 459134 [details]
Output of "rpm -qa|fgrep .fc12.|sort" after the upgrade of F12 to F14

Description of problem:
After upgrading my F12 system to F14 I have discovered that many packages were not upgraded and the system still has .fc12 versions of those packages. Moreover, some of the packages have broken dependencies, because their libraries got upgraded, while the packages with binaries did not.

As an example, the problem is with vim package, as described in bug #650535.
It has broken dependency on libperl. The problem is probably that the vim
version in F12 is higher than in F14. I think anaconda should handle even downgrades gracefully. It definitely should not leave the system with broken dependencies, when possible.

How reproducible:
100 %

Steps to Reproduce:
1. Create a new virtual machine, install F12 on it, possibly using kickstart with "%packages --default" option
2. After the installation, run "yum -y update", just to be sure.
3. Reboot the F12 system and upgrade it to F14 using Fedora 14 DVD.
4. After the upgrade, run "yum -y update".
5. Run rpm -qa|fgrep .fc12.

Actual results:
There are over 100 packages with release containing the ".fc12." string.

Expected results:
All F12 packages should be replaced by F14 ones, provided that a F14 version of the same package exists. No library dependencies should be broken.

Additional info:
I will attach the list of packages which remained on a virtual machine created according to the above steps with release tag containing '.fc12.'.
Comment 1 Chris Lumens 2010-11-09 15:15:20 UTC 
If the F12 package has a higher version number than the F14 package, then the F12 package is going to win.  That's just how dependency resolution works throughout Fedora.  Changing this is no small task and would make anaconda inconsistent with the rest of the system.  I suggest you file bugs with the package that are causing problems.
Comment 2 Jan "Yenya" Kasprzak 2010-11-09 15:28:37 UTC 
It can win, but anaconda should not break its dependencies (yum does not break them, for example).
Comment 3 Jan "Yenya" Kasprzak 2010-11-09 15:32:16 UTC 
Anyway, do you suggest there is a version numbering bug in 100+ packages in F14?
If so, discovering this kind of bugs should become an integral part of pre-release tests: install two or three previous versions, upgrade to the release candidate, and fix either anaconda, or all packages which remain installed from the previous release.

In my opinion fixing anaconda would definitely be a better solution in the long term.
Comment 4 Brian Lane 2010-11-10 05:25:42 UTC 
The presence of packages with .fc12. in their name is perfectly normal. Take a look at the f14 mirror and you will see a number of these packages in the repo.