Bug 22588 - up2date of glibc-2.2-9 fails on K6 with "wrong architecture" message
Summary: up2date of glibc-2.2-9 fails on K6 with "wrong architecture" message
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Preston Brown
QA Contact: Jay Turner
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-20 17:43 UTC by Bob Plankers
Modified: 2015-01-07 23:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-02-20 01:33:45 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Bob Plankers 2000-12-20 17:43:57 UTC 
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.

...Bob
Comment 1 Bill Nottingham 2000-12-20 19:49:22 UTC 
What does 'uname -m' say?
Comment 2 Bob Plankers 2000-12-20 19:55:59 UTC 
1:57pm kurgan/plankers [~] 2>uname -m
i586
1:57pm kurgan/plankers [~] 3>uname -a
Linux kurgan 2.2.18 #1 Sun Dec 17 01:01:39 CST 2000 i586 unknown
Comment 3 Bill Nottingham 2000-12-21 03:25:32 UTC 
Odd. Is the RPM in /var/spool/up2date glibc-2.2-9.i386.rpm,
or glibc-2.2-9.i686.rpm?
Comment 4 Bob Plankers 2000-12-21 07:04:36 UTC 
Good call. In /var/spool/up2date/ there is only a 'glibc-2.2-9.i686.hdr'.
Comment 5 Bob Plankers 2000-12-22 02:15:29 UTC 
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.
Comment 6 Preston Brown 2000-12-27 21:52:22 UTC 
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).
Comment 7 Preston Brown 2001-02-09 05:33:03 UTC 
Cristian, any movement on this bug?
Comment 8 Cristian Gafton 2001-02-20 01:33:41 UTC 
Assigned QA to jturner
Comment 9 Preston Brown 2001-02-26 23:45:24 UTC 
fixed in current server code.
Note You need to log in before you can comment on or make changes to this bug.