cvs up and strange warnings for removed files

[Andrea Galbusera]

Hello CVS people,

I recently faced a strange behaviour, while using CVS update command.
Creating a file in my sandbox with the same name of a previously
removed file (I mean I file that some time in the past was in the
repository and then it was removed) and then running 'cvs -nq up',
ends up warning me with the following message:

cvs update: use 'cvs add' to create an entry for 'myfile'

Since I never noticed this before I decided to investigate and finally
found out that such a behaviour depends on the way I initially check
out my sandbox. Let me explain: checking out the source from a local
repository location draws to the warnings above, while checking out
from remote repository location gives no warning. Note that the
repository I check out from is the same: I simply change the method to
access it.

Here is the complete command sequence that makes the mismatching
behaviour reproducible. 'myfile' is a file that was previously removed
from repository.

Local checkout:
------------------------
$ cvs -d/cvsroot co -d ./sw-test-local -r mytag my/project
$ cd ./sw-test-local
$ touch myfile
$ cvs -n up
cvs update: use 'cvs add' to create an entry for 'myfile'

Remote checkout:
----------------------------
$ cvs -d:ext:address@hidden:/cvsroot co -d ./sw-test-remote -r mytag my/project
$ cd ./sw-test-remote
$ touch myfile
$ cvs -nq up
? myfile

I believe the 'remote' scenario is less confusing; this is also what I
was used to up to this morning, since I usually access the repository
from a different host.

Does anybody know the reasons behind this mismatch? Is there anything
I can do to avoid those confusing warnings. I have developers that
access the repository locally and others that connect remotely: since
I recently removed from cvs control some autotools artifacts that get
recreated inside sandbox at every build, this may lead to unnecessary
confusion for everybody.

TIA for any hint on this.

Regards,
Andrea