We used to have a shared SVN repository for several projects and yesterday, our SVN admin created a new SVN repository specific to our project.
I relocated my existing checkout of the project to the new SVN repository but now, when I make a SVN update, I get an error message like "No such revision 223297".
Indeed, the new repository has only the number of revisions specific to our project (around 33000 commits) while the old one had 223400.
I would like to know if it's possible to switch all my existing checked out folders to the new repository? Otherwise, I will have to do some clean checkouts.
Obviously your admin failed to include padding revisions which usually is highly recommended when using svndumpfilter to split repositories.
Otherwise it is absolute impossible to update your working copy with your repository, as SVN orients itself on revision numbers and your repository is (technical speaking) a different repository(usually the UUID of the repository should not match as well.. another quirk which should be fixed by your admin). Also if you use external tools like bugtracker which are saving the revision numbers to link contents to your sourcecode, these references are lost as well.
The best solution would be to redo the repository creation without svndumpfilter switch --drop-empty-revs however, then your work in your new repository is lost..