Your message dated Sat, 16 Aug 2014 15:26:02 +0000
with message-id <e1xifrm-00054d...@franck.debian.org>
and subject line Bug#747786: fixed in libwfut 0.2.1-3
has caused the Debian Bug report #747786,
regarding libwfut: FTBFS: Unable to find zlib
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.)


-- 
747786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libwfut
Version: 0.2.1-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> checking for SIGC... yes
> checking for CURL... yes
> checking for CURL_PIPE... yes
> checking for main in -ltinyxml... no
> checking for crc32 in -lz... no
> configure: error: Unable to find zlib

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/05/10/libwfut_0.2.1-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
Source: libwfut
Source-Version: 0.2.1-3

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

Debian distribution maintenance software
pp.
Tobias Frost <t...@debian.org> (supplier of updated libwfut 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 16 Aug 2014 12:59:03 +0000
Source: libwfut
Binary: libwfut-0.2-1 libwfut-0.2-1-dbg libwfut-0.2-dev wfut
Architecture: source amd64
Version: 0.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Tobias Frost <t...@debian.org>
Description:
 libwfut-0.2-1 - WorldForge Update Tool (libraries)
 libwfut-0.2-1-dbg - WorldForge Update Tool (debugging libs)
 libwfut-0.2-dev - WorldForge Update Tool (development files)
 wfut       - WorldForge Update Tool (executable)
Closes: 747786
Changes:
 libwfut (0.2.1-3) unstable; urgency=medium
 .
   * QA upload.
   * Setting maintainer to QA-Group
   * add "Build-Depends: zlib1g-dev" to fix FTBFS (Closes: #747786)
     (Patch from the BTS by Hideki Yamane)
Checksums-Sha1:
 1643fa08b9fc4cabe3999f139bc9993ec029013a 1903 libwfut_0.2.1-3.dsc
 de67d1b9df450d8a3a01ffd498d149b7787787aa 3636 libwfut_0.2.1-3.diff.gz
Checksums-Sha256:
 37a152357cbaeb2774b271e6161914897fbbfd85a6380eee01b223c4d5957967 1903 
libwfut_0.2.1-3.dsc
 61d6fefb07fa58c18ba7094ff4d087ce6e2ed4ccd9f6bf910fd42d9fa8e97ded 3636 
libwfut_0.2.1-3.diff.gz
Files:
 5711745e9c303a4e9e39bac8c77110a5 1903 libs optional libwfut_0.2.1-3.dsc
 059d39d918ea3b0bac3382978806a4cd 3636 libs optional libwfut_0.2.1-3.diff.gz

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

iQIcBAEBCAAGBQJT72PuAAoJEJFk+h0XvV02Bf8P/1I/5IdpmyGJKnM6oT/3EB89
Abg3xcf+YvYK7bXeB5vonWTzooWIySwogjuTkQFc5XnNtI2RVbtCIOAmJc+U/Lg0
jMvunfQQnpIsVmf8QUc90g6X4mJSZdt1RmY1oifaHNlsUxoPPGnfH9YZAxGqz7gx
HrOOiUwpafmFpS5hPl0RXv+YIiaHdAhNzb9/olc456eRKft/K9cY3s5Mxo577yem
BUIRA/ocRlmwXifyAfXPIt9mUrmLePSTeLk0nUAqYro3oEMaTkt8DKIJORJ+Rc/N
rBTZ/7q86BZ5dnQ/4yA7nfa4GdPVL2d/2Fu4ahRoB7ixDuA+tUXzPSe25wB3+9Pp
crIbgWRfXTuR8P8ef+eFXEAiA8nP4ewIpa1BA5OJPGqJwPWvk1sMSF/YiRDr7ia3
f26U4W0EBk/Ld3+3ZAA5SFu4OQTl6x3QFQ8/wKcGr8tDKX4dspBriZm0eEIMH9yv
ug0GwA1/h4fUGArElJIRPYMvNhKd4HunV8fHIY+oyZ9O5f66tRI7bhTgqKrB4eTz
UZWN03NAMLOUr+WCFDD1Hf5fqkRgGioVU6ZX+R7k6y74kOHQqaMk+MH8MQXaafHH
1tqnCLs54cjqw02o0MLx7N4BpRYeEI2qHPIGte7ZPF9QiH2hkIyidjJduYu6cHJI
rG7QRIlKYo7k2MKWSuym
=EIVx
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to