Your message dated Mon, 12 Nov 2007 05:27:46 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#449165: fixed in zangband 1:2.7.5pre1-3
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: zangband
Version: 1:2.7.5pre1-1
Severity: serious
Heya, building your package failed on my powerpc buildd:
| Automatic build of zangband_1:2.7.5pre1-1 on anakreon.ftwca.de by
sbuild/powerpc 98-farm
| Build started at 20071103-1416
| ******************************************************************************
[...]
| Checking correctness of source dependencies...
| Toolchain package versions: libc6-dev_2.6.1-6 gcc-4.2_4.2.2-3 g++-4.2_4.2.2-3
binutils_2.18-1 libstdc++6-4.2-dev_4.2.2-3 libstdc++6_4.2.2-3
| ------------------------------------------------------------------------------
| aclocal
| make[1]: aclocal: Command not found
| make[1]: *** [configure] Error 127
| make[1]: Leaving directory `/build/buildd/zangband-2.7.5pre1'
| make: *** [delete] Error 2
| dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules clean gave error
exit status 2
| ******************************************************************************
| Build finished at 20071103-1417
| FAILED [dpkg-buildpackage died]
| Build needed 00:00:09, 12976k disk space
A complete build log can be found at
http://experimental.debian.net/build.php?arch=powerpc&pkg=zangband&ver=1:2.7.5pre1-1
Looks like you are missing a build-dep on automake to provide aclocal.
Marc
--
BOFH #387:
Your computer's union contract is set to expire at midnight.
--- End Message ---
--- Begin Message ---
Source: zangband
Source-Version: 1:2.7.5pre1-3
We believe that the bug you reported is fixed in the latest version of
zangband, which is due to be installed in the Debian FTP archive:
zangband-data_2.7.5pre1-3_all.deb
to pool/non-free/z/zangband/zangband-data_2.7.5pre1-3_all.deb
zangband_2.7.5pre1-3.diff.gz
to pool/non-free/z/zangband/zangband_2.7.5pre1-3.diff.gz
zangband_2.7.5pre1-3.dsc
to pool/non-free/z/zangband/zangband_2.7.5pre1-3.dsc
zangband_2.7.5pre1-3_i386.deb
to pool/non-free/z/zangband/zangband_2.7.5pre1-3_i386.deb
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.
Drew Parsons <[EMAIL PROTECTED]> (supplier of updated zangband 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.7
Date: Sun, 04 Nov 2007 22:41:10 +1100
Source: zangband
Binary: zangband-data zangband
Architecture: source i386 all
Version: 1:2.7.5pre1-3
Distribution: unstable
Urgency: low
Maintainer: Drew Parsons <[EMAIL PROTECTED]>
Changed-By: Drew Parsons <[EMAIL PROTECTED]>
Description:
zangband - A single-player, text-based, roguelike game
zangband-data - A single-player, text-based, roguelike game (datafiles)
Closes: 449165
Changes:
zangband (1:2.7.5pre1-3) unstable; urgency=low
.
* The upstream makefile has a series of dependencies requiring
automake (aclocal, autoconf) to be present. configure must be
newer than configure.in, of course, but configure.in must be newer
than .version in order to ensure the automated versioning (from
src.defines.h) is correctly used. The problem is that the
upstream tarball ships configure.in but not .version.
configure.in is updated locally when autoreconf is performed, but
the refreshed configure.in is the same in content as the one in
the original tarball, only the timestamp differs. It is therefore
ignored by dpkg-source when generating zangband_2.7.5pre1-3.diff.gz,
since diff pays no attention to timestamps. So, when unpacking the
original tarball and Debian diff ready for building, configure.in
is extracted from the original tarball with the original timestamp
while .version is extracted from the diff with a date matching the
unpacking time. Hence .version is newer than configure.in,
causing configure.in to be regenerated at build time, requiring
aclocal, autoheader and autoconf.
This is the long explanation why automake and autoconf have been
added as Build-Dependencies. It's just simpler than unravelling
upstream's automake or tarballing issues. Closes: #449165.
Files:
0639e9169a376ec10c76fc108af3ca6a 750 non-free/games optional
zangband_2.7.5pre1-3.dsc
7a28f54f8f2f65c44889368cf65f3df0 90452 non-free/games optional
zangband_2.7.5pre1-3.diff.gz
8adb57efd6b9d3172ccf845eb38e80e4 1072702 non-free/games optional
zangband-data_2.7.5pre1-3_all.deb
51b9c5e0c8db2346d0495f4ec3ba6d0f 877470 non-free/games optional
zangband_2.7.5pre1-3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHLbRRts5wQWQSTkoRAsWiAJ0cV/SkQWHw8DMHVs964ze2EsxEJACdHrxs
jJh69TsnjOteQihw0CEemc4=
=kQfV
-----END PGP SIGNATURE-----
--- End Message ---
