"bzr log -rbefore:" crashes with ReadOnlyError
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
High
|
Unassigned |
Bug Description
I've been fooling around with bzr, trying to figure out how to get an "annotated" diff of changes introduced by a merge.
First, it appears to fail reporting via Apport, then the ReadOnlyError.
$ bzr log -r before: blogs/rsc/
bzr: failed to report crash using apport:
IOError(13, 'Permission denied')
bzr: ERROR: bzrlib.
Traceback (most recent call last):
File "/usr/lib/
return the_callable(*args, **kwargs)
File "/usr/lib/
ret = run(*run_argv)
File "/usr/lib/
return self.run_
File "/usr/lib/
return self._operation
File "/usr/lib/
self.cleanups, self.func, *args, **kwargs)
File "/usr/lib/
result = func(*args, **kwargs)
File "/home/
cmd_
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
revision, file_list)
File "/usr/lib/
"log")
File "/usr/lib/
rev1 = rev2 = revisionspec_
File "/usr/lib/
return self._match_
File "/usr/lib/
info = self._match_
File "/usr/lib/
r = RevisionSpec.
File "/usr/lib/
return self._try_
File "/usr/lib/
return rs.in_history(
File "/usr/lib/
return self._match_
File "/usr/lib/
info = self._match_
File "/usr/lib/
branch.
File "/usr/lib/
self.
File "/usr/lib/
return self.control_
File "/usr/lib/
raise errors.
ReadOnlyError: A write attempt was made in a read only transaction on LockableFiles(lock, file://
bzr 2.1.1 on python 2.6.5 (Linux-
arguments: ['/usr/bin/bzr', 'log', '-r', 'before:', 'blogs/
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'de_DE.UTF-8'
plugins:
bisect /home/user/
builddeb /usr/lib/
bzrtools /usr/lib/
etckeeper /usr/lib/
extmerge /home/user/
fastimport /home/user/
gtk /usr/lib/
launchpad /usr/lib/
loom /home/user/
netrc_
news_merge /usr/lib/
pager /home/user/
qbzr /usr/lib/
rebase /usr/lib/
search /home/user/
shell_hooks /home/user/
stats /home/user/
upload /usr/lib/
*** Bazaar has encountered an internal error. This probably indicates a
bug in Bazaar. You can help us fix it by filing a bug report at
https:/
including this traceback and a description of the problem.
"bzr log -rbefore:" reproduces this. It might be a side-effect of the DWIM-revspec code.
Note that "before:" by itself isn't a valid revisionspec, you need to specify a revision to be before. See the examples listed in "bzr help revisionspec".