[cvsnt] Re: corruption of binary files on checkout

[Corey Wirun]

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?

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

Corey.

----- Original Message ----- >
> Sure.
>
> My source tree has .zip .doc (Word docs), .bmp, .jpg (image files), as
well
> as source code files.
>
> I imported a new module into my repository.  Without doing anything else,
I
> checkedout
> the same module into another directory tree.
>
> I binary compare the original file tree to the tree I just checked out and
> the .zip's and the .doc
> do not match - they are corrupted.  The binary image files (.jpg, .bmp,
etc)
> compared
> properly.  Hense my comment that some files compared properly (the
> image/picture files)
> and some did not.   Perhaps you misunderstood my phrasing of 'image'
files.
> :)
>
> The Word doc, for example, is exactly 21 bytes smaller than the original.
>
> I tried both build 2125 and 2127 to the same result.
>
> I hope this makes the problem clearer.  I really hope to stay with cvsnt,
> since it's
> much more fully featured than cvs!
>
> Thanks for any assistance.
>
> Corey.
>
>
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt