bzr 0.12.0: upgrade fails: 'module' object has no attribute 'workingtree'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
High
|
John A Meinel |
Bug Description
mfx@harmonia:
Format <RepositoryFormat4> for file://
starting upgrade of file://
making backup of tree history
file://
if conversion fails, you can move this directory back to .bzr
if it succeeds, you can remove this directory if you wish
starting upgrade from format 4 to 5
note: upgrade may be faster if all store files are ungzipped first
upgraded to weaves:
2 revisions and inventories
0 revisions not present
38 texts
starting upgrade from format 5 to 6
adding prefixes to weaves
adding prefixes to revision-store
starting upgrade from format 6 to metadir
bzr: ERROR: exceptions.
Traceback (most recent call last):
File "/home/
return run_bzr(argv)
File "/home/
ret = run(*run_argv)
File "/home/
return self.run(
File "/home/
upgrade(url, format)
File "/home/
Convert(url, format)
File "/home/
self.convert()
File "/home/
self.bzrdir = converter.
File "/home/
self.
AttributeError: 'module' object has no attribute 'workingtree'
bzr 0.12.0 on python 2.4.3.final.0 (linux2)
arguments: ['/home/
** please send this report to <email address hidden>
This is a similar bug as bug 66349. On line 1877 of bzrlib/bzrdir.py it directly accesses bzrlib. workingtree. X but before that point it has never explicitly imported it. (It used to be imported as a side effect of other functions).
With a plugin like bzrtools installed, workingtree is imported by the plugin at startup time. So the current workaround is to just install bzrtools. The patch is pretty minor, though. I'll attach a patch.