Bug 54854 - Can't install kernel because of missing packages
Can't install kernel because of missing packages
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.1
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-10-21 06:18 EDT by Henrik Karlsson
Modified: 2007-04-18 12:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-12-03 17:30:41 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)
Output from rpm (656 bytes, text/plain)
2001-10-21 06:22 EDT, Henrik Karlsson
no flags Details

  None (edit)
Description Henrik Karlsson 2001-10-21 06:18:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010816

Description of problem:
When trying to install the new kernel packages (2.4.9-6) for i686 and
i686-smp rpm complains about missig packages (modutils & mkinitrd) and a
conflict with one package (e2fsprogs).

Trying to solve these problems by installing the missing packages from the
update directory on ftp.redhat.com leads to one more missing package
(filesystem).



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


How reproducible:
Always

Steps to Reproduce:
1. rpm -ivh kernel-smp-2.4.9-6.i686.rpm kernel-2.4.9-6.i686.rpm
2. rpm -Uvh modutils-2.4.6-4.i386.rpm mkinitrd-3.2.6-1.i386.rpm
e2fsprogs-1.23-1.7.1.i386.rpm e2fsprogs-devel-1.23-1.7.1.i386.rpm

	

Additional info:
Comment 1 Arjan van de Ven 2001-10-21 06:22:12 EDT
"filesystem" is a noarch package (eg contains no binaries and is shared between
i386/alpha/ia64) and is in the noarch/ directory....
Comment 2 Henrik Karlsson 2001-10-21 06:22:52 EDT
Created attachment 34501 [details]
Output from rpm

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