Applying a patch to Drupal CVS checkout
Applying a patch.
You can just use the link to the patch from the issue queue (in this example, in a post by galapas to my usability request) to fetch the patch directly with wget:
ben@server:/var/www/drupal6$ sudo wget http://drupal.org/files/issues/system-admin-inc.193034.patch
Then apply the patch:
ben@server:/var/www/drupal6$ sudo patch -p0 < system-admin-inc.193034.patch
Didn't like it much, so reversed it:
ben@server:/var/www/drupal6$ sudo patch -p0 -R < system-admin-inc.193034.patch
and got the alternatives supplied by the same amazing galapas:
ben@server:/var/www/drupal6$ sudo wget http://drupal.org/files/issues/system-module.193034-alt.patch
ben@server:/var/www/drupal6$ sudo wget http://drupal.org/files/issues/system-admin-inc.193034-alt.patch
All this followed setting up a test environment, which had been done like so:
ben@server:/var/www$ sudo cvs -z9 -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal checkout -d drupal6 drupal
Edited an apache sites-available file to point at the new directory.
(In this case, I reused a database, so skipped that case)
And then made the directories writable:
/var/www/drupal6$ sudo chown www-data:www-data sites/default
and:
/var/www/drupal6$ sudo chown www-data:www-data files
Aside: can the CVS be made to checkout with the proper permissions? (Answer: permissions apparently yes, but ownership goes to root if you have to use sudo to do the checkout.)
Comments
Post new comment