Trying to update some older boxes for the sec vuln (that's not in a GLSA yet), but still avoid the 1.4 series, and I noticed that the SLOT on 1.2 series has changed from "1.2" to "0", but there was NO slotmove entry added to the profiles/updates. This might explain a LOT of the complaints of users about blockers. # emerge -pv libpng These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild NS ] media-libs/libpng-1.2.43-r2 [1.2.37] 527 kB [blocks B ] <media-libs/libpng-1.2.43-r2 ("<media-libs/libpng-1.2.43-r2" is blocking media-libs/libpng-1.2.43-r2) [blocks B ] media-libs/libpng:1.2 ("media-libs/libpng:1.2" is blocking media-libs/libpng-1.2.43-r2) Total: 1 package (1 in new slot), Size of downloads: 527 kB Conflict: 2 blocks (2 unsatisfied) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. ('installed', '/', 'media-libs/libpng-1.2.37', 'nomerge') pulled in by media-libs/libpng:1.2 required by world ('ebuild', '/', 'media-libs/libpng-1.2.43-r2', 'merge') pulled in by libpng For more information about Blocked Packages, please refer to the following section of the Gentoo Linux x86 Handbook (architecture is irrelevant): http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked
This line added to the updates fixes the problem perfectly: slotmove <=media-libs/libpng-1.2.43 1.2 0 # emerge -pv libpng These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] media-libs/libpng-1.2.43-r2 [1.2.37] 527 kB Total: 1 package (1 upgrade), Size of downloads: 527 kB
Created attachment 235029 [details, diff] preserve libs logic for libpng robbat, it can't hurt, so fine by me. i'm taking this opportunity to get this reviewed: - add preserved-libs logic to libpng ebuild (in order to get 1.4 stabilized) - clean up pacho added new emul- libraries for amd64 yesterday, built against libpng 1.4, so timeframe for this would be ~2-3 weeks together with new emul- packages. mike, any thoughts?
why is that || die being removed when the others are still there?
(In reply to comment #3) > why is that || die being removed when the others are still there? > because it's clear the file is there because it's in portage tree. but i have no preference whatsoever, so it can stay...