Re: Please block sed 4.2-1

2009-05-24 Thread Adeodato Simó
+ Andreas Metzler (Sat, 09 May 2009 09:05:02 +0200): > 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. exim4 4.69-11 is now in testing, so I've removed the block hint against sed. Cheer

Re: Please block sed 4.2-1

2009-05-09 Thread Julien Cristau
On Sat, May 9, 2009 at 13:35:16 +0200, Paolo Bonzini wrote: > Or just set export LC_CTYPE=C at the top of the script. > That doesn't work if LC_ALL is set. Cheers, Julien -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact lis

Re: Please block sed 4.2-1

2009-05-09 Thread Andreas Metzler
On 2009-05-09 Paolo Bonzini wrote: > Andreas Metzler wrote: >> On 2009-05-09 Adeodato Simó wrote: >> [...] >>> And, in any case, can exim4 stop using non-ASCII as a delimiter? Or is >>> there really *no* ASCII delimiter left that would be used for the >>> expression at and? >> I guess there is s

Re: Please block sed 4.2-1

2009-05-09 Thread Paolo Bonzini
Andreas Metzler wrote: > On 2009-05-09 Adeodato Simó wrote: > [...] >> And, in any case, can exim4 stop using non-ASCII as a delimiter? Or is >> there really *no* ASCII delimiter left that would be used for the >> expression at and? > > I guess there is safe one for each of the sed invocations. T

Re: Please block sed 4.2-1

2009-05-09 Thread Andreas Metzler
On 2009-05-09 Adeodato Simó wrote: [...] > And, in any case, can exim4 stop using non-ASCII as a delimiter? Or is > there really *no* ASCII delimiter left that would be used for the > expression at and? I guess there is safe one for each of the sed invocations. Thinking about which one is a PITA

Re: Please block sed 4.2-1

2009-05-09 Thread Adeodato Simó
+ Andreas Metzler (Sat, 09 May 2009 09:05:02 +0200): > 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 U

Please block sed 4.2-1

2009-05-09 Thread 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 s