[Build-common-hackers] Bug#824623: glib2.0 FTBFS: dh_install: libglib2.0-tests missing files: usr/lib/glib2.0/installed-tests

Simon McVittie smcv at debian.org
Wed May 18 06:20:22 UTC 2016


Package: cdbs
Version: 0.4.135
Control: reassign 824623 cdbs
Control: affects 824623 src:glib2.0
Control: found 824623 0.4.133

On Wed, 18 May 2016 at 06:21:15 +0200, Helmut Grohne wrote:
> glib2.0 FTBFS again. A few days ago, cdbs was responsible (#824083) for
> that. Now I cannot tell, but I wouldn't rule that out either and
> therefore put Jonas into Cc. Either way, glib2.0 didn't change so the
> cause is to be found in some other package.
...
> | dh_install: Cannot find (any matches for) "usr/lib/glib2.0/installed-tests" (tried in "debian/install/deb" and "debian/tmp")
...
> Those are actually installed as ".../usr/lib/glib2/installed-tests".

The expectation is that they will be in ${libexecdir}/installed-tests, and
previously we had libexecdir=/usr/lib/${source_package}, i.e. glib2.0.

>From your build log:

    --libexecdir="\${prefix}/lib/glib2"

This is not as expected.

glib2.0 doesn't explicitly specify libexecdir, so this must have come from
cdbs. autotools-vars.mk.in says:

    DEB_CONFIGURE_LIBEXECDIR ?= "\$${prefix}/lib/$(DEB_SOURCE_PACKAGE)"

and

    --libexecdir=$(DEB_CONFIGURE_LIBEXECDIR) \

>From the log, cdbs was version 0.4.133:

    Get:59 http://proxy:9999/debian sid/main amd64 cdbs all 0.4.133 [79.4 kB]

It seems this is what was fixed in 0.4.135:

    -DEB_SOURCE_PACKAGE := $(shell grep -Pom1 '^Source:\s*\K\w*' debian/control)
    +DEB_SOURCE_PACKAGE := $(shell grep -Pom1 '^Source:\s*\K[^\s]*' debian/control)

as demonstrated by:

    $ echo "Source: glib2.0" | grep -Pom1 '^Source:\s*\K\w*'
    glib2
    $ echo "Source: glib2.0" | grep -Pom1 '^Source:\s*\K[^\s]*'
    glib2.0

(I'm not sure why cdbs doesn't use dpkg-parsechangelog here, like dpkg's
pkg-info.mk does.)

Regards,
    S



More information about the Build-common-hackers mailing list