Your message dated Tue, 05 Jan 2016 11:57:23 +0100
with message-id <1451991443.18198.30.ca...@debian.org>
and subject line Re: ziproxy: FTBFS with libpng16
has caused the Debian Bug report #809910,
regarding ziproxy: 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 ow...@bugs.debian.org
immediately.)
--
809910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ziproxy
Severity: important
User: lib...@packages.debian.org
Usertags: libpng16-transition
Dear ziproxy 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/
ziproxy FTBFS during this rebuild. The buildlog is available at
https://libpng.sviech.de/ziproxy.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 ziproxy 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 ---
Version: 3.3.1-2
Rebuilt against new version and this seems fixed!
--
tobi
On Mon, 04 Jan 2016 20:28:41 +0100 t...@debian.org wrote:
> Source: ziproxy
> Severity: important
> User: lib...@packages.debian.org
> Usertags: libpng16-transition
>
> Dear ziproxy 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/
>
> ziproxy FTBFS during this rebuild. The buildlog is available at
> https://libpng.sviech.de/ziproxy.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 ziproxy 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 ---
