Closed (cannot reproduce)
Project:
Drupal.org infrastructure
Component:
Other
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Nov 2009 at 13:18 UTC
Updated:
20 Feb 2013 at 19:50 UTC
trying to update my local svn copy, and i'm getting the following:
526 colossus$~/svn.drupal.org: svn up
svn: Working copy '.' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
527 colossus$~/svn.drupal.org: svn cleanup
svn: In directory 'drupalcon/sf2010/trunk/sites/all/modules/wysiwyg'
svn: Error processing command 'modify-wcprop' in 'drupalcon/sf2010/trunk/sites/all/modules/wysiwyg'
svn: 'drupalcon/sf2010/trunk/sites/all/modules/wysiwyg/wysiwyg.api.php' is not under version control
i tried removing wysiwyg.api.php and re-running, but got the same messages.
Comments
Comment #1
sdboyer commentedUnhappy svn locks are never fun. Try removing (or, to be safe, just moving) the sites/all/modules/wysiwyg dir and running the cleanup/update again?
If that doesn't work, the output of
svn status -vwhen run on sites/all/modules/wysiwyg will be helpful to sort it out.Comment #2
hunmonk commentedmoved wysiwyg folder, ran svn cleanup, then svn up. it restored the wysiwyg folder no problem. went to the root, ran svn up -- still locked. ran svn cleanup, and i get this again:
here's the top of the svn status -v command. it looks like the base files aren't being recognized as under version control?
Comment #3
calebgilbert commentedThe problem here I believe is along the lines of corruption of some sort - I can produce this error, too. This is not a normal locking issue, which in my experience usually means I'm having a permissions issue on the system I'm trying to do the checkout on. I am also not used to seeing lock errors which include things like this:
svn: 'drupalcon/sf2010/trunk/sites/all/modules/wysiwyg/wysiwyg.api.php' is not under version control
svn deleting the wysiwyg directory, committing that, then adding it back in would do the trick to clean things up.
Comment #4
hunmonk commentedi don't think it's my place to do that in this directory... ;)
who can help out with this?
Comment #5
sdboyer commentedDid I say, "ugh, locks?" Oh yeah, I did. I'd agree with Caleb G, though, that the easiest way to fix this is really just to kill the directory and re-add the module. But if that's really not an option - request for two more types of output, from "colossus$~/svn.drupal.org/drupalcon/sf2010/trunk/sites/all/modules":
svn status -vu wysiwyg(I shoulda asked you to do the -u the first time), and alsosvn proplist -v wysiwyg. The latter prolly won't produce anything, but that 'modify-wcprop' code means its worth a shot. Probably all that is, though, is saying that it's having a problem clearing the locked property on the directory...You've prolly googled and realized it, but this doesn't seem to have an easy solution: http://article.gmane.org/gmane.comp.version-control.subversion.devel/101040
Only other thing I can really think of is trying to force it to svn update to an earlier revision, then re-updating back to the branch tip.
Comment #6
hunmonk commenteddoesn't produce any output, as you expected.
i await further instructions... ;)
Comment #7
drummNo more SVN.