[pkg-php-pear] What is needed for tests?

David Prévot david at tilapin.org
Sun Sep 21 20:03:42 UTC 2014


Le 21/09/2014 15:48, Daniel Beyer a écrit :

> even wasn't aware that uploads are not (re-)build by buildd if there is
> no need to (and of course especially not before passing the NEW queue).

Worse than that: buildd are currently not able to (re)build arch:all

> I assumed anything uploaded is (re-)build by an automated system and
> thus the build necessarily needs to work without local hacks.

Full disclaimer: if the build can’t work without local hacks, the
package definitely is RC-buggy (and that should soon be spotted thanks
to the people performing full archive rebuilds in a regular basis,
improving the QA status of Debian). Given the time constraints here, I’m
just ready to bend the rules a little bit (anyway, a package still in
NEW can’t really be RC-buggy, because it’s not even a candidate for the
release yet, and one can’t actually file a bug against it ;), since I’m
confident that the missing details will be dealt with in due time, i.e.,
once the package will be out of NEW (and I’m willing to deal with them
myself if they’re not fixed in the mean time).



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-php-pear/attachments/20140921/98c31d08/attachment.sig>

More information about the pkg-php-pear mailing list