1 |
Alan McKinnon wrote: |
2 |
> On Thursday 10 April 2008, Dale wrote: |
3 |
> |
4 |
>> Alan McKinnon wrote: |
5 |
>> |
6 |
>>> On Wednesday 09 April 2008, Uwe Thiem wrote: |
7 |
>>> |
8 |
>>>> Hi folks, |
9 |
>>>> |
10 |
>>>> emerge --update world tells me: |
11 |
>>>> [blocks B ] dev-util/gtk-doc-am (is blocking |
12 |
>>>> dev-util/gtk-doc-1.8-r2) |
13 |
>>>> |
14 |
>>>> emerge --unmerge gtk-doc-am tells me: |
15 |
>>>> --- Couldn't find 'gtk-doc-am' to unmerge. |
16 |
>>>> |
17 |
>>>> So let's be more specific: |
18 |
>>>> emerge --unmerge =dev-util/gtk-doc-am-1.10 tells me: |
19 |
>>>> --- Couldn't find '=dev-util/gtk-doc-am-1.10' to unmerge. |
20 |
>>>> |
21 |
>>> emerge -C gtk-doc |
22 |
>>> |
23 |
>>> Look closely at the error message, it's like one of those optical |
24 |
>>> illusions where you don't quite get it first time :-) |
25 |
>>> |
26 |
>> Well said. I'm still not sure I get it. I would have went to |
27 |
>> console and unmerged the whole lot and started over. LOL |
28 |
>> |
29 |
> |
30 |
> hehe, emerge's output can be tricky to parse. Here's the long version: |
31 |
> |
32 |
> In this line: |
33 |
> [blocks B ] dev-util/gtk-doc-am (is blocking |
34 |
> dev-util/gtk-doc-1.8-r2) |
35 |
> |
36 |
> everything there comes out of the gtk-doc-am ebuild, including what it's |
37 |
> not happy with. This specific case says that gtk-doc-1.8-r2 is already |
38 |
> installed and gtk-doc-am will not merge itself while it's there. |
39 |
> |
40 |
> The [blocks B ] bit says that gtk-doc-am is not already installed |
41 |
> (there isn't an R or U or D there at all) so there is nothing to |
42 |
> unmerge. |
43 |
> |
44 |
> Usually with blockers, you have to unmerge the thing being blocked (in |
45 |
> brackets on the above line) first. Or, if you don't want that, don't |
46 |
> merge the main package, or mask it out. |
47 |
> |
48 |
> The correct merge approach would be to build a suitable upgraded |
49 |
> gtk-doc, merge it (which unmerges the old one) and then merge |
50 |
> gtk-doc-am (on the assumption that gtk-doc-am is happy with the new |
51 |
> version of gtk-doc). For some reason portage can't do that this time, |
52 |
> probably build order, so it's telling the user to do it manually and |
53 |
> try again. |
54 |
> |
55 |
> If you want to look deeper into what is going on, the solution is in the |
56 |
> ebuild. From /var/portage/dev-util/gtk-doc-am/gtk-doc-am-1.10.ebuild: |
57 |
> |
58 |
> DEPEND="!<=dev-utils/gtk-doc-1.10" |
59 |
> |
60 |
> Aha, so the only current version that will work is gtk-doc-1.10-r1. This |
61 |
> was probably revised to accomodate gtk-doc-am. |
62 |
> |
63 |
> It gets even better. |
64 |
> From /var/portage/dev-util/gtk-doc/gtk-doc-1.8-r2.ebuild: |
65 |
> DEPEND="!dev-util/gtk-doc-am" |
66 |
> |
67 |
> and from /var/portage/dev-util/gtk-doc/gtk-doc-1.10-r1.ebuild: |
68 |
> DEPEND="=dev-util/gtk-doc-am-${PV} |
69 |
> |
70 |
> Now it all becomes clearer with a little reading between the lines. The |
71 |
> dev took gtk-doc and split it into two packages, to get the automake |
72 |
> (-am) stuff into it's own ebuild. But that will mean that gtk-doc-am |
73 |
> will trash files that gtk-doc put there. This is a collision and |
74 |
> portage won't do it. It's written to pass the buck to a human |
75 |
> instead :-) |
76 |
> |
77 |
> |
78 |
|
79 |
|
80 |
It appears this human is a bit dense. I !think! I get it but not real |
81 |
sure. May have to read that a few more times. Sounds like the clue is |
82 |
the missing U and D part. |
83 |
|
84 |
Thanks |
85 |
|
86 |
Dale |
87 |
|
88 |
:-) :-) |
89 |
-- |
90 |
gentoo-user@l.g.o mailing list |