Hi!

I'd like to ask if there are plans to update x11proto-core to version
7.0.13 before lenny release?

Upstream maintainers have added a new event GenericEvent which breaks
Tk toolkit because Tk uses hardcoded event numbers and adds its own
events (see [1]). Gentoo system is already affected (see [2]).

As far as I can see there's no fix which would retain binary compatibility yet.

Certainly affected packages are tk8.3, tk8.4, tk8.5, blt, tile. Also
perl-tk and ruby are likely to break after possible upgrade of
x11proto-core. (May be other packages which use Tk.)

So, if the upgrade of x11proto-core is planned then we have to find an
acceptable fix for Tk now. Otherwise we have some time to wait for a
solution from upstream.

[1] http://sourceforge.net/tracker/index.php?func=detail&aid=2010422&group_id=12997&a tid=112997
[2] http://bugs.gentoo.org/show_bug.cgi?id=225999
Cheers!
--
Sergei Golovan


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, Jul 11, 2008 at 14:07:02 +0400, Sergei Golovan wrote:

> Hi!
>
> I'd like to ask if there are plans to update x11proto-core to version
> 7.0.13 before lenny release?
>
No, x11proto-core in lenny will be 7.0.12.

Cheers,
Julien


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On 7/11/08, Julien Cristau <jcristau@debian.org> wrote:
> On Fri, Jul 11, 2008 at 14:07:02 +0400, Sergei Golovan wrote:
> > I'd like to ask if there are plans to update x11proto-core to version
> > 7.0.13 before lenny release?
>
> No, x11proto-core in lenny will be 7.0.12.

OK. Then there's no hurry in fixing Tk. Thanks!

--
Sergei Golovan


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

* Sergei Golovan:

> Certainly affected packages are tk8.3, tk8.4, tk8.5, blt, tile. Also
> perl-tk and ruby are likely to break after possible upgrade of
> x11proto-core. (May be other packages which use Tk.)

What about statically-linked, proprietary applications? Why hasn't this
happened in the past?

(I'm not saying that we should care much about proprietary apps, I'm
just trying to understand what's going on.)


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On 7/20/08, Florian Weimer <fw@deneb.enyo.de> wrote:
> * Sergei Golovan:
>
> > Certainly affected packages are tk8.3, tk8.4, tk8.5, blt, tile. Also
> > perl-tk and ruby are likely to break after possible upgrade of
> > x11proto-core. (May be other packages which use Tk.)
>
>
> What about statically-linked, proprietary applications? Why hasn't this
> happened in the past?

Tk adds its own X event numbers to a table of events. And puts it just
after the last existing event (the following is an excerpt from tk.h):

/*
*---------------------------------------------------------------------------
*
* Extensions to the X event set
*
*---------------------------------------------------------------------------
*/
#define VirtualEvent (LASTEvent)
#define ActivateNotify (LASTEvent + 1)
#define DeactivateNotify (LASTEvent + 2)
#define MouseWheelEvent (LASTEvent + 3)
#define TK_LASTEVENT (LASTEvent + 4)

#define MouseWheelMask (1L << 28)

#define ActivateMask (1L << 29)
#define VirtualEventMask (1L << 30)
#define TK_LASTEVENT (LASTEvent + 4)

It looks that until the last month there were exactly 35 events
(LASTEvent equals 35), so the Tk core library, all extensions linked
to it (which use event numbers directly) and all statically linked
propriatory binaries were binary compatible.

Now X people have added another event number (GenericEvent), which
means that in the former excerpt LASTEvent changes to 36. So, if two
extensions use the same tk.h but different x11proto-core versions
(7.0.12 and 7.0.13) they will not be binary compatible. Statically
linked proprietory binaries should be fine if they never receive
GenericEvent from X (I'm not an expert, so I realy don't know if its
possible to receive X event if an application doesn't know about it).

--
Sergei Golovan


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org