Bug 625317
Summary: | device-mapper-devel package incorrectly requires device-mapper, when it should probably only need device-mapper-libs, not both | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jasper O'neal Hartline <Jasper.Hartline> |
Component: | device-mapper-obsolete | Assignee: | Orphan Owner <extras-orphan> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | agk, bmarzins, dwysocha, extras-orphan, heinzm, jonathan, mbroz, prockai |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-08-19 10:51:26 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
Jasper O'neal Hartline
2010-08-19 04:23:17 UTC
The dependencies are kept minimal. You need the udev files in place to make any use of device-mapper in Fedora now, we will not support any users without dmsetup being installed anyway and the documentation files have to be there too. I have device-mapper installed, just not a version yum-builddep on anaconda.src.rpm file wanted. I don't see how needing device-mapper-devel to build anaconda against requires device-mapper at all. Fedora doesn't distinguish between packages installed only to be built against and packages installed actually to be used. You'd need a way to distinguish between 'install this package to compile against but I promise I will never actually run any of the contents because I know there are dependencies missing and things will break if I try that' and 'install this package actually to be used including all its runtime requirements'. If you know what you are doing, manage the dependencies yourself with --nodeps. |