Error message with all command line commands

Asked by Bruce Graham

I just installed the standalone version of 2.2.1 on my Windows XP machine

For all command line commands of the form:

C:\Work\project\dev> bzr help
             or
C:\Work\project\dev> bzr version

I get the following:

"Unable to load plugin u'rebase'. It requested API version (2, 1, 0) of module <module 'bzrlib' from 'C:\Program Files\Bazaar\lib\library.zip\bzrlib\__init__.pyo'> but the minimum exported version is (2, 2, 0), and the maximum is (2, 2, 1)"

followed by the correct output.

Can I continue to use this version or should I revert back to 2.1.1?

Question information

Language:
English Edit question
Status:
Solved
For:
Bazaar Edit question
Assignee:
No assignee Edit question
Solved by:
Vincent Ladeuil
Solved:
Last query:
Last reply:
Revision history for this message
Martin Pool (mbp) said :
#1

Hi Bruce,

'bzr plugins -v' will show you where this out-of-date plugin is coming from. I think that bzr-rewrite is included in the standard windows installer, so you should just be able to delete the old plugin.

Revision history for this message
Bruce Graham (bgraham) said :
#2

I moved the folder "C:\Program files\Bazaar\plugins\rewrite" to a temporary location on a network drive. I rebooted my system and I still get the error message that I quoted in my original post. The good news is that getting rid of the rewrite folder did not make things worse, but I think there is still a problem.

Revision history for this message
Vincent Ladeuil (vila) said :
#3

Could you try to upgrade to bzr-2.2.1 which is the latest stable release (https://edge.launchpad.net/bzr/+download) and post the output of 'bzr plugins -v' if the problem persist ?

The plugins shipped with the installer should not exhibit such a behaviour, so it may come from a plugin you installed yourself. If that's the case, you should be able to identify the faulty plugin by searching in the 'plugins' sub-directory of the bazaar configuration directory found in the output of 'bzr version'.

Revision history for this message
Vincent Ladeuil (vila) said :
#4

Bah, forget the first paragraph of my previous answer, you've already upgraded.

Revision history for this message
Bruce Graham (bgraham) said :
#5

As far as I know I have not installed any plugins "myself" that were not part of a prepackaged installer. I started using Bazaar in December 2009 and this is either the third or forth upgrade that I have installed. I could also try removeing the "rebase" plugin since that is the one the message seems to be complaining about. I'm confused by the first response that said to remove "rewrite". Did that poster mean "rebase" and his fingers and brain were disconnected so it came out "rewrite"?? I'm just sayin', but what do I know?

Revision history for this message
Bruce Graham (bgraham) said :
#6

Strange as it may seem I think my "off the wall" suggestion of 6 minutes ago was the ticket. When I removed the "rebase" folder from:
C:\Program Files\Bazaar\plugins the problem appears to have gone away.
In short the plugin to remove is "rebase"
NOT "rewrite"

Although there seems to be a suggestion that non of them are actually required anymore. Is this correct?

Revision history for this message
Best Vincent Ladeuil (vila) said :
#7

bzr-rebase has been renamed bzr-rewrite, hence the problem you're encountering and the first remark.

Can you try to run 'bzr plugins -v' and post the result ?

This should list all the plugins that load correctly and from where they are loaded. From there we may guess where the faulty plugin is located.

Revision history for this message
Vincent Ladeuil (vila) said :
#8

Yes, none of this should have been needed, there were early reports about such problems around the time the plugin was renamed but the installers are since supposed to take care of that.

Anyway, martin said: "so you should just be able to delete the old plugin" the *old* name was 'bzr-rebase' so indeed he told you to remove the 'rebase' directory containing the old plugin.

Glad to see you're out of trouble now.

Revision history for this message
Bruce Graham (bgraham) said :
#9

As you've requested here is the list of plugins from my installation
bzrtools 2.2.0
   Various useful commands for working with bzr.
   C:\Program Files\Bazaar\plugins\bzrtools

colo 0.1.0
   Work with colocated branches using current technology.
   C:\Program Files\Bazaar\plugins\colo

explorer 1.1.0
   Version Control for Human Beings.
   C:\Program Files\Bazaar\plugins\explorer

fastimport 0.9.0dev
   FastImport Plugin
   C:\Program Files\Bazaar\plugins\fastimport

launchpad 2.2.1
   Launchpad.net integration plugin for Bazaar.
   C:\Program Files\Bazaar\plugins\launchpad

loom 2.2.1dev
   Loom is a bzr plugin which adds new commands to manage a loom of patches.
   C:\Program Files\Bazaar\plugins\loom

netrc_credential_store 2.2.1
   Use ~/.netrc as a credential store for authentication.conf.
   C:\Program Files\Bazaar\plugins\netrc_credential_store

news_merge 2.2.1
   Merge hook for bzr's NEWS file.
   C:\Program Files\Bazaar\plugins\news_merge

pipeline
   Manage a series of branches as a pipeline.
   C:\Program Files\Bazaar\plugins\pipeline

qbzr 0.19.2
   QBzr - Qt-based frontend for Bazaar
   C:\Program Files\Bazaar\plugins\qbzr

rewrite 0.6.1
   Rebase support.
   C:\Program Files\Bazaar\plugins\rewrite

svn 1.0.4
   Support for Subversion branches
   C:\Program Files\Bazaar\plugins\svn

upload 1.0.0dev
   Upload a working tree, incrementally.
   C:\Program Files\Bazaar\plugins\upload

xmloutput 0.8.6
   This plugin adds an option (--xml) to log and provides an xml version of some builtin commands.
   C:\Program Files\Bazaar\plugins\xmloutput

Revision history for this message
Bruce Graham (bgraham) said :
#10

Thanks Vincent Ladeuil, that solved my question.

Revision history for this message
Marius Kruger (amanica) said :
#11

As far as I know, it is recommended that you first uninstall your current bzr before installing a new version.
That may have prevented this from happening.

Revision history for this message
Bruce Graham (bgraham) said :
#12

@Marius
Thank you for that observation; it appears to be correct. I removed the current installation and reinstalled it and the problem did not occur. When you only upgrade stuff occasionally it is easy to forget things like this. Some packages require it and some don't. Some will warn you and others won't -- life goes on.