SVN GNOME keyring issues

I recently had issues checking out an SVN repo.  The problem went something like this:

adam@nynaeve:~$ svn co https://server/path
Password for ‘default’ GNOME keyring:
svn: OPTIONS of ‘https://server/path’: authorization failed: Could not authenticate to server: rejected Basic challenge (https://server)

This was a little puzzling, not least of which because I don’t use GNOME.  The problem seems to be a bug, which the SVN guys say is a GNOME issue, and the GNOME guys say is an SVN issue.  To make a long story short, the answer was to delete ~/.gnome2/keyrings/default.keyring.  The GNOME keyring left me alone, SVN prompted for my credentials, and the day was saved.

2 Comments

  1. Posted October 13, 2012 at 9:38 pm | Permalink

    Thanks for this tip! I had been frustrated for hours as my password was not being saved, and in combination with changing my SVN settings, this allowed me to use subclipse properly so I could actually get my homeworks graded. Let’s hope I didn’t break anything else. My professor and TAs were no help at all, but hopefully I won’t lose another 15%. Do you use eclipse? Do you have any tips for someone who still prefers gedit and javac to this fancy IDE business?

  2. Posted October 14, 2012 at 10:06 am | Permalink

    I do use Eclipse. I don’t know if I have any general tips, but if you are going to program in Java a lot, I would recommend using an IDE. There is a bit of a learning curve, but once you get use to it, it speeds things up tremendously. For example, in Eclipse, if you’re editing a class X that calls a method Y.m(), you can ctrl-click on m() to go straight to its definition. Even if you want to stick with a “plain” text editor, I suggest trying out Emacs (although others would suggest vi).

Post a Comment

Your email is never shared. Required fields are marked *

*
*