Hi,

I've just spent ~4 days debugging some software we're developing only to
discover we were being hit by this bug.  It seems that the fix for this
didn't make it into sarge for amd64.

Would it be possible to make sure that the fix for this is included in
the next point release of sarge?

Thank you,

-mato


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to