Bug 1113601
| Summary: | autofs shouldn't have kernel as a dependency | |||
|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jan Pazdziora <jpazdziora> | |
| Component: | autofs | Assignee: | Ian Kent <ikent> | |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 20 | CC: | admiller, golang-updates, hushan.jia, ikent, lsm5, mattdm, mgoldman, s, vbatts | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | autofs-5.0.7-41.fc20 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1152862 (view as bug list) | Environment: | ||
| Last Closed: | 2014-10-28 06:40:27 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1152862 | |||
|
Description
Jan Pazdziora
2014-06-26 13:42:48 UTC
See https://lists.fedoraproject.org/pipermail/packaging/2014-March/010083.html I thiink the only reason autofs has this requirement is that it needs to run on a kernel newer than or equal to 2.6.17. So, I'm moving this bug to autofs. Of course, having that kernel package installed doesn't mean that one is running under that kernel. Docker obviously demonstrates this, but also, there's no reason one couldn't have a kernel 2.6.17 package installed but be running 2.6.16 since the system wasn't rebooted. However, all of that seems pretty much moot now, since we're long past the required kernel version in Fedora and even back to RHEL 5. My strong recommendation is to just remove the "Requires: kernel" line. (Another option would be to use "Conflicts: kernel < 2.6.17", but that still has the conceptual problem with package vs. running kernel. I say just drop it.) (In reply to Matthew Miller from comment #1) > See > https://lists.fedoraproject.org/pipermail/packaging/2014-March/010083.html > > > I thiink the only reason autofs has this requirement is that it needs to run > on a kernel newer than or equal to 2.6.17. So, I'm moving this bug to autofs. > > > Of course, having that kernel package installed doesn't mean that one is > running under that kernel. Docker obviously demonstrates this, but also, > there's no reason one couldn't have a kernel 2.6.17 package installed but be > running 2.6.16 since the system wasn't rebooted. > > However, all of that seems pretty much moot now, since we're long past the > required kernel version in Fedora and even back to RHEL 5. My strong > recommendation is to just remove the "Requires: kernel" line. > > > (Another option would be to use "Conflicts: kernel < 2.6.17", but that still > has the conceptual problem with package vs. running kernel. I say just drop > it.) Fair enough, I'll drop it. autofs-5.0.7-41.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/autofs-5.0.7-41.fc20 Sincere apologies for taking so long with this. It occurs to me that while this Requires is clearly obsolete now, for packages that need a Requires for a particular kernel, that Docker should handle it rather than trying to pull in the kernel dependency .... Just a thought. Ian Package autofs-5.0.7-41.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing autofs-5.0.7-41.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-13071/autofs-5.0.7-41.fc20 then log in and leave karma (feedback). autofs-5.0.7-41.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |