On Mon, 7 Jun 2010 14:02:50 +0200 Jeroen Roovers <j...@gentoo.org> wrote:
> I see more and more calls for either 1) "fixing the test suite", as if > that is suddenly not an UPSTREAM issue but the ebuilds' maintainers' > When instead a test suite should do a SKIP but erroneously does a FAIL, > then RESTRICT=test is not the solution. Fixing the test suite is, but > then that's not the maintainer's problem, but upstream's. Oddly enough > we have QA checks in place (for ICEs, for instance) that direct users > directly to upstream (through the HOMEPAGE variable), when it's > suddenly the maintainer's problem if a package fails its test suite > (because of FEATURES=userpriv or a missing kernel feature, perhaps - > nothing the maintainer can prepare the user's system for). I'm having trouble understanding how you can say fixing build failures is part of a maintainer's duties while fixing test failures is upstream's problem. A test failure _is_ a build failure. Yes, we should get it fixed upstream, just like any other bug. Packages can fail to compile with userpriv or missing kernel features too. Should we also send users directly to upstream in these cases? Can you explain the difference? I agree fully with all your other points. -- fonts, there's a hole in my neighbourhood gcc-porting, down which of late i cannot help but fall wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
signature.asc
Description: PGP signature
