309295 – inconsistency in dependencies of currently stable versions of udev, cryptsetup

Bug 309295 - inconsistency in dependencies of currently stable versions of udev, cryptsetup

Summary: inconsistency in dependencies of currently stable versions of udev, cryptsetup

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	AMD64 Linux

Importance:	High normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2010-03-13 19:22 UTC by Max Loparev
Modified:	2010-03-20 22:16 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Max Loparev 2010-03-13 19:22:07 UTC

udev-149 contains block for device-mapper in RDEPEND
cryptsetup-1.0.6-r2 however requires device-mapper

cryptsetup required by hal with enabled by default use flag crypt

Comment 1 Doktor Notor 2010-03-13 19:36:10 UTC

device-mapper has been moved to sys-fs/lvm2, don't install it. And no, cryptsetup does not require it.

DEPEND="|| (
                >=sys-fs/lvm2-2.02.45
                >=sys-fs/device-mapper-1.00.07-r1

Comment 2 Max Loparev 2010-03-13 19:48:40 UTC

thank you, that solves the problem.

shouldn't all requirements be switched to virtuals and deice-mapper added to package.mask if its functionality moved to lvm2?

Comment 3 Doktor Notor 2010-03-13 20:03:16 UTC

Good that it works now. You need a blocker in place, otherwise you'd get file conflicts when installing >=sys-fs/lvm2-2.02.45 on systems with the deprecated sys-fs/device-mapper still installed. :) Plus virtual for one remaining alive package is not needed at all :)

Comment 4 Max Loparev 2010-03-13 21:58:58 UTC

parted is another one. I didn't check the whole tree...

Comment 5 Doktor Notor 2010-03-13 22:38:49 UTC

(In reply to comment #4)
> parted is another one. I didn't check the whole tree...

No, you misunderstood me. By virtual I mean a virtual that'd only contain sys-fs/lvm2, that doesn't make any sense. || ( >=sys-fs/lvm2-2.02.45 >=sys-fs/device-mapper-1.00.07-r1 ) does the same job until device-mapper gets removed.