Announcement

Collapse
No announcement yet.

SVN login

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • SVN login

    Hi,

    I just tried to use Beyond Compare v4.2.10 on a Linux system to compare a local folder to a Subversion (SVN) repository. This failed with the following message:

    Code:
    19.09.2019 16:33:10 Unable to load https://server:port/svn/path/: svn: E215000: Unable to connect to a repository at URL 'x'
    svn: E215000: GNOME-Schlüsselring ist gesperrt und wir sind nicht-interaktiv
    I don't use a "GNOME keyring". Why is there no prompt for me to enter my credentials?


    After playing around a little I got a step further, now the error is:

    Code:
    19.09.2019 16:49:10  Unable to load https://x: Certificate validation handler is not assigned. Please handle the OnCertificateValidate event and implement proper certificate validation code there.
    Bottom line: I don't care. How can I just bypass all this junk and access the repository?


    Regards
    Last edited by 150d; 19-Sep-2019, 09:52 AM.

  • #2
    Hello,

    The quick version would be to use svn on the command line and accept the certificate. There are a few scenarios where certificate prompts aren't available within BC4, but accepting and saving them using the Terminal will then allow the profile to work.

    Also, are you using the SVN Profile in the Tools menu -> Profiles dialog with "https://server/folder" as the syntax? I do not have this precise certificate scenario setup in my test environment, but I would expect the log to show "svn+https://server/folder" in the error message if the "https://server/folder" profile is configured.
    Aaron P Scooter Software

    Comment


    • #3
      Hello,

      I'm already using svn on the shell. For example, I can run a command like "svn diff" without being prompted for anything. I seem to remember that the first time I did have to accept a certificate (and, of course, enter credentials), so that should have been done already.

      Yes, the URL I entered is indeed "https://server: port/path". What puzzles me is that the command is run without further prompting, and that it apparently tries to access "GNOME keyring" - a entity I never used and always have done my best to avoid, actually. ;-)

      If the process needs credentials, just prompt me for them.

      Regards

      Comment


      • #4
        What Linux distribution (Ubuntu 18.04, etc) and desktop environment (Gnome, KDE, etc) are you using?
        Chris K Scooter Software

        Comment


        • #5
          Hello,

          I'm running KDE Desktop on Debian v8.11.

          Regards

          Comment

          Working...
          X