Hi, I have a strange behavior of yum on my AMD Opteron System with yum 2.1.12 and FC3 (x86_64). For example I try to install flac which is an i386 and x86_64 RPM: ------------------------------------------- [root@xxxx ~]# yum list flac Available Packages flac.x86_64 1.1.0-7 base flac.i386 1.1.0-7 base [root@xxxx ~]# [root@xxxx ~]# yum install flac Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package flac.x86_64 0:1.1.0-7 set to be installed ---> Package flac.i386 0:1.1.0-7 set to be installed --> Running transaction check --> Processing Dependency: libc.so.6 for package: flac --> Processing Dependency: libc.so.6(GLIBC_2.1.3) for package: flac --> Processing Dependency: libm.so.6 for package: flac --> Processing Dependency: libogg.so.0 for package: flac --> Processing Dependency: libm.so.6(GLIBC_2.0) for package: flac --> Processing Dependency: libc.so.6(GLIBC_2.0) for package: flac --> Processing Dependency: libgcc_s.so.1(GCC_3.0) for package: flac --> Processing Dependency: libc.so.6(GLIBC_2.1) for package: flac --> Processing Dependency: libc.so.6(GLIBC_2.3) for package: flac --> Processing Dependency: libgcc_s.so.1 for package: flac --> Restarting Dependency Resolution with new changes. --> Populating transaction set with selected packages. Please wait. ---> Package glibc.i686 0:2.3.3-74 set to be installed ---> Package libogg.i386 2:1.1.2-1 set to be installed ---> Package libgcc.i386 0:3.4.2-6.fc3 set to be installed --> Running transaction check Dependencies Resolved Transaction Listing: Install: flac.i386 0:1.1.0-7 Install: flac.x86_64 0:1.1.0-7 Performing the following to resolve dependencies: Install: glibc.i686 0:2.3.3-74 Install: libgcc.i386 0:3.4.2-6.fc3 Install: libogg.i386 2:1.1.2-1 Is this ok [y/N]: n Exiting on user Command Complete! ------------------------------------------- As you can see yum tries to install both architectures instead of the "best", now I try to install expat which is also an i386 and x86_64 RPM but this time the x86_64 version is already installed: ------------------------------------------- [root@xxxx ~]# yum list expect Installed Packages expat.x86_64 1.95.7-4 installed Available Packages expat.i386 1.95.7-4 base [root@xxxx ~]# yum install expat Setting up Install Process Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package expat.i386 0:1.95.7-4 set to be installed --> Running transaction check --> Processing Dependency: libc.so.6(GLIBC_2.0) for package: expat --> Processing Dependency: libc.so.6 for package: expat --> Processing Dependency: libc.so.6(GLIBC_2.1.3) for package: expat --> Processing Dependency: libc.so.6(GLIBC_2.1) for package: expat --> Restarting Dependency Resolution with new changes. --> Populating transaction set with selected packages. Please wait. ---> Package glibc.i686 0:2.3.3-74 set to be installed --> Running transaction check Dependencies Resolved Transaction Listing: Install: expat.i386 0:1.95.7-4 Performing the following to resolve dependencies: Install: glibc.i686 0:2.3.3-74 Is this ok [y/N]: n Exiting on user Command Complete! ------------------------------------------- So instead of giving the message "nothing to do" because "expat.x86_64" is already installed it tries to install the i386 version as well. The same happens when you update RPMS, yum installs then both versions (if available). I don't know but I can't believe that this is the correct behavior, or am I wrong? Is this a "feature" of yum or a bug? And if it is a feature :) how can I turn it off :). Regards, J?rgen
