[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#761761: marked as done (ladr: libtool split: package needs a b-d on libtool-bin (or avoid using the libtool binary))

Your message dated Tue, 14 Oct 2014 11:22:19 +0000
with message-id <E1Xe0BH-0001CQ-Nw@franck.debian.org>
and subject line Bug#761761: fixed in ladr 0.0.200911a-2.1
has caused the Debian Bug report #761761,
regarding ladr: 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 owner@bugs.debian.org
immediately.)


-- 
761761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761761
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:ladr
Version: 0.0.200911a-2
Severity: wishlist
User: debian-cross@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/ladr_0.0.200911a-2_unstable_jdk-libtool.log
The last lines of the build log are at the end of this report.
	
[...]
User Environment
â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??

HOME=/sbuild-nonexistent
LOGNAME=user
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=unstable-amd64-sbuild
SCHROOT_CHROOT_NAME=unstable-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1000
SCHROOT_GROUP=user
SCHROOT_SESSION_ID=unstable-amd64-sbuild-e540d3e5-ac61-49bb-bc01-015a02b18c09
SCHROOT_UID=1000
SCHROOT_USER=user
SHELL=/bin/sh
USER=user

dpkg-buildpackage
â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??

dpkg-buildpackage: source package ladr
dpkg-buildpackage: source version 0.0.200911a-2
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Frank Lichtenheld <djpig@debian.org>
 dpkg-source --before-build ladr-0.0.200911a
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean
   dh_testdir
   dh_auto_clean
make[1]: Entering directory '/«PKGBUILDDIR»'
make clean
make[2]: Entering directory '/«PKGBUILDDIR»'
cd ladr             && make realclean
make[3]: Entering directory '/«PKGBUILDDIR»/ladr'
libtool --mode=clean /bin/rm -f *.lo *.la
/bin/sh: 1: libtool: not found
Makefile:56: recipe for target 'realclean' failed
make[3]: *** [realclean] Error 127
make[3]: Leaving directory '/«PKGBUILDDIR»/ladr'
make[2]: *** [clean] Error 2
Makefile:40: recipe for target 'clean' failed
make[2]: Leaving directory '/«PKGBUILDDIR»'
make[1]: *** [realclean] Error 2
dh_auto_clean: make -j1 realclean returned exit code 2
Makefile:46: recipe for target 'realclean' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [clean] Error 2
debian/rules:8: recipe for target 'clean' failed
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2

--- End Message ---
--- Begin Message --- 
Source: ladr
Source-Version: 0.0.200911a-2.1

We believe that the bug you reported is fixed in the latest version of
ladr, 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 761761@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <doko@debian.org> (supplier of updated ladr 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Thu, 09 Oct 2014 10:37:43 +0000
Source: ladr
Binary: libladr-dev libladr4 prover9 ladr4-apps
Architecture: source amd64
Version: 0.0.200911a-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Matthias Klose <doko@debian.org>
Description:
 ladr4-apps - the LADR deduction library, miscellaneous applications
 libladr-dev - the LADR deduction library, development files
 libladr4   - the LADR deduction library
 prover9    - theorem prover and countermodel generator
Closes: 761761
Changes:
 ladr (0.0.200911a-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build-depend on libtool-bin. Closes: #761761.
Checksums-Sha1:
 c42f199f389cb53ab86fbc385fc87e59ffe6f7f9 1337 ladr_0.0.200911a-2.1.dsc
 40a6c0502b2e1104a3bf7dd1f146283238d36276 19388 ladr_0.0.200911a-2.1.debian.tar.xz
 0487e50b9c14c9e2a8c8621602b11a183d65c808 277768 libladr-dev_0.0.200911a-2.1_amd64.deb
 d9b065fd263a8a6e4584025660891714ef246669 187086 libladr4_0.0.200911a-2.1_amd64.deb
 219f77f4d671b7d2020f0fe335c8a907c2cb302f 99924 prover9_0.0.200911a-2.1_amd64.deb
 dd2336810c4a8a1223cbb0c6c5070a2a3f5982de 156530 ladr4-apps_0.0.200911a-2.1_amd64.deb
Checksums-Sha256:
 c0623c2dd7c8a8f76570db9d606f50f367bf6cd83ddc6c17a43d2e74def660aa 1337 ladr_0.0.200911a-2.1.dsc
 000d2791796f1dabcfb366f284760bb59d4d66b10c8dd81cc0e1c307ef129694 19388 ladr_0.0.200911a-2.1.debian.tar.xz
 5e972d4ca27ccf49b1a54d214d35386c7871bb31a4585ce4885a4e481547ba3a 277768 libladr-dev_0.0.200911a-2.1_amd64.deb
 ad78292bcd4ea9205834c3a778c039757273efd143b54003b4737b55d86b1166 187086 libladr4_0.0.200911a-2.1_amd64.deb
 28c0a29a2bbd5aa09e9cdb1a414f98abd0ff548575386a0c4b848483f0b08653 99924 prover9_0.0.200911a-2.1_amd64.deb
 5999768aaf8548c0976631335a5384e20ffe2a63b43755949fdd2f81597d7ede 156530 ladr4-apps_0.0.200911a-2.1_amd64.deb
Files:
 7be5fc8c35dbbd1146305e8bea275743 1337 math optional ladr_0.0.200911a-2.1.dsc
 0fbb593b779deabb43303557995d05fc 19388 math optional ladr_0.0.200911a-2.1.debian.tar.xz
 355c972c0e9ce3cc2b88db1aee1eadf5 277768 libdevel optional libladr-dev_0.0.200911a-2.1_amd64.deb
 88a9f97994c6eb5a71566bbc547a9415 187086 libs optional libladr4_0.0.200911a-2.1_amd64.deb
 6e9c461a93ca42a24a4c1199916a3073 99924 math optional prover9_0.0.200911a-2.1_amd64.deb
 6d8c535f6a73e0a3fbc046ee4ff8c6d9 156530 math optional ladr4-apps_0.0.200911a-2.1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlQ2aAMACgkQStlRaw+TLJzX3gCgnVBrmXJeWCN68KRZ5Q71RilE
YHMAoKjqsURfQ0PVupFvq5a5X1Ca5zDE
=RaYh
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: