1 |
On 1/4/2013 10:23, James wrote: |
2 |
> Dustin C. Hatch <admiralnemo <at> gmail.com> writes: |
3 |
> |
4 |
> |
5 |
>> The problem is you are trying to downgrade sys-fs/udev but not |
6 |
>> virtual/udev. If you want to force using udev-171, you need to mask both |
7 |
>> the real and virtual atoms. Try this in /etc/portage/package.mask/udev: |
8 |
> |
9 |
>> >=sys-fs/udev-181 |
10 |
>> >=virtual/udev-181 |
11 |
> |
12 |
>> Then emerge -avuD1 udev and see if that fixes it. |
13 |
> |
14 |
> I get the downgrades you would expect: |
15 |
> |
16 |
> |
17 |
> |
18 |
> UD ] virtual/udev-171 [196] |
19 |
> UD ] sys-fs/udev-171-r9 |
20 |
> |
21 |
> I also get some weird companion downgrades: |
22 |
> |
23 |
> blocks B ] >x11-libs/qt-script-4.8.2-r9999:4 |
24 |
> (">x11-libs/qt-script-4.8.2-r9999:4" is blocking x11-libs/qt-declarative-4.8.2, |
25 |
> x11-libs/qt-webkit-4.8.2, x11-libs/qt-svg-4.8.2, x11-libs/qt-test-4.8.2, |
26 |
> x11-libs/qt-xmlpatterns-4.8.2, x11-libs/qt-multimedia-4.8.2, |
27 |
> x11-libs/qt-opengl-4.8.2) |
28 |
> [blocks B ] <x11-libs/qt-gui-4.8.4:4 |
29 |
> <snip> |
30 |
> |
31 |
I don't have Qt installed anywhere, so I can't reproduce that problem. I |
32 |
also don't see that particular version of qt-script in the tree, so I |
33 |
can't be sure, but my guess is some Qt dep that you already have |
34 |
installed depends on a newer version of udev than you will be getting |
35 |
after the downgrade, thus requiring it to downgrade as well. |
36 |
|
37 |
> and these: |
38 |
> |
39 |
> Multiple package instances within a single package slot have been pulled |
40 |
> !!! into the dependency graph, resulting in a slot conflict: |
41 |
> |
42 |
> virtual/udev:0 |
43 |
> |
44 |
> (virtual/udev-171::gentoo,ebuild scheduled for merge) pulled in by |
45 |
> <virtual/udev-196 required by (sys-fs/lvm2-2.02.88::gentoo, installed) |
46 |
> =virtual/udev-171 required by (kde-base/kdelibs-4.9.3::gentoo, installed) |
47 |
> (and 17 more with the same problems) |
48 |
> |
49 |
> (virtual/udev-196::gentoo, installed) pulled in by |
50 |
> >=virtual/udev-180 required by (sys-fs/udev-196-r1::gentoo, installed) |
51 |
> (and 1 more with the same problem) |
52 |
> |
53 |
> sys-fs/udev:0 |
54 |
> |
55 |
> (sys-fs/udev-196-r1::gentoo, installed) pulled in by |
56 |
> |
57 |
>> =sys-fs/udev-196-r1[gudev?,hwdb?,introspection?,keymap?,selinux?,static-libs?] |
58 |
> required by (virtual/udev-196::gentoo, installed) |
59 |
> |
60 |
> (sys-fs/udev-171-r9::gentoo, ebuild scheduled for merge) pulled in by |
61 |
> ~sys-fs/udev-171[gudev?,hwdb?,introspection?,keymap?,selinux?] required by |
62 |
> (virtual/udev-171::gentoo, ebuild scheduled for merge) |
63 |
> |
64 |
> <snip> |
65 |
> |
66 |
> Does this look normal? |
67 |
> |
68 |
Yes, I expected something like that. In all likelihood, you'll need to |
69 |
completely remove sys-fs/udev and virtual/udev and then reinstall the |
70 |
older version. You'll probably want to do this in single user mode (i.e. |
71 |
`rc single`), so running programs don't crash suddenly. A reboot |
72 |
afterward is probably a good idea as well. |
73 |
-- |
74 |
♫Dustin |