Comment 41 for bug 680529

Guys, I'm unable to reproduce this problem with my network and mapped drive from Windows 2000 machine.
But here is possible patch to fix the problem. You should be able to apply it with

bzr patch commit_data.diff

in your qbzr tree (you should have GNU patch utility in the PATH).

Please test it and say me if it helps or not.

For core dev: I'm explicitly taking the write lock for the entire branch.conf update procedure instead of leaving that to bzrlib. Therefore I should lock the branch once for 2 operations (2 locks one after another). I hope that reduce the possible race condition here.