bzr qdiff calls on global option 'change' only available in bzr >= 0.91
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QBzr |
Fix Released
|
Critical
|
Lukáš Lalinský |
Bug Description
bzr qdiff (from qbzr 0.7.0) fails when working with bzr 0.90 with the following traceback:
-------
bzr: ERROR: exceptions.
Traceback (most recent call last):
File "/usr/lib/
return run_bzr(argv)
File "/usr/lib/
ret = run(*run_argv)
File "/usr/lib/
args, opts = parse_args(self, argv, alias_argv)
File "/usr/lib/
parser = option.
File "/usr/lib/
o = option.
KeyError: 'change'
bzr 0.90.0 on python 2.5.1.final.0 (linux2)
arguments: ['/usr/bin/bzr', 'qdiff']
-------
The option 'change' is only available in bzr 0.91/0.92.
I guess either the package dependencies need to be updated or the reliance on this option needs to be removed ... ?
Related branches
description: | updated |
Changed in qbzr: | |
milestone: | none → 0.7.1 |
Changed in qbzr: | |
importance: | High → Critical |
Changed in qbzr: | |
assignee: | nobody → luks |
status: | Confirmed → Fix Committed |
Changed in qbzr: | |
status: | Fix Committed → Fix Released |
This is not actually "bug" in QBzr. But it should be fixed.
I see several ways to fix it.
1) Provide more precise information in QBzr description about supported version of bzr and leave it as is.
2) Check version info of QBzr and bzrlib to decide is it match or not (as in bzrtools). We also could start to make releases in sync with bzr, as bzrtools and bzr-gtk do.
3) Re-implement 'change' option inside QBzr to support older version of bzr.
Make releases in sync with bzr not big deal (at least for me) because I anyway build windows installers for bzr itself.