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