Hi, In data domenica 6 ottobre 2013 02:16:46, Osamu Aoki ha scritto: > control: reassign 724226 libinput-pad-dev > control: retitle 724226 libinput-pad-dev: Should depend on > libgtk-3-dev (not libgtk2.0-dev)
I think this is not enough (and might be harmful), see below. > On Sat, Oct 05, 2013 at 03:03:19PM +0200, Pino Toscano wrote: > > the problem is due to input-pad 1.0.2-1 switching to gtk3 instead of > > > gtk2: > Yes, I switched input-pad to use gtk3. ... without taking into account what possible gtk version is used by users of libinput-pad. > > this happens as input-pad is built against gtk3, while > > ibus-input-pad is currently built against gtk2, and a clean buildd > > chroot has no gtk3 installed. > > I thought I can keep ibus-input-pad in gtk2 while input-pad as gtk3. > That is what I did. So there is the ibus-setup-input-pad binary (built as part of src:ibus-input-pad) which is directly linked to gtk2 (as specified by its build dependencies) and libinput-pad, which is linked to gtk3. This poses two major issues: 1) gtk2 and gtk3 are not loadable in the same process, meaning ibus-setup-input-pad won't ever run (crash due to symbols conflict) 2) the build CFLAGS include both gtk2 (direct dependency) and gtk3 (part of the libinput-pad CFLAGS), so there's a build clash So... > I think what is needed is: > * Change dependency of libinput-pad-dev to libgtk-3-dev ... this is indeed the wrong fix, if it is the only change you are planning to do right now. Again, > > This means there are two possible solutions > > a) switch also ibus-input-pad to gtk3 > > b) switch back input-pad to gtk2 (and reassign this bug to it) ... because both input-pad and ibus-input-pad must use the *same* gtk version, be it gtk2 or gtk3, to avoid this clash. -- Pino Toscano
signature.asc
Description: This is a digitally signed message part.