|Summary:||upgrade of media-libs/libpng-1.5:0 to libpng-1.6:0 blocked by libpng-1.5:1.5 being pulled in as well|
|Product:||Gentoo Linux||Reporter:||Cédric Jeanneret <contact>|
|Component:||Current packages||Assignee:||Portage team <dev-portage>|
|Package list:||Runtime testing required:||---|
|Bug Depends on:|
|Bug Blocks:||300071, 462382|
Description Cédric Jeanneret 2013-04-12 08:21:13 UTC
Hello, emerge -aNuD @world @system ----8<---- [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)" ----8<---- [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:0 (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) Reproducible: Always Steps to Reproduce: 1. install slim 2. try to update libpng Actual Results: 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 Expected Results: 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 : RDEPEND="x11-libs/libXmu x11-libs/libX11 x11-libs/libXpm x11-libs/libXft ----> media-libs/libpng:0= virtual/jpeg x11-apps/sessreg consolekit? ( sys-auth/consolekit sys-apps/dbus ) pam? ( virtual/pam )"
Comment 1 Julian Ospald 2013-04-12 14:31:27 UTC
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
Comment 2 Zac Medico 2013-04-12 14:37:25 UTC
This is the same issue that was reported in bug 465356, comment #15. It's fixed in 126.96.36.199 and 2.2.0_alpha172 by this commit: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=62dbcaa4d873784f1082c184668fcdc34392925b
Comment 3 Zac Medico 2013-04-12 14:38:51 UTC
*** Bug 465356 has been marked as a duplicate of this bug. ***
Comment 4 Zac Medico 2013-04-12 14:47:01 UTC
(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 188.8.131.52 or 2.2.0_alpha172, and it will solve the blockers automatically.
Comment 5 Cédric Jeanneret 2013-04-15 06:04:28 UTC
I confirm portage-184.108.40.206 solves this issue - thank you!