On Mar 12, 2007, at 01:53, Jensen, Søren wrote:
>> > We have currently installed Subversion 14.3 on a Apache server
>> > 2.059 and it seems to work alle just fine - until - we tried to
>> > in a locked (read only as default) dos file for our PLC
>> > After having them commited in and out of the repository, som of the
>> > files are corrupted i.e. lines and charachters are corrupted.
>> > Is this because of the dos version of the files?
>> Can you provide more information? Can you show a series of
>> commands, beginning with the creation of an empty repository, and
>> ending with the files being corrupted? Can you define what you
>> mean by corrupted?
>> Wild guess: Are you setting the svn:eol-style property on these
>> files? If so, by doing so, you have instructed Subversion to
>> modify line endings. In some contexts, especially for most binary
>> (i.e. non-
>> text) files, this might be called "corruption." If this is the
>> case, your solution will be to not set svn:eol-style on those
>> files. If the files are already corrupted by this line ending
>> conversion, you may need to replace the files from non-corrupted
>> copies, as it may not be possible to reliably uncorrupt them.
> Started like this:
> svadmin create --fs-type fsfs MyNewRepository(named repos)
> Then i used Tortoise to fill in the files to the repository.
> Using Tortoise i set the files as read only and locked a group of
> dependent files for editing in a dos editing program (TISOFT).
> After commiting the files and opening them again there where added
> charahters in normally empty placeholders.
What characters? What placeholders?
If you can provide a sequence of commands that demonstrate the
problem, we can look into it. I'm talking about actual steps I can
perform on my machine to try to duplicate the problem -- a
reproduction recipe. Vague descriptions like saying you used
TortoiseSVN to fill in the files are not enough to help us see the
problem. What was the content of the files? Here is an example of a
good reproduction recipe:
I don't use Windows, and I'm not familiar with TortoiseSVN, so I
don't know what it means to use TortoiseSVN to set the files as read-
only or to lock the group of files. I haven't used Subversion's file
locking in any case, and I didn't know Subversion could make files
> Maybe this is a problem regarding Tortoise?!
Maybe, I don't know. Try reproducing the problem without TortoiseSVN,
using just the svn command-line client.
To reply to the mailing list, please use your mailer's Reply To All
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Mar 13 11:04:00 2007