1 |
On December 15, 2016 5:31:58 PM GMT+01:00, Mick <michaelkintzios@×××××.com> wrote: |
2 |
>On Wednesday 14 Dec 2016 06:48:41 J. Roeleveld wrote: |
3 |
>> On Wednesday, December 14, 2016 12:06:00 AM Philip Webb wrote: |
4 |
>> > I just updated Qt5 to 5.6.2 & ran into a familiar Portage problem. |
5 |
>> > |
6 |
>> > The emerge command responds with a list of "conflicts", |
7 |
>> > all involving 5.6.1 vs 5.6.2 versions of the c 15 pkgs. |
8 |
>> > The only way to get around this is to unmerge the existing pkgs via |
9 |
>'-C', |
10 |
>> > then install the new versions. That works, but it's brute force. |
11 |
>> > |
12 |
>> > Portage sb able to resolve this kind of conflict for itself. |
13 |
>> > If not, then at least it should advise users intelligently |
14 |
>> > to do what I've just described. It can happen with other sets of |
15 |
>pkgs. |
16 |
>> > |
17 |
>> > Yes, I did do 'backtrack==30'. |
18 |
>> > |
19 |
>> > Before I send in a bug, does anyone else have useful comments ? |
20 |
>> |
21 |
>> I did exactly the same upgrade on 2 machines, along with an entire |
22 |
>plasma |
23 |
>> upgrade, and didn't encounter this issue. |
24 |
>> |
25 |
>> For comparison, this is what I generally use: |
26 |
>> |
27 |
>> # emerge -vauDN --with-bdeps=y @world |
28 |
>> # emerge -va --depclean |
29 |
>> |
30 |
>> Do you only upgrade subsets? Or the full world? |
31 |
>> I found that with libraries like qt, python and similar, only |
32 |
>upgrading |
33 |
>> those makes it impossible for portage to properly handle the |
34 |
>blockers. |
35 |
>> |
36 |
>> -- |
37 |
>> Joost |
38 |
> |
39 |
>I came across a similar problem on 4 PCs. From memory the problem was |
40 |
>resolved when I manually unmerged dev-qt/qtcore and then updated world |
41 |
>with |
42 |
>backtrack=90. I did not have to run --with-bdeps=y. |
43 |
|
44 |
The with bdeps option actually meant I didn't have to unmerge anything. |
45 |
|
46 |
-- |
47 |
Joost |
48 |
-- |
49 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |