1 |
On Thursday 01 January 2009 10:10:08 meino.cramer@×××.de wrote: |
2 |
> Hi, |
3 |
> |
4 |
> HAPPY NEW YEAR ! :O) |
5 |
> |
6 |
> |
7 |
> I have got a problem while updateing my Gentoo-Linux-box: |
8 |
> |
9 |
> Witzh this command: |
10 |
> emerge Net-Daemon PlRPC DBI rxvt-unicode gstreamer e2fsprogs-libs nano |
11 |
> e2fsprogs zynaddsubfx sox boost autounmask cmake smplayer kdelibs wxGTK |
12 |
> firehol xulrunner xorg-server vlc |
13 |
> |
14 |
> |
15 |
> I got (beside a list of updateable/new package) the following warning: |
16 |
> |
17 |
> [blocks B ] x11-libs/qt-core ("x11-libs/qt-core" is blocking |
18 |
> x11-libs/qt-4.3.3) |
19 |
> > [blocks B ] <=x11-libs/qt-4.4.0_alpha:4 |
20 |
> ("<=x11-libs/qt-4.4.0_alpha:4" is blocking x11-libs/qt-script-4.4.2, |
21 |
> x11-libs/qt-dbus-4.4.2, x11-libs/qt-qt3support-4.4.2, |
22 |
> x11-libs/qt-sql-4.4.2, x11-libs/qt-gui-4.4.2, x11-libs/qt-svg-4.4.2, |
23 |
> x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2, x11-libs/qt-opengl-4.4.2) |
24 |
> |
25 |
> Due to that I decided to do a |
26 |
> |
27 |
> emerge -C qt-core |
28 |
> |
29 |
> which was answered with: |
30 |
> |
31 |
> --- Couldn't find 'qt-core' to unmerge. |
32 |
> |
33 |
> |
34 |
> How cabn I solve the problem to get blocking packages, which do not |
35 |
> exist? |
36 |
|
37 |
Long long ago when I used to fix electronic bits, the best advice I ever ound |
38 |
for my techies was |
39 |
|
40 |
"OYFEAL": Open your fscking eyes and look. Some of that would help you a lot |
41 |
right now :-) |
42 |
|
43 |
When emerge runs, it builds a tree in memory of what it intends to do, that's |
44 |
where the blockers come from. So it doesn't have to be what you already have, |
45 |
it's portage telling you it can't follow your instructions. |
46 |
|
47 |
Look carefully at the first block. It clearly says that qt-core (no version) |
48 |
cannot be merged because of a block with qt-4.3.3. The second block says that |
49 |
all versions of qt less than or equal to 4.4.0_alpha block a bunch of 4.4.2 |
50 |
qt stuff. |
51 |
|
52 |
What happened here is that qt was split into several small package instead of |
53 |
one huge one. The new is therefore not compatible with the old and cannot |
54 |
co-exist, so you must unmerge the old version to be able to put the new ones |
55 |
on the system. You want: |
56 |
|
57 |
unmerge -avC qt |
58 |
emerge -av qt |
59 |
|
60 |
IIRC, there is a new qt meta package that will install core and others in step |
61 |
2. If not, just emerge qt-core manually. |
62 |
|
63 |
emerge's block output is worded confusingly, the exact selection of words can |
64 |
lead you to believe that you have to do B in order to do A, when actually |
65 |
it's the other way round. this is because the devs block B in A's ebuild and |
66 |
also block A in B's ebuild, so that no stupid circumstances can arise. Best |
67 |
way to wrap your head around it is to open each ebuild, read it and compare |
68 |
it to the console output. Sooner or later a lightbulb will go on in your |
69 |
head, at least that's how it worked for me and most others I've helped over |
70 |
the years. |
71 |
|
72 |
|
73 |
|
74 |
-- |
75 |
alan dot mckinnon at gmail dot com |