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

[Talden]

On Thu, Jul 23, 2009 at 4:58 PM, Talden<talden at gmail.com> wrote:
> On Thu, Jul 23, 2009 at 12:55 PM, Jelmer Vernooij<jvernooij at gmail.com> wrote:
>> Hi Talden,
>>
>> Talden wrote:
>>> 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.
>
>> This should be fixed now, or at least the error message should be
>> clearer. Any chance you can try again?
>
> Okay I'm trying again with Bazaar 1.17 (bzr-svn 0.6.3 - not 0.6.3dev
> as before)...
>
> In trying other things with the previous bazaar 1.16.1 (bzr-svn
> 0.6.3dev) I tried 'svn-import' instead of 'branch' and defined the
> branch patterns in subversion.conf for that repo UUID.
>
> 'bzr svn-import' didn't bring in any of the .../projects/projectx/*
> revisions despite showing the patterns from the subversion.conf that I
> specified - it did still pull in about 25000 revisions from before
> those branches though.
>
> In addition to not pulling all the branches I wanted I hit an even
> bigger showstopper. Once it finished copying revisions into the 2a
> repository it tried to repack and got a memory error (the single pack
> it was repacking was ~4GB with ~25,000 revisions).
>
> After the failed pack I could "bzr heads --all" and see the branches
> it did pull in. "bzr init foo & bzr pull --overwrite -r
> revid:REVID_FOR_TIP_OF_FOO -d foo" got me branches for all of these
> and they look correct.  However I cannot pack the repo.
>
> I'm trying this sequence again with 1.17 so I'll let you know if the
> problem vanishes.  If I fail the repack again I'll rerun with
> performance monitors and see where process memory gets to at the point
> it aborts - I note from event logs that virtual memory was not
> exhausted so I expect the process address space was exhausted.
>
> I'm aware this repacking memory issue probably isn't a bzr-svn problem
> as much as an indication of problems repacking a largish 2a repo in
> Win32.  However I mention it here (and to you Jelmer specifically) as
> I suspect other Win32 users of svn-import with medium to large repos
> might hit it so you might want to watch out for it.

Okay "bzr svn-import" reports nearly 30000 revisions to transfer but
stops and begins packing at around 25000.  At that point the pack is
just short of 4GB.

Repack bombs with a memory error at a process size of 1.2GB (and more
than a gig of RAM free on the machine) while repacking texts.

There are no individual files in the repository larger than 50MB but
there is a single subversion revision that is 550MB - I don't know the
internal data-structure of Bazaar or the packing process so I don't
know enough to know if having migrated this subversion revision would
have bearing on this problem.

This stops me in my tracks right now and though I'm also looking into
an svn-fastexport option I'd be keen to help resolve this if I can.

--
Talden