[issue2369] "does not look like a ___ repository " instead of "___lib not available"
matt wilkie
bugs at mercurial.selenic.com
Thu Sep 9 22:17:36 UTC 2010
New submission from matt wilkie <maphew at gmail.com>:
If the conversion pre-reqs are not available and examining a directory for
possible conversion `hg convert` reports things like "foo does not look like
a Bazaar repository" instead of the more truthful "bzrlib not available,
skipping Bazaar check".
To reproduce, on an mercurial-virgin Windows machine which has a local
bazaar branch in k:\code\foo-bzr do:
1. Download and install tortoisehg*.msi
2. Open command shell and
pushd k:\code
hg convert -s bzr -d hg foo-bzr foo-hg
initializing destination foo-hg repository
foo does not look like a Bazaar repository
abort: foo: missing or unsupported repository
bzr check
Checking working tree at 'K:/code'.
Checking branch at 'file:///K:/code/'.
Checking repository at 'file:///K:/code/'.
checked repository <bzrlib.transport.local.LocalTransport url=file:///K:/code/>
format RepositoryFormat2a()
23 revisions
520 file-ids
checked branch file:///K:/code/ format Branch format 7
Host system is 64bit Win7 pro,
Bazaar installed from bzr-explorer-setup-1.1.0beta1.exe,
Mercurial from tortoisehg-1.1.3-hg-1.6.3-x64.msi
This is true for Bazaar, with the assumption the same holds true for other
candidates.
----------
messages: 13592
nosy: maphew
priority: bug
status: unread
title: "does not look like a ___ repository " instead of "___lib not available"
____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue2369>
____________________________________________________
More information about the Mercurial-devel
mailing list