On 21/08/17 22:15, Osamu Aoki wrote: > On Mon, Aug 21, 2017 at 08:28:14PM +0100, OmegaPhil wrote: > ... >> I'm building the libgtk-3-dev Debian source package with the usual >> 'dpkg-buildpackage -b --jobs=auto -i.*' (the bit at the end is to ignore >> changes so that I can trivially patch in my own stuff). The current >> situation happens without any changes. > > Oh, I overlooked and misunderstood your position. Did you check symbol > file situation and made proper library versioning. > > If you build your own libgtk-3-dev .... you must have used > wrong compilation option which caused to skip some wayland function > generation. This is your problem. Check your compile option. Run > ./configure by yourself. > > If ibus compile failes with libgtk-3-dev in unstable, I need to rebuild > ibus against updated libgtk-3-dev for unstable. Maybe I need to do > this. But if there is symbol change, library versioning scheme should > help prevent it if library is packaged properly. > > Anyway, then this isn't a bug on my package. > > Good luck with experimenting with compiler. I don't have time to help > your local experiment. > > Osamu
It shouldn't be possible for me to use the wrong compilation option - the configuration is defined in the Debian rules file. OK, if you think this is something local, I can't argue against that since I don't have enough experience. In terms of a library versioning issue, ibus-gtk3 is after libgtk-3-0 (>= 3.9.10) which is of course satisfied. For anyone else interested, you can test for the problem with: ==================================== apt-get source libgtk-3-dev cd <source dir> dpkg-buildpackage -b --jobs=auto ==================================== The build takes a long time but will eventually reach the testing stage, where the bug previously mentioned appears. In the meantime I'm building in a VM with ibus-gtk3 removed.
signature.asc
Description: OpenPGP digital signature