Red Hat Bugzilla – Bug 502401
yum picks older arch pkg instead of newer noarch one
Last modified: 2014-01-21 18:09:17 EST
we recently made the largish qt-doc pkg noarch (currently in updates-testing).
yum install qt-doc
chooses the older arch'd one.
Here's snippet from
yum -d10 install qt-doc
Setting up Install Process
Running compare_providers() for [<YumAvailablePackageSqlite : 1:qt-doc-4.5.0-14.fc11.x86_64 (0x2165290)>, <YumAvailablePackageSqlite : 1:qt-doc-4.5.1-11.fc11.noarch (0x2165350)>]
archdist compared 1:qt-doc-4.5.0-14.fc11.x86_64 to 1:qt-doc-4.5.1-11.fc11.noarch on ia32e
better arch in po 1:qt-doc-4.5.0-14.fc11.x86_64
archdist compared 1:qt-doc-4.5.1-11.fc11.noarch to 1:qt-doc-4.5.0-14.fc11.x86_64 on ia32e
Best Order: [(<YumAvailablePackageSqlite : 1:qt-doc-4.5.0-14.fc11.x86_64 (0x2165290)>, -1), (<YumAvailablePackageSqlite : 1:qt-doc-4.5.1-11.fc11.noarch (0x2165350)>, -6)]
okay, the problem here is that yum is not comparing these two pkgs against each other b/c they are not the same arch but it really needs to be b/c for this situation these are arch-comparable.
Just to be sure - there isn't a qt-doc.i386 installed/existent, too is there?
no qt-doc.i386 on x86_64 anyway (not multilib'd).
an obvious work around for the moment - make the new noarch pkg obsolete the old version of the same.
ok, I'll try that.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Let's take this off the Qt451 blocker as we worked around it in our Qt packaging (with the self-Obsoletes hack), but I'm adding it to F12Target as it's impacting the NoarchSubpackages feature.
yum-3.2.24-1.fc11 has been submitted as an update for Fedora 11.
yum-3.2.24-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
yum-3.2.24-2.fc10 has been submitted as an update for Fedora 10.
yum-3.2.24-2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.