On Mon, 2004-10-04 at 10:08, Matthias Saou wrote:
> Hi,
>
> I'm running rawhide on my laptop, and experienced something somewhat
> strange. I though I didn't have the latest kernel installed, so I tried to
> install it before updating the rest of my system, but I in fact already had
> it, but here is what happened :
> - I ran "yum install kernel"
> - It suggested to install the latest version, but i586...
> - I checked with "yum list kernel", I had the i686 installed
> - I checked with rpm -qa --qf '%{arch}\n' kernel, all i686
> - I checked my yum.conf file, I even have exactarch=1 in it
>
> So I decided to try and hoped yum would fail on the test transaction, since
> both i586 and i686 versions of the same kernel can't be installed in
> parallel, but...
> - I let yum do what it wanted, now that I recall it may have been "u"
> - The test transaction was successful, so it went on
> - The output threw some unresolved symbols for some modules, notably the
> x86 microcode.ko, not good...
> - The resulting is that my i686 kernel was replaced by the i586
> - I checked and "rpm -Va kernel" is perfectly silent
>
> Any ideas about why yum misbehaved this way? Seems pretty naughty to me ;-)
Yes - if you had run yum update kernel - it wouldn't have done it - but
yum install kernel said: "oh the user wants to install the latest
kernel, well, the latest, available, kernel is thisver and the best arch
for thisver is i586 (b/c i686 is already installed), oh the user must
know better than us, let's install the i586 version"
It's a FIXME I have labeled that needs to be corrected soon. All I need
to do, really, is say - if you're installing and you already have
foo.i686 installed then any other non-biarch archs of that package are
marked as not-available.
That's really what it comes down to.
-sv
