Bug#919413: Bug#921301: starpu: FTBFS with upcoming doxygen 1.8.15
Hello, Samuel Thibault, le mar. 05 févr. 2019 20:21:56 +0200, a ecrit: > Andreas Beckmann, le mar. 05 févr. 2019 10:54:49 +0100, a ecrit: > > Control: retitle -1 starpu: FTBFS while building documentation > > Ok, I give up with building the pdf version, doxygen+latex is too much > of a hassle. For information, I had to do it not only in starpu, but also in gtg-trace, hwloc, and litl, i.e. essentially almost all of my packages which build pdf out of doxygen. We had already had LaTeX dependency issues in the past, and now it seems to be a bug in the .tex file itself, I'm sorry I just can't spend time on fixing issues between doxygen and LaTeX, Debian will just only ship the html version for these packages. If anybody wants to try to fix the actual issue, just disable the doc-nopdf patch in those packages. Samuel
Bug#921301: starpu: FTBFS with upcoming doxygen 1.8.15
Control: tags -1 + pending Hello, Andreas Beckmann, le mar. 05 févr. 2019 10:54:49 +0100, a ecrit: > Control: retitle -1 starpu: FTBFS while building documentation Ok, I give up with building the pdf version, doxygen+latex is too much of a hassle. (FTR, Nathalie told me that the issue encountered by Andreas is typically because the pdf generation does not manage to create hyperlinks that are broken by a page break, which happens often with a documentation with long function names). Samuel
Bug#921301: starpu: FTBFS with upcoming doxygen 1.8.15
Control: retitle -1 starpu: FTBFS while building documentation Hi Paolo, On Mon, 4 Feb 2019 01:17:19 +0100 Paolo Greppi wrote: > Source: starpu > Severity: serious > I tested your package against a draft package for doxygen 1.8.15: > https://bugs.debian.org/919413 > > and it FTBFS with this error: > mv: cannot stat 'latex/refman.pdf': No such file or directory this problem seems to be unrelated to doxygen 1.8.15, as I can also reproduce it in sid. You other bug reports may be similarily misleading. Could you test the other affected packages in sid, too, to see whether it is actually a regression with doxygen 1.8.15? Andreas
Bug#921301: starpu: FTBFS with upcoming doxygen 1.8.15
Followup-For: Bug #921301 Control: severity -1 serious Hi, this seems to be unrelated to 1.8.15, since I can already reproduce this with 1.8.13-10 in sid: Making all in doc make[2]: Entering directory '/build/starpu-1.2.6+dfsg/build/doc' Making all in doxygen make[3]: Entering directory '/build/starpu-1.2.6+dfsg/build/doc/doxygen' warning: Tag `SYMBOL_CACHE_SIZE' at line 370 of file `../../../doc/doxygen/doxygen.cfg' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `XML_SCHEMA' at line 1507 of file `../../../doc/doxygen/doxygen.cfg' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `XML_DTD' at line 1513 of file `../../../doc/doxygen/doxygen.cfg' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" /build/starpu-1.2.6+dfsg/doc/doxygen/chapters/api/codelet_and_tasks.doxy:673: warning: explicit link request to 'STARPU_TASK_TYPE_INTERNAL' could not be resolved /build/starpu-1.2.6+dfsg/doc/doxygen/chapters/api/codelet_and_tasks.doxy:675: warning: explicit link request to 'STARPU_TASK_TYPE_NORMAL' could not be resolved /build/starpu-1.2.6+dfsg/doc/doxygen/chapters/api/data_management.doxy:391: warning: explicit link request to 'STARPU_ACQUIRE_NO_NODE_LOCK_ALL' could not be resolved /build/starpu-1.2.6+dfsg/include/starpu_stdlib.h:59: warning: The following parameters of starpu_memory_allocate(unsigned node, size_t size, int flags) are not documented: parameter 'flags' /build/starpu-1.2.6+dfsg/doc/doxygen/chapters/000_introduction.doxy:25: warning: included file foreword.html is not found. Check your EXAMPLE_PATH /build/starpu-1.2.6+dfsg/doc/doxygen/chapters/000_introduction.doxy:306: warning: unable to resolve reference to `ModuleDocumentation' for \ref command /build/starpu-1.2.6+dfsg/doc/doxygen/chapters/000_introduction.doxy:307: warning: unable to resolve reference to `FileDocumentation' for \ref command /build/starpu-1.2.6+dfsg/doc/doxygen/chapters/000_introduction.doxy:25: warning: included file foreword.html is not found. Check your EXAMPLE_PATH /build/starpu-1.2.6+dfsg/doc/doxygen/chapters/000_introduction.doxy:306: warning: unable to resolve reference to `ModuleDocumentation' for \ref command /build/starpu-1.2.6+dfsg/doc/doxygen/chapters/000_introduction.doxy:307: warning: unable to resolve reference to `FileDocumentation' for \ref command pdflatex latex/refman.tex mv latex/refman.pdf ../../doc/doxygen/starpu.pdf mv: cannot stat 'latex/refman.pdf': No such file or directory make[3]: *** [Makefile:949: ../../doc/doxygen/starpu.pdf] Error 1 make[3]: Leaving directory '/build/starpu-1.2.6+dfsg/build/doc/doxygen' make[2]: *** [Makefile:590: all-recursive] Error 1 make[2]: Leaving directory '/build/starpu-1.2.6+dfsg/build/doc' Hmm, where is the doxygen command line? And where is the output from pdflatex? Yes, it's a lot of clutter it it just works. But now? Oh great, the relevant targets in doc/doxygen/Makefile.in are all @-ed :-( And the refman.pdf target cannot fail. Or rather ignores all errors. Andreas
Bug#921301: starpu: FTBFS with upcoming doxygen 1.8.15
Source: starpu Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 and it FTBFS with this error: mv: cannot stat 'latex/refman.pdf': No such file or directory Paolo -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
