bzr-svn: Pushing existing BZR to new SVN repo.

[Jelmer Vernooij]

Ali Sabil wrote:
> On Thu, Aug 20, 2009 at 7:25 AM, Aaron Bentley<aaron at aaronbentley.com> wrote:
>   
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Eric Berry wrote:
>>     
>>> Ah. My apologies, I missed that.
>>>
>>> When I use -r 0.. I get this message:
>>> /Library/Python/2.5/site-packages/bzrlib/repository.py:2356:
>>> DeprecationWarning: NULL_REVISION should be used for the null revision
>>> instead of None, as of bzr 0.91.
>>>   revision_id = _mod_revision.ensure_null(revision_id)
>>> All changes applied successfully.
>>>       
>> This is bug #333961, which is fixed in bzr 1.18.
>>
>> To work around this, specify "-r 0..-1" instead.
>>
>>     
>
> Didn't bzr-svn use to provide an svn-push command just for this kind
> of situations ? Maybe you are still using an old bzr/bzr-svn combo,
> and you still need to use svn-push instead of push for the initial
> push?
>   
This used to be true, but recent versions of bzr-svn no longer have a
separate "svn-push" command. All functionality is now integrated into
"bzr push".

Cheers,

Jelmer