From Bugzilla Helper: User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.2-4GB i686) Description of problem: up2date should have grabbed and installed the glibc-2.2.4-18.7.0.3 patch. Instead I got a repeatable error about incorrect architechture. The system has: # rpm -qa | grep up2 up2date-2.7.11-7.x.1 # rpm -qa | grep rhn rhn_register-2.7.2-7.x.8 # uname -a Linux herculock.com 2.2.19-7.0.12 #1 Fri Oct 26 15:17:33 EDT 2001 i586 unknown # dmesg | grep -i cpu CPU: Intel Pentium MMX stepping 03 The system is a Dell Dimension M200a I was able to download apply the glibc updates from the command line. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: # up2date -u Retrieving list of all available packages... ######################################## ######################################## Removing installed packages from list of updates... ######################################## Removing packages marked to skip from list... ######################################## Getting headers for available packages... ######################################## Removing packages with files marked to skip from list... ######################################## Testing package set / solving RPM inter-dependencies... ######################################## RPM conflict error. The message was: Test install failed because of package conflicts: package glibc-2.2.4-18.7.0.3 is for a different architecture # rpm -qa | grep glibc glibc-common-2.2.4-18.7.0 glibc-2.2.4-18.7.0 Additional info:
I think the problem is the missing glibc rpm for the i586 architecture. I solved the problem by manually doing the update with the i386 glibc. # rpm -q glibc glibc-common --qf '%{arch} %{name} %{version}\n' i386 glibc 2.2.4 i386 glibc-common 2.2.4
I have also verified that this same bug exists on Red Hat 7.1 on an i586. Also, my problem solution is only a quick workaround, not a fix.
Part of this was a server side issue. Are you still seeing this behaviour?
I don't have any unpatched systems to test it on. If it a server side issue which has been corrected, then please mark it as fixed.
Havent seen any reports of this since the server side change, so closing it out. There is a client change as well that makes the client less picky about what the server sends, so that should be in the next version as well.
Should this be marked as resolved?