Corrupt binary files during conversion

Hi Paul and Karl,

I have found the same problem here (and another one).
To make Pauls report more complete:

1. I use a new_mime.types file with file extensions settings
like 

application/octet-stream    bin

2. I used the following line to execute cvs2svn

/usr/local/src/cvs2svn-1.3.0/cvs2svn --encoding=latin1
--no-prune --mime-types=/etc/new_mime.types
--eol-from-mime-type \
   --cvs-revnums -s /svn/repos   /cvs/repos

The cvs repository is a CVSNT (Windows) repository that has
been copied onto a debian linux machine for conversion.
Within the cvs repos - the binary files are correctly set as
-kb.

3. The broken binary files differ in size and content as
follows:

x0d -> x0a
x0d 0a -> x0a

4. The following properties have been set on such files:

cvs2svn:cvs-rev=1.1                                     #
correct
svn:mime-type=application/octet-stream     # correct
svn:keywords=Author Date Id Revision        # wrong - should
not be set for binaries
svn:eol-style=native                                     #
wrong

5. Partly solution

When adding the parameter --no-default-eol 
the wrong eol-style will disappear and binaries will be
correctly checked out by svn.



So I would say, that something went wrong within cvs2svn for
the binary detection as well
as for setting the keyword expansion.


Hope that helps.

Greetings

   PowerStat  / Kai

____________________________________________________________
__
Verschicken Sie romantische, coole und witzige Bilder per
SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193



------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: users-helpcvs2svn.tigris.org

Kai Hofmann wrote:
> I have found the same problem here (and another one).

Maybe the problem is capitalization-related?  Our
mime-detection code is
case-sensitive.  Could it be that your file had a name like
"*.BIN" or
"*.Bin" but your mime types file only listed
"bin"?

(Still, I don't understand how a file with
"-kb" set could ever end up
with keywords set.)

> To make Pauls report more complete:
> 
> [...]
> 
> 2. I used the following line to execute cvs2svn
> 
> /usr/local/src/cvs2svn-1.3.0/cvs2svn --encoding=latin1
--no-prune --mime-types=/etc/new_mime.types
--eol-from-mime-type \
>    --cvs-revnums -s /svn/repos   /cvs/repos

From this, I assume you were using version 1.3.0 of cvs2svn.
 Would you
be able to try the same test using the current trunk
version?  The EOL
and mime-type setting code has been changed since 1.3.0, and
it would be
nice to know if the problem is still there.

> The cvs repository is a CVSNT (Windows) repository that
has been copied onto a debian linux machine for conversion.
> Within the cvs repos - the binary files are correctly
set as -kb.

This is the best way for you to help us:

Would you be able to upload one of the CVS "*,v"
files for which cvs2svn
produces incorrect output, and the /etc/new_mime.types file
that you
use?  If we can reproduce the problem, we can fix it.

Thanks,
Michael

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: users-helpcvs2svn.tigris.org