Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <937EE7E4E8E0B946AB0E7049C379DC8EE9F00695@IRNTSV-MBX1.ifp.fr>
References: <937EE7E4E8E0B946AB0E7049C379DC8EE9F00623@IRNTSV-MBX1.ifp.fr>
	<trinity-486dd127-055d-40be-80cb-05e0fb63622c-1448626152114@3capp-gmx-bs03>
	<937EE7E4E8E0B946AB0E7049C379DC8EE9F00695@IRNTSV-MBX1.ifp.fr>
Date: Fri, 27 Nov 2015 08:35:02 -0500
Message-ID: 
 <CAOCN9rwRQoohEADkNnn5Kpp9tcRujgYVvdLAeih6wEUw=jiZhg@mail.gmail.com>
Subject: Re: restore error svnadmin: E160013: File not found
From: Nico Kadel-Garcia <nkadel@gmail.com>
To: MOKRANI Rachid <rachid.mokrani@ifpen.fr>
Cc: Andreas Stieger <Andreas.Stieger@gmx.de>,
	"users@subversion.apache.org" <users@subversion.apache.org>
Content-Type: text/plain; charset=UTF-8

On Fri, Nov 27, 2015 at 7:59 AM, MOKRANI Rachid <rachid.mokrani@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-revisions
> http://www.wandisco.com/svnforum/forum/opensource-subversion-forums/general-setup-and-troubleshooting/5377-missing-revisions-problem-svnadmin-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".