Comment 10 for bug 680529

Hi again,

one minute ago I could reproduce the behavior by committing via command line for the first time. I don't see any difference i made to former tries but this: I used the absolute file path of the file to be committed when triggering the "bzr commit".

However, the problem seems to be the same but the symptom is slightly different: The error message did not tell me there where problems with "./.bzr/branch/lock" but "./.bzr/repository/lock".

Could this be caused by the network drive's slower response speed (compared to a local disk)? Then it possibly could be solved by waiting a few milliseconds before creating/removing the lock file.

Devs: What do you think?

Best regards,
Bela

P.S.: sorry for the typos in my last message...