On Thu, Jul 23, 2009 at 5:09 AM, Stefan Sperling<stsp_at_elego.de> wrote:
> On Wed, Jul 22, 2009 at 07:55:51PM -0400, Nico Kadel-Garcia wrote:
>> On Sun, Jul 19, 2009 at 11:28 AM, Stefan Sperling<stsp_at_elego.de> wrote:
>> > On Sun, Jul 19, 2009 at 11:21:58AM -0400, Nico Kadel-Garcia wrote:
>> >> On Thu, Jul 9, 2009 at 10:26 AM, Marc Lustig<ml_at_marclustig.com> wrote:
>> >> > svnsync: Cannot accept non-LF line endings in 'svn:ignore' property
>> >> Did you ever get past this? I just addressed it in a big repository
>> >> that I was trying to upgrade by using the latest subversion 'trunk'
>> >> code, nominally labeled 1.7.0 internally, to build a working svnsync
>> >> that addresses this issue. I'm also hoping that 1.6.4 will be released
>> >> as quickly as possible to address this.
>> > This was fixed in 1.6.3.
>> > You don't have build trunk or wait for 1.6.4 for this.
>> Odd. It didn't work for me on RHEL 4 or RHEL 5, using the RPMforge
>> distribution of subversion 1.6.3 or a locally built one for RHEL 4.
> But it should work.
> And you said it worked for you using trunk, right?
I see it. That machine had it's subversion rolled back to an in-house
1.6.2-local release, to test soem features, and hadn't been re-updated
to 1.6.3 So 1.6.3 does, in fact, work.
>> > Version 1.6.3
>> > (22 Jun 2009, from /branches/1.6.x)
>> > http://svn.collab.net/repos/svn/tags/1.6.3
>> > User-visible changes:
>> > [...]
>> > * make svnsync normalize svn:* props to LF line endings (issue #3404)
>> > [...]
>> > Stefan
>> It's a new feature: maybe I tripped over a bug for svn:ignore, and not
>> for simpler characteristics such as svn:log?
> No, it normalizes all svn:* props. All of them.
> I just checked the 1.6.3 release code again to make sure.
> I'm not saying that there is no problem, just pointing out that to
> the best of our knowledge this should have been fixed with 1.6.3.
> Can you provide more information or otherwise help to diagnose the
> problem more precisely? Such as a public test repository to sync
> from which contains the property in question? Then others could test
> with their 1.6.3 clients to see if they can reproduce your problem.
I was mistaken about the version of subversion on the particular
server. I re-ran the process from scratch, and it does, in fact, work
with svnsync to mirror an old repository with such EOL issues.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-25 16:11:02 CEST