Processed: oops

2002-08-16 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > retitle 121899 libc6: getpt() documentation [no manpage, woohoo!] tells filthy lies >about how getpt() works, causing innocent programs to SEGV Bug#121899: xterm: SEGV when /dev/pts directory unreadable Changed Bug title. > thanks Stopping processing

Processed: retitle 121899 to xterm: SEGV when /dev/pts directory unreadable, tagging 121899

2002-08-16 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > retitle 121899 xterm: SEGV when /dev/pts directory unreadable Bug#121899: libc6: getpt() documentation [no manpage, woohoo!] tells filthy lies about how getpt() works, causing innocent programs to SEGV Changed Bug title. > tag 121899 + upstream Bug#1

Bug#156273: marked as done (SuperH support)

2002-08-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Aug 2002 12:03:01 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#156273: fixed in glibc 2.2.5-14 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

glibc 2.2.5-14

2002-08-16 Thread GOTO Masanori
Hi, I've duploaded glibc 2.2.5-14 for unstable, to fix especially for sh[34]eb build failure, alpha build failure and malloc security problem. Other works are not included, ex) cvs tree update, debian/patches clean up, gcc compat, etc... They're -15 work. I've tagged cvs as `glibc_2_2_5-14'.

glibc 2.2.5-14

2002-08-16 Thread GOTO Masanori
Hi, I've duploaded glibc 2.2.5-14 for unstable, to fix especially for sh[34]eb build failure, alpha build failure and malloc security problem. Other works are not included, ex) cvs tree update, debian/patches clean up, gcc compat, etc... They're -15 work. I've tagged cvs as `glibc_2_2_5-14'.

Bug#156923: More information

2002-08-16 Thread Peter Hawkins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi... This bug appears to be the same as the archived #66417 (which appears to have been closed because it couldn't be reproduced). I can quite easily reproduce it (although it is intermittent, sometimes requiring several attempts before the segf

Bug#156937: libc6-sparc64 2.2.5-11 conflicts with gcc-3.0

2002-08-16 Thread Frederik Bijlsma
Package: libc6-sparc64 Version: 2.2.5-11.1 While installing new version from libc6-sparc64 from security.debian.org error about conflict with gcc-3.0 turns up: [..] Preparing to replace libc6-sparc64 2.2.5-10 (using .../libc6-sparc64_2.2.5-11.1_sparc.deb) ... Unpacking replacement libc6-sparc6

Venez jouer sur GratGrat.com

2002-08-16 Thread GratGrat.com
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#156923: segmentation fault in nscd

2002-08-16 Thread Peter Hawkins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: nscd Version: 2.2.5-13 Severity: normal The following (strange, but not unreasonable) action causes nscd to segfault: warpcore:/home/peterh/src/nscdbreak# nscd -d Segmentation fault (core dumped). The backtrace is below. warpcore:/home/