Hi Santiago, > In particular, if something happens 1 every 20 times on average, the > fact that it did not happen when you try 10 times does not mean in any > way that it may not happen.
I must however say that I don't see why a package that fails to build once in 20 builds would have a release critical problem: There is nothing in our policy that requires a reproducible or even a always successful build. I totally agree that catching random failures is a good quality measure, but this is IMO severity "important" at maximum. And it would be nice to have this QA test not just before the release, but already early in the release cycle. This would help a lot to avoid stressful bugfixes just before the freeze. Best regards Ole -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
