severity 314408 important thanks Given that this bug is specific to amd64, it is not actually a release-critical bug for Debian (yet); there's no sense in letting this bug block glibc updates from reaching testing when amd64 isn't even in the archive... Does http://sources.redhat.com/ml/libc-hacker/2004-02/msg00022.html suggest that the fix is already included in glibc 2.3.5? Thanks, -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature