1 |
On 17/04/2016 14:09, Meino.Cramer@×××.de wrote: |
2 |
> Mick <michaelkintzios@×××××.com> [16-04-17 14:00]: |
3 |
>> On Sunday 17 Apr 2016 11:44:50 Alan McKinnon wrote: |
4 |
>>> On 17/04/2016 11:36, Meino.Cramer@×××.de wrote: |
5 |
>>>> Alan McKinnon <alan.mckinnon@×××××.com> [16-04-17 11:08]: |
6 |
>>>>> On 17/04/2016 05:45, Meino.Cramer@×××.de wrote: |
7 |
>>>>>> Hi, |
8 |
>>>>>> |
9 |
>>>>>> ...and the novice was buffled and even the master shifted a little bit |
10 |
>>>>>> after recognizing this words of the eternal being named emerge. |
11 |
>>>>>> I know, that there is a difference in knowing the path and walking the |
12 |
>>>>>> path, but it seems that I am not supposed to understand this: |
13 |
>>>>>> |
14 |
>>>>>> |
15 |
>>>>>> These are the packages that would be merged, in reverse order: |
16 |
>>>>>> |
17 |
>>>>>> Calculating dependencies... done! |
18 |
>>>>>> |
19 |
>>>>>> Total: 0 packages, Size of downloads: 0 KiB |
20 |
>>>>>> |
21 |
>>>>>> WARNING: One or more updates/rebuilds have been skipped due to a |
22 |
>>>>>> dependency conflict: |
23 |
>>>>>> |
24 |
>>>>>> dev-util/boost-build:0 |
25 |
>>>>>> |
26 |
>>>>>> (dev-util/boost-build-1.60.0:0/0::gentoo, ebuild scheduled for merge) |
27 |
>>>>>> conflicts with>>> |
28 |
>>>>>> =dev-util/boost-build-1.58* required by |
29 |
>>>>>> (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed) ^ |
30 |
>>>>>> ^^^^^ |
31 |
>>>>>> |
32 |
>>>>>> !!! The following update has been skipped due to unsatisfied |
33 |
>>>>>> dependencies: |
34 |
>>>>>> |
35 |
>>>>>> dev-libs/boost:0 |
36 |
>>>>>> |
37 |
>>>>>> !!! All ebuilds that could satisfy "=dev-util/boost-build-1.60*" have |
38 |
>>>>>> been masked. !!! One of the following masked packages is required to |
39 |
>>>>>> complete your request: - dev-util/boost-build-1.60.0::gentoo (masked |
40 |
>>>>>> by: ) |
41 |
>>>>>> |
42 |
>>>>>> |
43 |
>>>>>> For me it looks like boost not beeing updated/reinstalled because of |
44 |
>>>>>> another version of boost, which depends on boost. |
45 |
>>>>>> |
46 |
>>>>>> HELP, I need somebody, HELP, not just anybody hee-eee-eelp uuuuuhhhh! |
47 |
>>>>>> |
48 |
>>>>>> Thanks for any HELP in advance! May the source be with you... |
49 |
>>>>>> Best regards, |
50 |
>>>>>> Meino |
51 |
>>>>> |
52 |
>>>>> Hah! That's one of those blockers that makes little or no sense. |
53 |
>>>>> |
54 |
>>>>> |
55 |
>>>>> boost has this dep: |
56 |
>>>>> |
57 |
>>>>> DEPEND="${RDEPEND} |
58 |
>>>>> |
59 |
>>>>> =dev-util/boost-build-${MAJOR_V}*" |
60 |
>>>>> |
61 |
>>>>> and boost-build does not depend on boost. |
62 |
>>>>> |
63 |
>>>>> So, logically you'd expect boost to want to upgrade to 1.60, notice |
64 |
>>>>> boost-build's dep and upgrade boost-build as well to match. But it |
65 |
>>>>> doesn't, because boost-build-1.60 is masked for <null> reason. |
66 |
>>>>> |
67 |
>>>>> It really looks and smells like a bug in emerge[1] when updating world |
68 |
>>>>> where it considers boost-build first, fixes the version to use to match |
69 |
>>>>> current boost, and then can't find a way to upgrade boost. |
70 |
>>>>> |
71 |
>>>>> Solution would seem to be to emerge -C either of them and let portage |
72 |
>>>>> get on with it. Or upgrade just upgrade boost-build by itself then do |
73 |
>>>>> world |
74 |
>>>>> |
75 |
>>>>> |
76 |
>>>>> [1] I wouldn't go so far as to call it a "bug" as such, because nothing |
77 |
>>>>> in the spec requires a package manager to guarantee that it will always |
78 |
>>>>> find the best way to upgrade everything. It only needs to keep the |
79 |
>>>>> system consistent with the ebuilds it has. |
80 |
>>>> |
81 |
>>>> Hi Alan, |
82 |
>>>> |
83 |
>>>> thanks for your reply! :) |
84 |
>>>> |
85 |
>>>> ...and I thought it was me being too limited to see the real truth |
86 |
>>>> behind that what it is The Matrix. |
87 |
>>>> |
88 |
>>>> But it was only a deja-vu....oh wait! It was NO deja-vu ... no |
89 |
>>>> glitch in The Matrix...we had similiar emerge-ncies in the past. ;) |
90 |
>>>> |
91 |
>>>> I will see how far I can go...I was warned to use 060 of boost... |
92 |
>>>> |
93 |
>>>> Best regards, |
94 |
>>>> Meino |
95 |
>>> |
96 |
>>> It reminds me of many years back with two packages that depend on each |
97 |
>>> other and portage couldn't deal with updating both at the same time. |
98 |
>>> |
99 |
>>> emerge -C got a lot of use back then :-) |
100 |
>> |
101 |
>> Don't forget to use -1aDv when you emerge boost manually as Alan suggested, |
102 |
>> unless for some reason you want boost in your world file. |
103 |
>> |
104 |
>> -- |
105 |
>> Regards, |
106 |
>> Mick |
107 |
> |
108 |
> |
109 |
> |
110 |
> Hi Mick, |
111 |
> |
112 |
> thanks for the warning! Will do so... :) |
113 |
|
114 |
-1 is fine, but don't use -D in that manual step; you do not want deep here. |
115 |
|
116 |
That happens later when you do a regular world update |
117 |
|
118 |
|
119 |
-- |
120 |
Alan McKinnon |
121 |
alan.mckinnon@×××××.com |