Re: SSL handshake failed: SSL alert received
[ If possible, this list prefers bottom-posting / inline replies in plain text. More below ... ] On Wed, Jul 11, 2018 at 10:07 PM, Brandon L. Wisenburg wrote: > Hi Johan, > Yes, I edited out the actual domain. I can hit the URL via a browser and get > prompted for a password. The SSL Cert also checks out OK via SSLChecker. Any > other thoughts? Hm, just a generic problem-solving thought: this worked before (since you created a checkout from that url), so ... what changed? Something must have changed to cause the error. Is your pc the only one getting this error, and it works fine on other's pc in your environment? That would help pinpointing the problem to a either a central component or just your pc. First suspects, IMHO, are: - Something in the network infrastructure, or with the network configuration of your pc. Perhaps your connection is now sent to / manipulated by a proxy, whereas it wasn't before. Maybe you can experiment a bit with the http-proxy-* options (for instance configure http-proxy-exceptions for your domain) in the 'servers' configuration file in your Subversion runtime configuration directory (~/.subversion/servers on unix, or %APPDATA%/Subversion/servers on Windows). - A change in the server-side configuration (the httpd configuration). -- Johan
Re: SSL handshake failed: SSL alert received
On Wed, Jul 11, 2018 at 5:32 PM, Brandon L. Wisenburg wrote: > Greetings List, > I am getting an error when attempting to svn update. > > svn update > svn: OPTIONS of 'https://domain/src': SSL handshake failed: SSL alert > received: Handshake failed (https://www.domain.com) > > Odd part is I am not sure why it is failing. Has anyone seen this issue > before? I suppose you hand-edited the error message to replace the actual domain name with 'domain'. To double-check: the first url in the error message is without the www.*.com, yes? So the actual repository url does not have www.*.com, but the svn client seems to be forced to perform its ssl handshake with www.domain.com. Perhaps a proxy that is interfering? Other than that: a quick thing to try is to access the repository url from a web browser, and see if there is any connection problem or anything strange with the ssl certificate / connection. -- Johan
Re: Subversion Exception
On Wed, Jul 11, 2018 at 5:06 PM, Jeff Dege wrote: > I’m seeing a repeatable exception. > > > > If within TortoiseSVN Project Monitor, if I select “Show Range” and then > pick a Date Start Revision a couple of weeks back and an End Revision of > HEAD, I get an exception. (Picking an Date End Revision of today works > without error.) > > > > --- > > Subversion Exception! > > --- > > Subversion encountered a serious problem. > > Please take the time to report this on the Subversion mailing list > > with as much information as possible about what > > you were trying to do. > > But please first search the mailing list archives for the error message > > to avoid reporting the same problem repeatedly. > > You can find the mailing list archives at > > http://subversion.apache.org/mailing-lists.html > > > > Subversion reported the following > > (you can copy the content of this dialog > > to the clipboard using Ctrl-C): > > > > In file > > 'D:\Development\SVN\Releases\TortoiseSVN-1.9.7\ext\ > subversion\subversion\libsvn_client\ra.c' > > line 681: assertion failed (SVN_IS_VALID_REVNUM(peg_revnum)) > > --- > > OK > > --- > > > This could possibly be a bug in TortoiseSVN, rather than in core svn itself. I suggest to first report this to one of the TortoiseSVN mailinglists. See: https://tortoisesvn.net/community.html. -- Johan
SSL handshake failed: SSL alert received
Greetings List, I am getting an error when attempting to svn update. svn update svn: OPTIONS of 'https://domain/src': SSL handshake failed: SSL alert received: Handshake failed (https://www.domain.com) Odd part is I am not sure why it is failing. Has anyone seen this issue before? ===
Bug: svn copy --parents
Hi, all. I've recently discovered a bug in svn client code: copy operation fails with "svn: E155010: Directory 'dst_parent' is not under version control" under the following conditions: * it is repos-to-wc copy * dst parent directory exists, but unversioned * --parents flag is passed (make_parents=true) I've prepared a patch for this bug and I'm ready to both create a corresponding issue in the issue tracker and contribute the patch, but issue creation form warned me to discuss the issue first on the mailing list. What are my further actions? -- Nikita Slyusarev
