Re: Bug#203820: Incorrect expanding [] glob

2003-08-02 Thread GOTO Masanori
At Sat, 2 Aug 2003 03:23:35 +0200, Micha-B³ Politowski wrote: > On Sat, 2 Aug 2003 00:44:16 +0200, Artur R. Czechowski wrote: > > When LC_COLLATE is set to pl_PL [] glob does not work correctly: > > > [EMAIL PROTECTED]:/tmp/bash-test$ echo $LC_COLLATE > > pl_PL > > [EMAIL PROTECTED]:/tmp/bash-tes

Bug#186331: raising severity

2003-08-02 Thread Alastair McKinstry
Hi, I'm raising the severity of this bug to serious, as it breaks busybox-cvs build on alpha, which in turn breaks the debian-installer build on alpha. Regards, Alastair -- Alastair McKinstry <[EMAIL PROTECTED]> GPG Key fingerprint = 9E64 E714 8E08 81F9 F3DC 1020 FA8E 3790 9051 38F4 He that w

Processed: tags

2003-08-02 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 186331 serious Bug#186331: alpha static adjtimex Severity set to `serious'. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSU

Bug#186331: raising severity

2003-08-02 Thread Philip Blundell
On Sat, 2003-08-02 at 13:56, Alastair McKinstry wrote: > I'm raising the severity of this bug to serious, as it breaks > busybox-cvs build on alpha, which in turn breaks the > debian-installer build on alpha. If you need a quick resolution for that problem, the easiest thing would be to stop buil

Bug#186331: raising severity; was: busybox FTBTS problems

2003-08-02 Thread Alastair McKinstry
On Sat, 2003-08-02 at 15:26, Philip Blundell wrote: > On Sat, 2003-08-02 at 13:56, Alastair McKinstry wrote: > > I'm raising the severity of this bug to serious, as it breaks > > busybox-cvs build on alpha, which in turn breaks the > > debian-installer build on alpha. > > If you need a quick reso

What's going on with glibc?

2003-08-02 Thread Nathanael Nerode
I'm a little confused. packages.qa.debian.org claims that 2.3.2-1 was accepted on 2003-07-18. And that it's out of date on sparc because it needs to be version 2.3.1-17. (?!) What's the status of glibc and what's the expected status in the near future? -- To UNSUBSCRIBE, email to [EMAIL PROT

Bug#203921: libc6: mallopt segfaults

2003-08-02 Thread Uwe Zeisberger
Package: libc6 Version: 2.3.1-17 Severity: normal Tags: upstream while playing xblast[1], the program fails irregular with a segfault. Here is a sample output of xblast started in gdb: ->8--- Program received signal SIGSEGV, Segmentation fault. 0x

Bug#203921: libc6: mallopt segfaults

2003-08-02 Thread Daniel Jacobowitz
On Sat, Aug 02, 2003 at 09:19:33PM +0200, Uwe Zeisberger wrote: > Package: libc6 > Version: 2.3.1-17 > Severity: normal > Tags: upstream > > while playing xblast[1], the program fails irregular with a segfault. > > Here is a sample output of xblast started in gdb: Have you tried using a memory d

Bug#196028: marked as done (libc6-dev: [hppa] buggy kernel includes cause build failure)

2003-08-02 Thread Debian Bug Tracking System
Your message dated Sat, 2 Aug 2003 16:49:47 -0600 with message-id <[EMAIL PROTECTED]> and subject line no longer an issue 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 your responsibility t

Re: What's going on with glibc?

2003-08-02 Thread Philip Blundell
On Sat, 2003-08-02 at 18:28, Nathanael Nerode wrote: > packages.qa.debian.org claims that 2.3.2-1 was accepted on 2003-07-18. > And that it's out of date on sparc because it needs to be version > 2.3.1-17. (?!) The sparc upload of 2.3.2-1 was mistakenly directed to unstable rather than experime

Bug#203949: libc6-dev: gcc3.3 complains that ptrace.h on s390 fails ISO C

2003-08-02 Thread Chris Cheney
Package: libc6-dev Version: 2.3.1-17 Severity: critical This problem causes kdebase to fail to build on s390. Chris In file included from /usr/include/asm/ptrace.h:11, from /usr/include/linux/ptrace.h:24, from /usr/include/asm-s390/user.h:13, f

Processed: oops forgot to actually reassign

2003-08-02 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 203303 libc6-dev Bug#203303: glibc: gcc3.3 complains swab.h fails to conform to ISO standard Bug reassigned from package `kdemultimedia' to `libc6-dev'. > stop Stopping processing here. Please contact me if you need assistance. Debian bug tr

Processed: changing severity

2003-08-02 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 203303 critical Bug#203303: glibc: gcc3.3 complains swab.h fails to conform to ISO standard Severity set to `critical'. > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (admi

Bug#203921: marked as done (libc6: mallopt segfaults)

2003-08-02 Thread Debian Bug Tracking System
Your message dated Sun, 3 Aug 2003 01:24:45 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#203921: libc6: mallopt segfaults 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 you

Re: Bug#203820: Incorrect expanding [] glob

2003-08-02 Thread GOTO Masanori
At Sat, 2 Aug 2003 03:23:35 +0200, Micha-B³ Politowski wrote: > On Sat, 2 Aug 2003 00:44:16 +0200, Artur R. Czechowski wrote: > > When LC_COLLATE is set to pl_PL [] glob does not work correctly: > > > [EMAIL PROTECTED]:/tmp/bash-test$ echo $LC_COLLATE > > pl_PL > > [EMAIL PROTECTED]:/tmp/bash-tes

Bug#186331: raising severity

2003-08-02 Thread Alastair McKinstry
Hi, I'm raising the severity of this bug to serious, as it breaks busybox-cvs build on alpha, which in turn breaks the debian-installer build on alpha. Regards, Alastair -- Alastair McKinstry <[EMAIL PROTECTED]> GPG Key fingerprint = 9E64 E714 8E08 81F9 F3DC 1020 FA8E 3790 9051 38F4 He that w

Processed: tags

2003-08-02 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 186331 serious Bug#186331: alpha static adjtimex Severity set to `serious'. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

Bug#186331: raising severity

2003-08-02 Thread Philip Blundell
On Sat, 2003-08-02 at 13:56, Alastair McKinstry wrote: > I'm raising the severity of this bug to serious, as it breaks > busybox-cvs build on alpha, which in turn breaks the > debian-installer build on alpha. If you need a quick resolution for that problem, the easiest thing would be to stop buil

Bug#186331: raising severity; was: busybox FTBTS problems

2003-08-02 Thread Alastair McKinstry
On Sat, 2003-08-02 at 15:26, Philip Blundell wrote: > On Sat, 2003-08-02 at 13:56, Alastair McKinstry wrote: > > I'm raising the severity of this bug to serious, as it breaks > > busybox-cvs build on alpha, which in turn breaks the > > debian-installer build on alpha. > > If you need a quick reso

What's going on with glibc?

2003-08-02 Thread Nathanael Nerode
I'm a little confused. packages.qa.debian.org claims that 2.3.2-1 was accepted on 2003-07-18. And that it's out of date on sparc because it needs to be version 2.3.1-17. (?!) What's the status of glibc and what's the expected status in the near future?

Bug#203921: libc6: mallopt segfaults

2003-08-02 Thread Uwe Zeisberger
Package: libc6 Version: 2.3.1-17 Severity: normal Tags: upstream while playing xblast[1], the program fails irregular with a segfault. Here is a sample output of xblast started in gdb: ->8--- Program received signal SIGSEGV, Segmentation fault. 0x

Bug#203921: libc6: mallopt segfaults

2003-08-02 Thread Daniel Jacobowitz
On Sat, Aug 02, 2003 at 09:19:33PM +0200, Uwe Zeisberger wrote: > Package: libc6 > Version: 2.3.1-17 > Severity: normal > Tags: upstream > > while playing xblast[1], the program fails irregular with a segfault. > > Here is a sample output of xblast started in gdb: Have you tried using a memory d

Bug#196028: marked as done (libc6-dev: [hppa] buggy kernel includes cause build failure)

2003-08-02 Thread Debian Bug Tracking System
Your message dated Sat, 2 Aug 2003 16:49:47 -0600 with message-id <[EMAIL PROTECTED]> and subject line no longer an issue 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 your responsibility t

Re: What's going on with glibc?

2003-08-02 Thread Philip Blundell
On Sat, 2003-08-02 at 18:28, Nathanael Nerode wrote: > packages.qa.debian.org claims that 2.3.2-1 was accepted on 2003-07-18. > And that it's out of date on sparc because it needs to be version > 2.3.1-17. (?!) The sparc upload of 2.3.2-1 was mistakenly directed to unstable rather than experime

Bug#203949: libc6-dev: gcc3.3 complains that ptrace.h on s390 fails ISO C

2003-08-02 Thread Chris Cheney
Package: libc6-dev Version: 2.3.1-17 Severity: critical This problem causes kdebase to fail to build on s390. Chris In file included from /usr/include/asm/ptrace.h:11, from /usr/include/linux/ptrace.h:24, from /usr/include/asm-s390/user.h:13, f

Processed: oops forgot to actually reassign

2003-08-02 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 203303 libc6-dev Bug#203303: glibc: gcc3.3 complains swab.h fails to conform to ISO standard Bug reassigned from package `kdemultimedia' to `libc6-dev'. > stop Stopping processing here. Please contact me if you need assistance. Debian bug tr

Processed: changing severity

2003-08-02 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 203303 critical Bug#203303: glibc: gcc3.3 complains swab.h fails to conform to ISO standard Severity set to `critical'. > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (admi

Bug#203921: marked as done (libc6: mallopt segfaults)

2003-08-02 Thread Debian Bug Tracking System
Your message dated Sun, 3 Aug 2003 01:24:45 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#203921: libc6: mallopt segfaults 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 you