[cvsnt] Re: corruption of binary files on checkout

Tony Hoyle tony.hoyle at march-hare.com
Fri Oct 21 23:52:57 BST 2005


Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


Corey Wirun wrote:
> Additional information - I just tried importing a completely different
> module and some .lib, .bmp, and .ico's were corrupted.
> 
> I did an octal (od) dump on the two files (a .bmp file).
> 
> good file:
> 0324020 ... 323 136 *015* 110 110 110 110 110 057 136 136 146
> 
> bad file:
> 0324020 ... 323 136 *012* 110 110 110 110 110 057 136 136 146
> 
> This appears for every 012 character in the (good) source file.  Doesn't
> sound like 'regular' corruption to me, does it?

How are you checking these out?   Sounds like what would happen if you 
forced -kL on the command line.

> Wincvs insists the checked out file is -kb (binary), so some binary/ascii
> setting is getting clobbered somewhere.

Try using the command line... it's more likely to be a client problem 
than server I expect.

Tony



More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook