'bzr update' in readonly checkout broken in bzr.dev r5557
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Critical
|
John A Meinel |
Bug Description
Using a heavyweight checkout of "lp:bzr" it currently tries to write lock the Launchpad branch when doing "bzr update".
The failure is of the form:
$ bzr up
bzr: ERROR: Cannot lock LockDir(
The full traceback is:
37.899 Traceback (most recent call last):
File "C:\Users\
return the_callable(*args, **kwargs)
File "C:\Users\
ret = run(*run_argv)
File "C:\Users\
return self.run(
File "C:\Users\
return self._operation
File "C:\Users\
self.cleanups, self.func, *args, **kwargs)
File "C:\Users\
result = func(*args, **kwargs)
File "C:\Users\
old_tip = branch.
File "C:\Users\
result = unbound(self, *args, **kwargs)
File "C:\Users\
self.
File "C:\Users\
possible_
File "C:\Users\
result = unbound(self, *args, **kwargs)
File "C:\Users\
_override_
File "C:\Users\
overwrite)
File "C:\Users\
return operation.
File "C:\Users\
self.cleanups, self.func, self, *args, **kwargs)
File "C:\Users\
result = func(*args, **kwargs)
File "C:\Users\
add_
File "C:\Users\
remote_tokens = self._remote_
File "C:\Users\
repo_token or '', **err_context)
File "C:\Users\
return self._client.
File "C:\Users\
result, protocol = self.call_
File "C:\Users\
method, args, expect_
File "C:\Users\
expect_
File "C:\Users\
_translate_
File "C:\Users\
raise errors.
LockFailed: Cannot lock LockDir(
I think this is a regression of functionality, so I'm marking it as Critical.
Related branches
- Martin Pool: Approve
-
Diff: 107 lines (+35/-6)3 files modifiedbzrlib/branch.py (+8/-5)
bzrlib/tests/per_branch/test_update.py (+23/-1)
doc/en/release-notes/bzr-2.3.txt (+4/-0)
Changed in bzr: | |
assignee: | nobody → canonical-bazaar (canonical-bazaar) |
summary: |
- 'bzr update' broken in bzr.dev r5557 + 'bzr update' in readonly checkout broken in bzr.dev r5557 |
Changed in bzr: | |
assignee: | nobody → John A Meinel (jameinel) |
milestone: | 2.3.0 → 2.3b5 |
status: | Confirmed → In Progress |
Changed in bzr: | |
status: | In Progress → Fix Released |
This appears to be caused by the change to "merge_to". Off-hand I'm guessing that it is trying to update the tag dictionary of the master branch, unconditionally. And even though the tags it is getting from is the same as where it is trying to set.