emerge -aNuD @world @system
[ebuild U ] media-libs/libpng-1.6.1 [1.5.15] USE="apng (-neon) -static-libs"
[ebuild NS ] media-libs/libpng-1.5.15-r15 [1.2.50, 1.5.15] USE="apng (-neon)"
[blocks B ] =media-libs/libpng-1.5*:0 ("=media-libs/libpng-1.5*:0" is blocking media-libs/libpng-1.5.15-r15)
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
(media-libs/libpng-1.5.15::gentoo, installed) pulled in by
media-libs/libpng:0/0= required by (x11-misc/slim-1.3.5-r2::gentoo, installed)
(media-libs/libpng-1.6.1::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)
Steps to Reproduce:
1. install slim
2. try to update libpng
portage doesn't like it and refuse to proceed, I have to run this command in order to get my updates:
emerge -aNuD --exclude media-libs/libpng @world @system
should accept to update libpng-1.5.15 to libpng-1.5.15-r15
Most probably caused by RDEPEND in slim-1.3.5-r2.ebuild :
consolekit? ( sys-auth/consolekit
pam? ( virtual/pam )"
install libpng-1.6 with "--nodeps" first, then the blocker will go away
seems like portage can't handle this situation, although there is no logical reason for the blocker
This is the same issue that was reported in bug 465356, comment #15. It's fixed in 220.127.116.11 and 2.2.0_alpha172 by this commit:
*** Bug 465356 has been marked as a duplicate of this bug. ***
(In reply to comment #1)
> install libpng-1.6 with "--nodeps" first, then the blocker will go away
> seems like portage can't handle this situation, although there is no logical
> reason for the blocker
Please don't use --nodeps. Just use `emerge -1 portage` to update portage to at least 18.104.22.168 or 2.2.0_alpha172, and it will solve the blockers automatically.
I confirm portage-22.214.171.124 solves this issue - thank you!