On Mon, May 16, 2016 at 04:02:00PM +0100, Ghislain Vaillant wrote:
> It's an entry point to a GUI application. Not sure what the manpage is
> useful for then. Please consider giving a more precise advice.
https://www.debian.org/doc/debian-policy/ch-docs.html#s12.1
But anyway, evenwithout the policy stick, a manpage is just damn useful.
And surely a gui is not the only way to lunch a program.
Quite a lot (most?) of gui programs have flags to tweak the run (debug
things, etc). If the program deals with files the manpage can document
how to specify those files.
If the pogram doesn't have any of those things, a manpage can document
what the hell such program is.
The advice is pretty clear: drop that lintian override.
>
> * d/rules:
> > + what's the reason for disabling the tests? please document it in a
> > comment.
> >
>
> Test autodiscovery picks up tests whilst upstream does not officially
> declare
> a testsuite.
umh, not sure what that means. Are the tests broken/non-working then?
But I was intending to document it in a comment in d/rules. It needs to
be there for future references. If/when people look at the package they
should be able to understand why the tests are disabled, without
guessing or giving up. And trust me that it happens.
> Anyway, please consider this sponsorship on hold until further notice.
ok, please ping when ready and I'll look again.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature