[PATCH] bzr-0.0.7 selftest failure on Cygwin

[Jari Aalto]

John Whitley <whitley at acm.org> writes:
| This issue raises some hairy questions regarding cross-platform  
| source control semantics for line-endings.  My team has had a few  
| battles with CVS regarding line-ending changes confusing updates and  
| merges.
| 
| Cygwin is an annoying point in this space, since writing with 'wt'  
| forces Windows text-mode write semantics... which produces a file  
| whose line endings don't match os.linesep (Cygwin's os.linesep =  
| '\n', at least for a Unix-mode installation...)

The logic is:

- Cygwin provides Unix like environment, so the default line
  endings are \n

In order to treat everything \n, the user must mount all file systems 
with mount(1) option:

  -b, --binary     (default)    text files are equivalent to binary files
                                (newline = \n)

Could it be possible that your mount points are no "binary"? This may
have had something to do with it. In my installation the 0.0.7 test
complete cleanly:

  $ cd /usr/src/bzr
  $ PYTHONPATH=.:./bzrlib python bzrlib/selftest/blackbox.py
  <nothing>
  $ mount
  ...
  l:\data\src on /usr/src type system (binmode)


I'm not sure therefore that the patch is correct.

Jari