subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nico Kadel-Garcia <nka...@gmail.com>
Subject Re: restore error svnadmin: E160013: File not found
Date Sat, 28 Nov 2015 04:30:38 GMT
On Fri, Nov 27, 2015 at 10:27 AM, Philip Martin
<philip.martin@wandisco.com> wrote:
> MOKRANI Rachid <rachid.mokrani@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".

Mime
View raw message