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

Re: Strange problem with archive/extraction of working copy

From: Delbert D. Franz <ddf_at_sonic.net>
Date: 2004-02-23 20:41:56 CET

Thanks for your response. It seems that the behavior
in question is currently shrouded in a bit of mystery.

I did some more testing on my system. Moved my test case
to Linux, I run W2K under Vmware on Linux, so that was easy.
The repository is on a Linux box already.

1. Created a test dir on Linux that matches the one on W2K
but with the correct line endings for Linux.

2. Used svn import to create a new test case: testsvn2 on
the server. Checked the db strings, and yes, they only have
a LF as line endings. This differs from the result when importing from
W2K where the db strings have a CRLF as the eol signal!
This is not the expected result.

3. Did a checkout of testsvn2 to W2K and got the correct
line endings.

Page 121 of the Subversion Book, Revision 8770 states the
the line endings in the repository are supposed to be LF.

Therefore it seems to me there is a bug of some sort
in the W2K Subversion that retains the CRLF on import.
Or perhaps it is a bug in the server on Linux that does not
strip the LF when an import comes from a Windows client?

However, except for the archive problem, updates, commits,
etc. seem to work correctly with a repository that contains
CRLF line endings. This has been tested under W2K and
Linux. I am running with the config-file option
auto-props as yes and then setting eol-style: native on every
ASCII file.

Can anyone confirm if this behavior is:

1. A bug,

2. An undocumented "feature",

3. A mistake on my part in not setting some option
in a config file on the client or the server?

Also, I could transfer my main project from W2K to
Linux, change all the line endings with dos2unix,
then import to create the repository on the server.
Would this provide greater insurance against problems
latter? At least it gets the correct line endings in the
db strings for the repository.

Otherwise Subversion is working well. I'll be updating
to the 1.0.0 release this week but I expect the above
behavior to remain the same.


On Saturday 21 February 2004 05:24 am, you wrote:
> "Delbert D. Franz" <ddf@sonic.net> writes:
> > "The problem is that the text-base in the repository has CRLF line endings.
> > This is an error."
> >
> > I'm not clear on what this statement means: Did I do something
> > incorrect in setting up the repository or is there an error in Subversion?
> As I said:
> >> It works most of the time, but
> >> this problem with incorrect line endings in the repository has been
> >> reported before. Nobody with a Windows box has tracked it down, I
> >> don't know if they ever tried.
> You may have done something wrong, it may be a Subversion bug. I have
> only ever seen this reported by Windows users.
> --
> Philip Martin

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 23 20:41:48 2004

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.