| Summary: | libgnomecanvas 2.10.2 ebuild error due to missing dependency during config | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jacobo Cabaleiro <obmun.h> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED INVALID | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Jacobo Cabaleiro
2005-11-07 13:53:25 UTC
I've left the hardware option in AMD64 cause I haven't been able to reproduce this behaviour in other architecture than an 64 bits Gentoo system, but it would be surprising if it'd be specific of this arch. Another dependencies problem appeared in the dual Xeon system later after solving the libgnomecanvas problem with an individual emerge of the package. Also the Pentium 4 system (Titan) had calculated the dependencies incorrectly, as another problem appeared with pango / gtk / glib Portage seems to be becoming crazy when I use the --deep --newuse and --update flags!! (even the last version). Am I doing something wrong??? I've seen this to many times using the mix of --update --deep and --newuse while installing gnome. If this was a bug it should be widly known. Let's keep this close until I can find out more why Portage is failing. If it's a bug it's not a problem of Gnome components at all, so this should be asigned to Gnome component. I'm setting my own bug to invalid. |