Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
> C:\Program Files\Apache Group\Apache2\cgi-bin>cvs import -C -n -I
> EditCaseWorkShafiSieg.pl -I test_component04.mdb -I
test_component03.mdb -I
> test_component02.mdb -I test_component01.mdb -I test_components02.ldb -m
> "initial structure" CONVEX/cgi-bin vendor-tag start
As I wrote before in another reply, why did you specify a vendor branch
("vendor-tag") and release tag ("start") if you at the same time explicitly
tell CVS not to use them (-n)? I don't know how CVSNT reacts to this. It
will have to ignore either the -n or the tags...
What was the result of this import? Did it produce any errors? It is not
entirely clear from your descriptions (maybe I have just been missing some
bits of the discussion) at what point exactly CVS started to
misbehave/deviate from your expectations...
> I goofed and misspelled some file names and had to use cvs remove -f
*.mdb.
At what point exactly did that misspelling take place? Before the import?
Were the filenames themselved misspelled or did you just misspell them when
specifying them in a commandline?
> Was I supposed to perform the commit
> before I make modifications?
No, commit is always what comes last. Commit sends your local changes to the
server.
Taking into account the info from your other posts it seems that for some
yet unresolved reason the metadata in your sandbox is broken and thus CVS is
looking in the wrong place for files to append the new revisions to. I guess
if you take a look inside the ./CVS/Repository files you will find that they
do not contain the repository path that their parent directories are
supposed to correspond to. I have no idea though how that erroneous data got
into there...
Cheers,
--
Oliver
---- ------------------
JID: ogiesen at jabber.org
ICQ: 18777742 (http://wwp.icq.com/18777742)