[cvsnt] Why does CVSNT not update some folders????

[Bo Berglund]

Well,
I might have checked out the various submodules of the top module at
different times and there might have nbeen different versions of CVSNT
living both on the server and the client.

But my main question is really this:
Where does CVSNT keep its checkout data except in the CVS subdirectories?
AFAICT the CVS folder in the parent directory contains all needed info in
the Entries and Entries.Extra files to define my Module4 as a submodule.
And the CVS folder in Module4 contains valid info concerning the files and
folders contained therein. This is witnessed by the fact that an update
started from the Module4 folder runs without a hitch.
But an update one level up does not even go down into Module4 and if I add
the flag for creating the directories then I get the "move away" error
messages.
So there *must* be some extra trick being played here that makes Module4
different from all the other modules even though the Entries files in the
parent CVS folder lists Module4 as a directory just as the other modules.

Really puzzling!

BTW, if I move away the Module4 folder (rename to something else) and do
an update with create folder flag set then of course Module4 is recreated.
But that was really not my issue, I want to understand what is going on.

/Bo


-----Original Message-----
From: Glen Starrett [mailto:grstarrett at cox.net]
Sent: den 12 november 2003 00:03
To: bo.berglund at telia.com; cvsnt at cvsnt.org
Subject: RE: [cvsnt] Why does CVSNT not update some folders????


> When I do an update on Tools only 4 out of the 5 submodules get
> updated and if I check the "create missing directories..." checkbox
> the update issues a lot of error messages telling me to move away the
> files cause they are in the way.

Did you try:

--moving the offending directory,
--removing it's CVS directories,
--cvs up -d Tools

I'm guessing it's likely a case sensitivity problem or missing Module4\CVS
folder or similar.  Just let CVS straighten itself out.

Awhile ago I had thought you could just check out a module within another
sandbox (or perhaps move one in later after it was updated), but that didn't
work as I had expected when I tried it later.  Did you create this using a
non-standard method?

Regards,

Glen Starrett