Bug 116142

Summary:	up2date hangs/stalls on trying to install latest kernel and kernel-source eratta
Product:	[Retired] Red Hat Linux	Reporter:	Mike Burger <mburger>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED WONTFIX	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9	CC:	riel
Target Milestone:	---
Target Release:	---
Hardware:	athlon
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-09-30 15:41:49 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 Mike Burger 2004-02-18 16:05:51 UTC

Description of problem:

Upon receiving notification of a new eratta kernel package, I made use
of the (graphical) up2date program to download and install
kernel-2.4.20-30.9 kernel and kernel-source packages.  After
successfully downloading the packages, and clicking "forward", the
installation progress window just sat there, indicating no progress.

After I cancelled the process, I issued the appropriate "rpm -ivh"
command, and received a Failed dependencies message, saying that
/bin/sh was required by both kernel-2.4.20-30.9 and
kernel-source-2.4.20-30.9.

Of course, /bin/sh does exist on the system, as a symlink to /bin/bash.

Issuing the rpm command with the --nodeps option got around the problem.

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

2.4.20-30.9

How reproducible:

Very.

Steps to Reproduce:
1. Download kernel-2.4.20-30.9.athlon.rpm
2. Issue "rpm -ivh kernel-2.4.20-30.9.athlon.rpm"
3. 
  
Actual results:

Failed dependencies error.

Expected results:

Successful installation of the kernel and kernel-source packages.

Additional info:

Comment 1 Bugzilla owner 2004-09-30 15:41:49 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/