4

I'm not sure if this is specific to my particular repository or what but I got this error:

svnsync: Cannot accept non-LF line endings in 'svn:ignore' property

when I tried to import the repository at this url:

https://filenexus.googlecode.com/svn/trunk/

More specifics about the problem files/folders would be helpful when trying to resolve the problem.

flag
Hi Karim, I just tried doing the import with filenexus.googlecode.com/svn/trunk, and it worked fine. Can you confirm that this is working if you use the http scheme instead of https? – Rock Hymas♦ Oct 30 2009 at 21:35
Huh. That didn't work either. It had gotten somewhere between 50% and 100% (50% was the last time I looked at the installer before going back to the other thing I was doing). It did successfully discover the right version control this time (which it didn't do with the https address). – Karim Oct 30 2009 at 22:03
Tried it a third time: got to 73% if that helps at all. Anyway, I should mention this I'm trying this from behind a pretty agressive firewall. Most ports are locked out (though not HTTP/HTTPS obviously). Not sure if that's relevant here. – Karim Oct 30 2009 at 22:06
And you're getting the same error around 73% each time? Interesting. What version of subversion do you have installed? What version of mercurial? The fact that it looks like a mercurial repo on https is a good bug. I'll look into that one. – Rock Hymas♦ Oct 30 2009 at 22:22
Well, I only watched the progress the one time but I'm guessing that it is 73 each time since I know it got past 50 the first time. The version of the svn command-line client installed is 1.6.1. The version of mercurial installed is whatever Kiln client installed which when I do an "hg --version" on the command-line is "(version e3ce0c30798b)" whatever the hell that is. – Karim Oct 30 2009 at 22:59
show 1 more comment

2 Answers

4

This is a subversion bug that was fixed in 1.6.3. You can find more info on the bug at http://subversion.tigris.org/issues/show_bug.cgi?id=3404. If you upgrade to the latest Subversion, this should be fixed. I'll fix the importer to require that version of Subversion or later.

link|flag
0

Case opened! We'll try to get this fixed as quickly as possible.

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.