* Thomas Moulard <thomas.moul...@gmail.com>, 2013-06-14, 15:50:
the ViSP[1] software I maintain is causing GCC[2,3] and Doxygen[4] to
crash on some platforms.
Why does it build documentation on the buildds? You put documentation in
a separate arch:all package, so that sounds wasteful.
But anyway...
It is difficult for me to fix or to report these issues as:
1. I am neither a DD or a DM,
2. I do not have access to these architectures by myself.
I was wondering if opening a bug (on the Debian BTS) for GCC and
Doxygen is acceptable in this case?
In theory, yes. In practice, neither GCC nor Doxygen maintainers have
time (or goodwill...) to debug these issues for you, so you'll be asked
to it provide more information. So you might as well skip the bugfiling
part until you collected enough information. :)
The correct course of action is: Ask your sponsor to debug the problems
for you. If that doesn't work, ask for help on ports' mailing lists
(debian-mips@, debian-sparc@, debian-arm@).
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130616173125.ga8...@jwilk.net
