On Fri, 2012-03-30 at 19:15 +0200, Andy wrote: > Hi, > I'm running Scientific Linux 6.2 x86_64 (Redhat 6.2 clone) and I also manage a > repo for it, which has both i686 and x86_64 packages in it, that aren't always > exactly at the same version.
Yeh, don't do that. > The repo is here: > http://pkgrepo.linuxtech.net/el6/release/ > > As you can see the package ffmpeg-libs for example is at version 0.6.3-2 for > x86_64, while it's already at version 0.6.5-1 for i686. > > What happens now is that on the x86_64 box where I only have x86_64 packages > installed so far (including ffmpeg-libs-0.6.3-2) if I run 'yum update', yum > will try to use the newer i686 package (ffmpeg-libs-0.6.5-1) to update the > installed older x86_64 package. Traditionally we had that option, and implemented that behaviour because of repos. releasing glibc.i386 before the corresponding glibc.i586 and everything dying if the user moved to the "new version" ... so it was about staying on the "exact" arch within the same arch family. Nowadays the biggest set of complaints is about arch movements to different families ... Eg. foo.i686 disappearing and all users should move to foo.x86_64 or foo.noarch. > This happens despite I have 'exactarch=1' in /etc/yum.conf. This setting is the default. > Isn't 'exactarch=1' supposed to prevent this, or am I misunderstanding the > purpose of 'exactarch=1'? Probably not, but there might be bugs, and the documentation might not be clear. > If 'exactarch=1' isn't supposed to prevent this, how else can I avoid this, as > upgrading a x86_64 with a i686 package will obviously cause a mess and > therefore shouldn't happen? Fix the repo. ... really. If you can't do that for some reason, then I'd probably recommend using excludes. _______________________________________________ Yum-devel mailing list Yum-devel@lists.baseurl.org http://lists.baseurl.org/mailman/listinfo/yum-devel
