Subversion 1.6.6 Error "Could not open the requested SVN filesystem" - linux

I am running ubuntu server with Subversion 1.6.6.
In windows I use the latest Tortoise SVN compiled against Subversion 1.6.6.
I create a new Repository and when I attempt to view the repository or import my files and get the following error:
"Could not open the requested SVN filesystem"
I can view the repositories via the command line (as root) but want to view them in Tortoise. Some repositories however are fine and I can view and comit without any problem via Tortoise.
I am sure its a user / permission thing but not sure where to look?
Any suggestions are greatly accepted.
Thank you

How do you access the repository on your server? If you're using file:///, that won't work since the repository format isn't compatible between OS. You have to use either svn:// or http(s):// to access the repository (and set up the corresponding server app).
If you're already using svn:// or http:// to access the repository, you can check the apache error log or run svnserve in console mode to get more detailed error messages.
your repositories must have full read/write access for the user who runs the server (svnserve or apache).

I ended up perforoming a repository dump then re-installing ubuntu, subversion, then installed USVN (great app). I next restored the repository from the dump. Everything is working great now.

Related

Subversion not authenticating when using Android Studio

This is a follow up question to this question:
Android Studio can't authenticate with SVN
I got an Android project which I used in Eclipse and I just converted it to a working AS project. When using Eclipse, the SVN works fine. When using AS for some reason, every time I try to commit or update, I get a prompt asking for my user name and password and it keeps repeating itself without ever succeeding. When I press cancel I get this error:
Error:svn: E170012: When using svn+ssh:// URLs, keep in mind that the --username and --password options are ignored because authentication is performed by SSH, not Subversion
svn: E170012: Unable to connect to a repository at URL 'svn+ssh://...
svn: E170012: Can't create tunnel
svn: E720002: Can't create tunnel: The system cannot find the file specified.
What I tried until now was Uncheck follow two items
Use command line client
Use system default Subversion configuration directory
Also, I tried editing the servers file in the SVN config's folder with:
store-passwords = yes
store-ssl-client-cert-pp = yes
store-plaintext-passwords = yes
store-ssl-client-cert-pp-plaintext =yes
What else can be done?
I ended up just checking out the project again to a new folder even without setting all the things I wrote in the question and everything started working

Git Configuration with eclipse--not able to push code from eclipse to remote git server

1)I have just configured GIT on my local centos 6.4 server and created a repository
2)Generated key also and kept at server
2)I am able to checkout code from this remote server to my dev machine in eclipse no problem till here
But when I tried to push code from Eclipse the it always says that "Can't connect to any repository: ssh://homepage#1.1.1.1/var/git/demo/ (An internal Exception occured during push: ssh://homepage#1.1.1.1/var/git/demo/: error occurred during unpacking on the remote end: unpack-objects abnormal exit)"
Not sure why ? Is there anything which i missed ?
I fixed the problem by changing the permission on the directories
It's definitely a permissions issue on the repo. I had the same problem, but was using Netbeans. Managed to temporarily fix it by giving 777 permissions to the repo.
I also experienced this. It was due to something else, a bit stupid, really. I put a bare repository inside of a bare repository and expected them to behave individually. Once I moved the file structure of the inner bare repository out, it worked.
I just had to change the remote configuration of the local repository to point to the new location (outside of the other repo).
I faced the same issue when checking into Git via Eclipse (EGit). The root cause turned out as space crunch on Git server. After deleting some unused projects we were able to checkin the code.

SVN Commit error: Can't open file txn-current-lock Permission denied

I can do checkouts, update and such. But when I try to commit changes, SVN gives me the following error:
Can't open file '/svn/p/pokemonium/code/db/txn-current-lock': Permission denied
I am using Windows 7 x64 SP1 with latest version of TortoiseSVN.
UAC is off, my account has read and write access, etc.
I can commit fine to other svn repositorys.
For me it ended up being a permissions issue on the server. I have my repo on a linux box, and ssh in to use svnadmin. For convenience sake, I had executed my create repository command as root. I was looking to get source I had on my Windows box into the repo, so was using TortoiseSVN to set up trunk/branches/tags. The directory containing the repo on the server was owned by root, and Tortoise was coming in as apache. I chowned the directory on the server to apache:apache, and it all went smoothly.
chown apache:apache -R my_repo_root
This is a server configuration issue. On windows host Visual SVN server runs under NETWORK SERVICE account by default. I solved this problem by granting full access rights to the repository folder to this account. Another option is switching Visual SVN service to the SYSTEM account, but that could pose a potential security risk.
Try this.
Make a back up copy of your working copy (just to be safe).
Make another copy your entire working copy off somewhere else.
Take the copy and delete all of the SVN folders out of it
Delete your working copy and do a fresh checkout
now copy/paste your corrupted working copy over your fresh checkout.
it is critical for this to work that you have completely removed ever _svn or .svn folder from your corrupted working copy before you perform the copy/paste.
This will leave you (hopefully) with a working copy that shows (!) on all the files you had modified since your last commit. And fixes your lock issue.
I had the same problem after I re-installed Windows 7 and just copied the SVN Repository from the old Windows to the new one.
After trying the steps that Mr. Manager proposed, the problem was still not fixed in my case.
After making sure that the permissions was setup correctly for the SVN Repository folder I just deleted the file 'txn-current-lock' in the /db folder of the project. That fixed it for me. From thereon I could commit my project again.
I had faced same issue on Unix box
Restarting the Apache service of the SVN server solved myproblem.
-f httpd.conf -k stop
-f httpd.conf -k start
In my own case, my linux server had been restarted after a power loss. The file system remained mounted as read-only since some journal repairs had been made. Rebooting the machine restored full function.
permissions worked for me too
error
repo/db/txn-current-lock: Permission denied
fix
chown apache:apache -R my_repo_root

Copying files from svn repository

I wanna copy files and folders from my svn repository on server, but I dont want to install svn client, can I do it without svn client?
PS server - linux (CentOS 5.5), svnadmin version 1.4.2 (r22196)compiled Aug 10 2009, 17:54:46.
UPD: files are already exported to server: I want to import files from svn repository to directory, where web-server runs. For example: svn repository located at /var/svn/repos, I wanna dump repository to /var/www, but in /var/svn/repos no files I needed.
PSS sorry for my bad english =\
The Subversion repository isn't in a readable format that you can peruse like you could with CVS. To read the files in the repository you need someone with a client somewhere.
If your Subversion repository uses Apache httpd for its server, you can use wget or curl to pull off the last revision on a specific directory since as an added bonus, the Subversion Apache httpd modules allow you to see the latest version.
$ wget http://svn/repos/foo/trunk/myfile.java
The other option is to use a Subversion repository browser like (ViewVC)[http://www.viewvc.org/] or Sventon. These will allow you to browse the entire repository (including older revisions) without having to install the Subversion client on the local machine. I like Sventon because it doesn't have to run from the Subversion repository server.
If you're on Centos 5.5, you should already have the Subversion command line client installed on your system. In that case, if you don't want the .svn directories, use the svn export command instead of svn checkout.
Or, setup your web server to ignore the .svn directories. That way, you can do an svn update and update the files on your web server without having to redownload everything.
Well, if you have physical access to the server you could use the Subversion client on that box to export files/folders and then copy them from the server to the client machine. If you're trying to do this purely from the client, the only way I can think of would be to manually download the file(s) from the web client but this will only work if you're using Apache as your Subversion server.
Unless the server has an HTTP interface (is the repository URL prefixed with http://? Just open it up in a web browser), no.
It might be simplest to export the files you want on the server (svn export file://repo/path/to/directory), then copy them to the client using http or scp or something.

SVN checkout over secure http fails with Memory Fault

I built subversion client (1.6.5) along with its required dependency libs on SuSe 10.
I am trying to access our central repository server over https a secured URL.
But when i run the svn checkout command giving proper credentials it gives me memory fault.
What is that i have missed in building SVN or is that something to do with set up # client side?
I run make check to confirm the subversion client build, firts 30 tests is succesful.
And also svn co over http:"URL" errs out with proper message for we do not have any repository over that URL.Does this mean the build is good but something to do with openssl library configuration?
svn --version gives what all clients it supports and found that it was supporting only http.I rebuilt the subversion with correct config options and currently has following options:
svn, version 1.6.5 (r38866)
compiled Sep 8 2009, 18:05:39
Copyright (C) 2000-2009 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).
The following repository access (RA) modules are available:
ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
handles 'http' scheme
handles 'https' scheme
ra_svn : Module for accessing a repository using the svn network protocol.
handles 'svn' scheme
ra_local : Module for accessing a repository on local disk.
handles 'file' scheme
ra_serf : Module for accessing a repository via WebDAV protocol using serf.
handles 'http' scheme
- handles 'https' scheme
but still no luck.I will be creating a local and http repository to check the same.
Have you tried installing a pre-built binary? Does it give you any other errors? Hard to determine your problem without more details ... plenty of people use the SVN client on SUSE Linux without any problems.
I had to rebuild openssl with "no-asm" configuration setting and subversion started working for "https" repository.

Resources