bzr init crashed for dir with existing files

Bug #725577 reported by Libor Jelinek on 2011-02-26
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Medium
Unassigned

Bug Description

1. Let's say I have dir ~/Clients/company/sources with subdirs html and db.
2. $ brz init in this dir crashed with output

bzr: ERROR: exceptions.UnicodeDecodeError: 'ascii' codec can't decode byte 0xe1 in position 15: 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/libor/.cache/crash/bzr-20110226142245-9616.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.

3. Subdirs doesn not contain anything "special" - just SQL scripts, PHP sources, PNG/JPG images...

Libor Jelinek (ljelinek) wrote :
Jelmer Vernooij (jelmer) wrote :

It looks like this is caused by files with a non-standard encoding that are already present in that directory.

Changed in bzr:
importance: Undecided → Medium
status: New → Confirmed
tags: added: encoding init
Libor Jelinek (ljelinek) wrote :

*** brz command are not atomical?! *** bzr init crashed but dir seems to be versioned (contains .bzr) and brz status produce correct information.

I think that every bzr operation should be atomical! Is it supported (via some line parameter?)?

Thanks to the ouput of brz add . I find which filename is causing UnicodeDecodeError bug. Renaming solved the issue but I thinkg that bzr should react to strange character more gracefully!

Martin Packman (gz) wrote :

In bzr 2.2 or later you get a much clearer error message.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers