I think the focus on merge is a red herring. it happened to me when creating a brand new repository. AFAICT any operation on a file name with an extended char will trigger this.
me repro steps are:
cd /usr/share
bzr init
bzr add
Result similar to above:
bzr: ERROR: exceptions.UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in p
This was on a gentoo system.
Portage 2.1.4.4 (default-linux/x86/2007.0, gcc-4.1.2, glibc-2.5-r4, 2.6.16.29-11774_3 i686)
Linux: 2.6.16.29-11774_3 i686 Intel
perhaps it is trying to interpret characters as double byte when in fact it should be treating them as single byte special characters such as um lattes.
see Bug #187267 for a good and simple repro
I think the focus on merge is a red herring. it happened to me when creating a brand new repository. AFAICT any operation on a file name with an extended char will trigger this.
me repro steps are:
cd /usr/share
bzr init
bzr add
Result similar to above: UnicodeDecodeEr ror: 'ascii' codec can't decode byte 0xe2 in p
bzr: ERROR: exceptions.
This was on a gentoo system. linux/x86/ 2007.0, gcc-4.1.2, glibc-2.5-r4, 2.6.16.29-11774_3 i686)
Portage 2.1.4.4 (default-
Linux: 2.6.16.29-11774_3 i686 Intel
perhaps it is trying to interpret characters as double byte when in fact it should be treating them as single byte special characters such as um lattes.