Please block sed 4.2-1

[Andreas Metzler]

Hello,

sed's behavior has changed in respect to using non-ASCII chars as a
pattern delimiter. Previously sed -e 's§text§replacement§' worked
no matter which locale was used. (The "§" being represented in
ISO-8859-1 encoding, not as a two-byte UTF-8 character.)

Now with version 4.2 sed's unicode support seems to grown, it now sees
the "§", realizes it is neither ASCII nor a valid UTF-8 character and
throws an error message:
sed: -e expression #1, char 2: delimiter character is not a single-byte character

This breaks exim4 for anybody running an UTF-8 locale who has
fine-tuned the locale configuration by setting not just LANG but
LC_CTYPE (or LC_ALL). See #527445.

Please stop sed from migration to testing until a to-be-uploaded
version of exim4 (i.e. >= 4.69-10.1) that has a workaround for the bug
has reached lenny.

Thanks, cu andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sedtest.latin1.sh.gz
Type: application/octet-stream
Size: 81 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-exim4-maintainers/attachments/20090509/868bf545/attachment.obj>