Bug#976043: d/control: moving to libgdk-pixbuf-2.0-dev and what about dh-sequence-gnome

[Simon McVittie]

On Sat, 28 Nov 2020 at 20:09:41 +0100, Patrice Duroux wrote:
> I am using cowbuilder + pbuilder to build gtkmm3.0 from source and before
> facing #959602, I got the following:
> 
> $ pdebuild --pbuilder cowbuilder -- --distribution bullseye --basepath
> /var/cache/pbuilder/base-bullseye.cow
> I: using cowbuilder as pbuilder
> dpkg-checkbuilddeps: error: Unmet build dependencies: dh-sequence-gnome doxygen
> libgdk-pixbuf2.0-dev (>= 2.35.5) mm-common (>= 0.9.10) xvfb

Is your base image up to date?

gtkmm3.0 3.24.2-2, which I uploaded today, builds successfully in sbuild
using an unstable chroot.

I don't use cowbuilder myself; if that can't build gtkmm3.0 but sbuild
can, then that suggests that there's a problem with either cowbuilder's
build-dependency resolver or the base image you're using.

Note that packages intended for upload to unstable are meant to be built
in unstable, not testing.

> dh-sequence-gnome is a virtual package supplied by gnome-pkg-tools

That's correct. Build-dependency resolvers should be able to work out
that this means they need to install gnome-pkg-tools (sbuild does that
successfully).

> Finally in d/control, I just removed dh-sequence-gnome.

Please don't. This will break the mechanism that updates debian/control
from debian/control.in, and might break the package's build in other ways.

> But also, main point of this report, I also replaced libgdk-pixbuf2.0-dev by
> libgdk-pixbuf-2.0-dev
>
> The built was ok then.

Installing libgdk-pixbuf2.0-dev as a build-dependency should work fine in
an up-to-date chroot. For example, I tried building tumbler in sbuild. It
correctly installs the transitional libgdk-pixbuf2.0-dev, which pulls in
libgdk-pixbuf-2.0-dev and libgdk-pixbuf-xlib-2.0-dev.

For packages that don't need the deprecated Xlib integration it's better
to switch the build-dependency to libgdk-pixbuf-2.0-dev, as I did in
gtkmm3.0 3.24.2-2 before seeing this bug report, but not doing that
shouldn't break the build.

    smcv