On Sun, 28 Jan 2018 at 06:29:19 +0200, Adrian Bunk wrote: > I've prepared an NMU for gconf (versioned as 3.2.6-4.1) and uploaded > it to DELAYED/5. ... > + * Update gtk-doc.make from gtk-doc-tools 1.27-1, > + fixing a FTBFS with gtk-doc-tools >= 1.26. (Closes: #876592)
This seems a reasonable solution. Feel free to reschedule to DELAYED/0. gconf has been dead upstream since about 2010, and is one of the obsolete packages that the GNOME team are trying to avoid including in buster, so GNOME maintainers are unlikely to be uploading it any time soon. Since this is an obsolete package, the solution proposed by John Paul Adrian Glaubitz (not building the documentation at all) would also have been reasonable: there is less need for documentation for libraries that we actively don't want people to be developing against. FYI, for packages with a sufficiently recent/sane Autotools setup to be compatible with an autoreconf with current Autotools (which I was surprised to see seems to include gconf), I think the canonical way to fix this class of bug is to ensure that dh-autoreconf runs gtkdocize, either by running upstream's autogen.sh (if it's in the tarball): https://salsa.debian.org/gnome-team/gtk3/commit/490e3220dfc976d181aab3e89c34e7a75080d94a or by providing a simplified version ourselves: https://salsa.debian.org/debian/flatpak/commit/d8004c50ffb6c99e20a77873e8cf48967afddfe8 https://salsa.debian.org/debian/flatpak/commit/8686daaf43a6d5674d1d545435f19b89773790b4 That doesn't seem like something that would justify a re-upload, though. Thanks, smcv
