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