Comments on: ‘cvs update: move away foo.bar; it is in the way’

By: gemGirl

gemGirl — Fri, 11 Mar 2011 05:08:26 +0000

Hi,

I was having the same problem, and my cvs folder structure was something like this

D:\CVS\ProjectName which has my dev, docs and all other cvs folders and ALSO a “ProjectName” folder having all the same dev, docs and other cvs folders. I was getting the “cvs update: move away xxxx.xx; it is in the way” error when ever i try to do an update.

I did a fresh cvs check out and there is no “ProjectName” folder inside my D:\CVS\ProjectName after new checkout. The cvs update is working fine now :)

By: david weisz

david weisz — Fri, 13 Nov 2009 17:15:57 +0000

i had this problem in win cvs after someone else copied one file and gave it the same name with the first letter capitalized

after moving the first file to the recycling bin i got the new one.

i think even though my local is on a samba share windows gives us a hard time bc it considers both files the same

By: Harry Mahoney

Harry Mahoney — Fri, 11 May 2007 21:37:56 +0000

In a case of this happening to us, we finally figured out a work-around using WinCVS:

We were trying to do a checkout with a tag and a module name to update a folder. We were getting this “move away” error on every file. Repeating the same command in WinCVS did not show any errors.

As you probably know, WinCVS shows its command line for each command you do. We noticed that it was always adding the global option -d with the login information for the repository. After much trial and error, we added this same option string to our command line and the problem disappeared. We are running CVSNT 2.5.03.2303 on Windows Server 2003.