By luyendao on

I've tried a number of upgrade paths from Drupal 6.15 -> Drupal 6.20 encountering major problems because of SVN version control, copying and pasting from another folder causes a lot of conflicts, the closest I got was to use 'rsync' which seemed to partially work, but then I got all kinds of code errors from the modules themselves and also causes versioning problems.

I've been able to update contributed modules very easy using drush pm-update --svnsync --svncommit _module_name but haven't been able to try it with core yet because i was still resolving errors above.

Anyway, i won't bore you with the details, i'm hoping someone has done this before can just tell me has worked so I can save some time!

Thanks for any tips.

⋅ Categories: Drupal 6.x

Comments

Ross-Hunter’s picture

Ross-Hunter commented

I can't speak specifically to upgrading from 6.15 -> 6.20 - but we use Drush up --svnsync but we don't use --svncommit. We then revert the files directory and .htaccess, then commit. I am assuming you are not versioning the files directory (because you shouldn't) and so whenever a module tries to make changes to the files directory it is causing your error.