[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Property encoding (was: Error during svnadmin load (svnadmin: E125005: Cannot accept non-LF line endings in 'svn:log' property))

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Wed, 26 Oct 2011 18:39:35 +0200

On Wednesday, October 26, 2011 4:52 PM, "Bert Huijben" <bert_at_qqmail.nl> wrote:
>
>
> > -----Original Message-----
> > From: Markus Schaber [mailto:m.schaber_at_3s-software.com]
> > Sent: woensdag 26 oktober 2011 16:49
> > To: Subversion Users (users_at_subversion.apache.org)
> > Subject: Property encoding (was: Error during svnadmin load (svnadmin:
> > E125005: Cannot accept non-LF line endings in 'svn:log' property))
> >
> > Hi,
> >
> > Von: Stefan Sperling [mailto:stsp_at_elego.de]
> > > BTW, another trick to fix the issue is to copy the repository using
> > > svnsync. As of Subversion 1.6.3 (which is fairly old), svnsync
> normalizes
> > > all svn:* properties to LF line-endings automatically.
> >
> > Out of curiosity: how do Svn and svnsync distinct between binary and text
> > properties?
> >

Use the source -> svn_prop_needs_translation()

> > Could svnsync mistakenly "fix" a binary property which happens to contain
> > CR-LF byte sequences?
>
> Within the svn:* namespace there are no binary properties.
>

But if svn 1.8 defines a binary svn:* prop, then svnsync 1.7 will try and normalize its line endings :-(
Received on 2011-10-26 18:40:07 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.