Re: cvs update: move away xyz; it is in the way

[Gary Heuston]

The reason this error is popping up is CVS is detecting a difference between
what the Entries file says and whats actually sitting in the directory.  You
might want to manually examine your Entries file for that directory (or any
you are having a problem with) and see what the differences are...as Larry
said it could even be just a random extra character in there.  Regular
changes to the repository shouldn't cause this (after all thats what update
is for!)

BTW when you blew your sandbox away, I assume you did a checkout before an
update?  I'm pretty sure you can't do an update without having some entry in
the Entries file somewhere to actually update...otherwise it should give you
a "there is no version here" error...

Gary
address@hidden

Chad Loder wrote:

> Gary,
>
> This is not the case. Yesterday, I blew away my sandbox (including all
> the CVS/ subdirectories) and did a fresh cvs update. Today, having not
> touched any of the source files, I do an update and get the messages
> I described.
>
> Now, changes maybe HAVE been made to the repository by other
> developers since yesterday's "clean" update, but not by me.
>
> Would it be worth trying to correlate these possible repository
> changes with what I'm seeing? I'd have to hunt down the logs on the
> server...
>