Bug#809863: marked as done (criticalmass: FTBFS with libpng16)
Your message dated Tue, 12 Jan 2016 09:49:28 +0000
with message-id <E1aIvZw-0007tf-Hc@franck.debian.org>
and subject line Bug#809863: fixed in criticalmass 1:1.0.0-4
has caused the Debian Bug report #809863,
regarding criticalmass: 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.)
--
809863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809863
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: criticalmass
Severity: important
User: libpng@packages.debian.org
Usertags: libpng16-transition
Dear + maintainers,
Currently we are preparing the transition of libpng1.2 to libpng1.6.
The transition bug is #650601.
A rebuild of all packages depending on libpng-dev and
libpng(3,12,12-0)-dev has been done. The result with buildlogs can be
found here: https://libpng.sviech.de/
criticalmass FTBFS with libpng16, you can see the buildlog here:
https://libpng.sviech.de/criticalmass.build
criticalmass also (build-)depends an versioned development package
libpng12-dev. Please update your (build-)depends to libpng-dev to
help in the transition.
This bug will become RC as soon as the transition starts, as it is
planned to remove libpng12.
Thanks!
--
tobi
--- End Message ---
--- Begin Message ---
Source: criticalmass
Source-Version: 1:1.0.0-4
We believe that the bug you reported is fixed in the latest version of
criticalmass, 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 809863@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adam Borowski <kilobyte@angband.pl> (supplier of updated criticalmass 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 ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 12 Jan 2016 10:12:01 +0100
Source: criticalmass
Binary: criticalmass criticalmass-data
Architecture: source
Version: 1:1.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Adam Borowski <kilobyte@angband.pl>
Description:
criticalmass - Shoot-em-up a la galaxian
criticalmass-data - Shoot-em-up a la galaxian (data files)
Closes: 599061 809863
Changes:
criticalmass (1:1.0.0-4) unstable; urgency=medium
.
* QA upload.
* Fix FTBFS with libpng16, depend on libpng-dev (closes: #809863).
* Build autoconfage from source (needed to detect libpng16).
* Use system libcurl (closes: #599061).
* Add build-arch and build-indep targets.
* Properly use zlib encludes.
Checksums-Sha1:
7894105339409354d91bc8404e30772b84a28e80 1676 criticalmass_1.0.0-4.dsc
7b169b0cbf95484fa481ec6a3fcd7af2fa572108 11012 criticalmass_1.0.0-4.debian.tar.xz
Checksums-Sha256:
6ebd1871210fafd3aa3c538aa23ecf48ee5661810c8118c724fd611299864fb4 1676 criticalmass_1.0.0-4.dsc
be702ae8cc6ff756923ccb99c3fe45bf7dea866519e45a47890ef00e54fab768 11012 criticalmass_1.0.0-4.debian.tar.xz
Files:
f583fd09fa22027afb5a13fdfb36ac99 1676 games optional criticalmass_1.0.0-4.dsc
c9606e808e5bdee02836dce844c5d873 11012 games optional criticalmass_1.0.0-4.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWlMN3AAoJECw7Q2/qxoEBMA4H/iBgXyCsXXW9F33+G63i7VtV
RdcXitPxRc5IXI27drv+eVbIZM6oKmLIxu4YMJaJobGP/F0MdH59ntAed5F9k48E
OneAcf0e7Otc5fLccAc1h68THxyPlDLqOca/rj0hw/4FliwX8V6VKMZO6u7IkLih
ytIxQGgQIPubznLcfF/R4pje+0anpsqUBwRgTOXzqTpVNImwJQGGpFH4OkgQp4xF
NTrDvAcBEfA9r0bWimZSxrMLgRsuatgVBIGJ8V0Qh4SN0jvkMrQgonRdoxjXbdRV
EGZI+ssz9E0P1AlBHEiu/Dw6VJeZi0dYFi1/y53xH8Fw1oJ+Bs4V232aduxJpT4=
=F1VN
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: