Am Wed, 14 Dec 2016 00:06:00 -0500
schrieb Philip Webb <purs...@ca.inter.net>:

> I just updated Qt5 to 5.6.2 & ran into a familiar Portage problem.
> 
> The emerge command responds with a list of "conflicts",
> all involving 5.6.1 vs 5.6.2 versions of the  c 15  pkgs.
> The only way to get around this is to unmerge the existing pkgs via
> '-C', then install the new versions.  That works, but it's brute
> force.
> 
> Portage sb able to resolve this kind of conflict for itself.
> If not, then at least it should advise users intelligently
> to do what I've just described.  It can happen with other sets of
> pkgs.
> 
> Yes, I did do 'backtrack==30'.
> 
> Before I send in a bug, does anyone else have useful comments ?

I constantly see the same conflict and haven't nailed it down exactly
right now. It seems to happen when one package requires a binary
compatibility to an older version of a depend but can also be built
against the newer version. Usually, emerge should trigger a rebuild
then. But this doesn't seem to work when both packages (the depend and
the depender) are updated at the same time. Portage then pulls in the
old and the new version of the same package at the same time, resulting
in a conflict.

Upgrading the depends with "-1a" first sometimes helps but usually I'll
also resolv it by unmerging the conflicting package first.

-- 
Regards,
Kai

Replies to list-only preferred.


Reply via email to