Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 146162 - RFE: remove the explicit kernel dependency
RFE: remove the explicit kernel dependency
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2005-01-25 13:55 EST by Enrico Scholz
Modified: 2014-03-16 22:52 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-03 16:33:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Enrico Scholz 2005-01-25 13:55:54 EST
Description of problem:

Please remove the 'Requires: kernel >= 2.6' statement because it
bloats up minimal chroot installations.

As it is possible to have both a working kernel-2.4 and a kernel-2.6
package for testing purposes, the new initscripts could be installed
without problems. But when going back to 2.4, the system will fail to
boot as e.g. lvm does not work anymore.

Therefore, the dependency should be a 'Conflicts: kernel < 2.6' which
will signal in the situation above that kernel-2.4 is not supported.

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

Comment 1 Bill Nottingham 2005-01-25 14:51:30 EST
Because various package updaters use install-not-upgrade for the
kernel,  this is problematic; it will break upgrades from a kernel 2.4

Now, if we want to do that....
Comment 2 Warren Togami 2005-01-26 02:37:18 EST
If it is impossible to remove this dep, we could instead use a bogus
virtual provides package for buildroots that satisfies this dep.
Provides: 999:kernel-999

Bad idea?
Comment 3 Bill Nottingham 2005-10-03 16:33:52 EDT
It's a conflicts ATM.

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