Bug#817242: pocketsphinx: FTBFS when built with dpkg-buildpackage -A (failed to create symbolic link)
Package: src:pocketsphinx
Version: 0.8+5prealpha-1
User: sanvila@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:
--------------------------------------------------------------------------------
[...]
debian/rules build-indep
dh build-indep --with autoreconf,python2
dh_testdir -i
dh_update_autotools_config -i
dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
[... snipped ...]
/bin/mkdir -p '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha/debian/tmp/usr/lib/python2.7/dist-packages/pocketsphinx'
/usr/bin/install -c -m 644 __init__.py '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha/debian/tmp/usr/lib/python2.7/dist-packages/pocketsphinx'
Byte-compiling python modules...
__init__.py
Byte-compiling python modules (optimized versions) ...
__init__.py
make[6]: Nothing to be done for 'install-data-am'.
make[6]: Leaving directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha/swig/python'
make[5]: Leaving directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha/swig/python'
make[4]: Leaving directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha/swig/python'
make[4]: Entering directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha/swig'
make[5]: Entering directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha/swig'
make[5]: Nothing to be done for 'install-exec-am'.
make[5]: Nothing to be done for 'install-data-am'.
make[5]: Leaving directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha/swig'
make[4]: Leaving directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha/swig'
make[3]: Leaving directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha/swig'
make[3]: Entering directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha'
make[4]: Entering directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha'
make[4]: Nothing to be done for 'install-exec-am'.
/bin/mkdir -p '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
/usr/bin/install -c -m 644 pocketsphinx.pc '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
make[4]: Leaving directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha'
make[3]: Leaving directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha'
make[2]: Leaving directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha'
for file in $(find debian/tmp/usr/lib/ -name "*.la"); do \
rm $file ; \
done
make[1]: Leaving directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha'
dh_install -i
debian/rules override_dh_installdocs
make[1]: Entering directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha'
dh_installdocs
ln -sf /usr/share/javascript/jquery/jquery.js debian/pocketsphinx/usr/share/doc/pocketsphinx/html/jquery.js
ln: failed to create symbolic link 'debian/pocketsphinx/usr/share/doc/pocketsphinx/html/jquery.js': No such file or directory
debian/rules:24: recipe for target 'override_dh_installdocs' failed
make[1]: *** [override_dh_installdocs] Error 1
make[1]: Leaving directory '/<<BUILDDIR>>/pocketsphinx-0.8+5prealpha'
debian/rules:7: 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. The common hints are:
* If the only architecture-independent packages are dummy transitional
ones and they were released with jessie, the easy fix is to drop them
now.
* When using "dh", it is allowed to use (independently)
optional targets override_dh_foo-arch and override_dh_foo-indep
(for several values of "foo").
Once that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, the package would be suitable to be uploaded in source-only
form if you wish.
Thanks.
Reply to: