Comments on: ‘cvs update: move away foo.bar; it is in the way’ http://www.missiondata.com/blog/system-administration/81/cvs-update-move-away-foobar-it-is-in-the-way/ Louisville-based Web Development & Software Engineering Thu, 13 May 2010 10:34:28 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: david weisz http://www.missiondata.com/blog/system-administration/81/cvs-update-move-away-foobar-it-is-in-the-way/comment-page-1/#comment-165440 david weisz Fri, 13 Nov 2009 17:15:57 +0000 http://www.missiondata.com/blog/utilities/81/cvs-update-move-away-foobar-it-is-in-the-way/#comment-165440 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 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 http://www.missiondata.com/blog/system-administration/81/cvs-update-move-away-foobar-it-is-in-the-way/comment-page-1/#comment-19742 Harry Mahoney Fri, 11 May 2007 21:37:56 +0000 http://www.missiondata.com/blog/utilities/81/cvs-update-move-away-foobar-it-is-in-the-way/#comment-19742 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. 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.

]]>