Hi Tobi! I quickly scanned through the build logs you mentioned. It appears to me that an old package was used during the build. There are the two latest patches missing which are available in version 0.11.9-6
Especially patch 06_gcc5.patch fixes all the compiler warnings/errors for gcc5. The build log mentions version 0.11.9-4. Could you take a look at it again? Greetings Peter On 01/04/2016 08:28 PM, t...@debian.org wrote: > Source: bomberclone > Severity: important > User: lib...@packages.debian.org > Usertags: libpng16-transition > > Dear bomberclone 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/ > > bomberclone FTBFS during this rebuild. The buildlog is available at > https://libpng.sviech.de/bomberclone.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 bomberclone 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, >
