I have two version of gtk+ installed: 2.2.1 and 1.2.10. If I do an "emerge -Up world" portage wanna update version 1.2.10-r10 to 2.2.1. # emerge -Up world >>> --upgradeonly implies --update... adding --update to options. These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild UD] net-mail/bogofilter-0.11.2 [0.12.3] [ebuild UD] x11-wm/enlightenment-0.16.5-r4 [0.16.6] [ebuild U ] x11-libs/gtk+-1.2.10-r10 [2.2.1] [ebuild UD] net-www/mozilla-1.3-r2 [1.4b] But if I do an "emerge -Up gtk+" it doesn't show me the update. emerge -s gtk shows: * x11-libs/gtk+ Latest version available: 2.2.1 Latest version installed: 2.2.1 Size of downloaded files: 6,363 kB Homepage: http://www.gtk.org/ Description: Gimp ToolKit + So there must be a bug. Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: on emerge -Up world ist shouldn't show the update from 1.2.10 to 2.2.1 since both are installed.
no, it doesn't want to replace gtk2 with gtk1 -- they both co-exist very happily on your system, and portage knows the difference between 1 and 2. it's a bug only in the way portage displays things. if you do the upgrade, you will see your system is just fine.
Think there may be more of a problem than how things are displayed. When I do an emerge -p kde I see: [ebuild U] x11-libs/gtk+-1.2.10-r10 [2.2.1] Yet I've already installed that, shown when I do an emerge -p gtk+ and see: [ebuild R] x11-libs/gtk+-2.2.1 Now, I haven't run emerge kde yet to see if it needlessly reinstalls gtk+-2.2.1, but if it actually does as it "pretends," it will right? Isn't the same logic used?
*** This bug has been marked as a duplicate of 4698 ***
