Summary: | libcroco: 2 version installed (slotted), but only one needed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | VERIFIED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Toralf Förster
2004-12-03 12:11:03 UTC
librsvg-2.8 needs libcroco-0.6 or greather while any version of librsvg below 2.8 needs the older version of libcroco. Your grepping of the librsvg ebuilds shows that, what is the bug here? Although that doesn't really matter here, as librsvg isn't slottable - so it can only depend on one version of libcroco at any time. But this isn't a bug, say you had application-x that DEPEND'd upon =dev-libs/libcroco-0.5*, but you also wanted to have librsvg-2.8.1 installed, which DEPEND'd on >=dev-libs/libcroco-0.6*. not a bug. The only ebuild which needs libcroco is librsvg. This is a dependency of gnome which I emerged some weeks ago. A 'emerge -uD world' has updated gnome, including an implicit update of librsvg: Sat Aug 14 14:55:39 2004 >>> emerge (71 of 131) gnome-base/librsvg-2.6.5 to / Sat Aug 14 16:31:48 2004 >>> emerge (71 of 131) gnome-base/librsvg-2.6.5 to / Sat Aug 14 16:32:31 2004 ::: completed emerge (71 of 131) gnome-base/librsvg-2.6.5 to / Thu Nov 11 11:19:54 2004 >>> emerge (10 of 39) gnome-base/librsvg-2.8.1 to / Thu Nov 11 11:42:00 2004 >>> emerge (10 of 39) gnome-base/librsvg-2.8.1 to / Thu Nov 11 11:43:48 2004 ::: completed emerge (10 of 39) gnome-base/librsvg-2.8.1 to / The former version of librsvg needed =libcroco-0.5, the actual needs >=libcroco-0.6. MThe problem is that portage did not remove the old version of libcroco while updating world. portage is not supposed to do that at this time, those are known deficiencies (well depclean is supposed to handle it, but it is not safe to use). Now once again, this isn't harmful, it is slotted correctly, if it bothers you, just remove it. There is nothing to see here, move along. 3 devs wasted time saying 3 times the same thing, enough for this report. |