set_stacked_on_location doesn't take a write lock

Bug #283457 reported by Michael Hudson-Doyle
2
Affects Status Importance Assigned to Milestone
Bazaar
Fix Released
Undecided
Unassigned

Bug Description

set_stacked_on_location doesn't write lock the branch (at least in the case where no revisions need to be fetched) which means you can call it when another process has the branch write locked.

This doesn't seem like a good thing.

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 283457] [NEW] set_stacked_on_location doesn't take a write lock

I think this is a BranchConfig object bug - its not honouring the lock
info of the branch.

-Rob

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

r4292 of bzr.dev fixes this.

Changed in bzr:
status: New → 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.