Your message dated Tue, 14 Oct 2014 11:23:28 +0000
with message-id <[email protected]>
and subject line Bug#761772: fixed in libvisca 1.0.1-1.1
has caused the Debian Bug report #761772,
regarding libvisca: 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 [email protected]
immediately.)
--
761772: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761772
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:libvisca
Version: 1.0.1-1
Severity: wishlist
User: [email protected]
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/libvisca_1.0.1-1_unstable_jdk-libtool.log
The last lines of the build log are at the end of this report.
[...]
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for ANSI C header files... (cached) yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking for unistd.h... (cached) yes
checking for size_t... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating examples/Makefile
config.status: creating config.h
config.status: executing depfiles commands
if [ -e ./libtool ]; then cp -f /usr/bin/libtool ./libtool; fi
cp: cannot stat '/usr/bin/libtool': No such file or directory
make: *** [debian/stamp-autotools] Error 1
/usr/share/cdbs/1/class/autotools.mk:42: recipe for target
'debian/stamp-autotools' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: libvisca
Source-Version: 1.0.1-1.1
We believe that the bug you reported is fixed in the latest version of
libvisca, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose <[email protected]> (supplier of updated libvisca 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Thu, 09 Oct 2014 10:45:53 +0000
Source: libvisca
Binary: libvisca0 libvisca-dev
Architecture: source amd64
Version: 1.0.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Alan Woodland <[email protected]>
Changed-By: Matthias Klose <[email protected]>
Description:
libvisca-dev - Development files for libvisca
libvisca0 - Protocol implementation of VISCA cameras control interface
Closes: 761772
Changes:
libvisca (1.0.1-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Build-depend on libtool-bin. Closes: #761772.
Checksums-Sha1:
157928cd1771f8a04cfd545325418f7ea8f25545 1163 libvisca_1.0.1-1.1.dsc
f12022a2eed9741ef86089e023863b1757acbc8f 1514 libvisca_1.0.1-1.1.diff.gz
d2b7689f63c9a64701b4211ef03fbbf4ca2687f1 17712 libvisca0_1.0.1-1.1_amd64.deb
89ebc01c00045eb49499c8acfb146ae891f17cfa 27956 libvisca-dev_1.0.1-1.1_amd64.deb
Checksums-Sha256:
0378f03cc12beb5e3222514a35d9aa10f9999a959ab7e02e81d6ce44a9178856 1163
libvisca_1.0.1-1.1.dsc
6cc456d41b0e093d86208aaa5c132df14b215a9481741628b9c0514d3adc617d 1514
libvisca_1.0.1-1.1.diff.gz
d454bfb17ed681c3bebee449381a5a82fda1c81da01bd33d567a8c1bbf9ee80e 17712
libvisca0_1.0.1-1.1_amd64.deb
d222b6fd56654f14ebe8784d1d7615810a3ceb52e590f369578e1fc6600896c0 27956
libvisca-dev_1.0.1-1.1_amd64.deb
Files:
fc499845a5e52272d321e2ed47a056bd 1163 libdevel extra libvisca_1.0.1-1.1.dsc
a72218bf7902758d3f412dfb1e9cf397 1514 libdevel extra libvisca_1.0.1-1.1.diff.gz
2acb10437fe38a4b7b88e839e72a1c0f 17712 libdevel extra
libvisca0_1.0.1-1.1_amd64.deb
a584be18ba918cd7e7d0b52d53dc5cae 27956 libdevel extra
libvisca-dev_1.0.1-1.1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlQ2aBwACgkQStlRaw+TLJwmewCeIurl5OO52ereIwNAglbwH2gi
vh4AnjZHp3anTjROLtWjnXtYa5LjCtYf
=Z29a
-----END PGP SIGNATURE-----
--- End Message ---
