working copy path ‘foo’ does not exist in repository.
3 Apr, 2006
Once in a while Subversion will come back at you with a strange error like the "working copy path does not exist in repository" one I was just stuck on for half an hour.
In most cases, this one included, the problem can be alleviated by wiping out the offending directory in your working copy and re-updating. Of course, if you've got changes you're trying to commit you'll want to back those up somewhere so you can re-edit the file(s) in question once you check them back out.
One instance of this problem mentioned that it was also necessary to rename the offending file, commit the change, then rename it back, but so far I haven't needed to do that.
Tagged:
Also
- Login to post comments
Popular
Recently Perused
- If you're attending #drupalcon and you happen to be a #freemason, how about a BoF and/or lodge visit? http://is.gd/byget #mason — 4 years 38 weeks ago
- RT @nicklewisatx: I think I speak for all of #drupalcon when I ask @dries to announce that #drupal is declaring war on volcanoes — 4 years 38 weeks ago
- If science had been able to harness the power of Jack Webb's hatred for hippies, we could have stopped using oil decades ago. #fb — 4 years 38 weeks ago
- The #Drupal blueprint module adds its own JS which may break various ajax form submission modules. http://is.gd/bx5YE — 4 years 38 weeks ago
- Remember, kids: Check your #drupal module weights when your hook_form_alter() seems not to be working. — 4 years 38 weeks ago
5 comments
Fancy meeting you here. I
Fancy meeting you here.
I just had this problem, and, indeed, renaming the file, committing, merging (which is where I got the error), and then renaming the file back did the trick.
svn is beginning to really bug me with all its ghosts.
(Errr… That was left by
(Errr… That was left by Jeremy Rice!)
You’re the second
You’re the second acquaintance to express that sentiment about svn lately. It’s actually been a pretty good while since I ran into any weird ghost/locking problems, but maybe that’s because I’m usually the only person working with a given section of the repository.
I have heard good things about Mercurial (http://www.selenic.com/mercurial/wiki/).
Subversion is driving me
Subversion is driving me nuts. I have to handle very large changesets and merge problems with a fairly large team of developers, and when I get stuck with this problem (Working copy path X does not exist in repository) I just want to scream. It’s clearly there! Why can’t you see it? sob
This error is KILLING ME. The
This error is KILLING ME. The other devs I work with want to use Visual SourceSafe for source control (PUKE), but I can’t very well justify choosing SVN over VSS when they see me stuck for hours on nonsense like this. I’m going to close the door and cry now…