Corrupted dos files for our PLS controllers

["Jensen, Søren" <So...@EU.SunChem.com>]

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 edit in a locked (read
only as default) dos file for our PLC controllers. 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?

Kind regards 
Soren Jensen



This message may contain confidential, proprietary or legally privileged information and is
intended only for the use of the addressee named above.  No confidentiality or privilege is
waived or lost by any error in transmission.  If you are not the intended recipient of this
message you are hereby notified that you must not use, disseminate, copy it in any form or
take any action in reliance on it.

Notice for all correspondence to or from a UK based Sun Chemical company:
Sun Chemical Europe and Ault&Wiborg are trading divisions of Sun Chemical  Limited,    
Registered in England No. 2647054
Registered Office:  3 High View Road, South Normanton, Derbyshire, DE55 2DT, UK
VAT Registration Number: GB216018402

Re: Corrupted dos files for our PLS controllers

[Ryan Schmidt <su...@ryandesign.com>]

On Mar 9, 2007, at 05:00, 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  
> edit in a locked (read only as default) dos file for our PLC  
> controllers. 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.


-- 

To reply to the mailing list, please use your mailer's Reply To All  
function


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org