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

Daniel Shahaf commented on SVN-4620:
------------------------------------

Reproduction:

{noformat}
% svnadmin create r
% python -c "open('r/db/fs-type', 'w').write('fsfs\r\n')"
% svnlook youngest r
'vnlook: E160033: Unknown FS type 'fsfs
zsh: exit 1     svnlook youngest r
{noformat}

As I said on the post Michael links to, it might be nice to have an 
svn_error_createf() printf format code that quotes-and-escapes its argument 
(but that's not a prerequisite to fixing this issue).


> svn command output manged if file-based repo does not have the line ending of 
> the given system
> ----------------------------------------------------------------------------------------------
>
>                 Key: SVN-4620
>                 URL: https://issues.apache.org/jira/browse/SVN-4620
>             Project: Subversion
>          Issue Type: Bug
>          Components: cmdline client, libsvn_ra_local
>    Affects Versions: 1.9.3
>         Environment: FreeBSD bsd10 10.2-RELEASE FreeBSD 10.2-RELEASE #0 
> r286666: Wed Aug 12
> 15:26:37 UTC 2015 [email protected]:/usr/obj/usr/src/sys/GENERIC
> amd64
> and Windows 10
> svn, version 1.9.3 (r1718519)
>    compiled Dec 22 2015, 09:12:06 on x86_64-microsoft-windows6.2.9200 
>            Reporter: Michael Osipov
>         Attachments: test-repo-svn-crashing.zip
>
>
> run {{svn ls file://path/to/repo}} and the output is
> {noformat}
> svn ls file:///D:/Entwicklung/Projekte/test-repo-svn
> svn: E170013: Unable to connect to a repository at URL 
> 'file:///D:/Entwicklung/Projekte/test-repo-svn'
> svn: E180001: Unable to open repository 
> 'file:///D:/Entwicklung/Projekte/test-repo-svn'
> 'vn: E160033: Unknown FS type 'fsfs 
> {noformat}
> There seems to be a unescaped {{\r}} from the repo's internal files. This 
> issue has been confirmed on the mailing list: 
> http://svn.haxx.se/users/archive-2016-02/0022.shtml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to