Your message dated Tue, 28 Oct 2014 18:39:29 +0100
with message-id <20141028173929.ga12...@sym.noone.org>
and subject line Re: Bug#761791 closed by Johannes Schauer <j.scha...@email.de>
(Bug#761791: fixed in vifm 0.4-1.1)
has caused the Debian Bug report #761791,
regarding vifm: 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.)
--
761791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vifm
Version: 0.4-1
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/vifm_0.4-1_unstable_jdk-libtool.log
The last lines of the build log are at the end of this report.
[...]
dpkg-buildpackage: host architecture amd64
fakeroot debian/rules clean
test -f Makefile && /usr/bin/make distclean
debian/rules:34: recipe for target 'clean' failed
make: [clean] Error 1 (ignored)
rm -f config.h TAGS ID Makefile config.cache config.log stamp-h \
depcomp install-sh missing mkinstalldirs \
stamp-h[0-9]* config.status src/*.tab.c src/TAGS src/ID \
src/.deps src/Makefile src/config.cache src/config.log \
src/stamp-h src/stamp-h[0-9]* src/vifm src/*.o src/core \
src/*.core debian/files
rm -rf `pwd`/debian/tmp autom4te.cache
dpkg-source -b vifm-0.4
dpkg-source: warning: no source format specified in debian/source/format, see
dpkg-source(1)
dpkg-source: info: using source format `1.0'
dpkg-source: info: building vifm using existing vifm_0.4.orig.tar.gz
dpkg-source: info: building vifm in vifm_0.4-1.diff.gz
dpkg-source: warning: ignoring deletion of file mkinstalldirs, use
--include-removal to override
dpkg-source: warning: ignoring deletion of file missing, use --include-removal
to override
dpkg-source: warning: ignoring deletion of file install-sh, use
--include-removal to override
dpkg-source: warning: ignoring deletion of file depcomp, use --include-removal
to override
dpkg-source: warning: ignoring deletion of directory autom4te.cache
dpkg-source: warning: ignoring deletion of file autom4te.cache/traces.0, use
--include-removal to override
dpkg-source: warning: ignoring deletion of file autom4te.cache/requests, use
--include-removal to override
dpkg-source: warning: ignoring deletion of file autom4te.cache/output.0, use
--include-removal to override
dpkg-source: warning: the diff modifies the following upstream files:
Makefile.in
aclocal.m4
config.guess
config.sub
configure
ltmain.sh
pauseme.1
src/Makefile.in
src/commands.c
src/config.c
src/config.c~
src/filelist.c
vifm.1
dpkg-source: info: use the '3.0 (quilt)' format to have separate and documented
changes to upstream files, see dpkg-source(1)
dpkg-source: info: building vifm in vifm_0.4-1.dsc
debian/rules build
./autogen.sh
**Error**: You must have `libtool' installed.
Get ftp://ftp.gnu.org/pub/gnu/libtool-1.2d.tar.gz
(or a newer version if it is available)
make: *** [config.status] Error 1
debian/rules:26: recipe for target 'config.status' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Version: 0.7.8-1
Hi,
Debian Bug Tracking System wrote:
> vifm (0.4-1.1) unstable; urgency=medium
> .
> * Non-maintainer upload.
> * Check for libtoolize rather than libtool. Closes: #761791
For the record and for properly tracking fixed versions in the BTS:
This fix/patch/NMU was no more more necessary since the 0.7.5 upstream
release. Hence the first 0.7.8 upload also fixed this issue.
From the upstream changelog:
0.7.7 to 0.7.8-beta
Removed ltmain.sh script, which is part of libtool, which is
not used anymore. Thanks to Hendrik Jaeger (a.k.a. henk).
[...]
0.7.4b to 0.7.5-beta
[...]
Don't use libtool in build process on *nix platforms (thanks
to Merovius).
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
signature.asc
Description: Digital signature
--- End Message ---
