From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 66324139084 for ; Thu, 15 Dec 2016 16:32:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 640AAE0C0B; Thu, 15 Dec 2016 16:32:21 +0000 (UTC) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id DF429E0C01 for ; Thu, 15 Dec 2016 16:32:20 +0000 (UTC) Received: by mail-wm0-x244.google.com with SMTP id a20so7573429wme.2 for ; Thu, 15 Dec 2016 08:32:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:reply-to:subject:date:message-id:user-agent:in-reply-to :references:mime-version; bh=FThYXMrf1VIAoJggXV1WRXLJbIcGjD8+yE7z5vPq0pY=; b=dE0Po7ou2/9z41rZomLW1YDRi9nnZc0ty8r4ECkWbjGWTtXfKxeNiZ9AD/x4/P3Y5W vsjwOO5x81llgj+UvFnFCKmw91Kr3tOLI3J8zCRya1keaR7qWy17jKDW82ZSxgMJ4sei Ckr0uS2IKvTgnUo+ejIYGqA+36yf3dncUInoI5BP5DThiQc/ZgdQuoB/B83zriug0qa8 1VuPdG/HmEAUR76NvbH+YWoupGCXxZAbYy03d4/gVhNHkiN/XyoBwMIknWk+HRO6SGcg CY16Sy2tcDT9fm7o3nsTj9cTbAQhegVOiO+LUC7RuOMsD6ucGK7W5QGEhcVGFM9LHHZn 1xZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:reply-to:subject:date:message-id :user-agent:in-reply-to:references:mime-version; bh=FThYXMrf1VIAoJggXV1WRXLJbIcGjD8+yE7z5vPq0pY=; b=rWapjVf1EaqShxGfN1odfSK9wzDMftA0XC91CUP0HsavxJvzDu9V+6a0VegPayiLCp x3AF61cIQkB88ZTl/i7MNW8Ios4iumMtTnb/a9wOEF/7KnC2dDCAO8tDlDWSLH/XRSD2 SgBdVwcKtBCp4HgYIRJxUT27f74+q5+utR/8i4jwQR3qC6McEREL/Zwa/V+3xX704rlD FIn0HWX35PodGXfkvFRzIqAu3dn2DYoPT32azHP6hNzFpFv3MZibGzr+dyctT6VUgXjh blACxagsJroVLTSaGYbGBQbhvfflFS2pTkYgU8X3On0JjqTTJ0DqORvSmmCi6vp442T1 IhRQ== X-Gm-Message-State: AIkVDXLIPy6RIxDS6vQjw2mpNzeMnm01swcmGZ1dpbV+jUJIwZt+kWnUOiPBpp9o0nZziw== X-Received: by 10.28.232.85 with SMTP id f82mr2132106wmh.127.1481819539156; Thu, 15 Dec 2016 08:32:19 -0800 (PST) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by smtp.gmail.com with ESMTPSA id vr9sm2742278wjc.35.2016.12.15.08.32.18 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 15 Dec 2016 08:32:18 -0800 (PST) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Portage vs Qt Date: Thu, 15 Dec 2016 16:31:58 +0000 Message-ID: <2731991.4hz4QkTVRI@dell_xps> User-Agent: KMail/4.14.10 (Linux/4.4.26-gentoo; KDE/4.14.24; x86_64; ; ) In-Reply-To: <2621000.uqvyzQ2Htx@eve> References: <20161214050600.GC1795@ca.inter.net> <2621000.uqvyzQ2Htx@eve> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1498823.fWD5pR02BD"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-Archives-Salt: f56cea4f-7f4f-4eb4-a852-9f3d205e1990 X-Archives-Hash: fec657e0331a866281ed8186ceffc7db --nextPart1498823.fWD5pR02BD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" On Wednesday 14 Dec 2016 06:48:41 J. Roeleveld wrote: > On Wednesday, December 14, 2016 12:06:00 AM Philip Webb wrote: > > I just updated Qt5 to 5.6.2 & ran into a familiar Portage problem. > >=20 > > 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. > >=20 > > 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 p= kgs. > >=20 > > Yes, I did do 'backtrack=3D=3D30'. > >=20 > > Before I send in a bug, does anyone else have useful comments ? >=20 > I did exactly the same upgrade on 2 machines, along with an entire pl= asma > upgrade, and didn't encounter this issue. >=20 > For comparison, this is what I generally use: >=20 > # emerge -vauDN --with-bdeps=3Dy @world > # emerge -va --depclean >=20 > Do you only upgrade subsets? Or the full world? > I found that with libraries like qt, python and similar, only upgradi= ng > those makes it impossible for portage to properly handle the blockers= . >=20 > -- > Joost I came across a similar problem on 4 PCs. From memory the problem was=20= resolved when I manually unmerged dev-qt/qtcore and then updated world = with=20 backtrack=3D90. I did not have to run --with-bdeps=3Dy. =2D-=20 Regards, Mick --nextPart1498823.fWD5pR02BD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQEcBAABCAAGBQJYUsV/AAoJELAdA+zwE4YezeAIAMBA/MzFwWLZcdqcXqll5qvi ACi/6noe7qbGIUReKYtbeMI22kKx5uihlM7wICyDUkIlQnlCEJ1M/Z++b4sXO9Vi 72EVT8o5/7Q4Jit8prjDLQug7+typ6az4mvHSZe8XYAm9Fifmvr1dt8jaJt6D7AK Z+MmymMFAX3+yTW1Ea6E8X8JYtivakgfalsKAlR7mFjuXl2AnRuZGKPwXrDIAAL9 /dZ/rRUlr8JMxvdNtRFOD8/Zs4ipyBxQ/hLnhiCh0BYXqLRugBmi7OU3kAPMITim 3egG/8DiN5tB2lGB3EWrjARwvtrFKP7uNwtF/0S1RYcORU4/yV0R3F6MwH7ZNAE= =Ww1D -----END PGP SIGNATURE----- --nextPart1498823.fWD5pR02BD--