I've come across an interesting behavior in the Portage dependency resolution. Currently, whenever I do # emerge --update --deep world Portage either upgrades me to media-libs/libpng-1.2.8-r1 or downgrades me to media-libs/libpng-1.2.12, depending on which is installed. What I mean is that if I have 1.2.8-r1 installed, I get: # emerge -pv --update --deep world These are the packages that would be merged, in order: Calculating world dependencies... done! [ebuild U ] media-libs/libpng-1.2.12 [1.2.8-r1] USE="doc" 0 kB ... but if I have 1.2.12 installed, I get: # emerge -pv --update --deep world These are the packages that would be merged, in order: Calculating world dependencies... done! [ebuild UD] media-libs/libpng-1.2.8-r1 [1.2.12] USE="doc" 0 kB The expected behavior would, of course, be to pick one and stick with it. I think this may have something to do with a DEPEND in my currently installed net-print/cups-1.1.23-r7, which specifies "<media-libs/libpng-1.2.10". Possibly relevant emerge --info: Gentoo Base System version 1.6.15 Portage 2.1-r1 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r4, 2.6.14-gentoo-r5 i686) ================================================================= System uname: 2.6.14-gentoo-r5 i686 AMD Athlon(tm) processor dev-lang/python: 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-tbird -O3 -pipe" CHOST="i686-pc-linux-gnu" CXXFLAGS="-march=athlon-tbird -O3 -pipe" FEATURES="autoconfig distlocks metadata-transfer parallel-fetch sandbox sfperms strict test" MAKEOPTS="-j2 -w" USE="x86 3dnow X aalib acl alsa bash-completion berkdb bzip2 cjk crypt dga directfb doc esd fbcon flac gdbm gif gnome gpm gtk gtk2 ipv6 java jpeg ldap mad mbox mmx mpeg mysql ncurses nls offensive ogg oggvorbis opengl oss pam perl png python readline sdl skey slang ssl svga tcltk tcpd tetex tiff truetype unicode xv zlib elibc_glibc input_devices_evdev input_devices_jamstudio input_devices_keyboard input_devices_mouse kernel_linux userland_GNU video_cards_fbdev video_cards_r128 video_cards_vesa" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS
*** This bug has been marked as a duplicate of 138736 ***
Are you sure about that? I could, of course, be wrong, but this seems to be a bug in Portage's dependency resolution, not in the libpng package itself.
same problem for me
