bzr log fails with "Invalid line in bugs property"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
High
|
Unassigned | ||
Breezy |
Fix Released
|
High
|
Jelmer Vernooij |
Bug Description
Hi (help!)
My copy of the emacs-24 branch of the Emacs repository (and I fear, everyone else's copy as well) has started
throwing an error on `bzr log':
bzr: ERROR: Invalid line in bugs property: 'http://
(that is the only output).
You can see the branch at
http://
This is on an up-to-date Debian testing system, using
Bazaar (bzr) 2.6.0dev2
Python interpreter: /usr/bin/python 2.7.3rc2
Python standard library: /usr/lib/python2.7
The .bzr.log entry is:
Thu 2012-12-27 18:59:14 -0800
0.031 bazaar version: 2.6.0dev2
0.032 bzr arguments: [u'log']
0.034 looking for plugins in /home/gm/
0.035 looking for plugins in /usr/lib/
0.047 encoding stdout as sys.stdout encoding 'UTF-8'
0.061 encoding stdout as sys.stdout encoding 'UTF-8'
0.079 Transferred: 0kB (0.0kB/s r:0kB w:0kB)
0.081 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 "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
Logger(b, rqst).show(lf)
File "/usr/lib/
self.
File "/usr/lib/
for lr in generator.
File "/usr/lib/
for revs in revision_iterator:
File "/usr/lib/
new_revs = [rev for rev in revs if _match_
File "/usr/lib/
'bugs': list(rev.
File "/usr/lib/
raise errors.
InvalidLineInBu
0.081 return code 3
I did recently make a commit that was supposed to fix bug #13285:
http://
I don't see that I did anything wrong there (and if I did, surely I should have not been able to commit).
bzr log -r111083 fails as described, but -r111082, and -r111084 work fine.
Plain bzr log and bzr log --limit 1 fail.
Here is the .bzr.log entry for the commit:
Thu 2012-12-27 09:56:17 -0800
0.029 bazaar version: 2.6.0dev2
0.029 bzr arguments: [u'commit', u'-m', u"Backport gnus-msg fix from trunk\n\n* lisp/gnus/
0.032 looking for plugins in /home/gm/
0.032 looking for plugins in /usr/lib/
0.045 encoding stdout as osutils.
0.094 opening working tree '/misc/
0.110 preparing to commit
0.133 ssh implementation is OpenSSH
[ 6354] 2012-12-27 09:56:20.952 INFO: Committing to: bzr+ssh://<email address hidden>
2.954 Selecting files for commit with filter [u'lisp/
[ 6354] 2012-12-27 09:56:21.038 INFO: modified lisp/gnus/ChangeLog
[ 6354] 2012-12-27 09:56:21.063 INFO: modified lisp/gnus/
4.739 Using fetch logic to copy between CHKInventoryRep
4.739 fetching: <SearchResult search:
[ 6354] 2012-12-27 09:56:30.927 INFO: Committed revision 111083.
12.929 Committed revid <email address hidden> as revno 111083.
13.127 return code 0
As the commit message suggests, this was a change that had been previously made on the trunk branch.
Here is the relevant piece of my bazaar.conf:
bugtracker_
TIA for any help!
Related branches
- Martin Packman: Approve
-
Diff: 266 lines (+135/-33)5 files modifiedbreezy/bugtracker.py (+30/-1)
breezy/log.py (+20/-15)
breezy/revision.py (+2/-9)
breezy/tests/test_bugtracker.py (+33/-0)
breezy/tests/test_log.py (+50/-8)
tags: | added: check-for-breezy |
tags: | removed: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in brz: | |
assignee: | nobody → Jelmer Vernooij (jelmer) |
status: | Triaged → Fix Committed |
milestone: | none → 3.0.0 |
Changed in brz: | |
status: | Fix Committed → Fix Released |
Oh, it looks like a newline somehow got into the --fixes argument:
mkdir /tmp/foo debbugs. gnu.org/ 124'
cd /tmp/foo
bzr init
touch 1
bzr add
bzr commit -m "commit" --fixes debbugs:123
bzr log # fine
echo foo >> 1
## Use ctr-l-q ctrl-j to get a literal newline in the fixes argument:
bzr commit -m "commit" --fixes 'debbugs:124
'
## commit succeeds fine, but:
bzr log
bzr: ERROR: Invalid line in bugs property: 'http://
How can I recover from this?