On Sun, 20 Dec 2020 11:59:11 +0100, Bo Berglund
<bo.berglund_at_gmail.com> wrote:
>On Sun, 20 Dec 2020 09:05:52 +0100, Bo Berglund
><bo.berglund_at_gmail.com> wrote:
>
>>>If you do get a list of credential caches that the SVN client
>>>recognizes, then you should pick one and ensure it is setup correctly.
>>
>>How do I "pick one"?
>>Inside the ~/.subversion/config ot ~/.subversion/servers files????
>>And how to "setup"?
>
>So I made the following test:
>
>1) Modified the ~/.subversion/config file (note NOT the servers file
>as suggested in another thread):
>Uncommented the following line:
>password-stores = gpg-agent,gnome-keyring,kwallet
>
>2) Rebooted the RPi just to get rid of possible cached stuff
>
>3) Edited a documentation file in the project I am working on and
>issued the svn ci command.
>
>4) After entering the log message a login dialog appeared in the PuTTY
>terminal, where I could enter my subversion login.
>
>5) Then the commit worked!
>
>So it seems like the svn config file must be modified and then it
>starts working again.
>
Except now it has reverted to popping up the GUI login dialog when I
am checking in via a PuTTY session.
In PuTTY it just sits there doing nothing, if I then open the VNC
window into the RPi then I see the login dialog there. :(
How should the setting in subversions config file look like?
Right now it is as follows (uncommented the existing line)
password-stores = gpg-agent,gnome-keyring,kwallet
Should something be taken out or something else added to make it stop
this behaviour and always demand login on the terminal that issues the
svn operation?
It seems so strange that svn would use a completely different window
to get the credentials from than the one where svn itself runs.
--
Bo Berglund
Developer in Sweden
Received on 2020-12-28 21:16:17 CET