I run an OpenVZ kernel : linux-2.6.32-openvz-feoktistov.1 - this is the latest for OpenVZ as far as I can tell; so have masked udev > 171 and am currently running: Code: * virtual/udev Latest version available: 171 Latest version installed: 171 Size of files: 0 kB Homepage: Description: Virtual for udev implementation and number of its features License: * sys-fs/udev Latest version available: 197-r3 Latest version installed: 171-r10 Size of files: 2,007 kB Homepage: http://www.freedesktop.org/wiki/Software/systemd Description: Linux dynamic and persistent device naming support (aka userspace devfs) License: LGPL-2.1 MIT GPL-2 The latest set of updates bring in virtual/dev-manager which then tries: Code: jared ~ # emerge -kuavNDt world * IMPORTANT: 1 news items need reading for repository 'gentoo'. * Use eselect news to read news items. These are the packages that would be merged, in reverse order: Calculating dependencies... done! [nomerge ] virtual/dev-manager-0 [binary N ] sys-fs/static-dev-0.1 0 kB If I mask static-dev I get: Code: jared ~ # emerge -kuavNDt world * IMPORTANT: 1 news items need reading for repository 'gentoo'. * Use eselect news to read news items. These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild R ] sys-apps/busybox-1.20.2 USE="ipv6 mdev* pam static -livecd -make-symlinks -math -savedconfig (-selinux) -sep-usr -systemd" 0 kB Looking at the ebuild this is also an option in dev-manager's RDEPEND list. As is static-dev and virtual/udev (which I have installed). So why is it ignoring my virtual/udev? (I have also created a thread here: http://forums.gentoo.org/viewtopic.php?p=7254732 )
Created attachment 340154 [details] Emerge info
non-OpenVZ kernel 2.6.32 has DEVTMPFS support and works with =sys-fs/udev-197* but OpenVZ for some reason have disabled this option from the kernel source, supposedly this kernel option is not compatible with OpenVZ. How did you mask new udev? Did you remember to mask both, the package and the virtual? /etc/portage/package.mask: >=sys-fs/udev-197 >=virtual/udev-197 And there are plenty of packages in tree already requiring at least >=197, like sys-apps/hwids when USE="udev" is enabled, sys-fs/udisks always, and some more... you have to selectively figure this out, mostly by hand :P needless to say staying with 171 is a dead end
I only had the virtual package masked. I have now masked sys-fs/udev-197 as well and dev-manager is now satisfied... Thank you! Not sure what status to set on this bug; its certainly not obvious to me why adding an additional package mask suddenly solves the problem - there is no way I would have guessed to do that and I'm not really a Gentoo/Linux beginner. As for sticking with udev-171; I'm hoping that we'll see an OpenVZ 3.X kernel sometime later this year, otherwise I'll have to switch away from udev.
