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

Julian Foad commented on SVN-4620:
----------------------------------

To clarify: according to the mailing list discussion, it is accepted that the 
repo has been corrupted by having '\r' inserted into the 'fs-type' file (and 
other files), and the fact of that corruption is not the subject of this issue.

Therefore the expected output is still an error message, but one that more 
clearly shows the fs-type value found; for example:
{code}
svnlook: E160033: Unknown FS type 'fsfs\r'
{code}

> svn command output mangled 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: libsvn_fs, libsvn_subr
>    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.4.14#64029)

Reply via email to