"Drew Jetter" <ajetter1@cox.net> writes:
> > If 'svn import' incorrectly guesses at the text/binariness, this
> > shouldn't be a big deal at all. Just check out a working copy, fix
> > the properties by hand, and recommit. The data won't change one whit
> > in the repository.
> >
> > Are you actually seeing data corruption somewhere? Or are you just
> > *assuming* that things are corrupted, having been scarred by cvs's
> > "-kb" flags in the past? :-)
>
> Well, maybe you're right, because the sizes of the files seem to be about
> the same. Let me tell you exactly what happens. When I try to compile
> in Borland C++, I get the following error:
>
> [Linker Error] RLINK32: Unsupported 16bit resource in file "C:\...(a .DFM
> file)"
> [Linker Error] Unknown RLINK32 error
>
> So if the file hasn't had any bytes changed in it, what could be
> causing this error? I tried doing it like the cmpilato suggested,
> but I still got the error when I checked out the file, even though I
> committed it as a binary file. This has happened to me with CVS as
> well. Any ideas as to what the problem could be? Thanks for your
> guys' help
Do you have the original file lying around, the one you
committed/imported to the repository? Do a byte-for-byte comparison.
Use 'cmp' or something. We don't have to sit around guessing if the
checked-out file is different from the original. Find out for sure.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 22 19:19:28 2002