On Fri, May 17, 2019 at 08:58:03AM +0100, Chris Lamb wrote: > Wwat would you say this only triggered if the package had a testsuite > or autopkgtests?
As Dmitry mentioned in a later mail, that would be wrong.
> > I don't think test-building the whole package every commit is useful
>
> Can you elaborate why? I find this a somewhat curious statement
> in 2019.
Maybe I'm just too old-fashioned despite being in the youngest
generation of DDs.. :D
I usually try to think of the archive itself a QA staging point, where
things are tested, that's why I don't really want to bother nor be
bothered about testing more often. If I'm doing a change that I know
can effects on autopkgtests, piuparts or stuff I just test that single
change myself, otherwise I'll rely on the automatic checks that are
performed after the upload to unstable, without checking twice that
every and each commit also conforms to the standards expected of a
package in the testing suite.
> (This kind of conversation always makes me wonder if we need another
> level of "extra pendatic" that people need to opt into... *g*)
Nah. I just think that lintian should be less pro-active at adding
checks for things that are far from accepted.
And as usual I'd love of somebody else could chime in, somebody else
other than me disagreeing, the OP, and the maintainer…
--
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 `-
signature.asc
Description: PGP signature
