[Yum] Strange kernel package behavior with 2.1.4

seth vidal skvidal at phy.duke.edu
Mon Oct 4 14:55:23 UTC 2004


On Mon, 2004-10-04 at 10:53, Matthias Saou wrote:
> seth vidal wrote :
> 
> > 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.
> 
> OK, I understand now. But why was the exactarch=1 from my yum.conf ignored
> in this case? I don't mind that much the "user seems to think he's more
> clever than I am, let him do it" way of thinking, but for the arch, unless
> it's explicitly given (i.e. kernel.i586), then yum probably shouldn't think
> about changing it, not on the packages I'd list as "exactarchpkgs" (and
> that would be kernels and glibc at the very least).

exactarch doesn't come into play on an install. Only on an update.

Think about it in the case of a biarch system

yum install foo.x86_64 - when you have foo.i686 already installed.

it'll be fixed so it doesn't do stupid things either way.
-sv





More information about the Yum mailing list