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

Re: [Subclipse-users] mixed with eol-style in svn: properties under Windows breaks svn(sync) 1.6

From: B Smith-Mannschott <bsmith.occs_at_gmail.com>
Date: Mon, 30 Mar 2009 12:51:18 +0200

On Mon, Mar 30, 2009 at 11:06, B Smith-Mannschott <bsmith.occs_at_gmail.com> wrote:
> I just want to alert you to this thread:
> <http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1448375>
> particularly, this message:
> <http://subversion.tigris.org/ds/viewMessage.do?dsForumId=106&dsMessageId=1479616>
> In short:
> I think I've discovered a tendency for Subclipse (1.4.7 and 1.6.x) to
> sprinkle carriage returns (^M) into textual svn: properties (e.g.
> svn:log, svn:ignore. This is problem because Subversion 1.6.x is
> stricter about EOL-style purity in the content of its textual
> properties than previously.
> For example, svnsync 1.6 will refuse to sync a repository in which a
> log comment contains a ^M character. It is my understanding from the
> linked thread that subversion 1.6 will also refuse such commits.
> The logical consequence of this should be an inability to commit
> anything with a log comment of more than one line from a Windows
> client running Subclipse (in our particular case on Rational
> Application Developer 7.5.1) to a Subversion server running 1.6. Has
> anyone else observed this?

I have since been able to reproduce this using plain Eclipse 3.4.1 (no
RAD required) under Windows with both Subclipse 1.4.8 *and* Subclipse

In the process, I have discovered a work-around, of a sort.

(1) check out a project form a repository hosted on svnserve 1.6.0
(2) make local changes
(3) commit
(4) enter a commit message of at least two lines length
(5) commit
=> 'SVN Commit' has encountered a problem.
org.tigris.subversion.javahl.ClientException: Wrong or unexpected property value
svn: Commit failed (details follow):
svn: Cannot accept non-LF line endings in 'svn:log' property.
=> commit failed.
(6) commit (again)
(7) select the previously entered commit message form <Choose a
previously entered comment>
=> Commit succeeds.
=> It appears that entry into and retrieval from commit log history
normalizes linebreaks implicitly.

IMHO this is something that should be fixed once in core, rather than
N times in all the various clients. I'll post post this to the
original thread on users_at_subversion...

// Ben


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-03-30 12:51:38 CEST

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

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