[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: restore error svnadmin: E160013: File not found

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Fri, 27 Nov 2015 23:30:38 -0500

On Fri, Nov 27, 2015 at 10:27 AM, Philip Martin
<philip.martin_at_wandisco.com> wrote:
> MOKRANI Rachid <rachid.mokrani_at_ifpen.fr> writes:
>
>> Oups...i think i need to do an upgrade.
>>
>> And on the new server with SVN release 1.8 I need to do :
>>
>> svn upgrade my_hotcopy_repo
>>
>> Is it a good approach ? (actually dump/load is not working for me)
>
> You can run "svnadmin upgrade" but you do not need to:
>
> http://subversion.apache.org/docs/release-notes/1.8.html#compatibility
>
> "There is no need to dump and reload your repositories. Subversion 1.8
> servers can read and write to repositories created by earlier versions"
>
> However your repository is corrupt and it is hard to predict exactly
> what will work and what will fail.

I think a hotcopy, brought over theo the Subversion 1.8 server, has a
better chance of being able to dump and reload and upgrade from that
revision. There can be differences between "bad revision that can't be
salvaged with an up-to-date software version", and "confusing revision
that svnadmn dump is having trouble dumping cleanly".
Received on 2015-11-28 05:30:52 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.