| 1 |
Kerin Millar writes: |
| 2 |
|
| 3 |
> On 04/10/2013 11:50, Alex Schuster wrote: |
| 4 |
|
| 5 |
[...] |
| 6 |
|
| 7 |
> > (mail-client/claws-mail-3.9.0-r1::gentoo, ebuild scheduled for |
| 8 |
> > merge) pulled in by ~mail-client/claws-mail-3.9.0 required by |
| 9 |
> > (mail-client/claws-mail-address_keeper-1.0.7::gentoo, ebuild |
| 10 |
> > scheduled for merge) |
| 11 |
> > |
| 12 |
> > (mail-client/claws-mail-3.9.2::gentoo, ebuild scheduled for merge) |
| 13 |
> > pulled in by (no parents that aren't satisfied by other packages in |
| 14 |
> > this slot) |
| 15 |
> > |
| 16 |
> > Looking at the ebuild, I see that claws-mail-address_keeper rdepends |
| 17 |
> > on claws-mail-3.9.0. But being on ~amd86, 3.9.2 would be current. |
| 18 |
> > |
| 19 |
> > I can solve this by masking versions greater than 3.9.0. Two |
| 20 |
> > questions: |
| 21 |
> > |
| 22 |
> > Why can't portage deal with this itself, and simply install the |
| 23 |
> > highest version that fulfills all requirements? |
| 24 |
> |
| 25 |
> Your use of --emptytree makes it slightly harder to determine from the |
| 26 |
> above output, because the conflict messages will not correctly |
| 27 |
> distinguish merged (installed) packages from those that are yet to be |
| 28 |
> merged. |
| 29 |
|
| 30 |
I get some more errors without --emptytree (media-libs/x264, |
| 31 |
dev-libs/icu, dev-libs/boost, app-text/poppler, dev-util/boost-build, |
| 32 |
dev-lang/ocaml, x11-base/xorg-server), so I gave -e a try. |
| 33 |
|
| 34 |
> Do you have mail-client/claws-mail-address_keeper in your world file? |
| 35 |
|
| 36 |
Sure. |
| 37 |
|
| 38 |
> If so, that would mandate its installation as part of the @world set |
| 39 |
> (no if or buts). In turn, that would exhibit a hard dependency on |
| 40 |
> claws-mail-3.9.0, which obviously cannot co-exist with 3.9.2, even if |
| 41 |
> you have unmasked it. |
| 42 |
|
| 43 |
Right. |
| 44 |
|
| 45 |
> Try removing the entry from the world file if it's there, then seeing |
| 46 |
> whether the conflict is handled any differently. |
| 47 |
|
| 48 |
I guess this would install 3.9.2, as there's no reason not to do this. |
| 49 |
|
| 50 |
> > And how do I notice an update to claws-mail-address_keeper that would |
| 51 |
> > allow a newer version of claws-mail? Other than remembering those |
| 52 |
> > masks and go through them once in a while? |
| 53 |
> |
| 54 |
> As of the 3.9.1 ebuild, there is a comment above the collection of |
| 55 |
> blocks that states: |
| 56 |
> |
| 57 |
> "Plugins are all integrated or dropped since 3.9.1" |
| 58 |
> |
| 59 |
> Further, from the 3.9.1 release notes: |
| 60 |
> |
| 61 |
> "All plugins previously packaged as 'Extra Plugins' are now contained |
| 62 |
> within the Claws Mail package." |
| 63 |
> |
| 64 |
> Thus, it's possible that the address_keeper plugin has been folded into |
| 65 |
> the core. In turn, that would explain why it must block the plugin as a |
| 66 |
> separate package. |
| 67 |
|
| 68 |
Good catch! Thanks, also to Neil. I unmerged this plugin, and claws |
| 69 |
updates just fine. |
| 70 |
|
| 71 |
Well. Sort of. Emerge also wanted to re-merge libreoffice, I have no idea |
| 72 |
why. The same happened yesterday when I upgraded portage. Whatever :) This |
| 73 |
time, I used --exclude app-office/libreoffice to avoid this. |
| 74 |
|
| 75 |
Alex |
Archives