Your message dated Wed, 18 May 2016 16:17:42 +0200
with message-id <[email protected]>
and subject line Re: [Build-common-hackers] 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 [email protected]
immediately.)
--
824623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824623
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: glib2.0
Version: 2.48.1-1
Severity: serious
User: [email protected]
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 ---
Version: 0.4.135
Quoting Simon McVittie (2016-05-18 08:20:22)
> 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.
[...]
> 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 agree, and it seems Simon intended to close the bug but the -done
suffix in recipient address apperently was applied before reassiging
which then lost it again. Now closing as solved.
> (I'm not sure why cdbs doesn't use dpkg-parsechangelog here, like
> dpkg's pkg-info.mk does.)
To ease backporting.
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
--- End Message ---
