On 2016, നവംബർ 26 6:34:26 PM IST, "Jérémy Lal" <kapo...@melix.org> wrote:
>i've been doing in all my latest uploads this setup:
>- autopkgtest runs the package test suite
>- build does not run tests
>1) it feels wrong to add Depends to Build-Depends,
>and debian/tests/control already have all the info to properly run the
>2) when an autopkgtest fails, archive-wide testing reports the failure
>as a package bug,
>rendering tests during build useless anyway

Are you sure this is automatic? I don't think autopkgtest failure is considered 
serious bug where as FTBFS is serious. tests during build helps find problems 
in archive wide rebuilds, which is very common.

>I know that in some cases, one really need a built tree to run the
>but it's not the majority. Usually a tree with patches applied is
>So please Team, don't re-add to all my packages "run tests during
>(and, of course, do whatever you see best when you're packaging it

I don't think that is the right way to approach team maintained packages. If we 
are looking at "my package" and "your package" inside the team, that defeats 
the purpose of team maintenance. Instead we should be setting standards for the 
whole team and document it as team policy.

If you think this is better way of enabling tests, lets do it across all team 
maintained packages.


Pkg-javascript-devel mailing list

Reply via email to