I'm subversion beginner user and I have created a server on my raspberry pi.
And the service is running.
I would like to checkout, commit, ... but I'm trying to commit with this syntax:
svn checkout 192.168.2.18/repository
svn checkout snv://192.168.2.18/repository
so the response is:
Unable to connect to a repository at URL 'svn://192.168.2.18/repository'
I'm thinking that I don't use the good syntax.
Can you help me please?
Thanks
Related
I have been using git-svn for a few months now as an interface to the SVN repository for my company.
However, about a week ago my company changed their policy such that SVN is only reachable if connected by way of Cisco VPN.
I have no trouble connecting to VPN on my Linux Mint VM (which is where I do my coding), but I am now no longer able to pass authentication when I, for example, run git svn dcommit to checkin code changes.
I have tried:
rm -rf ~/.subversion, to get rid of any saved SVN authentication credentials and force it to take new ones, but this seems to have no effect, nor does it ever prompt me for fresh credentials, surprisingly.
starting in a freshly created directory and running git svn clone to initiate a new link to the SVN repository, but with the same authentication failures.
Here is what I see when running git svn dcommit or git svn clone:
$ git svn dcommit
Committing to https://<redacted>:2443/svn/LS/branches/PRODUCTION-SUPPORT-1/ls-policygen ...
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-wCQwzG/pkcs11: No such file or directory
Authorization failed: OPTIONS of 'https://<redacted>:2443/svn/LS/branches/PRODUCTION-SUPPORT-1/ls-policygen': authorization failed: Could not authenticate to server: ignored NTLM challenge, rejected Basic challenge (https://<redacted>:2443) at /usr/local/libexec/git-core/git-svn line 943
The gnome-keyring warning has always been present, and never stopped commits before VPN was required.
take a look at this snipped from your error code:
Authorization failed: OPTIONS of 'https://<redacted>:2443/svn/LS/branches/PRODUCTION-SUPPORT-1/ls-policygen': authorization failed: Could not authenticate to server: ignored NTLM challenge, rejected Basic challenge (https://<redacted>:2443) at /usr/local/libexec/git-core/git-svn line 943
specially at this part: Could not authenticate to server: ignored NTLM challenge
It looks like your company also changed autentication methods too.
Take a look at: Does git clone work through NTLM proxies?
I would take this steps:
connect to your repository within your browser
try to connect with another user account - probably you have some cache files in your home directory
configure git or even svn according to NTLM auth
Good Luck,
LEslie
We have own linux server, with a git server. But for some reasons we create bitbucket account (private repos) and now we want use it as "backup".
Now i want set when someone push code on own server -> server make other push on bitbucket.
It is possible? Has someone script for this or some idea .....?
I believe you can do this via git post-receive hook.
I am attempting to follow http://mondrian.pentaho.com/documentation/developers_guide.php in the download and compilation of the Mondrian source code.
I have installed the P4V client from www.perforce.com/downloads/complete_list on a fresh install of Windows 7 and configured it for:
host: perforce.eigenbase.org
port: 1666
All I seem to be able to get is "TCP Connection to perforce.eigenbase.org:1666 failed. connect: 72.14.190.177:1666: WSAECONNREFUSED"
I did also attempt to "telnet perforce.eigenbase.org 1666" and received the same type of error.
Has the repository moved contrary to the documentation? or am I using the wrong Perforce Client?
Any provable direction would be appreciated.
I think that mondrian is now hosted on github, it was migrated from perforce a few months ago. Maybe ping them to update the doco..
I am the CM person for a small company that just started using Git. We have two Git repositories currently hosted on a Windows box that is our all-purpose Windows server. But, we just set up a dedicated server for our CM software on an Ubuntu Linux server named "Callisto".
So I created a test Git repository on Callisto. I gave its directory all of the proper permissions recursively. I had the sysadmin create a login for me on Callisto, and I created a key to use for logging in via SSH. I set up my key to use a passphrase; I don't know if that could be contributing to my problems? Anyway, I know my SSH login works because I tested it through puTTY.
But, even after hours of trials and head scratching, I can't get my Windows Git bash (mSysGit) to talk to Callisto for the purposes of pushing or pulling Callisto's git repository files.
I keep getting "Fatal error. The remote end hung up unexpectedly." And I've even gotten the error that Git doesn't recognize the test repository on Callisto as a git repository. I read online that the "Fatal error...hung up unexpectedly" is usually a problem with the server connection or permissions. So what am I missing or overlooking here? And why doesn't a pull using the git:// protocol work, since that only uses read-only access? Group and public permissions for the git repository's directory on Callisto are set to read and execute, but not write.
If anyone could help, I would be so grateful. Thank you.
If you use putty/pageant, check if your host is in the know_hosts file in
docssettings/userdir/.ssh
If not, try putty first and accept the key your server provides.
Do you have similar lines in .git/config?
[remote "origin"]
url = ssh://user#server/.../repo.git
I have only passing familiarity with mSysGit, but I don't think it installs an ssh client. Without the ssh client, git cannot connect to the server. (This functionality isn't baked into git as per the Unix philosophy.) As for the git protocol, unless the server has that enabled, it won't work. Since it seems you have the server setup for ssh access, I doubt you'll get anywhere with the git protocol.
Anyway, I know my SSH login works
because I tested it through puTTY.
Have you confirmed that you can SSH to the server from your msysgit client?
i.e. what happens when you ssh user#callisto.com from the msysgit command line?
For further details about setting up your git server, you may want to review Pro Git: Chapter 4 "Git on the Server".
And why doesn't a pull using the
git:// protocol work, since that only
uses read-only access?
For the git protocol to work, you must setup the git daemon on your server as described in Chapter 4.9 of Pro Git.
You may also want to take a look at this answer to a related SO question. It has a more detailed checklist of things to consider.
i have strange behaviour of git - push is working, but clone is not :(
alec$ git clone git://host/repo.git
Initialized empty Git repository in /Users/alec/Temp/repo/.git/
host[0: x.x.x.x]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)
whats wrong?
Push is probably working over SSH (port 22) but clone works over the git port (port 9418). You (or your network admin) will have to open this port if you want to be able to clone repositories.
Try using the Github or Bitbucket (Sourcetree) apps. They usually have less errors, and do most of everything that the command line does. I use bitbucket because their GUI git app is complex and provides many options.
Bitbucket http://bitbucket.org
GitHub http://github.com