rcs 5.8-1 corrupt files?

[Dave Korn]

On 11/12/2011 08:24, Jay E. wrote:

> Suspected line-ender problem.
> Started over and used 'flip' to go with unix line-ender.
> Same problems.
> BUT it looks like the DOS lime ender was added after the flip by ci, or co.

  It looks like the line-ends are getting flipped in the actual RCS/*,v file,
and that's probably because of your current directory:

> Cygwin installations found in the registry:
>   System: Key: c5e39b7a9d22bafb Path: C:\cygwin
> 
> c:  hd  NTFS     64999Mb  44% CP CS UN PA FC     Preload
> d:  cd             N/A    N/A                    
> 
> C:\cygwin        /          system  binary,auto
> C:\cygwin\bin    /usr/bin   system  binary,auto
> C:\cygwin\lib    /usr/lib   system  binary,auto
> cygdrive prefix  /cygdrive  user    text,posix=

  Your /cygdrive is set to text mode, so when RCS tries to create files under
that part of the tree, they'll get DOS CR-LF line endings.  (This presumably
reflects an underlying portability bug in RCS itself: it must not be using the
"b" file mode in open calls.  On Linux and Unix systems, binary mode is the
same as text mode, but that isn't true everywhere, and even though it doesn't
make a difference on those systems, the code should still correctly use binary
or text mode when it opens a file according to the semantics of what it's
going to write there.)

  You should be alright if you only use RCS inside other cygwin paths except
for those under /cygdrive, or if you remove the text mode setting from your
cygdrive prefix.

    cheers,
      DaveK



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple