Summary: | gnome-base/libgnomecanvas: unfulfillable dependencies with gtk+-2.14.4 or higher | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Malte Skoruppa <malte> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | liumengjiang |
Priority: | High | ||
Version: | 2008.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Malte Skoruppa
2009-03-02 13:24:49 UTC
Well the devs added a dummy version of gail as being shown in gail's ChangeLog: *gail-1000 (25 Sep 2008) 25 Sep 2008; Mart Raudsepp <leio@gentoo.org> +gail-1000.ebuild: New dummy version that is a migration helper, as gail is now part of gtk+ since gtk+-2.14 Mixing stable and unstable branches can lead to this kind of problems. I'm not sure if this bug is valid at all, but by looking at https://bugs.gentoo.org/192727#c6 I'd say this is a dupe. *** This bug has been marked as a duplicate of bug 192727 *** Hi, well, I didn't see that package - so if x11-libs/gtk+ is used in an unstable version on a system, one should make sure that gnome-base/gail is also used in the unstable version. I didn't have that, nor did I notice there was this dummy package, this is why I ran into that error. Using a dummy package named gail-1000 is of course a much cleaner and more elegant way to get rid of the problem, instead of updating all packages depending on gail thoughout the portage tree with a much more complex dependency specification. Not bad at all ;-) But no, this is a different problem than the bug you marked this one as a duplicate of. That other bug concerns a circular dependency between libgnomecanvas and gail, as I see it, which has nothing to do with this bug here, although admittedly the same packages are concerned. However you may well argue this bug is not valid, as it is solved by that dummy gail package... Cheers, Malte Reopening for marking as INVALID *** Bug 262626 has been marked as a duplicate of this bug. *** |