Your message dated Wed, 18 May 2016 07:20:22 +0100 with message-id <20160518062022.ga12...@perpetual.pseudorandom.co.uk> and subject line Re: Bug#824623: glib2.0 FTBFS: dh_install: libglib2.0-tests missing files: usr/lib/glib2.0/installed-tests has caused the Debian Bug report #824623, regarding glib2.0 FTBFS: dh_install: libglib2.0-tests missing files: usr/lib/glib2.0/installed-tests to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 824623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: glib2.0 Version: 2.48.1-1 Severity: serious User: helm...@debian.org Usertags: rebootstrap Hi, 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. The earliest occurrence of this issue (in a cross build setting) was observed at 2016-05-17 23:10 UTC. I am attaching a native build log for amd64. The relevant excerpt is: | dh_install -plibglib2.0-tests --sourcedir=debian/install/deb -X.la | dh_install: Cannot find (any matches for) "usr/lib/glib2.0/installed-tests" (tried in "debian/install/deb" and "debian/tmp") | dh_install: libglib2.0-tests missing files: usr/lib/glib2.0/installed-tests | dh_install: missing files, aborting | /usr/share/cdbs/1/rules/debhelper.mk:240: recipe for target 'binary-install/libglib2.0-tests' failed | make: *** [binary-install/libglib2.0-tests] Error 255 | dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2 Those are actually installed as ".../usr/lib/glib2/installed-tests". Hope this helps Helmut
glib2.0_2.48.1-1_amd64-20160518-0557.build.xz
Description: application/xz
--- End Message ---
--- Begin Message ---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
--- End Message ---
