Your message dated Sun, 17 May 2009 21:24:58 +0100
with message-id <4a10729a.4010...@p10link.net>
and subject line fixed in a version that wasn't uploaded
has caused the Debian Bug report #529017,
regarding liboggz: FTBFS: configure: error: cannot run /bin/sh ./config.sub
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.)
--
529017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liboggz
Version: 0.9.9-2
Severity: serious
Hi,
There was an error while trying to autobuild your package:
> Automatic build of liboggz_0.9.9-2 on nautilus by sbuild/amd64 98
> Build started at 20090511-1738
[...]
> Build-Depends: debhelper (>= 7.0.0), libogg-dev, doxygen, docbook-to-man,
> binutils (>= 2.12.90.0.9)
[...]
> Toolchain package versions: libc6-dev_2.9-12 g++-4.3_4.3.3-9 gcc-4.3_4.3.3-9
> binutils_2.19.1-1 libstdc++6_4.4.0-4 libstdc++6-4.3-dev_4.3.3-9
[...]
> /usr/bin/fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> rm -f build-stamp
> # Add here commands to clean up after the build process.
> [ ! -f Makefile ] || /usr/bin/make distclean
> rm -f config.sub config.guess
> dh_clean
> debian/rules build
> dh_testdir
> # Add here commands to configure the package.
> ./configure --build x86_64-linux-gnu --prefix=/usr
> --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info CFLAGS="-g -O2"
> LDFLAGS="-Wl,-z,defs"
> configure: error: cannot run /bin/sh ./config.sub
> make: *** [config.status] Error 1
> dpkg-buildpackage: failure: debian/rules build gave error exit status 2
A full build log can be found at:
http://buildd.debian.org/build.php?arch=amd64&pkg=liboggz&ver=0.9.9-2
Kurt
--- End Message ---
--- Begin Message ---
version: 0.9.9-3
According to the changelog this was fixed in -3 but it seems that
version was never accepted so there was no autogenerated close message.
Buildd logs seem to indicate it is indeed now fixed in that archive.
>liboggz (0.9.9-3) unstable; urgency=low
>
> * Add libtool to Build-Depends
>
> -- John Francesco Ferlito <jo...@inodes.org> Tue, 12 May 2009
01:28:27 +1000
--- End Message ---
