[Xcb] New libxcb and xcb-proto releases (code name: "Oh, shit")

Arnaud Fontaine arnau at debian.org
Mon Nov 18 03:37:00 PST 2013


Thanks for the list. Just updating the steps after merging some patches
and what we have been talking about lately.

Uli Schlachter <psychon at znc.in> writes:

> So here is my list of patches:
> xcb-proto
> - "[PATCH libxcb] Fix alignment issues in FD passing code"
> - "Add NEWS entries for release 1.9"
> libxcb-master:
> - "Add NEWS entries for releases 1.9.1 to 1.9.3"
> - bump XKB soname due to ABI break

- bump xinput soname due to ABI break

- bump sync soname due to ABI break

Because xcb_sync_{change,create}_alarm_sizeof were removed, see:

> - revert 9ae84ad187e2ba440c40f44b8eb21c82c2fdbf12 "fix deadlock with
>   xcb_take_socket/return_socket v3"
> - revert bc6a4f557ff4e497acdafdcebb006e5a7b4c5b11 "Build xcb-xkb by default"
>   (is this needed? xkb's current state confuses me. Someone please
>   tell me.)

Not sure about that, still waiting for Daniel or Ran output.

> - Depend on newest xcb-proto release
> Issues left (or at least "Things I collected from the 'Next Release?'-thread"):
> - http://lists.freedesktop.org/archives/xcb/2013-August/008541.html
>   "xkb: Unify events into single event"
> - https://bugs.freedesktop.org/show_bug.cgi?id=68387
>   "xinput2 XIQueryDevice reply not read correctly"
> - http://lists.freedesktop.org/archives/xcb/2013-October/008689.html
>   "every structure having a fixed size field after a variadic field/list is
>   broken!" (Does this have a Bugzilla entry that I didn't find yet? If not, we
>   should create one)
> - We are renaming things in xcb_ge_event_t (this time on purpose). How are
>   people supposed to deal with it so that they work both with old and new
>   libxcb? There doesn't seem to be a #define which could easily be used for
>   deciding if pad0 or extension is the right field to use.

Arnaud Fontaine

More information about the Xcb mailing list