| 1 |
|
| 2 |
|
| 3 |
|
| 4 |
|
| 5 |
|
| 6 |
On 03/30/2013 11:24 PM, Tanstaafl |
| 7 |
wrote:
|
| 8 |
|
| 9 |
Ok, |
| 10 |
I don't understand this... |
| 11 |
|
| 12 |
|
| 13 |
Why is it that when I comment out the package.mask entries for |
| 14 |
udev: |
| 15 |
|
| 16 |
|
| 17 |
#>=sys-fs/udev-181 |
| 18 |
|
| 19 |
#>=virtual/udev-181 |
| 20 |
|
| 21 |
|
| 22 |
emerge -pvuND world shows updates to udev-197, with no mention of |
| 23 |
udev-200, but... |
| 24 |
|
| 25 |
|
| 26 |
when I uncomment them: |
| 27 |
|
| 28 |
|
| 29 |
>=sys-fs/udev-181 |
| 30 |
|
| 31 |
>=virtual/udev-181 |
| 32 |
|
| 33 |
|
| 34 |
emerge -pvuDN world shows updates to BOTH virtual/udev-197-r2 |
| 35 |
*and* udev-200, with strange Blockers referencing udev-186??? |
| 36 |
|
| 37 |
|
| 38 |
[ebuild�������� U #] sys-fs/udev-200 [171-r10] |
| 39 |
USE="acl%* firmware-loader%* kmod%* openrc%* -doc% -gudev -hwdb |
| 40 |
-introspection -keymap (-selinux) -static-libs% |
| 41 |
(-action_modeswitch%) (-build%) (-debug%) (-edd%) (-extras%) |
| 42 |
(-floppy%) (-rule_generator%*) (-test%)" 2,063 kB |
| 43 |
|
| 44 |
[ebuild�������� U #] virtual/udev-197-r2 [171] USE="kmod -gudev |
| 45 |
-hwdb -introspection -keymap (-selinux) -static-libs" 0 kB |
| 46 |
|
| 47 |
[ebuild�� N������ ~] sys-fs/udev-init-scripts-25�� 5 kB |
| 48 |
|
| 49 |
|
| 50 |
... |
| 51 |
|
| 52 |
[blocks B���������� ] <sys-fs/udev-186 |
| 53 |
("<sys-fs/udev-186" is blocking sys-fs/udev-init-scripts-25) |
| 54 |
|
| 55 |
[blocks B���������� ] sys-apps/module-init-tools |
| 56 |
("sys-apps/module-init-tools" is blocking sys-apps/kmod-12-r1) |
| 57 |
|
| 58 |
[blocks B���������� ] sys-apps/kmod ("sys-apps/kmod" is blocking |
| 59 |
sys-apps/module-init-tools-3.16-r2) |
| 60 |
|
| 61 |
|
| 62 |
|
| 63 |
|
| 64 |
|
| 65 |
My reading is: there are some packages either in your tree or being |
| 66 |
pulled in that require a later version of udev. So even if you mask |
| 67 |
udev-197, it's still being pulled in by something else.�� You have to |
| 68 |
uninstall / mask those package versions as well. How they got there |
| 69 |
or what they are, I don't know. If you're unlucky that might just be |
| 70 |
because the portage tree was in the middle of syncing...
|
| 71 |
|
| 72 |
As for 186, emerge is hilariously tripping all over itself here. |
| 73 |
sys-fs/udev is being upgraded, but it requires udev-init-scripts to |
| 74 |
be installed. And udev-init-scripts conflicts with older versions of |
| 75 |
udev which is installed, so...
|
| 76 |
|
| 77 |
Try increasing the backtrack to see if emerge can resolve it |
| 78 |
automatically. --backtrack=30. If it can't, the canon advice would |
| 79 |
be to manually uninstall (emerge -C --deselect=n) the older version |
| 80 |
before installing the newer one.
|
| 81 |
|
| 82 |
|
| 83 |
|
| 84 |
|
Archives