Bug#968975: glib2.0: FTBFS in experimental fails doc-test on glib
On Tue, 25 Aug 2020 at 08:59:52 +0100, Simon McVittie wrote: > On Mon, 24 Aug 2020 at 23:44:35 +0100, Dimitri John Ledkov wrote: > > I am observing in experimental & groovy-proposed > > > > 271/273 glib / gio-doc-checkOK 0.07s > > Running suite(s): gtk-doc-glib > > glib-unused.txt:1:E: 36 unused documentation entries > > > > 75.0%: Checks 4, Failures: 1 > > 272/273 glib / glib-doc-check FAIL > > 0.07s (exit status 1) > > I think this might mean we need a newer snapshot of gtk-doc with more > bugs fixed. I've been trying to get upstream closer to making an actual > release of gtk-doc. I think the reason we don't see this on Debian buildds (or during my release process for GLib, which behaves the same as the Debian buildds by doing Architecture: any and Architecture: all builds separately) is that in the glib2.0 packaging, dh_auto_test is skipped when you are only doing Architecture: all builds. If I remember correctly, Ubuntu buildds produce the Architecture: all packages as a side-effect of the amd64 build, instead of building them separately? That's the only situation under which the current packaging would run glib-doc-check. smcv
Bug#968975: glib2.0: FTBFS in experimental fails doc-test on glib
On Mon, 24 Aug 2020 at 23:44:35 +0100, Dimitri John Ledkov wrote: > I am observing in experimental & groovy-proposed > > 271/273 glib / gio-doc-checkOK 0.07s > Running suite(s): gtk-doc-glib > glib-unused.txt:1:E: 36 unused documentation entries > > 75.0%: Checks 4, Failures: 1 > 272/273 glib / glib-doc-check FAIL 0.07s > (exit status 1) I think this might mean we need a newer snapshot of gtk-doc with more bugs fixed. I've been trying to get upstream closer to making an actual release of gtk-doc. Unfortunately we also need a special branch of gtk-doc to be able to build gtk+4.0, and there's only one experimental, so we can't have two different gtk-doc versions in it. My next step on that when I have time will probably be to bundle a copy of the GTK 4 branch of gtk-doc into gtk+4.0 for now, and use that for its build, to decouple it from the rest of the GTK/GNOME ecosystem. Disabling the gtk-doc completeness check would be a possible stopgap solution, although that'll mean the HTML documentation is incomplete. smcv
Bug#968975: glib2.0: FTBFS in experimental fails doc-test on glib
Package: glib2.0 Version: 2.65.1-1 Severity: important Dear Maintainer, I am observing in experimental & groovy-proposed 271/273 glib / gio-doc-checkOK 0.07s Running suite(s): gtk-doc-glib glib-unused.txt:1:E: 36 unused documentation entries 75.0%: Checks 4, Failures: 1 272/273 glib / glib-doc-check FAIL 0.07s (exit status 1) Running suite(s): gtk-doc-gobject 100.0%: Checks 4, Failures: 0 273/273 glib / gobject-doc-checkOK 0.07s Ok: 270 Expected Fail: 0 Fail: 2 Unexpected Pass:0 Skipped:1 Timeout:0 I am observing this failure with 2.65.2 too. Will hunt the other failure too and report it separately. Regards, Dimitri.
