Re: [gentoo-user] Re: Confusion about slot conflict

[Alan McKinnon <alan.mckinnon@gmail.com>]

On 06/01/2014 19:58, »Q« wrote:
> On Sun, 5 Jan 2014 15:57:10 +0000
> 张东亚 <fortitude.zhang@gmail.com> 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