On Tue, Sep 1, 2015 at 8:01 PM, Branko Čibej <br...@apache.org> wrote:
> On 02.09.2015 03:26, Dmitriy Setrakyan wrote: > > Brane, > > > > Since recently I am constantly asked to confirm an SVN certificate before > > updating or committing. This is really hurting my productivity :) > > Yeah, right, one extra keypress, heh. > > > Any advise on how this can be fixed? > > You should be able to permanently trust the certificate (that Infra > replaced a while ago). Can you show me the command-line transcript from > an svn commit? If the client doesn't offer you to permanently trust the > cert, you're probably Doing Something Wrong™. Don't forget to include > the output of 'svn --version'. > Brane, the situation is actually the reverse. The client always offers to accept a certificate every time I execute any SVN command, even after I had already previously accepted it "permanently". Here is the output of "svn --version": -------------- dsetmac:root $ svn --version svn, version 1.7.19 (r1643991) compiled Jun 17 2015, 13:48:11 Copyright (C) 2014 The Apache Software Foundation. This software consists of contributions made by many people; see the NOTICE file for more information. Subversion is open source software, see http://subversion.apache.org/ The following repository access (RA) modules are available: * ra_neon : Module for accessing a repository via WebDAV protocol using Neon. - handles 'http' scheme - handles 'https' scheme * ra_svn : Module for accessing a repository using the svn network protocol. - handles 'svn' scheme * ra_local : Module for accessing a repository on local disk. - handles 'file' scheme * ra_serf : Module for accessing a repository via WebDAV protocol using serf. - handles 'http' scheme - handles 'https' scheme --------------- > -- Brane >
