perl isn't ready for release with hurd yet. This bug will be blocked by the tracking bug in perl (#648623).
Dominic Hargreaves, le Sat 26 Nov 2011 11:52:39 +0000, a écrit : Because 8, that is, 0.4% of the perl testsuite fails?? That seems exageration to me. The failures are often corner cases which don't actually have so much impact. Probably we can take the time to check whether that really is the case, just like we can probably take the time to fix all bugs in the world... Samuel
The reason for filing this tracking bug is because we don't want hurd to become a release architecture with tests which haven't been investigated in perl disabled (as per #648623). Sorry if I didn't make that clear. I don't actually know how much of your above paragraph is sarcasm, but I hope that you do think that we should investigate the failures. I'm going to create more specific bugs per test failure in the perl soon, and then those can be reassigned to hurd as needed where there is functionality missing in hurd. When we have a good idea of what issues are present, we can revisit the severity of this bug (of course, you are free to downgrade this now if you prefer). Cheers, Dominic.
Dominic Hargreaves, le Sat 26 Nov 2011 12:13:47 +0000, a écrit : I do, indeed, and before any kind of release. But I believe the failure effects themselves don't warrant preventing a releases. Ok, things are clear now, thanks for explanation ): Samuel
Hi Dom, I am checking old rc bugs in unstable to see whether affected packages should be removed and this bug popped up. Did this get any further? I looked at a current perl build for hurd-i386 and indeed there are quite a few tests that are being skipped, buut i386 has a similar number of skips. Could you mark this bug as being blocked by the individual failures? If there are no individual failures left, can this bug be closed? Thanks for looking Helmut
I don't remember I'm afraid, and won't have any time to work on this any time soon. I don't have current context on the state of the hurd port to know whether this bug should be closed - I guess that is for debian-hurd@ to comment on.