bzr pull fails on windows if a file is locked
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Unassigned |
Bug Description
If a file happens to be open and is locked (eg. open with Word or Visual Studio), doing a bzr pull fails with the error message:
bzr: ERROR: [Errno 22] Invalid argument: u'Some file name'
What is more, every other file modified in that pull (by someone else) is listed as missing, and is deleted from the file system. This means that if you are in the middle of something, your repository becomes useless, because you cannot tell what changes you have lost, and if you happen to have local modifications to one of those files, those changes are lost. This means that people have to be very careful before doing a pull, as it is sometimes not obvious if an app has a file locked. This makes bzr very risky to use on windows.
Steps to reproduce:
(in a command prompt)
mkdir temp
bzr init
(edit temp.txt)
bzr add temp.txt
bzr commit temp.txt
mkdir temp2
cd temp2
bzr branch ../temp
open editing file in temp2\temp with Word
make changes in temp version
bzr commit in temp
bzr pull in temp2\temp
error:
bzr: ERROR: [Errno 22] Invalid argument: u'C:/temp2/
This does not show the implications to other files in the pull, but adding that is trivial ...
Related branches
Changed in bzr: | |
importance: | High → Medium |
Changed in bzr: | |
status: | Confirmed → Fix Released |
Should this be upgraded to High importance?