Summary: | sys-fs/lvm2-2.02.56-r2 needs updated sys-fs/udev dependancy | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Daniel Kerwin <daniel> |
Component: | [OLD] Core system | Assignee: | Robin Johnson <robbat2> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | cardoe |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Daniel Kerwin
2010-01-14 17:08:48 UTC
Does udev appear in the list of packages when you use the following emerge command? emerge -uDpv --with-bdeps=y world No. This command doesn't make udev show up. This is really strange... Okay, how about this command? emerge -uDpv system In case this doesn't work as well, does the command grep -Hr udev /etc/portage give any output? What version of udev did you have before that your system broke? Upstream's specs simply say that udev should exist, not that it needs to be any minimum version. When i append udev to my emerge world command: [binary U ] sys-fs/udev-146-r1 [141] USE="devfs-compat%* -extras% (-selinux)" [0] So it's updated from 141 to 146-r1 You said that udev-141 didn't work with this new lvm. Can you find the earliest version that did? Test the following: - 141-r1 - 145-r3 - 146-r1 This isn't really the problem. It definitively works with 146-r1 but i have to emerge it manually. The real problem is that it was not part of a world update. I need to know if 145 is good enough, to see if the dep needs to be 145 or 146! I'm sorry but i can't verify that in the moment. All systems are already updated and i don't have a system to test that... (In reply to comment #7) > This isn't really the problem. It definitively works with 146-r1 but i have to The question is: What does or does not work if udev-version is bad? Is it about the persistent links /dev/disk/by-id/dm-name-* and /dev/disk/by-id/dm-uuid-*. If these link do not work, then this is not about too old udev, but too old sys-apps/util-linux, as that does provide /sbin/blkid. But this all is just a guess. > emerge it manually. The real problem is that it was not part of a world update. The problem of udev not being part of your worldfile cannot be solved for lvm2, as lvm2 itself does not depend on udev. There are still people not wanting udev on the system. So you need to emerge udev yourself if you want to use it (and this will add it to your worldfile). What I can image is: You did once install some package that did depend on udev, and then unmerged it, so you got udev installed but world does not have and update it. (In reply to comment #8) > I need to know if 145 is good enough, to see if the dep needs to be 145 or 146! > At this point, 146-r1 is stable. Would you want to add that? .63 and newer have: || ( =sys-fs/udev-146-r3 >=sys-fs/udev-151-r2 ) Because of other changes, so this is moot now. |