Your message dated Sat, 2 Apr 2016 12:37:23 +0200 with message-id <20160402103723.ga5...@fatal.se> and subject line libgdk-pixbuf2.0-dev -> libpng-dev vs pbuilder has caused the Debian Bug report #819779, regarding gdk-pixbuf: libgdk-pixbuf2.0-dev depends on libpng-dev but gdk-pixbuf2.0.pc requires libpng12-dev 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.) -- 819779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libgdk-pixbuf2.0-dev Version: 2.32.3-1.2 Severity: grave Justification: renders package unusable Hello, While trying to build a new version of my package latexila for experimental, I noticed it was failing because of libgtk-pixbuf2.0-dev. Indeed, that package, in unstable and in experimental as well: * ships a gdk-pixbuf2.0.pc that requires libpng12.pc; * depends on libpng-dev which: - on experimental, is a real package that does not ship libpng12.pc but only libpng16.pc and libpng.pc; - on unstable, is provided by libpng12-dev which does provide libpng12.pc, but that situation should change to that of experimental whenever the new libpng-dev real package is uploaded to it. Basically, when requiring libpng12.pc, it does not seem right to depend on a package, either virtual or real, that is not guaranteed to provide it. In my opinion, in its current state, libgdk-pixbuf2.0-dev should depend on libpng12-dev as this is what it uses, and not on libpng-dev which may or may not provide what it currently needs. Since there is a transition to make to libpng-dev, one solution would be to rebuild gdk-pixbuf for experimental, but doing it in an environment with libpng12-dev not installed and libpng-dev installed from experimental. That way, its configure script (l. 18507) would just pick libpng16 and the resulting gdk-pixbuf2.0.pc would require the libpng16.pc it provides: >for l in libpng16 libpng15 libpng14 libpng12 libpng13 libpng10; do > […] In the longer term, it could be better to have the configure script check for libpng before libpng16 or libpng12: >for l in libpng libpng16 libpng15 libpng14 libpng12 libpng13 libpng10; do > […] That way, it would not even need to be adapted for future versions of libpng. Regards, -- Tanguy
--- End Message ---
--- Begin Message ---Hello Tanguy! As discussed on IRC the problem you're experiencing is a pbuilder bug and not an issue in the package itself. Also, whatever is being prepared w.r.t. libpng in experimental is not something we can use in unstable (which the version of the package you reported this bug against is in). Regards, Andreas Henriksson
--- End Message ---
