1 |
On Sunday 17 Apr 2016 11:44:50 Alan McKinnon wrote: |
2 |
> On 17/04/2016 11:36, Meino.Cramer@×××.de wrote: |
3 |
> > Alan McKinnon <alan.mckinnon@×××××.com> [16-04-17 11:08]: |
4 |
> >> On 17/04/2016 05:45, Meino.Cramer@×××.de wrote: |
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 |
20 |
> >>> dependency conflict: |
21 |
> >>> |
22 |
> >>> dev-util/boost-build:0 |
23 |
> >>> |
24 |
> >>> (dev-util/boost-build-1.60.0:0/0::gentoo, ebuild scheduled for merge) |
25 |
> >>> conflicts with>>> |
26 |
> >>> =dev-util/boost-build-1.58* required by |
27 |
> >>> (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed) ^ |
28 |
> >>> ^^^^^ |
29 |
> >>> |
30 |
> >>> !!! The following update has been skipped due to unsatisfied |
31 |
> >>> dependencies: |
32 |
> >>> |
33 |
> >>> dev-libs/boost:0 |
34 |
> >>> |
35 |
> >>> !!! All ebuilds that could satisfy "=dev-util/boost-build-1.60*" have |
36 |
> >>> been masked. !!! One of the following masked packages is required to |
37 |
> >>> complete your request: - dev-util/boost-build-1.60.0::gentoo (masked |
38 |
> >>> by: ) |
39 |
> >>> |
40 |
> >>> |
41 |
> >>> For me it looks like boost not beeing updated/reinstalled because of |
42 |
> >>> another version of boost, which depends on boost. |
43 |
> >>> |
44 |
> >>> HELP, I need somebody, HELP, not just anybody hee-eee-eelp uuuuuhhhh! |
45 |
> >>> |
46 |
> >>> Thanks for any HELP in advance! May the source be with you... |
47 |
> >>> Best regards, |
48 |
> >>> Meino |
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 |
> >> |
57 |
> >> =dev-util/boost-build-${MAJOR_V}*" |
58 |
> >> |
59 |
> >> and boost-build does not depend on boost. |
60 |
> >> |
61 |
> >> So, logically you'd expect boost to want to upgrade to 1.60, notice |
62 |
> >> boost-build's dep and upgrade boost-build as well to match. But it |
63 |
> >> doesn't, because boost-build-1.60 is masked for <null> reason. |
64 |
> >> |
65 |
> >> It really looks and smells like a bug in emerge[1] when updating world |
66 |
> >> where it considers boost-build first, fixes the version to use to match |
67 |
> >> current boost, and then can't find a way to upgrade boost. |
68 |
> >> |
69 |
> >> Solution would seem to be to emerge -C either of them and let portage |
70 |
> >> get on with it. Or upgrade just upgrade boost-build by itself then do |
71 |
> >> world |
72 |
> >> |
73 |
> >> |
74 |
> >> [1] I wouldn't go so far as to call it a "bug" as such, because nothing |
75 |
> >> in the spec requires a package manager to guarantee that it will always |
76 |
> >> find the best way to upgrade everything. It only needs to keep the |
77 |
> >> system consistent with the ebuilds it has. |
78 |
> > |
79 |
> > Hi Alan, |
80 |
> > |
81 |
> > thanks for your reply! :) |
82 |
> > |
83 |
> > ...and I thought it was me being too limited to see the real truth |
84 |
> > behind that what it is The Matrix. |
85 |
> > |
86 |
> > But it was only a deja-vu....oh wait! It was NO deja-vu ... no |
87 |
> > glitch in The Matrix...we had similiar emerge-ncies in the past. ;) |
88 |
> > |
89 |
> > I will see how far I can go...I was warned to use 060 of boost... |
90 |
> > |
91 |
> > Best regards, |
92 |
> > Meino |
93 |
> |
94 |
> It reminds me of many years back with two packages that depend on each |
95 |
> other and portage couldn't deal with updating both at the same time. |
96 |
> |
97 |
> emerge -C got a lot of use back then :-) |
98 |
|
99 |
Don't forget to use -1aDv when you emerge boost manually as Alan suggested, |
100 |
unless for some reason you want boost in your world file. |
101 |
|
102 |
-- |
103 |
Regards, |
104 |
Mick |