Bug#809839: mgp: FTBFS with libpng16
Source: mgp Severity: important User: lib...@packages.debian.org Usertags: libpng16-transition Dear mgp 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/ mgp builds fine with libpng16, you can see the buildlog here: https://libpng.sviech.de/mgp.build Howver, mgp (build-)depends an versioned development package libpng12-0.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
Bug#809863: criticalmass: FTBFS with libpng16
Source: criticalmass Severity: important User: lib...@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
Bug#809882: abiword: FTBFS with libpng16
Source: abiword Severity: important User: lib...@packages.debian.org Usertags: libpng16-transition Dear abiword 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/ abiword FTBFS during this rebuild. The buildlog is available at https://libpng.sviech.de/abiword.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 abiword 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
Bug#809896: analog: FTBFS with libpng16
Source: analog Severity: important User: lib...@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
Bug#99590: Report for investors
http://i13.tinypic.com/2w5t5ap.jpg Getting LIB and Extension DLL into Synch Robert H. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
