I ran up2date today via the command line (sudo up2date -u) to pick up the
new stunnel and slocate fixes, and not only did I receive all kinds of
unpublished fixes to the compilers and libraries (put 'em on your web page
when you release them!) but the glibc update, when attempted by me (sudo
up2date glibc) failed, saying:
"There was a fatal RPM error. The message was:
Test install failed:
package glibc-2.2-9 is for a different architecture"
My machine is an AMB K6-2 300 with a custom kernel built for K6es. I now
have the -devel-2.2-9 package installed, and can force the other one when
it becomes available on your FTP site or its mirrors, but don't wish to if
it will break my system (which is i386-compatible).
Thanks for taking a look! Have a good holiday season.
What does 'uname -m' say?
1:57pm kurgan/plankers [~] 2>uname -m
1:57pm kurgan/plankers [~] 3>uname -a
Linux kurgan 2.2.18 #1 Sun Dec 17 01:01:39 CST 2000 i586 unknown
Odd. Is the RPM in /var/spool/up2date glibc-2.2-9.i386.rpm,
Good call. In /var/spool/up2date/ there is only a 'glibc-2.2-9.i686.hdr'.
FYI, I have removed everything from /var/spool/up2date and retried, and I have
upgraded to up2date 2.1.7. No luck either time. It still thinks the machine is
an i686 and retrieves glibc-2.2-9.i686.hdr.
cristian, this must be a server side issue. Please look into it so we can fix
this user's problem (and all others using K6 computers).
Cristian, any movement on this bug?
Assigned QA to jturner
fixed in current server code.