Bug 198144 - sys-fs/device-mapper should not DEPEND on sys-fs/udev
|
Bug#:
198144
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: base-system@gentoo.org
|
Reported By: petre.rodan@simplex.ro
|
|
Component: Core system
|
|
|
URL:
|
|
Summary: sys-fs/device-mapper should not DEPEND on sys-fs/udev
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-11-05 09:07 0000
|
please remove the unconditional *DEPEND on sys-fs/udev for this package. I'm
happily using device-mapper with static dev on different configurations both on
servers and workstations with no problems.
udev is not a mandatory tool and should not become one.
please test with device-mapper and lvm2 + static dev on baselayout2 and report
back if everything still works for you, because the dm/lvm init scripts now
work differently than they did in baselayout1.
If it does work, then I'll change the RDEPEND statement to be:
"!<sys-fs/udev-115-r1" so that you can use it without udev, while other folks
will upgrade to the new udev before using it.
It also leads to annoying block cycles when trying to emerge from older
versions of device-mapper:
emerge -pv -u device-mapper
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] sys-apps/sysvinit-2.86-r8 [2.86-r3] USE="(-ibm) (-selinux)
-static (-bootstrap%) (-build%)" 0 kB
[ebuild N ] virtual/init-0 0 kB
[ebuild U ] sys-apps/debianutils-2.23.1 [2.14.1-r1] USE="-static (-build%)"
133 kB
[ebuild N ] sys-apps/mktemp-1.5 69 kB
[ebuild U ] sys-apps/baselayout-1.12.9-r2 [1.11.14-r2] USE="unicode
-bootstrap -build -static" 214 kB
[ebuild U ] sys-apps/module-init-tools-3.2.2-r3 [3.0-r2] USE="-old-linux%
(-debug%)" 166 kB
[ebuild U ] sys-fs/device-mapper-1.02.22-r5 [1.01.03] USE="(-selinux)" 186
kB
[ebuild U ] sys-fs/udev-115-r1 [079-r1] USE="(-selinux)" 210 kB
[blocks B ] <sys-fs/device-mapper-1.02.19-r1 (is blocking
sys-fs/udev-115-r1)
The newer portages do not show that block cycle either.
Please test as I requested in comment #1, and report back.
hi Robin,
(In reply to comment #1)
> please test with device-mapper and lvm2 + static dev on baselayout2 and report
> back if everything still works for you, because the dm/lvm init scripts now
> work differently than they did in baselayout1.
by using
sys-fs/lvm2-2.02.28-r2
sys-apps/baselayout-2.0.0_rc6
sys-fs/device-mapper-1.02.22-r5
and a static dev, the system boots up mounting all logical volumes OK right out
of the box.
do you also want me to test mounting cryptfs partitions?
> If it does work, then I'll change the RDEPEND statement to be:
> "!<sys-fs/udev-115-r1" so that you can use it without udev, while other folks
> will upgrade to the new udev before using it.
thanks,
peter
no, plain lvm volumes are fine.
Thanks for testing.
I've inverted the DEPEND now.