I have been looking for a solution to my SVN problem but have not yet found one. We have been using svn for a number of years without problems but I have been unsuccessful adding a new project as of late.
SVN is installed on a central computer we use as a server running Windows 7. We have TortoiseSVN installed on our clients and on the server. To create new projects in the past we would log onto the server and execute svnadmin create [drive]:/archive/new project. We would then create the trunk, tags, and branches folders using the repo-browser. Once that was done we could use TortoiseSVN to import the code on our local machines to create the archive.
Now when I create a new project archive the client computers return the error: "Could not open the requested SVN filesystem". The repo-browser says the same thing. I can perform all of the usual SVN activities from the client computers on all of the existing repositories, just not on any new ones. Also, if I use the repo-browser on the server it works.
What I have done so far is uninstall subversion and TortoiseSVN from the server and reinstalled TortoiseSVN 1.9.4 along with the command line tools and recreated the svn service. I also updated TortoiseSVN to 1.9.4 so there shouldn't be any version conflicts but it still does not work. Since everything works as long as I am on the server I suspect the problem lies in the network access configuration but I don't know what would be different from when it was working.
Also note that when I try to browse the archive with Firefox I can navigate down into the project trees of the older projects but not any new ones. Firefox displays:
<D:error>
<C:error/><m:human-readable errcode="160043">Could not open the requested SVN filesystem</m:human-readable>
</D:error>
Any help will be greatly appreciated.
PS: Access to the repositories on the server is through Apache 2.2
1. Using file-type access to repository over LAN is always The Bad Idea (tm)
2. Source of your problem (except the above) is changing format of repository-storage between version and inability of old versions read directly repositories of new versions: your client's SVN is older, than server-side (and worse - use|know only old format of repo)
Check version on client's hosts (I suppose, they are pre-1.6) and
update to version, compatible with server's version (1.7+ for 1.9.*)
OR
add any real network layer (svnserve is easy and lightweight choice) for accessing repositories (don't use file:/// anymore) - in this case old clients can communicate with fresh repositories
OR
run svnadmin create with additional option --compatible-version and correct version number as ARG
This is Permissions&Ownership Problem. User, under which Apache is running, now can't read filesystem-tree, created by user, used for remote login. Ask local admin "WTF?" and fix errors
How to overcome SVN — could not open the requested SVN file system
SVN Error: Could not open the requested SVN filesystem
Could not open the requested SVN filesystem on windows7 (start from answer HERE!!!)
Related
Newbe to Team Services...
Vs2015 Desktop Community for original setup.
I stumbled through the setup of our ...visualstudio.com account and it is working on two PCs. I went down the GIT path but I'm not really clear on the process, I just kept banging on it until it worked. It is working (mostly) for two VB.Net WinForm projects on two PCs.
I'm now setting up a brand new PC and I installed VS2017. I didn't install any extra software for GIT (can't find any directions for source control install for that either, TS GIT quick start doesn't mention setting up GIT) I logged into the visualstudio cloud from the new install and cloned one of the projects from the cloud GUI. The files came down OK but the project type is evidently wrong because the Solution Explorer always lists all files and I can't open a form in the GUI. I also tried to use VS2017 to clone/download the project with the same result.
Do I need to install GIT in a fresh install of VS2017? Download from where/how to get a proper hookup with VS2017?
Why am I getting the files OK but the project type is not VB.Net Winform? Can that be tweaked or should I start over?
I was able to download using the .zip option from visualstudio.com but it isn't connected to a local or cloud repository. I'm not sure it is a good idea to connect these "out of band" files to an exisitng repository. The project is of the correct type and it builds OK and works.
Thanks!
View of solution in broken project:
It’s unnecessary to install extra software after you installed VS2017.
In short, use VS to work with git repo on VSTS (visual studio team services), you just need to connect your VSTS account in VS and clone a local repo as working copy for VSTS git repo. Operations in VS 2017 should be:
Connect your VSTS account in VS2017.
VS2017 -> team explorer -> manage connections -> connect to project.
If your VSTS account (sign up email address) hasn’t connected yet, click add an account. After that, you can select your VSTS project/repo to connect/clone.
Clone VSTS git repo locally.
If you didn’t clone git repo in step1, then right click a VSTS repo -> clone.
Work on the local repo.
After successfully cloned a repo, you are working on the local repo, you can also find the local repo’s name and branch you are working for in the right bottom of VS2017. Now the solutions should be same as what you find in VSTS.
And you can make change and commit for them. And then push your local commit(s) to VSTS git repo.
For VS2017, there are two forms to view solutions and files: solution related and all files/folders.
If you can’t find .Designer.vb and .resx files, you must use the second mode as the above graph.
To view all files/folder, you can switch the view to first mode as below graph.
How do I save/commit/push such that the network has the latest version?
I have never used version control before.
I am new to Visual Studio 2015 (I mainly used VS 2005).
I am a VB.net developer.
I am running Windows 10 and have a Windows 2008R2 Server (not AD).
I need to keep my code private and local (no cloud).
I will eventually need to have up to 3 developers collaborate with my code.
I am not a fan of using the command line unless I absolutely have to. (GUI for me).
I feel that version control should be integrated with Visual Studio.
I think the code should be stored on the server and a local (working) copy on my machine.
I believe I would benefit from using Git. (Not GitHub).
I may also check out Gogs or Bonobo. I hate Java so not (Gitblit)
I Installed Git on my server - although I'm not sure I needed to do this.
I have installed it on my local machine.
I mapped a shared directory (v:)
I have attempted (successfully - I think) to copy my code into a repository and make a few commits.
I thought I was having some success using the Visual Studio 2015 - Built-It / Extension
However, after attempting to use/create a local clone eg C:\Users\My User Name\Source\Repos
Making some changes, Commit All, Then attempting to Push I get the following Error:
"Failed to push to the remote repository. See the Output window for more details."
Output window says:
"Error encountered while pushing to the remote repository: Local push doesn't (yet) support pushing to non-bare repos."
I've read but not sure how to apply to VS Git push error '[remote rejected] master -> master (branch is currently checked out)'
PS. Because of my specific set-up/needs I’m struggling to find help. Any tutorial recommendations are welcome.
Sorry if this is too verbose.
I had many problems trying to solve this.
One of which was attempting to use the Network Drive as the Master when I Believe the local is the Master.
I am sure that I am to much of a noob with this (even now), however just because it may help someone try bonobo git server. This allowed me to create a LAN based Git repository on windows that I seem to have got to work.
I still think that my problem was trying to find good help that was relevant to what I was trying to do was lacking (or I was looking in the wrong places).
We have a productive GitLab 6.8.1 running. I've set up a parallel VM with GitLab 7.10.4. Now I want to move all data from the old installation to the new one. I've already found a way how to move the bare repositories, but I have no clue how to import the user account information, issues, etc.
EDIT: The thing is further complicated by the fact that the original installation was built from source, was running on Debian, used MySQL as a database and the whole installation was pretty much messed up. That's why I didn't manage to migrate the old server and decided to set up a new one. The new server is an Ubuntu machine with GitLab installed from apt-get package (I think that's Omnibus, but I'm not sure what this means.) The new installation seems to use PostgreSQL.
FYI You haven't specified whether the old or new server is running a source installation or omnibus, or whether you're running a MySQL or Postgres database. Instructions differ depending on these factors, so please clarify and I will update my answer.
The first thing is that you will need your old and new servers to be on the same version of GitLab. You cannot migrate anything other than repos without having synchronized versions.
Depending on your reply to the above you will either follow instructions similar to the backup and restore tasks or by running the backup and restore tasks. Both options generally require you to manually copy configuration files or migrate settings from multiple files to a single new file (in the case of going from a source install to Omnibus). The Omnibus upgrade guide above lists the configuration files that need to be migrated depending on your environment.
Update based on edited question: There's a guide specifically for that scenario in this section of the Omnibus upgrade guide, using Option 2. You still need to have the same version on both old and new servers, though, I believe.
I imported Apache Nutch source code into my local ubuntu installation. I have subversion installed on my eclipse kepler. The sourcecode has several branches and one main project in trunk. I was thinking of specifying this source-code location as my repo location to svn and check out & or commit changes based off of this. However SVN always seem to expect a remote repo location. Is there anyway I can make this dumping ground of apache nutch source code as my repo location for svn?
Thanks
DVCS systems may help, such as git, Hg, etc.
Subversion is a centerized version control system, all workspaces directly connect to center repository.
But DVCS have local repository, before you commit to remote repository, you need commit to local rep first.
Ok, perhaps I'm trying to accomplish something not doable.
I am a single developer (not part of team).
I'm trying to get some kind of versioning system going. I had used CVS with XCode 3, but XCode 4 no longer has that as an option. I've heard that SVN and Git are better alternatives anyway.
Basically, I've wasted more than half a day trying to get XCode to work with SVN / Git out of the box. I do not have a server running, and would rather not expose my project on a server.
It doesn't make sense for me to have a separate user just to run the Git/SVN Servers, either.
I'm just trying to have version control using either one, in the simplest possible way.
I've tried to add Repo, using local file path (/Volumes/AAA/BBB/Repo) where I manually created the "Repo" directory. I've set the type as Subversion (and also tried Git). XCode says "Host is reachable". But, the Commit functionality is not there (Disabled). I can't import my working directory.
I just don't get it - must I have a server running in order to have SVN/Git, or can XCode just do it through command line? I much more prefer it being done over command line, since the server is complete overkill. Or, am I missing something? Maybe I'm putting in the wrong settings into XCode?
This isn't strictly an XCode 4 issue, I had the same issue with XCode3, but at least it had the CVS option - now it's gone.
With Git you don't need a central server or even a central repository unless you have multiple people on the project. SVN requires you to have a central repo & server running all the time, but with Git you can simply git init a new repo and start using it. If you don't have a central repo you will never use push, pull, or fetch.
Xcode's help mentions the following:
Choose Git or Subversion Xcode supports two SCM systems: Subversion
(often abbreviated svn) and Git. Subversion is always server-based and
the server is normally on a remote machine, though it is possible to
install one locally. Git can be used purely as a local repository, or
you can install a Git server on a remote machine to share files among
team members. The Xcode 4 installer installs the Git and Subversion
tools when you select System Tools. If you are working alone, it’s
generally easiest to use Git, as you don’t need to set up a server. In
fact, Xcode can automatically set up a Git repository for you when you
create a new project (see “Create a Git Repository For Your New
Project”). For a group project, the choice of Subversion or Git is
usually a matter of taste and prior experience. In so far as is
possible, Xcode provides a consistent user interface and workflow for
users of either Subversion or Git.
So the official advise is that in your case, Git is the easiest solution. I'm now in the same position as you described and will be trying Git as advised.
Previously, when working for a small company, we used a dedicated leftover MacMini as an SVN server; this was quite easy to set up, and worked like a charm for many years. Be aware that the SVN integration of Xcode 3 was better than that of Xcode 4 though, so that I ended up using Xcode 4 for development and basic SVN usage, together with Xcode 3 for SVN stuff that Xcode 4 wouldn't do anymore.