Yum strange behavior after upgrade to Release 14

Alan J. Gagne alanjgagne at gmail.com
Wed Dec 1 20:36:55 UTC 2010


> On Wed, Dec 1, 2010 at 1:07 PM, John Vo <jvo at eagle.net> wrote:
>> Greetings:
>>
>> I am new to the list so I will apologize for any problem with my post.
>>
>> I upgraded my Fedora 13 to 14 using the "yum" method.
>
> Although that method is pseudo-supported, I would try preupgrade in
> the future as recommended by
> http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum
>
>> After the upgrade, when I ran yum upgrade, I ran into a few problem:
>
> Did you run yum upgrade or yum update?
>
>> Error: Package: PackageKit-0.6.6-2.fc13.x86_64 (@updates/13)
>>            Requires: PackageKit-yum-plugin = 0.6.6-2.fc13
>>            Removing: PackageKit-yum-plugin-0.6.6-2.fc13.x86_64
>> (@updates/13)
>>                PackageKit-yum-plugin = 0.6.6-2.fc13
>>            Updated By: PackageKit-yum-plugin-0.6.9-4.fc14.x86_64 (fedora)
>>                PackageKit-yum-plugin = 0.6.9-4.fc14
>>  You could try using --skip-broken to work around the problem
>>
>>
>> And...many many of these..
>>
>> ** Found 313 pre-existing rpmdb problem(s), 'yum check' output follows:
>> ImageMagick-6.6.4.1-14.fc14.1.x86_64 is a duplicate with
>> ImageMagick-6.5.8.10-6.fc13.x86_64
>> PackageKit-0.6.9-4.fc14.x86_64 is a duplicate with
>> PackageKit-0.6.6-2.fc13.x86_64
>> PackageKit-device-rebind-0.6.9-4.fc14.x86_64 is a duplicate with
>> PackageKit-device-rebind-0.6.6-2.fc13.x86_64
>> PackageKit-glib-0.6.9-4.fc14.x86_64 is a duplicate with
>> PackageKit-glib-0.6.6-2.fc13.x86_64
>> PackageKit-gtk-module-0.6.9-4.fc14.x86_64 is a duplicate with
>> PackageKit-gtk-module-0.6.6-2.fc13.x86_64
>>
>>
>> I'm a casual Fedora users. Help please.
>
> Don't take this the wrong way as it can be difficult to discern "tone"
> in an email but, the site I referenced specifically states:
> "Although upgrades with yum works, it is not explicitly tested as part
> of the release process by the Fedora Project. If you are not prepared
> to resolve issues on your own if things break, you should probably use
> the recommended installation methods instead."
>
> There may be a more automated method but I ran into some issues
> orphaned packages after upgrading with preupgrade and did the
> following for each problem package:
>
> Uninstall the old package:
> rpm -e --nodeps <package>
>
> Install the new package:
> yum install <package>
>
>
> Richard

	I used preupgrade, but yum distro-sync did a great job of cleaning up 
the packages identified by running package-cleanup --orphans.

Alan


More information about the users mailing list