1 |
On 04/10/2013 11:50, Alex Schuster wrote: |
2 |
> Hi there! |
3 |
> |
4 |
> Some may remember me from posting here often. But since a year, I have a |
5 |
> new life, and much less time for sitting at my computer. Sigh. And my |
6 |
> beloved Gentoo got a little outdated. |
7 |
> |
8 |
> So, a @world update does not work. I thought I give emerge -e @world a |
9 |
> try, this should sort out the problems, but this also does not go well. |
10 |
> |
11 |
> I don't want to bother you with the whole lot of output emerge gives me, |
12 |
> and just ask a specific question at the moment. I get the 'Multiple |
13 |
> package instances within a single package slot have been pulled into the |
14 |
> dependency graph, resulting in a slot conflict' message, and several |
15 |
> affected packages. One example is claws: |
16 |
> |
17 |
> mail-client/claws-mail:0 |
18 |
> |
19 |
> (mail-client/claws-mail-3.9.0-r1::gentoo, ebuild scheduled for merge) |
20 |
> pulled in by ~mail-client/claws-mail-3.9.0 required by |
21 |
> (mail-client/claws-mail-address_keeper-1.0.7::gentoo, ebuild scheduled |
22 |
> for merge) |
23 |
> |
24 |
> (mail-client/claws-mail-3.9.2::gentoo, ebuild scheduled for merge) |
25 |
> pulled in by (no parents that aren't satisfied by other packages in |
26 |
> this slot) |
27 |
> |
28 |
> Looking at the ebuild, I see that claws-mail-address_keeper rdepends on |
29 |
> claws-mail-3.9.0. But being on ~amd86, 3.9.2 would be current. |
30 |
> |
31 |
> I can solve this by masking versions greater than 3.9.0. Two questions: |
32 |
> |
33 |
> Why can't portage deal with this itself, and simply install the highest |
34 |
> version that fulfills all requirements? |
35 |
|
36 |
Your use of --emptytree makes it slightly harder to determine from the |
37 |
above output, because the conflict messages will not correctly |
38 |
distinguish merged (installed) packages from those that are yet to be |
39 |
merged. |
40 |
|
41 |
Do you have mail-client/claws-mail-address_keeper in your world file? If |
42 |
so, that would mandate its installation as part of the @world set (no if |
43 |
or buts). In turn, that would exhibit a hard dependency on |
44 |
claws-mail-3.9.0, which obviously cannot co-exist with 3.9.2, even if |
45 |
you have unmasked it. |
46 |
|
47 |
Try removing the entry from the world file if it's there, then seeing |
48 |
whether the conflict is handled any differently. |
49 |
|
50 |
> |
51 |
> And how do I notice an update to claws-mail-address_keeper that would |
52 |
> allow a newer version of claws-mail? Other than remembering those masks |
53 |
> and go through them once in a while? |
54 |
|
55 |
As of the 3.9.1 ebuild, there is a comment above the collection of |
56 |
blocks that states: |
57 |
|
58 |
"Plugins are all integrated or dropped since 3.9.1" |
59 |
|
60 |
Further, from the 3.9.1 release notes: |
61 |
|
62 |
"All plugins previously packaged as 'Extra Plugins' are now contained |
63 |
within the Claws Mail package." |
64 |
|
65 |
Thus, it's possible that the address_keeper plugin has been folded into |
66 |
the core. In turn, that would explain why it must block the plugin as a |
67 |
separate package. |
68 |
|
69 |
> |
70 |
> Similar problems happen with sys-boot/syslinux, pulled in by |
71 |
> sys-boot/unetbootin, media-sound/jack-audio-connection-kit, pulled in by |
72 |
> app-emulation/emul-linux-x86-soundlibs, and all dev-qt packages, where I |
73 |
> did not yet figure out what to do. |
74 |
> |
75 |
> I am running portage 2.2.7. |
76 |
> |
77 |
> Alex |
78 |
> |