From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011012 Description of problem: up2date attempts to upgrade glibc for the incorrect system architecture. Attempting to apply updates to glibc on an i586 machine fails because up2date attempts to install the i686 glibc package. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.run up2date -p 2.On a i586 machine, it attempts to install glibc for an i686 3. Actual Results: The command output was: Test install failed because of package conflicts: package glibc-2.2.4-19.3 is for a different architecture Expected Results: up2date should have downloaded and installed the packages required. Since the current package it was trying to upgrade was built for an i386,perhaps it should have honored the already installed package? Manually downloading glibc-2.2.4-19.3.i386.rpm and putting it in /var/spool/up2date didn't help either. I had hoped up2date would see the package and use it Additional info: # cat /proc/cpuinfo processor : 0 vendor_id : CentaurHauls cpu family : 5 model : 4 model name : WinChip C6 # rpm -q kernel --qf "%{NAME} %{VERSION} %{ARCH}\n" kernel 2.4.9 i586 # rpm -q glibc --qf "%{NAME} %{VERSION} %{ARCH}\n" glibc 2.2.4 i386 [root@firestorm up2date]# ls glibc-2.2.4-19.3.i686.hdr glibc-common-2.2.4-19.3.i386.hdr glibc-devel-2.2.4-19.3.i386.hdr
Above: Steps to Reproduce: 1.run up2date -p Should of course be: Steps to Reproduce: 1.run up2date -u
I have the same problem on one machine running rh7.1, it tries ti install a i686 package Is there a difference between rh7.2 and rh7.1 because on rh7.2 the glibc i386 package is chosen.
This was partly a server side issue. Are you still seeing this behaviour?
I don't know, to be honest. I manually updated the packages, so I'm at a loss as to how to test it. If you have a suggestion, I'd be happy to try it.