RE: [TSVN] Error using 1.2 nightly on local 1.1 repository

Molle Bestefich wrote:
> Jean-Marc van Leerdam wrote:
>> Normally one can simply run svnadmin recover to upgrade a Berkeley DB
>> repository in-place. However, due to a bug in the way this command
>> invokes the db_recover() API, this won't work correctly when
>> upgrading from BDB 4.0/4.1/4.2 to BDB 4.3.
>>
>> Use this procedure to upgrade your repository in-place to BDB 4.3:
>>
>> * Make sure no process is accessing the repository (stop Apache,
>> svnserve, restrict access via file://, svnlook, svnadmin, etc.)
>>
>> * Using an older svnadmin binary (that is, linked to an older
>> BerkeleyDB):
>> 1. Recover the repository: 'svnadmin recover
>> /path/to/repository'
>> 2. Make a backup of the repository.
>> 3. Delete all unused log files. You can see them by running
>> 'svnadmin list-unused-dblogs /path/to/repeository'
>> 4. Delete the shared-memory files. These are files in the
>> repository's db/ directory, of the form __db.00*
>>
>> The repository is now usable by Berkeley DB 4.3.
>
> If you're lazy, you can also use the new binaries and first 'svnadmin
> recover' (will print an error) and after that 'svnlook youngest'. It
> will also work, but keep a backup handy just in case. The safe way
> to do it is of course the above.

Can you explain why this better than the approach I took:
1) svnadmin dump repo-path > backup
2) delete repo
3) create new repo
4) svnadmin load repo_path < backup
5) keep the backup around 'just in case'
I'm sure I'm missing something here.

Bill

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
*** Confidentiality Notice *** Proprietary/Confidential
Information belonging to CGI Group Inc. and its affiliates
may be contained in this message. If you are not a recipient
indicated or intended in this message (or responsible for
delivery of this message to such person), or you think for
any reason that this message may have been addressed to you
in error, you may not use or copy or deliver this message
to anyone else.  In such case, you should destroy this
message and are asked to notify the sender by reply email.