Summary: | Dia links with the wrong version of the slotted pango library | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Per Cederberg <per> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED CANTFIX | ||
Severity: | major | ||
Priority: | High | ||
Version: | 1.4_rc2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Per Cederberg
2003-10-08 03:31:47 UTC
I've just verified that this is indeed the cause of my font problem in Dia. It can be demonstrated by testing Dia with the normal Pango installled, and then doing: emerge =pango-1.2.3 After that, Dia displays fonts just as it was supposed to. On more careful consideration, looks like the Pango library isn't slotted at all. But how come that I got both version 1.2.3 and 1.2.5 installed after updating to Gnome 2.4. Indeed, if I now do "emerge -upv --deep dia gnome" it suggests updating Pango to 1.2.5, without showing the blocker that Dia should cause with Pango >= 1.2.4... Is this really a Portage or Pango bug? The ebuilds did get reslotted. This shouldn't be a problem, only the pango problem with fonts turned up. Just remove the other pango directly or alltogether first if you have problems, but you already did that so it shouldnt be a problem anymore. The problem you describe is not portage but probably the suggested order of your emerge, the gnome part doesn't know about dia, dia is fine with the pango as it is and only after that gnome updates it to .5 . Not quite sure I understood that answer completely. I now have this situation: * Gnome 2.4 requires Pango 1.2.5 * Dia 0.91 requires Pango < 1.2.4 or no fonts show at all So, isn't this a bug? At least Pango 1.2.5 should be considered unstable, or a similar solution. Dia 0.92 will be fixed in this respect. Also, have a look at bug #30663 which is another problem that is also caused by Pango 1.2.5. i dont see it as one, afaik the problem is the dia usage of pango, not pango itsself. Same may be true for gdm, although i don't see that behaviour. About the deps i can't do much, they are correct in both cases : the gnome meta package just follows the release verions and i have little reason to believe pango is the problem (see up). That these two things conflict is unfortunate, but the number of gnome meta users is far greater than the number of dia users, so the last group has a bit of bad luck in this. But we could probably up the dia versions soon to one of the prereleases, although i'm not a big fan of these practices ;) Or someone could maybe extract the relevant pango patching for dia from CVS to use adapt to 0.91 Ok, I understand the reasoning. It is just so hard to be part of a minority... ;-) Maybe I also misread the Gnome Dia bug a bit. It seemed like the error was in Pango, but reading carefully between the lines it is possible that the problem was actually in Dia. (Oh, we developers, never admitting a bug to be ours...) http://bugzilla.gnome.org/show_bug.cgi?id=123430 Anyway, I'll see if I can make contact with the Dia developers about this. I'll get annoying again if I find a smoother solution. well, dia-0.92_pre4 is now in portage. that should solve the pango dilema for the moment. |