subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Turner <synfina...@gmail.com>
Subject Re: svn add: Unrecognized line ending style
Date Tue, 06 Jul 2010 15:18:50 GMT
Yes.  The same Trac pre & post commit hooks I've been using for years.
 Btw, the svn server is still 1.6.9 and hasn't changed in months.

Honestly, I don't believe the hooks to be the problem, since the
problem happens when I run "svn add", NOT "svn commit".  Committing
changed files/properties works just fine.    Running "svn
--no-auto-props <file>" and then setting svn:eol-style = native seems
to work, but obviously is a PITA.

-Aaron


On Tue, Jul 6, 2010 at 3:12 AM, Nico Kadel-Garcia <nkadel@gmail.com> wrote:
> Do you have some sort of upstream pre-commit or other hooks on your server?
>
> On Mon, Jul 5, 2010 at 6:43 PM, Aaron Turner <synfinatic@gmail.com> wrote:
>> Maybe this started happening after upgrading to svn 1.6.12, but not
>> really sure about the timing, but all of a sudden I can't add any new
>> files to my svn repo on my Mac (10.6.4) because I'm getting
>> "Unrecognized line ending style" when I do an 'svn add'.
>>
>>> file pcapinfo.c
>> pcapinfo.c: ASCII c program text
>>
>>> xxd pcapinfo.c | head
>> 0000000: 2f2a 2024 4964 2420 2a2f 0a0a 2369 6e63  /* $Id$ */..#inc
>> 0000010: 6c75 6465 2022 636f 6e66 6967 2e68 220a  lude "config.h".
>> 0000020: 2369 6e63 6c75 6465 2022 6465 6669 6e65  #include "define
>> 0000030: 732e 6822 0a23 696e 636c 7564 6520 2263  s.h".#include "c
>> 0000040: 6f6d 6d6f 6e2e 6822 0a0a 2369 6e63 6c75  ommon.h"..#inclu
>> 0000050: 6465 203c 6663 6e74 6c2e 683e 0a23 696e  de <fcntl.h>.#in
>> 0000060: 636c 7564 6520 3c73 7973 2f74 7970 6573  clude <sys/types
>> 0000070: 2e68 3e0a 2369 6e63 6c75 6465 203c 7379  .h>.#include <sy
>> 0000080: 732f 7569 6f2e 683e 0a23 696e 636c 7564  s/uio.h>.#includ
>> 0000090: 6520 3c75 6e69 7374 642e 683e 0a23 696e  e <unistd.h>.#in
>>
>> As you can see, looks like a standard Unix text file to me, using line
>> feeds (0x0a).
>>
>> In vim, I've done a ":w ++ff=unix" to force the file to unix text
>> format just to be sure, but still having the same problem.

-- 
Aaron Turner
http://synfin.net/         Twitter: @synfinatic
http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & Windows
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
    -- Benjamin Franklin
"carpe diem quam minimum credula postero"

Mime
View raw message