Control: reassign -1 devscripts [ Leaving context for the reassignment. ]
Hi! On Sat, 2018-03-10 at 13:01:46 +0100, jean-christophe manciot wrote: > Package: dpkg > Version: 1.19.0.5 > binary is supposed to be an alias for any,all as described by the > dpkg-buildpackage documentation > <https://manpages.debian.org/unstable/dpkg-dev/dpkg-buildpackage.1.en.html>. > It is not completely the case. > For instance: > 1) *Building libixion 0.13.0-2 with --build=any,all*: > debuild -i -I --no-sign *--build=any,all* -j1 -m'Jean-Christophe Manciot < > manciot.jeanchristo...@gmail.com> > > leads to an issue with a missing .changes file which is a fatal error for > debuild: > ... > dpkg-deb: building package 'libixion-dev' in > '../libixion-dev_0.13.0-2_amd64.deb'. > dpkg-deb: building package 'libixion-0.13-0' in > '../libixion-0.13-0_0.13.0-2_amd64.deb'. > dpkg-deb: building package 'libixion-0.13-0-dbgsym' in > '../libixion-0.13-0-dbgsym_0.13.0-2_amd64.deb'. > dpkg-deb: building package 'python3-ixion' in > '../python3-ixion_0.13.0-2_amd64.deb'. > dpkg-deb: building package 'python3-ixion-dbgsym' in > '../python3-ixion-dbgsym_0.13.0-2_amd64.deb'. > dpkg-deb: building package 'libixion-doc' in > '../libixion-doc_0.13.0-2_all.deb'. > dpkg-genbuildinfo --build=binary > dpkg-genchanges --build=binary -mJean-Christophe Manciot < > manciot.jeanchristo...@gmail.com> >../libixion_0.13.0-2_amd64.changes > dpkg-genchanges: info: binary-only upload (no source code included) > dpkg-source -i -I --after-build libixion-0.13.0-2 > dpkg-buildpackage: info: binary-only upload (no source included) > debuild: fatal error at line 1039: > can't open libixion_0.13.0-2_all.changes for reading: No such file or > directory As can be seen here, the error comes from debuild. Reassigning. > 2) *Building the exact same sources libixion 0.13.0-2 with --build=binary*: > debuild -i -I --no-sign *--build=binary* -j1 -m'Jean-Christophe Manciot < > manciot.jeanchristo...@gmail.com> > > leads to a correct build: > ... > dpkg-deb: building package 'libixion-dev' in > '../libixion-dev_0.13.0-2_amd64.deb'. > dpkg-deb: building package 'libixion-0.13-0' in > '../libixion-0.13-0_0.13.0-2_amd64.deb'. > dpkg-deb: building package 'libixion-0.13-0-dbgsym' in > '../libixion-0.13-0-dbgsym_0.13.0-2_amd64.deb'. > dpkg-deb: building package 'python3-ixion' in > '../python3-ixion_0.13.0-2_amd64.deb'. > dpkg-deb: building package 'python3-ixion-dbgsym' in > '../python3-ixion-dbgsym_0.13.0-2_amd64.deb'. > dpkg-deb: building package 'libixion-doc' in > '../libixion-doc_0.13.0-2_all.deb'. > dpkg-genbuildinfo --build=binary > dpkg-genchanges --build=binary -mJean-Christophe Manciot < > manciot.jeanchristo...@gmail.com> >../libixion_0.13.0-2_amd64.changes > dpkg-genchanges: info: binary-only upload (no source code included) > dpkg-source -i -I --after-build libixion-0.13.0-2 > dpkg-buildpackage: info: binary-only upload (no source included) > Now running lintian libixion_0.13.0-2_amd64.changes ... > > This strange behaviour be applied to any other source package. > The following full build logs are attached: > 1) *-**-build=any,all: libixion_0.13.0-2_all.build* > 2) *--build=binary: *libixion_0.13.0-2_amd64.build Thanks, Guillem
