Bug#746268: gdcm: hundreds of "sh: 1: dot: not found" messages
There are actually two alternatives to fix this bug on the upstream side: * Either convert the .dox files actual man pages and then use these directly (i.e, no longer invoking doxygen to create them). Since man pages are actually text files this would be also a proper source format to apply changes. * Or create two different doxygen files: one for creating the man pages only, and another one to create the reference documentation and handle these accordingly. Best, Gert
Bug#746268: gdcm: hundreds of "sh: 1: dot: not found" messages
Control: forwarded -1 https://sourceforge.net/p/gdcm/bugs/366/ On Mon, Dec 14, 2015 at 1:03 PM, Gert Wollnywrote: > There are actually two alternatives to fix this bug on the upstream > side: > > * Either convert the .dox files actual man pages and then use these > directly (i.e, no longer invoking doxygen to create them). Since man > pages are actually text files this would be also a proper source > format to apply changes. Point taken. Will try to use doxygen + GENERATE_DOCBOOK to bootstrap a conversion to docbook. Thanks for taking care of GDCM package. -M
Bug#746268: gdcm: hundreds of sh: 1: dot: not found messages
Control: severity -1 wishlist On Mon, Apr 28, 2014 at 5:50 PM, Matthias Klose d...@debian.org wrote: see the buildd logs, missing build dependency. Would be tempted to marked as wontfix. I am using doxygen to build the manpage(s) only. doxygen wont let me specify which target to build and thinks I am building the full -doc package... I'll leave it open to prevent duplicate. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746268: gdcm: hundreds of sh: 1: dot: not found messages
Hi, On Wed, Apr 30, 2014 at 08:41:10AM +0200, Mathieu Malaterre wrote: Control: severity -1 wishlist On Mon, Apr 28, 2014 at 5:50 PM, Matthias Klose d...@debian.org wrote: see the buildd logs, missing build dependency. Would be tempted to marked as wontfix. I am using doxygen to build the manpage(s) only. doxygen wont let me specify which target to build and thinks I am building the full -doc package... I'll leave it open to prevent duplicate. Without having dived into this: Isn't dot not found simply a sign for a missing (build-)dependency from graphviz? Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746268: gdcm: hundreds of sh: 1: dot: not found messages
On Wed, Apr 30, 2014 at 8:54 AM, Andreas Tille ti...@debian.org wrote: Hi, On Wed, Apr 30, 2014 at 08:41:10AM +0200, Mathieu Malaterre wrote: Control: severity -1 wishlist On Mon, Apr 28, 2014 at 5:50 PM, Matthias Klose d...@debian.org wrote: see the buildd logs, missing build dependency. Would be tempted to marked as wontfix. I am using doxygen to build the manpage(s) only. doxygen wont let me specify which target to build and thinks I am building the full -doc package... I'll leave it open to prevent duplicate. Without having dived into this: Isn't dot not found simply a sign for a missing (build-)dependency from graphviz? No. Because it wont change the manpage(s) output anyway. The actual long term solution would be to tweak the input doxygen file to say 'hey this debian package do not build the full doc, but simply the manpages'. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746268: gdcm: hundreds of sh: 1: dot: not found messages
Package: gdcm Version: 2.4.2-1 sh: 1: dot: not found see the buildd logs, missing build dependency. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org