I am using AnkhSVN v2.5 and TortoiseSVN 1.9.4
I am not able to browse through the directories on my local drive.
Running as administrator didn't help either. However when using VisualSVN the issue is resolved.
Unfortunately, I can only use AnkhSVN, please help.
TortoiseSVN 1.9.x is based on Subversion 1.9. Local repository it creates and that you access via file:/// has FSFS format 7, by default. This FSFS format is new in SVN 1.9; SVN 1.8 and older clients and servers will not be able to read this repository unless you dump-load its data into an clean repository with older format.
AnkhSVN 2.5.x is based on SVN 1.8 (via SharpSVN) and this explains why it is unable to access this repository. The problem is that AnkhSVN does not display full error message in your case. The error could help you find out what's going on. I'm not sure, but I guess that this is the error that AnkhSVN had to display in your case: svnadmin: E125006: 'REPOS\db\format' contains invalid filesystem format option 'addressing physical'.
These steps should help you solve the problem:
Install VisualSVN Server or another Subversion server on Windows and access your repositories via HTTP(S) or svnserve instead of local file:/// access. The repository internals will not matter for your client in this case as the client will communicate with the server, not with the repository directly. This will help you avoid such problems in future.
Update to AnkhSVN 2.6.x. It should be compatible with SVN 1.9.x and Visual Studio 2012. I guess will access that repository without errors. I'm not sure, but I guess that there is no practical reason to use older AnkhSVN builds.
Related
I have a Windows Server 2012 with an active repository on VisualSVN version 3.3.1.
We want to copy this to a new VisualSVN Server instance version 5.1.0 on a Windows Server 2019 and replace the old server.
Is there a way to duplicate the repository completely and with all permissions etc. and import it on the other server?
We have already done it with the commands
svnadmin dump REPOS_PATH [-r LOWER[:UPPER]] [--incremental] [--deltas]
and
svnadmin load REPOS_PATH [-r LOWER[:UPPER]].
However, it does not retain the permissions and locks here.
Also, I found a post saying to only copy the files in the repository directory but I am not sure whether this is the right and correct way: Post
Migrating VisualSVN Server
You don't need to use svnadmin dump and svnadmin load when migrating VisualSVN Server onto a new server computer.
You should not mix up the server migration and upgrade tasks. They have to be approached separately if you plan to migrate the server and all repositories from one computer to another. Normally, you need to either to upgrade your existing server installation to the latest version and then upgrade, or upgrade you existing server installation and upgrade later.
Migration instructions are given in the article KB166: Migrating VisualSVN Server to another computer.
Upgrade instructions are given in the article KB204: Upgrading to VisualSVN Server 5.1.
Migrating a repository
You don't need to use svnadmin dump and svnadmin load when importing only one or a few repositories onto another VisualSVN Server installation.
If your task is to migrate the server with all the repositories, see the section above.
When you want to import an individual repository from another server installation (without needing to migrate the server itself and all other repositories), you need to follow the instructions from the article KB10: Importing Repositories into VisualSVN Server:
Create a backup of the repository and restore it on the new computer.
or
Copy the directory of the individual repository onto a new computer and import it.
Repository settings including user permissions and hook scripts will be retained with both approaches.
We are working on Xcode Project connected to our local TFS 2013 (Update 3) Server via TFS Provided Git Repository.
When we use older version of Xcode, we are successfully able to check-in the files and perform all other Git operations. We are also able to perform all Git Operations via command line Git.
The trouble is when we use latest version of Xcode - Version 7.1 (7B91b).
On entering valid credentials, we are getting error saying
Authentication failed because the user name or password was incorrect.
The same credentials / configuration work on older version of Xcode and Git Command Line Options.
To add more to the surprises, we are able to connect to github.com successfully.
We are able to reproduce issue on other systems too. Please provide us the best way to resolve this error.
For us it turned out to be because Xcode 7 does not support Windows Authentication. The solution described here solved it for us:
"This happens because XCode 7 doesn't support Windows Authentication.
I don't know why. It seems to be a common problem amongst users
because there are many posts about it in google.
To make it all work you should enable Basic Authentication in your IIS
TFS website on "tfs" virtual folder.
Be careful though because basic authentication sends your credentials
over network as plain text. You definitely must use SSL in this case."
(source)
I am setting up SVN for a programming project. I downloaded the binaries, set my PATH variable and can now use SVN from my command line.
After installing a plugin for VS2015 (VisualSVN) it informed me, that i did not install TortoiseSVN and am losing some functionality. I never heard of it so i googled it and it says, that TortoiseSVN is a client that incorporates SVN into the windows explorer.
Now i am kinda confused. Can i work with the binaries only, using the command line (clone repo, commit, push, pull, etc), or do i have to install some kind of enhanced client?
The command line utilities can do everything you mentioned. VS2015/VisualSVN is telling you you could have greater integration with the IDE if you had TortoiseSVN installed. I install them both on my machine. Sometimes the CLI is better and sometimes the GUI is better depending on what I'm doing.
I have been using Tortoise SVN in windows using a local repository(copy also available in dropbox). Now for sake of work I have to migrate to Mac OS. Tortoise SVN is unavailable for mac and hence I decided to use SmartSVN. I have copied the Tortoise repository to my mac system. However I am not sure how (If it is even possible) to checkout the project files using SmartSVN.
Also is it possible to browse the tortoise repository using smartsvn.
Please advice.
PS: I am new to Mac and not experienced with smartsvn.
Regards
Just point SmartSVN to the repository using file:// access scheme. It doesn't matter whether it's TortoiseSVN, SmartSVN or a command-line client -- the repository itself is a regular Subversion repository and neither of these tool should have any issues accessing it.
Running on Windows Server 2008 R2 with Windows 7 client.
I downloaded and installed VisualSVN Server 2.5.2 without a problem. The page here indicates that this is built against Subversion 1.7.2.
I downloaded and installed TortoiseSVN 1.7.3 without a problem. The page here indicates that this is built against Subversion 1.7.2.
Now I would like to install ankhsvn for use with Visual Studio 2010. The latest version is 2.3.10509 and the page here indicates that this is built against Subversion 1.7.1.
Does anyone know if this will run correctly against my SVN server? Or do I need to wait until ankhsvn release a version built agains SVN 1.7.2? If I need to wait, how promptly do ankhsvn releases usually appear?
Source control is obviously critical so I don't want to risk losing any data by "just trying it".
Subversion versioning requires clients to have the same minor version. So any 1.7.X client should be compitable with every other 1.7.Y client.
For the server, any 1.X client will work with any 1.Y client.
Of course it's a good idea to keep things as up-to-date as possible, but you're not risking anything by combining 1.7.1 and 1.7.2.
The release of AnkhSVN based on 1.7.2 will be out in the coming days, the daily builds are already using this.
From what I'm aware of, we had to upgrade SVN on our servers to be compatible with the latest version of ankhsvn. It was a big deal, for the leads let us know we couldn't use ankh until we updated.
We are also using Tortoise.
Hope that helps.