This afternoon I ran into an issue that a lot of people probably don’t have which is the need to either use or test multiple SVN logins from the same computer. I manage a couple SVN repositories for a company and like to verify the SVN login credentials before sending the end user the information. The SVN repository is configured on a Linux server however most users use TortoiseSVN on Windows to login.
I recently upgraded the Project Management Software, which happened to be Redmine, for a company and after the upgrade I received some complaints regarding SVN not functioning properly. I initially thought there is no way that the upgrade caused an issue with SVN since SVN and Redmine are completely separate however you can browse the SVN repositories from within Redmine. Below I describe the error in more detail including an image of the error from TortoiseSVN, what I did to resolve the issue, and another possible resolution if your issue is different than the one mentioned in this article.
If you have been working on a project that is synced with the other developers using SVN which has recently moved don’t worry as you can update its remote repository location instead of trying to manually merge all of the file into a new copy of the repository. All you need to do is use the SVN switch command with the relocate switch.
TortoiseSVN Switch Relocate Described:The below is from the TortoiseSVN help files.
I beat my head on the wall for awhile with the below error because the information online was fairly limited. Let me start by saying that using TortoiseSVN as a SVN client for Windows will authenticate against a Linux server running svnserve using SASL DIGEST-MD5 encryption. This means you should be able to authenticate against svnserve set up with these options configured which are “use-sasl = true”, “min-encryption = 128”, and “max-encryption = 256”.
When all of this started my goal was to create a SVN server with one repo for testing. I upgraded from TortoiseSVN 1.5.2 to the latest stable build of TortoiseSVN which was version 220.127.116.112. I downloaded the latest stable release from the TortoiseSVN site here. Once installed everything was going fine with my original goal until I got to checking out the repository on my local PC.
TortoiseSVN uses a lot of system resources attempting to make sure that the SVN cache on your system is up to date. By default TortoiseSVN will attempt to keep all “Fixed Drives” up to date which will in most cases use a lot of unnecessary system resources such as CPU cycles and RAM. Below are two options to either cut down on the amount of resources used or to turn of the TortoiseSVN Status Cache all together.