Your message dated Wed, 26 Apr 2006 07:39:58 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closing this bug as it was resolved with libc-2.3.6-4
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: coreutils
Version: 5.94-1
Severity: normal
Hi,
uniq and sort -u give completely different output depending on locale
settings.
Example - file "test" with these lines:
10.107.54.77
10.107.54.77
10:107:54:78
10:107:54:78
10-107-54-79
10-107-54-79
$ LANG=C uniq < test
10.107.54.77
10:107:54:78
10-107-54-79
$ LANG=cs_CZ uniq < test
10.107.54.77
10.107.54.77
10:107:54:78
10:107:54:78
10-107-54-79
10-107-54-79
and same difference between e.g. de_DE and sk_SK. Same goes for sort -u.
This problem is only with numbers combined with other characters that
are not letters.
This problem does not appear on sarge, but versions of sort and uniq
from sarge has the same problem on recent testing/unstable. So it has
something to do with libc6, IMHO.
Thanks,
Martin Kourim
-- System Information:
Debian Release: testing/unstable
APT prefers testing-proposed-updates
APT policy: (990, 'testing-proposed-updates'), (990, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.15-3-k7
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2)
Versions of packages coreutils depends on:
ii libacl1 2.2.35-1 Access control list shared library
ii libc6 2.3.6-3 GNU C Library: Shared libraries an
ii libselinux1 1.28-4 SELinux shared libraries
coreutils recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
This was bug caused by wrong collation patch in glibc and was resolved
with libc-2.3.6-4, as confirmed by the original submitter.
I'm therefore closing the bug.
--
Miroslav Kure
--- End Message ---
