#1859 SVN update broken
Hello,
I'm using:
openjdk version "1.8.0_91"
JEdit 5.3.0
SVNPlugin 1.8.6
First I configured the SVN plugin to use https and kwallet. Everything works apart from update. If I start SVN update I get this message on the console:
Updating ...
svn: E215000: GNOME Keyring is locked and we are non-interactive
Committing ...
Sending ptest/ht/xxxxxxxx/M-ABF/M-MaSc_Fu_M100_li-ABF.m4
Transmitting file dataCommitted revision 2532.
Updating ...
svn: E215000: GNOME Keyring is locked and we are non-interactive
Then I tried "svn+ssh". Again everything works, but when it comes to update I get again an error.
Updating ...
svn: E170001: Authentication required for 'svn+ssh://myhost'
It seems SVN update behaves differently compared to SVN checkout, status, log, ... in regard to authentication.
Regards,
Bernhard
Thanks for the report. I suspect there may be a few other commands that would do similar: merge, mkdir, property, resolved, revert, status (when checking against the repository), switch, and update as you've reported. Would you be able to test any of these other commands to confirm? I'm not using either kwallet or gnome keyring, so I'm not able to test your configuration myself.
Hello,
just tested the properties command, here is the result.
Output of the status command:
At least this two commands are working.
By the way at the very beginning of my jedit tests i did not use kwallet, but I was not able to do anything with SVN. I always got the keyring error message. Then I found the config file in ~/.jedit/plugins/ise.plugin.svn.SVNPlugin/.subversion and set password-stores to kwallet. So I am not keen in kwallet but it was the only way to get started with SVN.
Should I do further tests with the other SVN commands you mentioned?
Regards,
Bernhard
Last edit: dumischbaenger 2016-07-27
Personally, I find gnome keyring to be annoying and mostly useless, so I've disabled it like this:
First, rename /usr/bin/gnome-keyring-daemon to /usr/bin/gnome-keyring-daemon.bak.
Find the running keyring daemon and kill it:
ps ax | grep keyring
kill -9 pid
Then remove the keyrings:
rm -rf ~/.gnome2/keyrings
I also have
store-passwords=no
and
store-auth-creds=no
in my ~/.subversion/config file. I find this eliminates most of the annoyance of gnome keyring.
There is a bug (or several, depending on your point of view) in that the commands I mentioned are using the wrong svn configuration. They all should be using the configuration from ~/.subversion, which is the one your command line svn will be using. There really shouldn't be a ~/.jedit/plugins/ise.plugin.svn.SVNPlugin/.subversion. A temporary fix is to make sure both your ~/.subversion configuration and the ~/.jedit/plugins/ise.plugin.svn.SVNPlugin/.subversion are the same. I'll fix the commands so they all use the ~/.subversion configuration so there is only one place for the configuration.
Killing the keyring service and removing the password-stores item from the .jedit/.../.subversion config file did the trick. To my shame I have to admin I didn't realize gnome keyring is up and running. I knew it is installed but didn't care about it because I thought it won't be used/started with KDE. I guess gdm starts it on Centos 7.
One Question ist still open. Why tried SVNKit to use gnome keyring at all? password-stores was unset in ./subversion and .jedit/.../.subversion at the beginning.
Sorry a second one. Is it possible to get more logs from SVN plugin - which config is used, which type of authentication, ...
Thank you for your help.
Regards,
Bernhard
Last edit: dumischbaenger 2016-07-28