trouble with mixed-EOL files with svn:eol-style=native
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad CSCVS |
Triaged
|
Low
|
Unassigned | ||
SciPy |
New
|
Undecided
|
Unassigned |
Bug Description
Occasionally somebody manages to create a Subversion repository in which some revisions of a file contain a mixture of end-of-line styles, but svn:eol-
$ svn cat -r998 svn://svn.
svn: Inconsistent line ending style
This broke the putty import:
http://
While Subversion itself doesn't make it easy to do this, it is possible to end up in this situation due to a conversion from CVS, as indeed is the case for putty. We should somehow arrange to be able to import such branches anyway.
There are a couple of possibilities, which mostly look like they would involve reimplementing svn_client_cat2. We could ignore the svn:eol-style property on anything that raises this exception, or we could arrange to set the repair flag for svn_subst_
From what I can tell, Subversion's pedantry here is in order to avoid corrupting binary files that mistakenly have svn:eol-
Changed in launchpad-cscvs: | |
importance: | Undecided → Medium |
status: | New → Triaged |
tags: | added: svn |
Oh, interesting, we've seen this error code a bunch of times before:
https:/ /help.launchpad .net/VcsImportR equests#[svn]%20ClientE rror:%20Code: %2000020f58
Thanks for digging into it! No thanks for how grotty the problem turns out to be, but I guess that's not your fault :)