bzr-svn: The branch file:///c:/.../foo has no revision None.

[Talden]

WinXP.  Bazaar standalone installer 1.16.1 with bundled bzr-svn 0.6.3dev

This looks like maybe related to https://bugs.launchpad.net/bzr-svn/+bug/233964

CMD> bzr init-repo --2a migration
CMD> cd migration
CMD> bzr branch file:///c:/migration/test/projects/projectx/mainlines/foo

After it has apparently transferred nearly all revisions and looks
like it's about to finish I get the following at the command-line:

"bzr: ERROR: The branch
file:///c:/migration/test/projects/projectx/mainlines/foo has no
revision None."

In the log I see (after many references to unsupported svn:eol-style)
---------------------------
47595.640  Traceback (most recent call last):
  File "bzrlib\commands.pyo", line 729, in exception_to_return_code
  File "bzrlib\commands.pyo", line 924, in run_bzr
  File "bzrlib\commands.pyo", line 560, in run_argv_aliases
  File "bzrlib\builtins.pyo", line 1153, in run
BzrCommandError: The branch
file:///c:/migration/test/projects/projectx/mainlines/foo has no
revision None.
---------------------------

* URLs above have been altered as they would disclose commercially
sensitive details - they remain very close to the originals.
* The same occurs for --1.9-rich-root albeit a much much much slower
branching process.  This was with the same install of the bazaar.
* The repo root is file:///c:/migration/test
* The branch layout is atypical and, over-time, has changed from the
more conventional form. detail below.

In early revisions (a cvs2svn migration) the structure was (and is)

     ROOT/projects/cvsproject/[trunk|branches|tags]

this area (the result of the cvs2svn migration is read-only via svn permissions)

After the migration the following was created

     ROOT/projects/projectx/[mainlines|branches|tags]

and then ROOT/projects/cvsproject/trunk was copied to
ROOT/projects/projectx/mainlines/foo

In subsequent revisions foo has been branched many times, extensively
reorganised (svn mv, cp, rm, etc)  and also copied to produce a new
mainline ROOT/projects/projectx/mainlines/bar.  foo and bar have since
diverged somewhat though early on there were merges from foo to bar.

Is this another presentation of the above bug or is it a symptom of
this atypical layout?

I'll try to make this happen with a test-case repository that I can
publish - this one's commercially sensitive.

I have just confirmed that branching
file:///c:/migration/test/projects/cvsproject/trunk (the ancestor of
that mainline) works so it is either an issue with the later revisions
or with the transition between these two branching structures.

--
Talden