Paul Gevers <elbrus@debian.org> writes: > > Notwithstanding the wording, the Release Team is happy with the bugs > that Sudip is filing. Because of the way that autopkgtests are used in > the Debian infrastructure to influence migration from unstable to > testing [1], it is very important that autopkgtests are recognized for > what they are. If an autopkgtest isn't really testing the installed > binaries (and yes, the boundary is unfortunately not well defined) it's > crucial that the test is marked as superficial, conform our rc_policy > [2]. The Release Team has decided that the examples that Sudip tagged, > i.e. --version, --help, checking for some installed file and the Python > import check, are superficial. OK, that's all very well, I understand the release team needs to do things for its own needs. However 1) Such an autopkgtest would have prevented an actual RC (as in makes the package unusable) bug in a recent upload of ledger 2) I'm now even less motivated to add autopkgtests. So, there can, and will be unintended consequences. Maybe that's an acceptable tradeoff, I don't know. Don't, as they say in the twit-sphere, @-me. d
Attachment:
signature.asc
Description: PGP signature