[Debichem-devel] Bug#806049: indigo: FTBFS when built with dpkg-buildpackage -A (No such file or directory)
Santiago Vila
sanvila at debian.org
Tue Nov 24 15:26:32 UTC 2015
Package: src:indigo
Version: 1.1.12-1
User: sanvila at debian.org
Usertags: binary-indep
Severity: important
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:
--------------------------------------------------------------------------------
[...]
fakeroot debian/rules binary-indep
dh binary-indep --with autotools_dev,javahelper,python2 --parallel
dh_testroot -i -O--parallel
dh_prep -i -O--parallel
debian/rules override_dh_auto_install
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_installdirs
mkdir -p debian/python-indigo/usr/lib/`pyversions -d`/dist-packages
install /<<PKGBUILDDIR>>/api/python/indigo.py /<<PKGBUILDDIR>>/api/plugins/renderer/python/*.py \
debian/python-indigo/usr/lib/`pyversions -d`/dist-packages
install /<<PKGBUILDDIR>>/utils/chemdiff/chemdiff.sh \
debian/indigo-utils/usr/bin/chemdiff
install: cannot create regular file 'debian/indigo-utils/usr/bin/chemdiff': No such file or directory
debian/rules:37: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules:15: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit status 2
--------------------------------------------------------------------------------
Sorry not to have a fix, as I am reporting many bugs similar to
this one, but I can give some general hints:
* If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now.
* If not, debian/rules should be modified so that the binary-indep
target works in all cases, even when binary-arch is not used (this is
what the "Architecture: all" autobuilder does). For that:
* If you are using debhelper, you might want to use options -a and -i
for dh_* commands so that they do not act on packages they do not
have to act.
* Also, if you are using dh, the (independently) optional targets
override_dh_foo-arch and override_dh_foo-indep (for several values
of "foo") may be useful to write a debian/rules which behaves exactly
as desired.
After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B"
work properly, this package will be suitable to be uploaded in
source-only form if you wish (you might want to try it).
Thanks.
More information about the Debichem-devel
mailing list