Bug#809896: marked as done (analog: FTBFS with libpng16)
Your message dated Fri, 22 Jan 2016 12:48:27 +0100
with message-id <56A2170B.5030001@debian.org>
and subject line Re: analog: builds for me
has caused the Debian Bug report #809896,
regarding analog: FTBFS with libpng16
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.)
--
809896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809896
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: analog
Severity: important
User: libpng@packages.debian.org
Usertags: libpng16-transition
Dear analog maintainer,
Currently we are preparing the transistion of libpng1.2 to libpng1.6.
The transistion bug is #650601.
A rebuilt of all packages depending on libpng-dev and libpng12-dev
has been done. The result with buildlogs can be found here:
https://libpng.sviech.de/
analog FTBFS during this rebuild. The buildlog is available at
https://libpng.sviech.de/analog.build
The Titanpad at https://titanpad.com/libpng16-transistion might give
you clues about what went wrong as well as some recipes/pointers how
to fix them. Please feel free to amend the information on the pad as
you might see fit. A plain-text, non java-script version is here:
https://titanpad.com/ep/pad/export/libpng16-transistion/latest
Please try to make analog compatible with libpng16 and then make sure
to B-D on libpng-dev only, if the fix makes it possible to compile it
against libdev12 and libdev16. If you can only make in a non-backward
compatible way, please B-D on libpng16-dev.
This bug will become RC as soon as the transistion starts.
Best regards,
--
tobi
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Tue, 12 Jan 2016 10:46:28 +0100 Adam Borowski <kilobyte@angband.pl>
> In the log you provided, it builds successfully too, just for some
> reason hangs after a successful build.
>
seems building fine now!
closing,
G.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJWohcLAAoJEPNPCXROn13ZhE4P/1vaa3RTyBIRa4ujDJdESLwz
vlCI8O4znLFStX5Kur5OJ5uf3OcB7z+E3TltGpCUkjRAKh9ZRkP+WUUBAs5vCOg9
3EjLZrK7pNFsCLXnritpNaZdxdpN4wZWKH64lzLBIy1NSphioDETQfeJfOEVYKA8
y8cDucsaCzNsZ1AI4lGNp+zyhKQyrI5Ag1OblsCkbtNM4uJZODdd9oqncmazgPQ1
AKkG1Z9w520Tv5pzSaejIRKicbLV6DwNunuwxZFrnDC0bsYOk313Vdx8wVxCY+fW
QtUtSMs8QZnRa8g15YIbKB5t36PpgiyFUSPdu8IiOwjTuMrVMZ1vqLiH3R+bnZLt
7f6pBT1Yc9RVSwgZLTKX7H5/W+2H92ROcn7BZK8oe2G+v+kzK+BiOE527tTlNaZz
gJm8gkaFy/9Uul+QJJ6MljdNDtEM5wzTk9GOUz+W3O9FIXZWlsqe46rr74OwYZ+b
5zHHarlFc9X+K0hEU2sSBwLkO+DB1ly217b+EaHd7s4/5pukrHUIPYfZJvlV1Dzx
9Hbo65l4cC5vd/PPpHPeEq4r3naAoO4oSy92JZzxv1am4zvfe6qkIxbRjvcm6eha
EuVKNCOvRbK7CQMokgx0n7k38kyK7oheZs1uAdsKJ90k4EmYOSJUSir5keKku0iA
xIQUCPfbL5+8elrdzn3K
=vDFL
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: