Bug 55722

Summary:	kernel-source-2.2.19-6.2.12.i386.rpm upgrade/install fails at sound archive snd.o?
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <jjef>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
URL:	ftp.redhat.com ...... kernel-source-2.2.19-6.2.12.i386.rpm
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-09-30 15:39:15 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Need Real Name 2001-11-05 17:09:59 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (Win98; U)

Description of problem:
kernel-source-2.2.19-6.2.12.i386.rpm install or upgrade fails at snd.o? gnurpm complains that archieve is corrupt.   Second identical 
download.  Chances are the soundblaster archieve actually went into the rpm incorrectly.  On 2.2.19-6.2.12 this did not happen.

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

kernel-source-2.2.19-6.2.12.i386.rpm


How reproducible:
Always

Steps to Reproduce:
1. Download kernel-source-2.2.19-6.2.12.i386.rpm from ftp.redhat.com
2. rpm -ivh kernel-source-2.2.19-6.2.12.i386.rpm
	

Actual Results:  message similiar to 
"archive checksum corrupt snd.o (sbpro.o?)"
rpm install failed

Expected Results:  rpm install lands source in /usr/src/linux-2.2.19

Additional info:

kernel-source-2.2.19-6.2.10 was installed previously.

Comment 1 Bugzilla owner 2004-09-30 15:39:15 UTC

Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/