[Master] revisionspec in_history calls fetch, which requires the branch to be writable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Ken Basye <email address hidden>
to bazaar
This error report asked me to mail itself to this address, so I did.
Best,
Ken B.
C:\kbasye\
bzr/coe_repo/
Connected (version 2.0, client OpenSSH_4.5)
SSH kbasye1@
Authentication (password) successful!
Secsh channel 1 opened.
Opened sftp connection (server version 3)
bzr: ERROR: bzrlib.
transaction on LockableFiles(lock, file://
ory/)
Traceback (most recent call last):
File "c:\python251\
_catch_errors
return run_bzr(argv)
File "c:\python251\
ret = run(*run_argv)
File "c:\python251\
v_aliases
return self.run(
File "c:\python251\
pipe
result = func(*args, **kwargs)
File "c:\python251\
to_
File "c:\python251\
_status
rev_id = revision[
File "c:\python251\
history
return self._match_
File "c:\python251\
tch_on_and_check
info = self._match_
File "c:\python251\
tch_on
branch.
File "c:\python251\
_locked
self.
File "c:\python251\
te
repo_token = self.repository
File "c:\python251\
write
result = self.control_
File "c:\python251\
ock_write
raise errors.
ReadOnlyError: A write attempt was made in a read only transaction on LockableFi
les(lock, file://
bzr 0.90.0 on python 2.5.1.final.0 (win32)
arguments: ['c:\\python251
1@128.220.
** please send this report to <email address hidden>
C:\kbasye\
Related branches
- John A Meinel: Approve
- Martin Pool: Approve
-
Diff: 56 lines (+27/-2)2 files modifiedbzrlib/revisionspec.py (+14/-2)
bzrlib/tests/blackbox/test_log.py (+13/-0)
summary: |
- Master: revisionspec in_history calls fetch, which requires the branch + [Master] revisionspec in_history calls fetch, which requires the branch to be writable |
Changed in bzr: | |
milestone: | none → 2.2.0 |
status: | Confirmed → Fix Released |
The root problem is that we should not be implicitly fetching when we just want to look up the tip of the other branch.