2013-04-20 09:59 AEST by Arthur Barrett - When you use CVSNT client with CVS 1.x server and import a 'binary' file (a file that the 'client' or 'server' 
identifies as 'b') then it fails:


cvs import -I ! -m "Initial import" this/is/anotherthree/test vendor start
N this/is/anotherthree/test/aaa.aaa
cvs: import.c:635: process_import_file: Assertion `entdata->options[0] == '-' && entdata->options[1] 
== 'k'' failed.
cvs [import aborted]: received abort signal


This can commonly occur with '.exe' files...


The CVSNT client sends:
Argument this/is/anotherone/test
Argument vendor
Argument start
Directory .
/tmp/cvsrepo/this/is/anotherone/test
Kopt b
Modified aaa.exe
u=rw,g=r,o=r
8
aaa
aaa
Modified aaa.txt
u=rw,g=r,o=r
8
aaa
aaa
import




The CVS 1.x client sends:
Argument this/is/athree/test
Argument vendor
Argument start
Directory .
this/is/athree/test
Modified test.txt
u=rw,g=r,o=r
10
test
test
Kopt -kb
Modified test.exe
u=rw,g=r,o=r
10
test
test
import




Since the CVSNT server should accept either "Kopt -kb" or "Kopt b" it's probably easiest to force the 
CVSNT import to use the 'older' method.  The alternative is to send different variations depending on the 
server version.

2013-04-20 10:09 AEST by Arthur Barrett - I've tested and reproduced this here using
Client: Concurrent Versions System (CVSNT) 2.8.01 (Soolin) Build 4377 (client/server)
Server: Concurrent Versions System (CVS) 1.12.13 (client/server)



The workaround is to use TortoiseCVS to 'add' the directory, then use tortoisecvs 'add all'.  I've checked 
that this works OK.