I have better news for you
Subversion store all history between changes.
When you accidently svn copy
you added additional commit into destination branch. You can
svn up GOODREV
to good commit (or svn co BRANCH@GOODREV
into fresh WC) and commit (minor edit-save-commit) on top of bad
- Undo bad commit by reverse-merge
For svnadmin dump
You have to identify, are these backups incremental (--incremental) or full. In case of full you have to find backup, in which GOODREV exist, svnadmin load
this dump into new repo, svn copy
from NEW-REPO branch to OLD-REPO branch, kill restored repository
Hint: you have to learn repository administration better: pp. 4-5 is just delirium - SVN repository have absolutely different file-tree and repostory's subtree doesn't exist as physical tree of same structure (and .svn files are Working Copy attribute and storage of WC-metadata)
Bust logical and better (than your) usage of svndump is, again, different. If you still want hide your error from eyes, you have
- Create new, full dump for the range of revisions (-r LOWER:UPPER option), which will exclude BADREVISION.
- Disable all connection
- Remove old repository (rm REPODIR + mkdir REPODIR)
- Restore repo from dump