Should newer packages from a different arch really advertise themselves as updates to an older package of a different arch?

Latest response

I've recently discovered a problem where a new version of firefox.i686 can become available via YUM sooner than firefox.x86_64. (long story)

In hosts that pick up updates automatically, they cheerfully remove firefox.x86_64 and install the newer version of firefox.i686, bringing along a ton of other i686 dependent packages and making a real mess to clean up by hand later on.

I realize that I can exclude 'firefox.i686' pretty easily, but my question is more fundamental than resolving my problem - my question is - should a newer version of a package that is a different arch really be considered an update to that package of another arch?

I do not think it should, but I may be missing something so I wanted to check my understanding.

Thanks,
- KSF

Responses

With "exactarch=1" being set as default parameter in yum.conf file this should update only matching architecture packages. I am not sure if there is an override parameter being set/configured in case of using "satellite" to pull updates, otherwise, I may be missing something when we defaults to using regular method of pulling updates using subscription.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.