Try doing a SVN Cleanup. I had the same issue and after doing that the locks cleared up. Specifically from the Tortoise SVN Cleanup Documentation: If a Subversion command cannot complete successfully, perhaps due to server problems, your working copy can be left in an inconsistent state. In that case you need to use TortoiseSVN … Read more
Yes you can! http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packages The current NuGet workflow has always been to commit the Packages folder into source control. The reasoning is that it matches what developers typically do when they don’t have NuGet: they create a ‘Lib’ or ‘ExternalDependencies’ folder, dump binaries into there and commit them to source control to allow others to … Read more
this answer can be confusing do read the comments attached to this post and make sure this is what you are after ‘svn delete’ works against repository content, not against the repository itself. for doing repository maintenance (like completely deleting one) you should use svnadmin. However, there’s a reason why svnadmin doesn’t have a ‘delete’ … Read more
No, you just have to search for all .svn folders and delete them. Alternatively, doing a svn export allows you to get the folder without the svn folders.
The secret is to make sure it’s on the ignore list before you commit the delete. If you do it in that order, the delete won’t propagate to others’ working copies. We’re still using svn 1.4 so the –keep-local option isn’t available. But you can achieve the same thing by deleting it using a server … Read more
Take a look at Boar, “Simple version control and backup for photos, videos and other binary files”. It can easily handle huge files and huge repositories.
git svn uses SVN commands directly and thus the internally saved password of SVN. Run the command: svn checkout –username user –password pass svn://server/repo and let SVN remember your password. If this does not work remove the saved SVN authentications: $HOME/.subversion/auth/svn.simple/* Then git svn clone will prompt you for the password.
There are two ways with subversion, one is specific to the user and the other is actually maintained in the repository, and therefore affects everyone. For a list of globally ignored files (exclusive to each user/machine), you need to edit the subversion config file and alter the global-ignores directive in the miscellany section. The config … Read more
I ended up having to delete the auth directory all together and allow Subversion to rebuild it for me. Nothing else seemed to work. For anyone who doesn’t know, the auth directory is in ~/.subversion (Mac/Linux).