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.
svn update brings changes from the repository into your working copy. If no revision is given, it brings your working copy up to date with the HEAD revision. Otherwise, it synchronizes the working copy to the revision given by the --revision ( -r ) option.
Subversion is pretty smart about updating and never just overwrites files that have local changes with copies from the repository. The most important thing to take away from this section is: If you collaborate with others on one repository, remember to update your working copy regularly.
If you want more control over the update process, you should use TortoiseSVN → Update to Revision... instead. This allows you to update your working copy to a specific revision, not only to the most recent one.
Examples. Use the svn upgrade command to upgrade the working copy to the most recent metadata format supported by your version of Subversion.
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..
Back up the working directory
Delete the .svn directory under the top working directory
Check out the entire working directory.
Worked for me...
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With