Comment 13 for bug 77657

In what sense is this bug 'fixed'? I've just encountered the same problem with bzr 2.0.2, which produced a crash report and suggested I file it as a bug...

From the discussion above, I appreciate the issue. My preferred solution would be to escape the offending characters and preserve their literal values, as suggested by codeslinger, if this is a viable option. Renaming the files is an option for me in this case, but since neither the error message nor the crash report allows me to identify the problem files. I attempted to apply David Henningsson's hack to print the filenames (I think the equivalent block of code in 2.0.2 is in dirstate.py??), but to no avail.

Can anyone suggest a way I can at least find out where the offending files are? I have to work with a large and messy tree!

Thanks!

 bzr: ERROR: exceptions.UnicodeDecodeError: 'ascii' codec can't decode byte 0xc0 in position 68: ordinal not in range(128)

 *** Bazaar has encountered an internal error. This probably indicates a
  bug in Bazaar. You can help us fix it by filing a bug report at
   https://bugs.launchpad.net/bzr/+filebug
  attaching the crash file
   /home/simon/.cache/crash/bzr-20100202025927-17893.crash
  and including a description of the problem.

  The crash file is plain text and you can inspect or edit it to remove
  private information.