I love drush, but since moving to version 3 recently, I'm having problems with drush up.
I use subversion for version control, and when I try to run update, the first thing it does is to move the entire directory of any module that needs updates to the backups tree. This sounds like a good idea, but unfortunately my .svn files are moved too, giving me subversion errors, and essentially losing my historical changelog.
I don't see any switches in the code that I could use to disable this function. I've seen references to cmd line options like "--version_control" and "--svnsync" in the code, but haven't found any documentation on how these are used.
Are these features working? Is there a tutorial or other resource documenting them? Can they be disabled without hacking the drush code?
I really miss being able to do a one click code and database update!
Comments
subscribe
subscribe
subscribe
subscribe
subscribe
subscribe
This looks like a bug, not a
This looks like a bug, not a support request, so it would be best to take it to the drush issue queue.
You can select the cvs package handler in your drushrc.php via:
$options['package-handler'] = 'cvs';
This will cause drush to use cvs instead of wget to get module code. Drush pm-update svn version control should be selected automatically when there are .svn files in the module directory; the fact that drush seems to be using backup version control is, I think, a bug.