From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C7558138247 for ; Mon, 6 Jan 2014 19:35:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 80B2FE0C5D; Mon, 6 Jan 2014 19:35:49 +0000 (UTC) Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 565A0E0AE8 for ; Mon, 6 Jan 2014 19:35:48 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id hm19so3255740wib.7 for ; Mon, 06 Jan 2014 11:35:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=kdznFIPTCqw/ja0jq9koDuxqSTXEH16Rzh382Ebt7fY=; b=epWbspsnl07NbTES0dWVbvVRjk9KtC2BtnYzpDIEwR8NTDimOzylmYd4TqfzJRgn4o nhMBGc581YiB4gFS1TEnnZPPShUjJTdB2WhoRGr7CjjQCazV2aVa/Q4vUm4MuhMMe0u6 tNkyez+98R8lt0z9SHdzsPoJK2trJdpQEjzDG2YK3iU/IIdGVlkEbjJQP7BhA6NiF76k /G0xdpAtNuSL16q7wH/Er2tv0tH/oEgRFScKCSte/toQSDa+0Mq4q0p4rob7ox8hlatT 6WtGqBl2zYdLmXuLM7bblKO3RNtuenb5OWTf2rRZrFe0zhPuiGjuRs5hqEeVw3qLVEus EDbw== X-Received: by 10.194.185.205 with SMTP id fe13mr41989165wjc.23.1389036947139; Mon, 06 Jan 2014 11:35:47 -0800 (PST) Received: from [172.20.0.41] (196-210-126-67.dynamic.isadsl.co.za. [196.210.126.67]) by mx.google.com with ESMTPSA id hv3sm19467639wib.5.2014.01.06.11.35.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 06 Jan 2014 11:35:46 -0800 (PST) Message-ID: <52CB058D.2040301@gmail.com> Date: Mon, 06 Jan 2014 21:35:41 +0200 From: Alan McKinnon User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Confusion about slot conflict References: <20140106115846.09d61679@fuchsia> In-Reply-To: <20140106115846.09d61679@fuchsia> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 42fa94e7-a6b0-44e7-9e06-5714ca604b51 X-Archives-Hash: 8a59d57f6b8f3950cfab34e3dd74aee8 On 06/01/2014 19:58, »Q« wrote: > On Sun, 5 Jan 2014 15:57:10 +0000 > 张东亚 wrote: > >> Hi list, >> >> When I do a world upgrade, I have encountered the following slot >> conflict: >> >> >> media-libs/libpng:0 >> >> (media-libs/libpng-1.5.17-r1::gentoo, installed) pulled in by >> media-libs/libpng:0/0= required by >> (dev-python/wxpython-2.8.12.1-r1::gentoo, installed) >> >=media-libs/libpng-1.4:0/0= required by >> (net-libs/webkit-gtk-1.8.3-r201::gentoo, installed) >> media-libs/libpng:0/0= required by >> (app-text/poppler-0.22.5::gentoo, installed) >> media-libs/libpng:0/0= required by >> (media-libs/libwebp-0.3.1::gentoo, installed) >> media-libs/libpng:0/0= required by >> (net-print/cups-filters-1.0.36-r1::gentoo, installed) >> media-libs/libpng:0/0= required by >> (kde-base/kdelibs-4.11.4::gentoo, installed) >> >> (media-libs/libpng-1.6.8::gentoo, ebuild scheduled for merge) >> pulled in by (no parents that aren't satisfied by other packages in >> this slot) >> >> >> My question is, seems upgrade to libpng-1.6.8 will solve the >> conflict, why emerge cannot proceed this automatically? or there are >> some switches to controller this? >> >> Thanks a lot. > > I had exactly the same weirdness after 1.6.8 was stabilized. I waited > a few hours, re-synced the tree, and then updated without any warnings > about blocks; the old libpng was unmerged and 1.6.8 was merged > automagically as one would expect. I don't know what caused the problem > or what fixed it. Ah, that explains it. I last synced 3 days ago Obviously, updating libpng in the tree was a two stage process, with a longer than expected delay between them. Or maybe a bug the dev didn't anticipate showed up right away and needed fixing. You and fortitude both sync'ed in this middle period and got hit by the bug. It happens a lot actually :-) -- Alan McKinnon alan.mckinnon@gmail.com