Hi,
> I have seen a similiar problem.
> I was unable to trace it to the source.
Yes, I did too. It happens with cvs if you mess-up somehow the
administrative files (CVS/Root, CVS/Repository). If you make a check-out of
the same module but with a different CVSROOT for example.
I'm not completly sure, thought.
Regards,
alex.
Alexandre Parenteau
Software Engineer
http://www.3d.com
----- Original Message -----
From: "Michael S. Tsirkin" <[EMAIL PROTECTED]>
To: "David L. Martin" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, August 18, 2000 3:18 AM
Subject: Re: WinCVS "In the way" Update Problem
> Hello!
> I have seen a similiar problem.
> I was unable to trace it to the source.
> MST
>
> Quoting r. David L. Martin ([EMAIL PROTECTED]) "WinCVS "In the way"
Update Problem":
> > Greetings,
> >
> > I'm using WinCVS 1.1b13 on NT in pserver mode against a Solaris 2.6
server running cvs 1.10.8. I have a checkout area in which I only perform
"cvs update -Pd" (no editing is done in this area). Occasionally for some
directories I get the following error for each file in the directory, such
as:
> >
> > cvs server: Updating
> > ics/infra/src/com/ec/infra/busproc/addressbook/exception
> > cvs update: move away
> >
ics/infra/src/com/ec/infra/busproc/addressbook/exception/AddressbookBusiness
Exception.java;
> > it is in the way
> > C
> >
ics/infra/src/com/ec/infra/busproc/addressbook/exception/AddressbookBusiness
Exception.java
> > cvs update: move away
> >
ics/infra/src/com/ec/infra/busproc/addressbook/exception/AddressbookExceptio
n.java;
> > it is in the way
> > C
> >
ics/infra/src/com/ec/infra/busproc/addressbook/exception/AddressbookExceptio
n.java
> >
> > I understand why this error is normally generated (when the user has
manually created a directory which CVS does not recognize from its Entries
file as having created, and CVS subsequently tries to create the directory
as a result of a cvs update). For this case, however, no manual editing has
been done in the working area.
> >
> > Looking at the CVS/Entries file under addressbook, there is no directory
entry for "exception"; therein lies the problem. For some reason, during
the checkout or update -d in which the exception directory was originally
created, the Entries or Entries.log file was not properly modified to
include "exception". The workaround is to delete the exception directory
and update again, at which time the Entries.log is created and then on
subsequent update, the Entries file is appropriately modified.
> >
> > Has anyone else seen this problem?
> >
> > Thanks,
> > David
> >
> >
> >
>
> --
> This message content is not part of Intel's views or affairs
> Michael S. Tsirkin
> > Four things are to be strengthened: Torah,and good deeds,
> > prayer and one's good manners (Berachoth)
>
>
