Solutions based on my experience:
1) Use a different Dir for your xml workspace, such as G:\newApacheXML, then
set CVSROOT (or alternatively use cvs -d ...), then cvs login, cvs checkout,
etc.

2) Delete every XML related packages and files (xml-xerces, xml-xalan, etc)
from under G:\download, then reset CVSROOT (or alternatively use cvs -d
...), then cvs login, cvs checkout, etc.

If you look at /path/to/xml-xerces/CVS/Root, you will find this line:
:pserver:[EMAIL PROTECTED]:/home/cvspublic (old one)
:pserver:[EMAIL PROTECTED]:/home/cvspublic (new one with xml.apache.org
as the cvs server).

It may have sth. to do with that difference of the names of the cvs server.

So, you may also be able to just hack that line by changing "dev.apache.org"
to "xml.apache.org", and see if it works without having to either use a new
workspace dir or deleting the old xml related package dirs.

Interesting how we can so often be trapped by all the unexpeted ripple
effects.

regards,
-Shaoping

----- Original Message -----
From: "Wong Kok Wai" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, November 27, 1999 8:27 PM
Subject: Re: Missing checkins?


> Ok I got a new problem with the new CVS server. Now whenever I checkout, I
always get a
> "CVS.EXE checkout: move away <filename>; it is in the way" message for
each file. Any
> ideas about this problem?
>
> G:\Download>cvs -z 3 -d :pserver:[EMAIL PROTECTED]:/home/cvspublic co
xml-x
> alan
> CVS.EXE checkout: warning: unrecognized response `cvs: setgroups:
Operation not
> permitted' from cvs server
> cvs server: Updating xml-xalan
> CVS.EXE checkout: move away xml-xalan/BUGS; it is in the way
> C xml-xalan/BUGS
>
> PS: The above is a snippet when checking out xalan but it is true for all
modules.
>
> Wong Kok Wai wrote:
>
> > I've got the answer from Brian: it is due to the change of CVS server,
it is now at
> > :pserver:[EMAIL PROTECTED]:/home/cvspublic
> >
> > Stefano Mazzocchi wrote:
> >
> > >
> > > I got them, but I'm not doing anonCVS. Maybe a group visibility
problem?
> > >
>

Reply via email to