severity 129034 important
thanks

Hi Brendan,

This bug seems to be biting us in testing rather frequently these days.
Even though there should not have been any ABI changes since version
5.8.7-3, we've gone through four perl uploads since then, each of which has
failed to build on one or more architectures for various reasons.  I agree
with Colin that there really needs to be some mechanism by which perl can
*declare* when the last time its XS ABI changed, so that we don't end up
with countless packages wedged behind what should have been a minor perl
update.  (Frustration of the week: arm was ignored for testing propagation
for not keeping up, 5.8.7-6 was allowed into testing as a result, 5.8.7-7
was uploaded shortly thereafter and FTBFS on two unrelated architectures,
causing blockage again... hppa should be a trivial rebuild with the new 2.6
kernel, mips less so...)

I appreciate that you do try to get perl built on all archs as quickly as
possible, but I think a more defensive design is called for here.

Not reassigning to policy, because I don't think this is a policy problem
until we have some sort of an agreement that perl will provide an alternate
mechanism for packages to use, and what that mechanism should look like.

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply via email to