Summary: | dependecy bug between udev, device-mapper and cryptoloop | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alex Efros <powerman-asdf> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | a_tevelev, cilly |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alex Efros
2009-11-09 16:53:22 UTC
device-mapper was merged upstream into lvm2. Emerge a recent lvm2, it will automatically unmerge old device-mapper. Really? I've got the same problem. # emerge -p lvm2 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] sys-apps/util-linux-2.16.1 [2.14.2] USE="-perl%" [uninstall ] sys-fs/e2fsprogs-1.41.3-r1 [blocks b ] <sys-fs/e2fsprogs-1.41.8 ("<sys-fs/e2fsprogs-1.41.8" is blocking sys-apps/util-linux-2.16.1) [uninstall ] sys-libs/e2fsprogs-libs-1.41.3-r1 [blocks b ] <sys-libs/e2fsprogs-libs-1.41.8 ("<sys-libs/e2fsprogs-libs-1.41.8" is blocking sys-apps/util-linux-2.16.1) [ebuild N ] sys-fs/lvm2-2.02.51-r1 USE="lvm1 readline static -clvm (-cman) (-selinux)" [blocks B ] sys-fs/device-mapper ("sys-fs/device-mapper" is blocking sys-fs/lvm2-2.02.51-r1) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. ('ebuild', '/', 'sys-fs/lvm2-2.02.51-r1', 'merge') pulled in by lvm2 And if I remove the device-mapper and run revdep-rebuild, I got long output of errors related to e2fsprogs, which seems to be the same problem as in bug 292622. for me, unmerging device-mapper solved issue (emerge -uDNa world has installed cryptsetup and lvm2) I had to do it in three steps: emerge -C device-mapper emerge -uDN e2fsprogs emerge -uDN world Yes, I had to update e2fsprogs first, because emerge -uDN world complains about blocking. Now it is hopefully updated. *** Bug 292786 has been marked as a duplicate of this bug. *** *** Bug 296151 has been marked as a duplicate of this bug. *** |