Martin Bischoff wrote on Tue, Mar 25, 2014 at 11:42:05 +0100:
> Thanks a lot for the quick answer.
>
> One additional question:
> It seems that after the dump/create/load cycle, I have to manually copy the
> hooks, authz and passwd files to the newly created repository.
>
> Is that correct?
Yes.
Martin Bischoff wrote on Tue, Mar 25, 2014 at 09:34:50 +0100:
> My questions:
> - what exactly is error E160004?
"Corruption found". It's not specific to this problem; it's used for
nearly every error from verify (except for OS-level permission problems
and the like).
Thanks a lot for the quick answer.
One additional question:
It seems that after the dump/create/load cycle, I have to manually copy the
hooks, authz and passwd files to the newly created repository.
Is that correct? Are there other files I have to copy?
On Tue, Mar 25, 2014 at 11:11 AM, Philip
Martin Bischoff writes:
> I then started "svnadmin verify" on the repository, which reported the
> following error:
>
> * Verified revision 2112.
> * Verified revision 2113.
> svnadmin: E160004: r2114's root node's predecessor is r2112 but should be
> r2113
>
> These revisions were committed in 2
This morning some users reported a problem with our subversion server
(update/commit was not possible). Once I restarted the service (Collabnet
Subversion svnserve 1.8.5.34819), everything seemed to work again.
I then started "svnadmin verify" on the repository, which reported the
following error:
