> it's a 64bit system and I don't want the 32bit RPM because the 64bit RPM > is already installed (in the same version) and so the 32bit RPM is not > the best fit for a 64bit system, if I want the 32bit RPMs I install them > with "xxx.i386". Of course I could always add a .x86_64 and this way yum > installs only x86_64 binaries but it would be nice to have an option in > the config file which uses the .x86_64 as default for the *install* if > nothing else is given, like the exactarch=1 for the update (which > somehow failed btw. for the boost lib with yum 2.1.12, see below). and how does the work for removals? should yum remove foo only remove foo.x86_64? or should it match foo.i386, too? > Btw. how handles yum dependencies when I install a xxxx.x86_64 RPM which > has as dependency the yyyy.x86_64 RPM which exist as yyyy.i386 as well, > what would yum do? Would it install the yyyy.x86_64 *and* the yyyy.i386 > version? Or would it install only the yyyy.x86_64 because I gave > xxxx.x86_64 as input and this way only the yyyy.x86_64 is the dependency > (I hope so :))? yes it sorts these out. > I admit only a few RPMs are available as .x86_64 and .i386 in the same > repository and so I can solve the problems manually when I see that yum > tries to install two versions of the the same RPM but a config option > would be handy :). it has that option - just specify the arch you want. > That's the other problem which I had with the update which I really > believe is wrong, because yum tried to update the boost.x86_64 with the > boost.i386 :) (exactarch=1 is set), or better yum tried to update the > boost.x86_64 and the boost.i386 but the boost.i386 is not installed. > > -------------------------- > [root@xxxx ~]# yum list boost > Installed Packages > boost.x86_64 1.31.0-9 installed > Available Packages > boost.x86_64 1.32.0-1.fc3 > updates-released > boost.i386 1.32.0-1.fc3 > updates-released > > [root@xxxx ~]# yum update > Resolving Dependencies > --> Populating transaction set with selected packages. Please wait. > ---> Package boost.i386 0:1.32.0-1.fc3 set to be updated > ---> Package boost.x86_64 0:1.32.0-1.fc3 set to be updated > --> Running transaction check > > Dependencies Resolved > Transaction Listing: > Update: boost.i386 0:1.32.0-1.fc3 > Update: boost.x86_64 0:1.32.0-1.fc3 > > Other Transactions: > Obsoleting: boost.x86_64 0:1.31.0-9 with boost.i386 0:1.32.0-1.fc3 read this list for today. boost.i386 claims to obsolete boost <= 1.31 now that being the case then boost.i386 does, in fact, obsolete boost.x86_64 if boost.x86_64 is <= 1.31. Try it with rpm on the command line. download the boost rpms that caused this problem and run: rpm -Uvh that.rpm and see if it doesn't remove the boost.x86_64, too. -sv
