I've a repository that's grown incredibly big and we're going to start
breaking out each project in the repo to separate repos. However I've
ran into a couple of issues in regards of Node-copyfrom-rev which
doesn't match up properly upon dump/load resulting in the following:
svnadmin: E160006: Rel
> I've a repository that's grown incredibly big and we're going to start
> breaking
> out each project in the repo to separate repos. However I've ran into a couple
> of issues in regards of Node-copyfrom-rev which doesn't match up properly
> upon dump/load resulting in the following:
>
> svnadmi
As mentioned, the repository is incredibly huge and it would take hours for
each project.
On Fri, Mar 1, 2013 at 7:36 PM, Bob Archer wrote:
> > I've a repository that's grown incredibly big and we're going to start
> breaking
> > out each project in the repo to separate repos. However I've ran
Guten Tag Jonathan Petersson,
am Freitag, 1. März 2013 um 19:54 schrieben Sie:
> As mentioned, the repository is incredibly huge and it would take hours for
> each project.
That's no reason at all, your computer is doing all the work. How many
hours did you try to implement your own solution to
I am going through a similar process myself and have some questions about
your concerns. I'm not trying to rock the boat, just looking fo clarity on
a few
points.
For perspective, I am working with around 300 individual projects
in a 70+ Gb repository containing over 300k revisions.
> If I und
Guten Tag Bryon Winger,
am Dienstag, 2. April 2013 um 23:32 schrieben Sie:
> Are you saying that appending to an existing dump file in general is a
>
> problem or just with all of his node-path processing? I have had no
>
> trouble appending to existing dump files.
I don't know if appending
Subject: Re: Splitting out project from repo
I am going through a similar process myself and have some questions about
your concerns. I'm not trying to rock the boat, just looking fo clarity on a few
points.
For perspective, I am working with around 300 individual projects
in a 7
> You probably still want the svndumpfilter processing to drop empty
> revisions before loading it in a new repository.
>
I believe that the current version of svndumpfilter only operates on
version 2 dump streams - which svnadmin dump produces. svnrdump
produces a version 3 dump stream
>
> for rev in `svn log -r0:HEAD ${url}/${project} | \
>
> egrep "^r[0-9]+ |" | cut -d " " -f1`; do
>
>svnrdump dump --incremental -r ${rev:1} ${url}/${project} >>
> ${project}.dump
>
> done
>
Basically, I am only dumping (incrementally) the revisions which actually
>
