upgrade to --development-rich-root in 1.14rc1

[Parth Malwankar]

On Fri, 10 Apr 2009 18:36:01 +0530, Jelmer Vernooij <jelmer at vernstok.nl>  
wrote:

> Parth Malwankar wrote:
>> On Thu, 09 Apr 2009 17:39:42 +0530, Parth Malwankar
>> <parth.malwankar at gmail.com> wrote:
>>
>>> Hello,
>>>
>>> In order to try out the new development format in 1.14rc1
>>> I am trying to upgrade a bzr-svn checkout but it doesn't seem
>>> to be working.
>>>
>>> Following is the listing:
>>>
>> <snip>
>>
>>>
>>> [clojure]% xbzr upgrade --development-rich-root
>>> starting upgrade of file:///storage/parth/src/bcore-test/clojure/
>>> making backup of file:///storage/parth/src/bcore-test/clojure/.bzr
>>>    to file:///storage/parth/src/bcore-test/clojure/backup.bzr
>>> starting repository conversion
>>> bzr: ERROR: Revision
>>> {('379 at a41a16f3-9855-0410-b325-31a011a03e7c:trunk%2Fsrc%2Fboot.clj',
>>> 'svn-v4:a41a16f3-9855-0410-b325-31a011a03e7c:trunk:501')} not present
>>> in "<bzrlib.groupcompress.GroupCompressVersionedFiles object at
>>> 0x8caf4ec>".
>>>
>>> [clojure]%  xbzr version
>>> Bazaar (bzr) 1.14rc1
>>>    Python interpreter: /usr/bin/python 2.5.2
>>>    Python standard library: /usr/lib/python2.5
>>>    bzrlib: /storage/parth/src/bzr/bzr-1.14rc1/bzrlib
>>>    Bazaar configuration: /home/parthm/.bazaar
>>>    Bazaar log file: /home/parthm/.bzr.log
>>> <snip>
>>>
>>> Below is the content of .bzr.log along with the output of "check".
>>> Is this expected? Do I need to do something differently for upgrade?
>>>
>>> Regards,
>>> Parth
>>>
>>
>> Looks like it was a case of RTFM (serves me right) :)
>> Based on the docs[1] I needed to use
>> --development-subtree and not --development-rich-roots.
>> Its working now.
>>
>> Does it make sense to get a more direct error message.
>> Something less scary, like "this looks like a svn branch.
>> use --development-subtree"?
> You don't need subtrees for branches originally created by bzr-svn. The
> error message above looks like a bug in bzr that should be fixed.
>
> Cheers,
>
> Jelmer
>
>

Thanks for confirming this Jelmer.
I have filed it here: https://bugs.launchpad.net/bzr/+bug/359393

A somewhat related question, are --development-subtree
and --development-rich-root both brisbane-core related? So,
if I want to try out brisbane core can I just upgrade to
--development-subtree for now and use it?

Regards,
Parth