Your message dated Thu, 13 Jul 2006 14:17:05 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#378132: fixed in belocs-locales-bin 2.4-2
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: belocs-locales-bin
Version: 2.4-1
Severity: normal
Tags: patch
(This was discovered by code inspection while trying to get the Ubuntu
installer working with glibc 2.4; I haven't actually reproduced a
problem in practice yet that can be attributed to this bug.)
The different handling of hash collisions that represents the difference
between magics 20031115 and 20051014 doesn't appear to work in
belocs-locales-bin's localedef, because ld-collate.c calls LIMAGIC at
one point with category 0 (LC_CTYPE) whereas the implementation of
LIMAGIC smashes 20051014 down to 20031115 for all categories other than
LC_COLLATE. Patch attached to fix the LIMAGIC call.
Thanks,
--
Colin Watson [EMAIL PROTECTED]
diff -u belocs-locales-bin-2.4/locale/programs/ld-collate.c
belocs-locales-bin-2.4/locale/programs/ld-collate.c
--- belocs-locales-bin-2.4/locale/programs/ld-collate.c
+++ belocs-locales-bin-2.4/locale/programs/ld-collate.c
@@ -2588,7 +2588,7 @@
/* The spot is already taken. Try iterating using the value
from the secondary hashing function. */
size_t iter = hash % (elem_size - 2) + 1;
- if ((LIMAGIC (0)) < 0x20051014)
+ if ((LIMAGIC (LC_COLLATE)) < 0x20051014)
{
iter--;
if (iter == 0)
--- End Message ---
--- Begin Message ---
Source: belocs-locales-bin
Source-Version: 2.4-2
We believe that the bug you reported is fixed in the latest version of
belocs-locales-bin, which is due to be installed in the Debian FTP archive:
belocs-locales-bin_2.4-2.diff.gz
to pool/main/b/belocs-locales-bin/belocs-locales-bin_2.4-2.diff.gz
belocs-locales-bin_2.4-2.dsc
to pool/main/b/belocs-locales-bin/belocs-locales-bin_2.4-2.dsc
belocs-locales-bin_2.4-2_i386.deb
to pool/main/b/belocs-locales-bin/belocs-locales-bin_2.4-2_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Denis Barbier <[EMAIL PROTECTED]> (supplier of updated belocs-locales-bin
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Thu, 13 Jul 2006 22:31:20 +0200
Source: belocs-locales-bin
Binary: belocs-locales-bin
Architecture: source i386
Version: 2.4-2
Distribution: unstable
Urgency: low
Maintainer: Denis Barbier <[EMAIL PROTECTED]>
Changed-By: Denis Barbier <[EMAIL PROTECTED]>
Description:
belocs-locales-bin - tools for compiling locale data files
Closes: 378132
Changes:
belocs-locales-bin (2.4-2) unstable; urgency=low
.
* Fix LC_COLLATE output for glibc 2.4. This bug occurs with hash
collision, which means that very few locales were affected.
Closes: #378132 Thanks Colin Watson.
* debian/prerm: Copied from the locales package.
Files:
f877cf5cff04841b53736fdde85b21fd 620 misc extra belocs-locales-bin_2.4-2.dsc
24997f57ac675b0591e949d94a154af8 148014 misc extra
belocs-locales-bin_2.4-2.diff.gz
8a069c622b642d00a27d889578250f11 188976 misc extra
belocs-locales-bin_2.4-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEtrZl8Ri1lR4WGvsRAjaTAJ4xA13QBFkTe1mfcPQ7MBc591Z2jwCeMwrG
qgd2eeaKYhStiDB7pBG2//s=
=k4sK
-----END PGP SIGNATURE-----
--- End Message ---
