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).
Guten Tag Tomas Javurek,
am Dienstag, 25. März 2014 um 16:52 schrieben Sie:
> svn: Commit blocked by pre-commit hook (exit code 1) with
> output:
> Some parts of your commit look suspiciously like merge
> conflict markers. Please double-check your diff and try
> committing again.
There is no bug
Hi svn developers,
once I tried to commit txt file with these two lines:
RUNNING:
===
written inside, I got following error message:
[tjavurek@lxplus0057]~/pMSSM/BooFactory/Tools2% svn ci -m
"" error.txt
Sendingerror.txt
Transmitting file data .svn: Commit failed (details
follow):
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:
