darcs to bzr not working

[ema@…]

I'm trying to switch a darcs repository to bazaar-ng, but it seems that tailor is not able to import BzrWorkingDir?.

ema@pcema:~/darcs/tailor$ ./tailor ~/darcs2bazaar.tailor 
19:29:48 [I] Bootstrapping "project" in "/home/ema"
19:29:48 [C] Cannot import 'BzrWorkingDir' from 'vcpx.bzr'
Bad invocation, use --help for details: 'bzr' is not a known VCS kind: No module named bzrlib.branch

The same problem is reported while testing Darcs:

ema@pcema:~/darcs/tailor$ ./tailor test -v Darcs
Test basic configuration ... ok
Test darcs to bazaar-ng and the other way around ... 19:32:11 [C] Cannot import 'BzrWorkingDir' from 'vcpx.bzr'

I've "darcs-getted" tailor as follows: darcs get http://darcs.arstecnica.it/tailor/

Here it is my config file, hope this helps:

[DEFAULT]
verbose = True

[project]
target = bzr:target
start-revision = INITIAL
root-directory = /home/ema
state-file = tailor.state
source = darcs:source
subdir = .

[bzr:target]
repository = /tmp/test/

[darcs:source]
repository = /home/ema/darcs/emdis

[brendan@…]

"No module named bzrlib.branch" looks like the culprit (though the exception path seems to eventually misreport the error). Where's bzrlib, and is in in your PYTHONPATH?

[Lele Gaifax]

Most probably, you are invoking Tailor with Python 2.3, while you need Python 2.4 to use BzrNG, since that requires version 2.4 of the interpreter.

[ema@…]

Lele is right: the problem is that I was using python 2.3 rather than 2.4: now I've tailored my darcs repository to bzr without problems.

What about warning the user if he's using an incorrect version of python? I'm changing the ticket Type to 'enhancement', since this is not a defect in tailor at all.

Thanks for your support and sorry for the noise.

[Lele Gaifax]

Now tailor emits a warning message that explains requirement for Python 2.4 when using BazaarNG-