Bug 37478 - kernel dependency on initscripts is insufficiently strict
kernel dependency on initscripts is insufficiently strict
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-04-24 16:25 EDT by Greg Hudson
Modified: 2007-04-18 12:32 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-04-24 16:43:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Greg Hudson 2001-04-24 16:25:06 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.14-12 i686)


kernel-2.4.2-2 depends on initscripts >= 3.64.  kernel's postinstall script
runs /sbin/mkkerneldoth, which does not exist until somewhere between
initscripts-5.49-1 and initscripts-5.83-1.  So if you are upgrading both
kernel and initscripts, kernel might be updated first, and its postinstall
script will fail.

Please fix the dependency to be on initscripts >= 5.83 (or some earlier
version which has been verified to contain mkkerneldoth).


Reproducible: Always
Steps to Reproduce:
Upgrade kernel without upgrading initscripts, or upgrade kernel and
initscripts at the same time but list kernel first.
Comment 1 Arjan van de Ven 2001-04-24 16:30:26 EDT
The kernel has the proper dependencies; however they are ignored
Comment 2 Jeff Johnson 2001-04-24 16:42:59 EDT
Up until rpm-4.0.2-8, there was dependency "white-out", removed now. Back to
you for further processing ...
Comment 3 Arjan van de Ven 2001-04-24 16:47:03 EDT
Luckily, you normally ever do this.....
I'll close this as fixed in rawhide as it will be for newer RPMs...
If you disagree, please reopen this bug.

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