Your message dated Thu, 16 Oct 2014 19:34:38 +0000
with message-id <e1xeqoo-0008oa...@franck.debian.org>
and subject line Bug#761760: fixed in jbigkit 2.1-3.1
has caused the Debian Bug report #761760,
regarding jbigkit: libtool split: package needs a b-d on libtool-bin (or avoid
using the libtool binary)
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.)
--
761760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jbigkit
Version: 2.1-3
Severity: wishlist
User: debian-cr...@lists.debian.org
Usertags: libtool-split
As part of the effort to cross-build the archive, the libtool package
needs a split into an architecture independent part and an
architecture dpendent part (the latter only consisting of the libtool
binary). The split is already done for jessie/sid, but to enable the
cross buildability, the dependency in libtool on libtool-bin needs to
be removed, and libtool-bin needs to depend on libtool instead.
The vast majority of packages using libtool via automake don't need
the libtool binary, and thus no changes in the build dependencies, however
about 60 source packages are using libtool directly, and need changes.
- some packages just check for the libtool binary, and then don't
use it for the build (but are using libtoolize instead). Such
usages are seen in a script called buildcheck.sh, and sometimes
in autogen.sh scripts. The solution for these cases is to patch
these scripts to check for libtoolize instead of libtool, and
not to introduce the new build dependency.
- other packages just need the additional build dependency on
libtool-bin.
To test your packages with the libtool-bin package removed, please use
the binaries found at
deb https://people.debian.org/~doko/tmp/20140820 ./
It is not clear, if all of these changes can be done in time for
the jessie release, but it would be nice to have to be able to
cross-build more packages in jessie.
For questions and help please email the debian-cross ML.
For additional pointers please see
https://lists.debian.org/debian-devel-announce/2014/08/msg00013.html
and some discussion in the orignal issue filed for libtool (#682045).
The full build log can be found at:
http://people.debian.org/~doko/logs/20140912/failed-libtool/jbigkit_2.1-3_unstable_jdk-libtool.log
The last lines of the build log are at the end of this report.
[...]
dh_testdir
dh_auto_clean
make[1]: Entering directory '/«PKGBUILDDIR»'
rm -f *~ core
cd libjbig && make clean
make[2]: Entering directory '/«PKGBUILDDIR»/libjbig'
rm -rf .libs
rm -f *.gcda *.gcno *.gcov *.a *.la *.o *.lo *~ core gmon.out dbg_d\=??.pbm
t82test.pbm
rm -f t82test.pbm
rm -f tstcodec tstcodec85
make[2]: Leaving directory '/«PKGBUILDDIR»/libjbig'
cd pbmtools && make clean
make[2]: Entering directory '/«PKGBUILDDIR»/pbmtools'
rm -f *.o *~ core pbmtojbg jbgtopbm pbmtojbg85 jbgtopbm85
ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded
(cannot open shared object file): ignored.
rm -f test-*.jbg test-*.pbm test-*.pgm test-*.jbg85 test-*.pbm85
ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded
(cannot open shared object file): ignored.
rm -f *.gcda *.gcno *.plist
ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded
(cannot open shared object file): ignored.
make[2]: Leaving directory '/«PKGBUILDDIR»/pbmtools'
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_clean
dpkg-source -b jbigkit-2.1
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building jbigkit using existing ./jbigkit_2.1.orig.tar.gz
dpkg-source: info: building jbigkit in jbigkit_2.1-3.debian.tar.xz
dpkg-source: info: building jbigkit in jbigkit_2.1-3.dsc
debian/rules build
dh build
dh_testdir
dh_auto_configure
dh_auto_build
make[1]: Entering directory '/«PKGBUILDDIR»'
cd libjbig && make -e
make[2]: Entering directory '/«PKGBUILDDIR»/libjbig'
libtool --mode=compile gcc -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -O2 -Wall -D_FORTIFY_SOURCE=2 -c jbig.c
make[2]: libtool: Command not found
Makefile:12: recipe for target 'jbig.lo' failed
make[2]: *** [jbig.lo] Error 127
make[2]: Leaving directory '/«PKGBUILDDIR»/libjbig'
make[1]: *** [lib] Error 2
Makefile:19: recipe for target 'lib' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
debian/rules:6: recipe for target 'build' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: jbigkit
Source-Version: 2.1-3.1
We believe that the bug you reported is fixed in the latest version of
jbigkit, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 761...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose <d...@debian.org> (supplier of updated jbigkit package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Mon, 13 Oct 2014 21:07:40 +0200
Source: jbigkit
Binary: jbigkit-bin libjbig-dev libjbig0
Architecture: source amd64
Version: 2.1-3.1
Distribution: unstable
Urgency: medium
Maintainer: Michael van der Kolff <mvanderko...@gmail.com>
Changed-By: Matthias Klose <d...@debian.org>
Description:
jbigkit-bin - JBIGkit binaries
libjbig-dev - JBIGkit development files
libjbig0 - JBIGkit libraries
Closes: 761760
Changes:
jbigkit (2.1-3.1) unstable; urgency=medium
.
* Non maintainer upload.
* Allow the package to cross build, remove libtool usage. Closes: #761760.
Checksums-Sha1:
705df8773d9d492d26dc23146a6f5b9501732193 1299 jbigkit_2.1-3.1.dsc
a8631fc6aee6795a0ca9e1be8f8f593009fc4c71 7600 jbigkit_2.1-3.1.debian.tar.xz
0de9640cb51032070a7b75541a126f8c1e581fb5 28760 jbigkit-bin_2.1-3.1_amd64.deb
e1e4cee3eefa75e237bf4d678df454611e2fda82 29934 libjbig-dev_2.1-3.1_amd64.deb
b52dfc33b6c3f4047b6f412ab18fc9c107e12ddb 30742 libjbig0_2.1-3.1_amd64.deb
Checksums-Sha256:
62c8812d508958c5d35f2b1579dc3052fb5bd8d2e77d023fad064c4b48c8c3f8 1299
jbigkit_2.1-3.1.dsc
ebc3c52deaf37d52baea54d648a713640dc262926abda7bf05cd08e7db5dd1ee 7600
jbigkit_2.1-3.1.debian.tar.xz
870ae233c7dba71da1df18d9a29c7f41b14ee668c4276785326c73bcc03abdd6 28760
jbigkit-bin_2.1-3.1_amd64.deb
21a110e8b22bcafdb199e7ce34e76e3a7126e7a4e364d35ef3e0407bef295c71 29934
libjbig-dev_2.1-3.1_amd64.deb
d0b55e2da6648d6b91ced51e8c8ccfbe024283ffbbc1484f704ff7b0c97f8c51 30742
libjbig0_2.1-3.1_amd64.deb
Files:
f69bcd81087a7984344051c70ed4e595 1299 libs optional jbigkit_2.1-3.1.dsc
b56f258cff5bd25e8f71964bab25256e 7600 libs optional
jbigkit_2.1-3.1.debian.tar.xz
3562d65c33155a81625989562b0f49a8 28760 graphics optional
jbigkit-bin_2.1-3.1_amd64.deb
f2677ad353401657ee17898dbccb9fa3 29934 libdevel optional
libjbig-dev_2.1-3.1_amd64.deb
3fb1eb3844b26e96ec957075b70f973f 30742 libs optional libjbig0_2.1-3.1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlQ8I9wACgkQStlRaw+TLJwJcQCeNtxF2E33IOEX4NYZcywI9jt6
kvwAnR/WoKWY7FcUFIvpa67E0RQWMT1P
=Juam
-----END PGP SIGNATURE-----
--- End Message ---
