On Tue, May 29, 2012 at 11:36:03AM -0500, Jonathan Nieder wrote: > This doesn't seem to be fixed upstream, so please report it to > <http://sourceware.org/bugzilla>, product glibc, component libc and > let us know the bug number so we can track it.
It is commonly accepted Debian practice for the maintainer to forward bugs upstream. I think this goes double for upstreams that require reporter accounts in their bug tracking systems or otherwise make reporting a matter of jumping through unnecessary hoops. However, I've done what you asked. http://sourceware.org/bugzilla/show_bug.cgi?id=14176 -- Antti-Juhani Kaijanaho, Jyväskylä, Finland http://antti-juhani.kaijanaho.fi/newblog/ http://www.flickr.com/photos/antti-juhani/ -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120529193453.gd2...@kukkavihko.kaijanaho.fi
