Update: I have installed the latest development version 2.0.9.1, and
it can now do imports without this assertion failed error.
On 18/07/07, chrisyate < chrisyate%40gmail.com">chrisyate
gmail.com> wrote:
>
>
>
>
>
>
>; Did anyone manage to resolve this issue? It's a bit of a non-starter
> if I can't import a project.
>
>; I've previously had to use Cygwin's cvs to import a project, which can
> then be managed from WinCVS. That's not really acceptable.
>
> I'm using the latest CVSNT 2.5.03 and WinCVS 2.0.2.4, with cvs 1.11.22
> on the server.
>
> thanks,
>
> Chris
>
> --- In cvsgui%40yahoogroups.com">cvsguiyahoogroups.com, "Oliver Giesen" <ogware...> wrote:
> >
>; > phuong tran wrote:
> >
>; > > We use WinCvs 2.0.2.4, cvsnt 2.5.03 on client side, we
> > > use putty,pagent to connect to server with ssh. On our
> > > suse server, we have CVS 1.12.12. I tried to use :ssh:
> > > instead of :ext: and still have the same error
> > > message.
> > > ----------------------------------------------------------
> > > Filtering 'C:devdevrootmodulessystemlib'...
> > > cvs -d
> > > :ssh;username=anhstar;hostname=cvssession:/usr/local/cvsroot
> > > import -I ! -I CVS -W "*.jar -k 'b'" -m "no message"
> > > -- system avendor arelease (in directory
> > > C:devdevrootmodulessystem)
> > > cvs import: Importing /usr/local/cvsroot/system/lib
> > > N system/lib/system.jar
> > > cvs [import aborted]: received abort signal
> > > cvs: import.c:640: process_import_file: Assertion
> > > `entdata->options[0] == '-' && entdata->options[1] ==
> > > 'k'' failed.
> > > ----------------------------------------------------------
> >
>; > Actually this is the first time I can remember where CVS reports this
>; > kind of low level information about an error, i.e. the source file and
> > the actual line of code the error occurred in. Could it be you're
> > running a debug build of CVS on your server or something like that?
> >
>; >
>; > > I also tried to import from the commandline but
> > > nothing happens once I press enter by using this
>; > > command in the console:
> > > cvs -d
> > > :ssh;username=anhstar;hostname=cvssession:usrloc
> > > alcvsroot import -m "" modulesspacedemo system
> > > initial
> >
>; > Hmm, sorry, I have no idea...
> > Try to rerun the command adding "-ttt" right after the "cvs". Maybe
> > there's something useful in the trace output...
> >
>; >
>; > > At first I thought that the .jar file was the problem,
> > > so I created a small project with some textfile in it
> > > and then try to do a commit, no error at all but
> > > winCvs dint mark the project and theres no CVS folder
> > > in the project on client side.
> >
>; > How on earth did you manage to do that??? You cannot commit files
> > unless the files have already been added and for that to happen in the
> > first place the folder they are located in has also already have to
> > have been added to the repository. There must have been a hidden CVS
> > folder even before the commit, otherwise CVS would have no idea where
> > in the repo to place the new files. But I guess I'm probably just
>; > completely misunderstanding you... :(
> >
>; >
>; > > However on the server
> > > side, the new project is there. I had to do an update
> > > on the project and delete all the files in it before I
> > > can see CVS folders in the project. And now, when I
> > > put a jar file in the project, I can use the commit
> > > command and it will be committed without error.
> >
>; > Very, very strange. Are you able to perform tests with a different
> > server?
> >
>; >
>; > > Wincvs dont like me, maybe jCVS is the solution.
> >
>; > AFAICT it isn't even working from the commandline so why should a
> > different frontend make a difference? Or is jCvs working indeed?
>
.
