Bug 76909 – rpm gives obscure error messages on athlon computers

Bug 76909 - rpm gives obscure error messages on athlon computers

Summary:	rpm gives obscure error messages on athlon computers

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	rpm (Show other bugs)
Sub Component:
Version:	8.0
Hardware:	athlon Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Jeff Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-10-29 04:24 EST by Vidar Langseid
Modified:	2008-05-01 11:38 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-11-01 09:20:33 EST
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.)

Groups: None (edit)

Description Vidar Langseid 2002-10-29 04:24:48 EST

Description of Problem:
Looks like rpm gives obscure errormessages when trying
to install a corrupted rpm on athlon systems

Try the following on pentium 4 computers:
[root@localhost root]# echo "" > foobar.rpm
[root@localhost root]# rpm -i foobar.rpm
error: foobar.rpm cannot be installed


However, when do the same on a athlon system you get this 
cryptic message:
[root@localhost root]# echo "" > foobar.rpm
[root@localhost root]# rpm -i foobar.rpm
foobar.rpm: read manifest failed: Success

I experienced this when I downloaded your updates from one (faulty) mirrorsite


Version-Release number of selected component (if applicable):


How Reproducible:
always

Comment 1 Jeff Johnson 2002-11-01 09:20:26 EST

FWIW, the code path traveled does not
need or use arch, so the "athlon" information
is a red herring.

What version of rpm? Same on both platforms?

Comment 2 Jeff Johnson 2002-11-16 15:07:11 EST

Closed for lack of input.

Note You need to log in before you can comment on or make changes to this bug.