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

[Markus Schaber <m....@3s-software.com>]

Hi,

Von: Stefan Sperling [mailto:stsp@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?

Could svnsync mistakenly "fix" a binary property which happens to contain CR-LF byte sequences?


Best regards

Markus Schaber
-- 
___________________________
We software Automation.

3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50

Email: m.schaber@3s-software.com | Web: http://www.3s-software.com 
CoDeSys internet forum: http://forum.3s-software.com
Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects

Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915

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

[Les Mikesell <le...@gmail.com>]

On Wed, Oct 26, 2011 at 11:39 AM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
>
>> > 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 :-(

That's one of those 'if it hurts, don't do it...' things.   While you
always need to know if something is text or not to handle local text
conventions in a usable way, it would seem awkward for svn to assume
that revision contents are binary unless told otherwise, but have the
opposite convention for svn:* properties.   Better to just never allow
non-text there.

-- 
  Les Mikesell
    lesmikesell@gmail.com

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

[Daniel Shahaf <d....@daniel.shahaf.name>]

On Wednesday, October 26, 2011 4:52 PM, "Bert Huijben" <be...@qqmail.nl> wrote:
> 
> 
> > -----Original Message-----
> > From: Markus Schaber [mailto:m.schaber@3s-software.com]
> > Sent: woensdag 26 oktober 2011 16:49
> > To: Subversion Users (users@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@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 :-(

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

[Bert Huijben <be...@qqmail.nl>]

> -----Original Message-----
> From: Markus Schaber [mailto:m.schaber@3s-software.com]
> Sent: woensdag 26 oktober 2011 16:49
> To: Subversion Users (users@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@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?
> 
> Could svnsync mistakenly "fix" a binary property which happens to contain
> CR-LF byte sequences?

Within the svn:* namespace there are no binary properties.

Svnsync doesn't transform other properties.

	Bert