missing extensions warning is unclear
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
High
|
Martin Pool |
Bug Description
I'm running bzr.dev from the source directory.
On normal operation (e.g. update of bzr.dev own repository) it started returning warnings:
$ bzr pull
Using saved parent location: http://
No revisions to pull.
/home/kgeorge/
No module named _chunks_
cannot import name _btree_
No module named _bencode_pyx
No module named _rio_pyx
No module named _dirstate_
No module named _chk_map_pyx
No module named _known_graph_pyx
No module named _annotator_pyx
No module named _knit_load_data_pyx
No module named _groupcompress_pyx
No module named _readdir_pyx
Bazaar can run, but performance may be reduced.
Check Bazaar is correctly installed or set ignore_
% '\n '.join(
magare:~/bzr.dev$
It's doing this on bzr version as well :
$ bzr --version
Bazaar (bzr) 2.1dev
from bzr checkout /home/kgeorge/
revision: 4692
revid: <email address hidden>
branch nick: bzr.dev
Python interpreter: /usr/bin/python 2.6
Python standard library: /usr/lib64/
Platform: Linux-2.
bzrlib: /home/kgeorge/
Bazaar configuration: /home/kgeorge/
Bazaar log file: /home/kgeorge/
Copyright 2005, 2006, 2007, 2008, 2009 Canonical Ltd.
http://
bzr comes with ABSOLUTELY NO WARRANTY. bzr is free software, and
you may use, modify and redistribute it under the terms of the GNU
General Public License version 2 or later.
/home/kgeorge/
No module named _chunks_
cannot import name _btree_
No module named _rio_pyx
No module named _dirstate_
No module named _chk_map_pyx
No module named _bencode_pyx
No module named _known_graph_pyx
No module named _annotator_pyx
No module named _knit_load_data_pyx
No module named _groupcompress_pyx
Bazaar can run, but performance may be reduced.
Check Bazaar is correctly installed or set ignore_
% '\n '.join(
Related branches
- Vincent Ladeuil: Approve
- Robert Collins (community): Approve
- Diff: None lines
Changed in bzr: | |
status: | In Progress → Fix Released |
milestone: | none → 2.1.0b1 |
Hi Joro,
What this means is that you should run 'make' in the source directory each time you update/pull into it, to make sure the compiled extensions are built. However, the message is apparently unclear and I'll update it so that it
- has a shorter list of the failed extensions
- specifically suggests running make