tags 314408 fixed-upstream thanks At Fri, 24 Jun 2005 03:58:02 -0700, Steve Langasek wrote: > 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 for your checks - looking through the bug report, it's already fixed in the recent glibc. I marked as fixed-upstream and I expect it'll be fixed in the next glibc 2.3.5. Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
