Processed: forcibly merging 585737 586489

2010-06-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 585737 586489 Bug#585737: locales: upgrade not atomic Bug#586489: locales needs higher dpkg priority Forcibly Merged 585737 586489. > thanks Stopping processing here. Please contact me if you need assistance. -- 585737: http://bugs.d

Bug#586241: libc6: Upgrade 2.10.2-9 to 2.11.1-3 breaks the system debian/squeeze, (segfaults on any command)

2010-06-20 Thread Aurelien Jarno
On Fri, Jun 18, 2010 at 04:37:48AM +0200, Thibault Manlay wrote: > Hello, > > Sure. It's a virtualbox virtual machine. > > I have put it there: Thanks for the image, but I can't download it. I get a 403 error. -- Aurelien Jarno

Bug#586241: libc6: Upgrade 2.10.2-9 to 2.11.1-3 breaks the system debian/squeeze (segfaults on any command)

2010-06-20 Thread Aurelien Jarno
On Fri, Jun 18, 2010 at 07:25:32AM +0200, Thibault Manlay wrote: > Well, now I could reproduce the crash by upgrading only linux-base and > linux-image-2.6-686 (which provides linux-image-2.6.32-5-686 at the > moment, and some others dependencies). Maybe then it's related to them. > Does it mea

Bug#586241: libc6: Upgrade 2.10.2-9 to 2.11.1-3 breaks the system debian/squeeze, (segfaults on any command)

2010-06-20 Thread Thibault Manlay
Hello, Thanks for the image, but I can't download it. I get a 403 error. Yep sorry for not told you, I had deleted the image since the results I got were totally weird. The bug was fixed somehow or not at all. Yesterday some package asked the libc6 2.11.1-3 to be installed in order to get

Bug#586241: libc6: Upgrade 2.10.2-9 to 2.11.1-3 breaks the system debian/squeeze, (segfaults on any command)

2010-06-20 Thread Aurelien Jarno
On Sun, Jun 20, 2010 at 10:14:16PM +0200, Thibault Manlay wrote: > I have there only my laptop, on which I have done all of this. I > hope I can do all of these tests on another computer, but since you > said you couldn't reproduce that bug, I'm beginning to think that it > may be a memory corrupti

Bug#451886: not a bug; in support of wontfix status

2010-06-20 Thread Rich Felker
In support of this not being a bug, I have code which uses the correct, standards-compliant behavior of fgets. Contrary to Andrew's report, it's very easy to know how much is read by fgets and use it with data containing '\0'. Simply ensure the buffer does not contain any occurrances of '\n' (for i