James Antill wrote: > > No, that's not how it works. Look at the Fedora/etc. repos. the > canonical way to set it up is: > > Blah/i386 > foo.i386 > libfoo.i386 > > Blah/x86_64 > foo.x86_64 > libfoo.x86_64 > libfoo.i386
Yes, I am aware of this commonly used structure. The reason why I didn't use it is because it is a huge waste of disk space and I only have limited space available. The structure that I'm using works perfectly fine, with the exception of this specific yum issue that I started this mail thread for. Apart from the disk space issue (which is a very serious concern in my case), I also cannot change the structure anymore as the repo is already used by a lot of people who manually installed the repo file so I have no feasible way to update that. > if you have "foo" package which is available as foo.i686 and > foo.x86_64, then _never_ release a newer version of foo for just > foo.i686 I realise that given the existence of this yum bug, from now on I will have to absolutely avoid having differing package versions. >> I would consider this behaviour a bug as I cannot think of any legimitate >> situation where anyone would want a x86_64 package replaced by a newer i686 >> package. > > And, yet, multiple people also tell me that if foo-1.arch1 is installed > and foo-2.arch2 is available ... then yum should _obviously_ upgrade, > because it's a newer version. I completely disagree. I can't think of any practical reason why anyone would want a x86_64 package replaced by a newer i686 package during a 'yum update'. Such an update will most likely break dependencies and therefore fail (or worse if it succeeds it will most likely break apps at runtime). > You also need to consider installs, in the above case do you want "yum > install foo" to install foo-1.x86_64 ... because I'm pretty sure > basically everyone will consider that a bug. Installs are a different matter, AFAIK the 'exactarch' is only used in case of updates, and it's with updates where the 'exactarch' option fails to behave as described in the man page. But of course IMHO when yum figures out dependencies for an install, it should only consider dependencies from the same arch. Back to the 'exactarch' option: Is there any chance the 'exactarch' can be fixed (in future yum releases) to work as specified in the yum.conf man page, i.e. when set to '1' to only update packages with newer versions of the exact same arch? If that's not doable then I think at the very least the man page should be updated to avoid confusing users with regards to what 'exactarch' does. _______________________________________________ Yum-devel mailing list [email protected] http://lists.baseurl.org/mailman/listinfo/yum-devel
