Your message dated Tue, 12 Jun 2007 22:39:46 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428571: bash: Expansion of range expressions not working 
correctly
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 to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: bash
Version: 3.1dfsg-8
Severity: normal

This is what happens when I try some bash commands on two different
systems, Etch and Slackware 10.1.

--- Etch machine ---
[EMAIL PROTECTED]:~$ bash --version
GNU bash, version 3.1.17(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2005 Free Software Foundation, Inc.
[EMAIL PROTECTED]:~$ fn=debian
[EMAIL PROTECTED]:~$ echo ${fn##[A-Z]*}

[EMAIL PROTECTED]:~$
--- End Etch machine ---

--- Slackware machine ---
[EMAIL PROTECTED]:~$ bash --version
GNU bash, version 3.00.15(2)-release (i486-slackware-linux-gnu)
Copyright (C) 2004 Free Software Foundation, Inc.
[EMAIL PROTECTED]:~$ fn=debian
[EMAIL PROTECTED]:~$ echo ${fn##[A-Z]*}
debian
[EMAIL PROTECTED]:~$
--- End Slackware machine ---

According to manual, Slackware does it correctly, and Etch not. I also
tried on Sarge i386 system and it behaves same as Etch, so the problem
is obviously due to some Debian specific patch, and is not architecture
related.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages bash depends on:
ii  base-files                  4            Debian base system miscellaneous f
ii  debianutils                 2.17         Miscellaneous utilities specific t
ii  libc6                       2.3.6.ds1-13 GNU C Library: Shared libraries
ii  libncurses5                 5.5-5        Shared libraries for terminal hand

bash recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Justin Pryzby wrote:
> On Tue, Jun 12, 2007 at 07:37:02PM +0200, Marko Randjelovic wrote:
>> Package: bash
>> Version: 3.1dfsg-8
>> Severity: normal
>>
>> This is what happens when I try some bash commands on two different
>> systems, Etch and Slackware 10.1.
>>
>> --- Etch machine ---
>> [EMAIL PROTECTED]:~$ bash --version
>> GNU bash, version 3.1.17(1)-release (x86_64-pc-linux-gnu)
>> Copyright (C) 2005 Free Software Foundation, Inc.
>> [EMAIL PROTECTED]:~$ fn=debian
>> [EMAIL PROTECTED]:~$ echo ${fn##[A-Z]*}
>>
>> [EMAIL PROTECTED]:~$
>> --- End Etch machine ---
>>
>> --- Slackware machine ---
>> [EMAIL PROTECTED]:~$ bash --version
>> GNU bash, version 3.00.15(2)-release (i486-slackware-linux-gnu)
>> Copyright (C) 2004 Free Software Foundation, Inc.
>> [EMAIL PROTECTED]:~$ fn=debian
>> [EMAIL PROTECTED]:~$ echo ${fn##[A-Z]*}
>> debian
>> [EMAIL PROTECTED]:~$
>> --- End Slackware machine ---
>>
>> According to manual, Slackware does it correctly, and Etch not. I also
>> tried on Sarge i386 system and it behaves same as Etch, so the problem
>> is obviously due to some Debian specific patch, and is not architecture
>> related.
> Hmm, I suspect this is a locale problem.  Please send the output of
> these commands
> 
> locale
> set |grep -e ^LANG -e ^LC_
> 
> Can you also try the above tests after setting LC_ALL=C?
> 
> Thanks
> 

[EMAIL PROTECTED]:~$ set |grep -e ^LANG -e ^LC_
LANG=en_US.UTF-8
[EMAIL PROTECTED]:~$ LC_ALL=C
[EMAIL PROTECTED]:~$ fn=debian
[EMAIL PROTECTED]:~$ echo ${fn##[A-Z]*}
debian
[EMAIL PROTECTED]:~$

Now it works. I also thought is is about locale, but tried only
"LANG=en_US". Now i see there is LC_COLLATE=C on Slackware. If i unset
it, then it behaves the same as Debian, so i guess i was wrong - this
was not a bug, so i am closing this report.

--- End Message ---

Reply via email to