[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: MOKRANI Rachid <rachid.mokrani_at_ifpen.fr>
Date: Fri, 27 Nov 2015 14:57:55 +0000

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)

Many thanks.

 

-----Message d'origine-----
De : MOKRANI Rachid
Envoyé : vendredi 27 novembre 2015 15:21
À : users_at_subversion.apache.org
Objet : RE: restore error svnadmin: E160013: File not found

Thanks for your answer.

this is a good approach to replace svnadmin dump / load by hotcopy? I have never done that.

On the server with svn 1.6 release I'll be able to $ svnadmin hotcopy my_repo /tmp/my_repo_copy

and after moving the copy from my old server /tmp /my_repo_copy to the new SVN server with version 1.8

Is this a good approach?

-----Message d'origine-----
De : Nico Kadel-Garcia [mailto:nkadel_at_gmail.com] Envoyé : vendredi 27 novembre 2015 14:35 À : MOKRANI Rachid Cc : Andreas Stieger; users_at_subversion.apache.org Objet : Re: restore error svnadmin: E160013: File not found

On Fri, Nov 27, 2015 at 7:59 AM, MOKRANI Rachid <rachid.mokrani_at_ifpen.fr> wrote:
> Hi,
>
> After reading the URL below, this is the only way I've found to do a
> complete dump of my repo with a lot of missing revisions
>
> http://stackoverflow.com/questions/15474513/svn-fix-or-remove-broken-r
> evisions
> http://www.wandisco.com/svnforum/forum/opensource-subversion-forums/ge
> neral-setup-and-troubleshooting/5377-missing-revisions-problem-svnadmi
> n-dump
>
>
> Regards.

Those look like useful scripts. I'd run them with a "nohup" to keep a copy of both stdout and stderr to in a local record, in case of missed errors.

There is also a point, when you're doing things like discarding revisions, that you need to consider "do I want to keep this whole thing and ofrce people to reload all their working copies, to skip the discarded revisions correctly? Sometimes, when people have committed bulky and unnecessary binaries or re-arranged and re-arranged the structure, or when there's a lot of broken old code or code with embedded plaintext passwords, that you can reasonable say "just export the specific working directories to a new repository, with no history, and add a README that says where the old repository is".
__________________________
Avant d'imprimer, pensez à l'environnement ! Please consider the environment before printing !
Ce message et toutes ses pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. IFP Energies nouvelles décline toute responsabilité au titre de ce message. This message and any attachments are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. IFP Energies nouvelles should not be liable for this message.
__________________________
Received on 2015-11-27 15:58:16 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.