| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
subversion [2012/05/10 15:32]
zeman |
subversion [2013/04/02 09:56] (current)
ufal |
| * nahledem pres Gitweb rozhrani: https://svn.ms.mff.cuni.cz/git (standardni webove overovani) | * nahledem pres Gitweb rozhrani: https://svn.ms.mff.cuni.cz/git (standardni webove overovani) |
| |
| * git klientem pres https: <code> git clone https://svn.ufal.ms.mff.cuni.cz/git/<repository_name.git> </code> | * git klientem pres https: <code> git clone https://svn.ms.mff.cuni.cz/git/<repository_name.git> </code> |
| |
| * pres ssh: <code> git clone user@svn.ms.mff.cuni.cz:/home/DATA/git/<repository_name>.git </code> | * pres ssh: <code> git clone user@svn.ms.mff.cuni.cz:/home/DATA/git/<repository_name>.git </code> |
| |
| ===== Troubleshooting ===== | ===== Troubleshooting ===== |
| | |
| | ==== Password for GNOME keyring ==== |
| | |
| | I had this issue on my workstation (''zen'') when Gnome was running. At the same time svn ran seamlessly on e.g. the ''lrc2'' machine because it is not a workstation. The issue: when in a working copy, type ''svn update''. The following prompt may pop up (and the following line is the result of typing something I thought might be set up as my password for the svn server): |
| | |
| | <code bash>zeman@zen:~/projekty/statmt$ svn update |
| | Password for '(null)' GNOME keyring: |
| | svn: OPTIONS of 'https://svn.ms.mff.cuni.cz/svn/statmt/trunk': authorization failed: Could not authenticate to server: rejected Basic challenge (https://svn.ms.mff.cuni.cz)</code> |
| | |
| | First, what is the Gnome keyring? According to [[http://en.wikipedia.org/wiki/GNOME_Keyring|Wikipedia]], it is a daemon application designed to take care of the user's security credentials, such as user names and passwords. The sensitive data is encrypted and stored in a keyring file in the user's home folder. The default keyring uses the login password for encryption, so users don't need to remember yet another password. |
| | |
| | Unfortunately, I do not seem to be able to get along with my login password either. Also, it is not clear why Subversion wants to consult the keyring when it apparently can work without it (on non-workstation machines, it probably uses its own copy of the credentials stored somewhere in the working copy). Milan lists the following possibilities: |
| | * set empty password for the keyring |
| | * remove the keyring |
| | * change the setting of Subversion |
| | |
| | One on-line forum suggests removing the keyring file. This sounds like a good idea because I do not think I use it otherwise. |
| | |
| | <code bash>rm ~/.gnome2/keyrings/login.keyring</code> |
| | |
| | This solution worked for me. For the sake of completeness: other fora suggest editing the svn configuration file and enable password storing: |
| | |
| | <code bash># Edit the file and add the following line in the [Auth] section (uncommented!): |
| | # password-stores = |
| | # Note that the line may already be there, commented, and/or with the value = no. |
| | vim ~/.subversion/config</code> |
| | |
| | ==== Working copy path does not exist in repository ==== |
| |
| If you get the message: | If you get the message: |
