I've read all comments and as I understand the problem: qcommit launch `bzr commit` in the subprocess and it worked fine. Then we're tyring to update branch.conf and that's failed, but only with network mapped drives. Therefore qbzr triggers some bug inside bzrlib related to such setup. Very interesting. Based on .bzr.log this problem exists since bzr 2.2, but I've never hit it. Why? My Windows XP is somewhat different from yours Windowses?
@Franjo Stipanovic: we're using bzr under the hood. Your comment is not very nice, you know?
I've read all comments and as I understand the problem: qcommit launch `bzr commit` in the subprocess and it worked fine. Then we're tyring to update branch.conf and that's failed, but only with network mapped drives. Therefore qbzr triggers some bug inside bzrlib related to such setup. Very interesting. Based on .bzr.log this problem exists since bzr 2.2, but I've never hit it. Why? My Windows XP is somewhat different from yours Windowses?
@Franjo Stipanovic: we're using bzr under the hood. Your comment is not very nice, you know?