Editing ~/.subversion/config as suggested in comment #23 fixes it, takes gnome keyring out the loop.
I also have to go with comment #28 here, I'm not sure what problems gnome-keyring is trying to solve, but they are not the ones I have. I've already had to turn off its SSH support as I kept on being prompted for keys which were in ~/.ssh and not password protected, now even svn is breaking.
It as if the use case "store passwords securely in one place for users" has forgotten about the other use case "let automated scripts and cron jobs do their work without user intervention"
I've seen this too, on 10.04.
Editing ~/.subversion/ config as suggested in comment #23 fixes it, takes gnome keyring out the loop.
I also have to go with comment #28 here, I'm not sure what problems gnome-keyring is trying to solve, but they are not the ones I have. I've already had to turn off its SSH support as I kept on being prompted for keys which were in ~/.ssh and not password protected, now even svn is breaking.
It as if the use case "store passwords securely in one place for users" has forgotten about the other use case "let automated scripts and cron jobs do their work without user intervention"