Bug#334534: Patch from bug 307724 breaks Eclipse
vektor at dumbterm.net
Fri Dec 16 22:59:05 UTC 2005
Loic Minier (lool at dooz.org):
> On Fri, Dec 16, 2005, Douglas Pollock wrote:
> > I would appreciate it if you could re-open this bug. Eclipse
> > continues to get bugs filed about this issue (e.g.,
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=119622). It means
> > that one of the first questions we must ask when debugging any focus
> > or key binding issue is: "Are you using Debian?" We're forced into
> > doing a lot of finger-pointing at Debian, which makes me
> > uncomfortable. This is also a drain on our resources -- triaging
> > bugs and replying to newsgroups.
> Well, there's nothing new, and we agreed there was no way to revert
> this (see the bug log and check with Billy Biggs for details). The
> short story is that we included a *fix*, which does help some
> application, and Eclipse maps the upstream version number of Gtk to a
> version which has not the fix and takes counter-measures, and this
> clashes. Reverting the fix is not only very difficult in a dist
> frozen like sarge is and for a core lib such as gtk, but would also
> break other apps (which don't have such dynamic workarounds).
I talked about this again with seb128 at UBZ. I really think the
right solution is for Debian to revert the change. It's a really
low-level X thing, and there is no good way for us to detect that it is
fixed. Changing the Eclipse code in our stable release, especially now
that it is so widely tested and used, is really hard.
I can appreciate that the same is true for Debian. However, in the
Debian case, there are also lots of other distributions which are
shipping unpatched versions (or, at leat differently patched versions)
of GTK+. Just in terms of re-introducing bugs - clearly the safer fix
is to revert a Debian-specific patch applied to GTK+, rather than patch
Eclipse for all distributions.
I urge you again to reconsider.
More information about the Pkg-gnome-maintainers