concurrent access problems
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Undecided
|
Jelmer Vernooij | ||
Bazaar Subversion Plugin |
Fix Released
|
High
|
Jelmer Vernooij |
Bug Description
There appear to be problems with bzr-svn and concurrent access. If another checkin occurs while the user is typing a commit message in the editor, bzr-svn will overwrite the other checkin rather than fail with an out-of-date error. The out-of-date check seems to occur before the editor is invoked, but not again afterwards.
Repro:
* Create a test svn repository and project:
$ svnadmin create /var/tmp/svn
$ mkdir test
$ echo "test file" > test/test.txt
$ svn import -m "test project" test file://
* Check out the svn project to a working directory:
$ svn co file://
* Create a bazaar repository and checkout the test project:
$ bzr init-repo --rich-root-pack /var/tmp/bzr
$ bzr co file://
* Checkin a change from bazaar but remain in the editor:
$ cd /var/tmp/bzr/test
$ echo "change from bazaar" >> test.txt
$ bzr commit
* Sneak in a change to the test project from another shell:
$ echo "change from subversion" >> test.txt
$ svn commit -m "change from subversion" test.txt
* Return to the editor in the bazaar session and complete the commit. Notice
that there are no out-of-date complaints. The change from subversion is
no longer present on HEAD and revision 2 is missing in the svn log.
We are using bzr 1.5 and bzr-svn 0.4.10 with the stock packages for
python and python-subversion from Ubuntu 8.04.
Related branches
Changed in bzr-svn: | |
assignee: | nobody → jelmer |
importance: | Undecided → Medium |
milestone: | none → 0.4.12 |
status: | New → Triaged |
Changed in bzr-svn: | |
importance: | Medium → High |
milestone: | 0.4.12 → 0.4.16 |
I've also been experiencing this issue. I hadn't noticed it until just recently, and when I looked back through the logs, it first occurred for me six months ago (01/23/08), and it's also occured with bzr 1.5 and bzr-svn 0.4.10.