On 03/30/2013 11:24 PM, Tanstaafl
wrote:
Ok,
I don't understand this...
Why is it that when I comment out the package.mask entries for
udev:
#>=sys-fs/udev-181
#>=virtual/udev-181
emerge -pvuND world shows updates to udev-197, with no mention of
udev-200, but...
when I uncomment them:
>=sys-fs/udev-181
>=virtual/udev-181
emerge -pvuDN world shows updates to BOTH virtual/udev-197-r2
*and* udev-200, with strange Blockers referencing udev-186???
[ebuild U #] sys-fs/udev-200 [171-r10]
USE="acl%* firmware-loader%* kmod%* openrc%* -doc% -gudev -hwdb
-introspection -keymap (-selinux) -static-libs%
(-action_modeswitch%) (-build%) (-debug%) (-edd%) (-extras%)
(-floppy%) (-rule_generator%*) (-test%)" 2,063 kB
[ebuild U #] virtual/udev-197-r2 [171] USE="kmod -gudev
-hwdb -introspection -keymap (-selinux) -static-libs" 0 kB
[ebuild N ~] sys-fs/udev-init-scripts-25 5 kB
...
[blocks B ] <sys-fs/udev-186
("<sys-fs/udev-186" is blocking sys-fs/udev-init-scripts-25)
[blocks B ] sys-apps/module-init-tools
("sys-apps/module-init-tools" is blocking sys-apps/kmod-12-r1)
[blocks B ] sys-apps/kmod ("sys-apps/kmod" is blocking
sys-apps/module-init-tools-3.16-r2)
My reading is: there are some packages either in your tree or being
pulled in that require a later version of udev. So even if you mask
udev-197, it's still being pulled in by something else. You have to
uninstall / mask those package versions as well. How they got there
or what they are, I don't know. If you're unlucky that might just be
because the portage tree was in the middle of syncing...
As for 186, emerge is hilariously tripping all over itself here.
sys-fs/udev is being upgraded, but it requires udev-init-scripts to
be installed. And udev-init-scripts conflicts with older versions of
udev which is installed, so...
Try increasing the backtrack to see if emerge can resolve it
automatically. --backtrack=30. If it can't, the canon advice would
be to manually uninstall (emerge -C --deselect=n) the older version
before installing the newer one.