Summary: | 2 versions of gtk+ installed but only one recognized. | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Martin Zwickel <martin.zwickel> |
Component: | Unclassified | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Zwickel
2003-06-18 01:30:02 UTC
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? |