| 1 |
On 06/01/2014 19:58, »Q« wrote: |
| 2 |
> On Sun, 5 Jan 2014 15:57:10 +0000 |
| 3 |
> 张东亚 <fortitude.zhang@×××××.com> wrote: |
| 4 |
> |
| 5 |
>> Hi list, |
| 6 |
>> |
| 7 |
>> When I do a world upgrade, I have encountered the following slot |
| 8 |
>> conflict: |
| 9 |
>> |
| 10 |
>> |
| 11 |
>> media-libs/libpng:0 |
| 12 |
>> |
| 13 |
>> (media-libs/libpng-1.5.17-r1::gentoo, installed) pulled in by |
| 14 |
>> media-libs/libpng:0/0= required by |
| 15 |
>> (dev-python/wxpython-2.8.12.1-r1::gentoo, installed) |
| 16 |
>> >=media-libs/libpng-1.4:0/0= required by |
| 17 |
>> (net-libs/webkit-gtk-1.8.3-r201::gentoo, installed) |
| 18 |
>> media-libs/libpng:0/0= required by |
| 19 |
>> (app-text/poppler-0.22.5::gentoo, installed) |
| 20 |
>> media-libs/libpng:0/0= required by |
| 21 |
>> (media-libs/libwebp-0.3.1::gentoo, installed) |
| 22 |
>> media-libs/libpng:0/0= required by |
| 23 |
>> (net-print/cups-filters-1.0.36-r1::gentoo, installed) |
| 24 |
>> media-libs/libpng:0/0= required by |
| 25 |
>> (kde-base/kdelibs-4.11.4::gentoo, installed) |
| 26 |
>> |
| 27 |
>> (media-libs/libpng-1.6.8::gentoo, ebuild scheduled for merge) |
| 28 |
>> pulled in by (no parents that aren't satisfied by other packages in |
| 29 |
>> this slot) |
| 30 |
>> |
| 31 |
>> |
| 32 |
>> My question is, seems upgrade to libpng-1.6.8 will solve the |
| 33 |
>> conflict, why emerge cannot proceed this automatically? or there are |
| 34 |
>> some switches to controller this? |
| 35 |
>> |
| 36 |
>> Thanks a lot. |
| 37 |
> |
| 38 |
> I had exactly the same weirdness after 1.6.8 was stabilized. I waited |
| 39 |
> a few hours, re-synced the tree, and then updated without any warnings |
| 40 |
> about blocks; the old libpng was unmerged and 1.6.8 was merged |
| 41 |
> automagically as one would expect. I don't know what caused the problem |
| 42 |
> or what fixed it. |
| 43 |
|
| 44 |
|
| 45 |
Ah, that explains it. I last synced 3 days ago |
| 46 |
|
| 47 |
Obviously, updating libpng in the tree was a two stage process, with a |
| 48 |
longer than expected delay between them. Or maybe a bug the dev didn't |
| 49 |
anticipate showed up right away and needed fixing. You and fortitude |
| 50 |
both sync'ed in this middle period and got hit by the bug. |
| 51 |
|
| 52 |
It happens a lot actually :-) |
| 53 |
|
| 54 |
-- |
| 55 |
Alan McKinnon |
| 56 |
alan.mckinnon@×××××.com |
Archives