[ 
https://issues.apache.org/jira/browse/SVN-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735276#comment-16735276
 ] 

Michael Osipov commented on SVN-4732:
-------------------------------------

[~danielsh], this looks different now:

{noformat}
PS D:\> svn --version
svn, version 1.10.3 (r1842928)
   compiled Oct  8 2018, 22:14:05 on x86-microsoft-windows

Copyright (C) 2018 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_svn : Module for accessing a repository using the svn network protocol.
  - with Cyrus SASL authentication
  - 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.
  - using serf 1.3.9 (compiled with 1.3.9)
  - handles 'http' scheme
  - handles 'https' scheme

The following authentication credential caches are available:

* Wincrypt cache in C:\Users\mosipov\AppData\Roaming\Subversion

PS D:\> svn ls file://D:\Entwicklung\Projekte\toll@repo@
svn: E170013: Unable to connect to a repository at URL 
'file://D:%5CEntwicklung%5CProjekte%5Ctoll@repo'
svn: E170000: Local URL 'file://D:%5CEntwicklung%5CProjekte%5Ctoll@repo' 
contains only a hostname, no path
PS D:\> svn ls file:///D:\Entwicklung\Projekte\toll@repo@
1@2/
non/
non@69/
sdfsdf@12
PS D:\> svn co file:///D:\Entwicklung\Projekte\toll@repo@
Checked out revision 9.
PS D:\> svn co file:///D:/Entwicklung/Projekte/toll@repo@
A    toll@repo\1@2
A    toll@repo\1@2\existent
A    toll@repo\1@2\existent2
A    toll@repo\1@2\existent2@2
A    toll@repo\1@2\existent@3
A    toll@repo\1@2\non
A    toll@repo\1@2\non\existent
A    toll@repo\1@2\non@69
A    toll@repo\non
A    toll@repo\non\existent
A    toll@repo\non\existent2
A    toll@repo\non\existent2@2
A    toll@repo\non\existent@3
A    toll@repo\non@69
A    toll@repo\sdfsdf@12
Checked out revision 9.
{noformat}

It does not crash, but it does not reject invalid URLs, infact the {{co}} with 
backslashes produces nothing while a proper URLs gives a correct WC. This looks 
like another bug to me.

> Subversion crashes during local (file://) checkout on Windows
> -------------------------------------------------------------
>
>                 Key: SVN-4732
>                 URL: https://issues.apache.org/jira/browse/SVN-4732
>             Project: Subversion
>          Issue Type: Bug
>          Components: libsvn_subr
>    Affects Versions: 1.9.7, 1.10.0-alpha3
>         Environment: {noformat}
> PS > [System.Environment]::OSVersion.Version
> Major Minor Build Revision
> ----- ----- ----- --------
> 10 0 16299 0{noformat}
> Tried two different Subversion clients:
> {noformat}
> PS > svn --version
> svn, version 1.9.7 (r1800392)
> compiled Aug 8 2017, 22:14:48 on x86-microsoft-windows{noformat}
> {noformat}
> PS > D:\Entwicklung\Programme\svn-1.10.0-alpha3\svn.exe --version
> svn, version 1.10.0-alpha3 (Alpha 3)
> compiled Aug 22 2017, 08:13:12 on x86_64-microsoft-windows10.0.14393{noformat}
>            Reporter: Michael Osipov
>            Priority: Major
>
> Ported from: [https://svn.haxx.se/users/archive-2018-03/0115.shtml].
> Running on Windows from PowerShell:
> {noformat}
> PS > svn co file://D:\Entwicklung\svn-repos\scm-svn-test-at-sign .
> svn: E235000: In file 
> 'D:\Development\SVN\Releases\TortoiseSVN-1.9.7\ext\subversion\subversion\libsvn_client\checkout.c'
>  line 87: assertion failed (svn_uri_is_canonical(url, scratch_pool)){noformat}
> {noformat}
> PS > D:\Entwicklung\Programme\svn-1.10.0-alpha3\svn.exe co 
> file://D:\Entwicklung\svn-repos\scm-svn-test-at-sign .
> svn: E235000: In file '..\..\..\subversion\libsvn_client\checkout.c' line 88: 
> assertion failed (svn_uri_is_canonical(url, scratch_pool)){noformat}
> I know that the URL should start with {{file:///}}, but I would expect 
> something like "invalid URL". The assert failed isn't really helpful to the 
> user.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to