Summary: | x11-misc/pcmanfm: Internal copy of xfce-base/exo is broken w/ GTK+-2.20 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marcus Becker <marcus.disi> |
Component: | [OLD] GNOME | Assignee: | LXDE team (DEFUNCT) <lxde+disabled> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | hwoarang |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://bugzilla.xfce.org/show_bug.cgi?id=6230 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 309237 |
Description
Marcus Becker
2010-06-19 09:33:27 UTC
Xfce team, this is the patch to include: http://git.xfce.org/xfce/exo/patch/?id=cd80ae7747aa87ab6d72f08386b0fd4bea7f05b3 (In reply to comment #1) > Xfce team, this is the patch to include: > http://git.xfce.org/xfce/exo/patch/?id=cd80ae7747aa87ab6d72f08386b0fd4bea7f05b3 > Thanks for your research, Pacho. pcmanfm is coming with internal copy of exo, it's not using the system version... so patching this is xfce-base/exo, won't help pcmanfm at all. (In reply to comment #3) > pcmanfm is coming with internal copy of exo, it's not using the system > version... so patching this is xfce-base/exo, won't help pcmanfm at all. > s/is/in/ Futhermore, this commit is included in the exo-0.3.107 we have in tree: commit c85fffcfa78dec9ae12251b9d2974927745ba7ce Author: Nick Schermer <nick@xfce.org> Date: Tue May 11 20:57:11 2010 +0200 Make the treeview work again with gtk 2.20 (bug #6230). not a xfce bug Other distros (fedora and debian, for example) seem to have bumped to the re-written 0.9.x version to go with GTK 2.20.x . While a patch might be possible, it probably is not the best long-term solution. All of the information so far suggest that 0.5.x really is dead and getting no attention. Any chance for this version to be un-masked and eventually worked in to stable? (In reply to comment #6) > Other distros (fedora and debian, for example) seem to have bumped to the > re-written 0.9.x version to go with GTK 2.20.x . While a patch might be > possible, it probably is not the best long-term solution. All of the > information so far suggest that 0.5.x really is dead and getting no attention. > > Any chance for this version to be un-masked and eventually worked in to stable? > I plan to unmask 0.9.7-r1 soonish 0.9.7-r1 unmasked We wont bother fixing 0.5.X |