(PATCH) replay_snapshot must take a write_lock on repository

Bug #144031 reported by Pieter Nagel
2
Affects Status Importance Assigned to Milestone
bzr-rewrite
Fix Released
Low
Jelmer Vernooij

Bug Description

"bzr selftest rebase" using bzr 0.90.0 gives lots of failures like the following:

Traceback (most recent call last):
  File "/home/pieter/.bazaar/plugins/rebase/test_rebase.py", line 74, in test_simple
    ["bloe"], {"bla": "bloe"})
  File "/home/pieter/.bazaar/plugins/rebase/rebase.py", line 312, in replay_snapshot
    revision_id=newrevid)
  File "/usr/lib/python2.5/site-packages/bzrlib/repository.py", line 466, in get_commit_builder
    self.start_write_group()
  File "/usr/lib/python2.5/site-packages/bzrlib/repository.py", line 507, in start_write_group
    raise errors.NotWriteLocked(self)
NotWriteLocked: KnitRepository('file:///tmp/testbzr-CWx9Rn.tmp/tmpNWjlfL/work/.bzr/') is not write locked but needs to be.

Revision history for this message
Pieter Nagel (pieter-equinox) wrote :
Jelmer Vernooij (jelmer)
Changed in bzr-rebase:
assignee: nobody → jelmer
importance: Undecided → Low
status: New → Fix Committed
milestone: none → 0.2
Jelmer Vernooij (jelmer)
Changed in bzr-rebase:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.