I use drush to install core and modules.

But as far as I can tell, drush cannot update core. Is this still correct?

I have been trying to understand a number of issues/posts about this subject, but I am not a coder and so I don't understand whether drush is now ready/capable of updating the core.

An update on the module would be much appreciated.

Comments

moshe weitzman’s picture

moshe weitzman commented
Status: Active » Closed (duplicate)

In another issue, we are contemplating how best to allow minor core updates. No code has been committed.

I should add that we already support the database part of updating both minor and major versions of core.

drupaloo-1’s picture

drupaloo-1 commented

Thanks very much for your quick response and the update.

I think it is as it stands now, it is already a very capable and worthwhile module/program.

However, since it cannot update core at this time, I have learned how to install and update core and modules using CVS.

But I would much rather use drush, so if I can help test a future release of this functionality (as a non-developer user) please let me know.

intuited’s picture

intuited commented

Hi,
I've been using the following method to update the drupal filesystem:

Note that there may be some options to diff or patch missing; I actually use git diff, as I've built a git repo whose revisions are the contents of successive versions of the Drupal install tarballs. git diff has a somewhat different (superior?) format to plain diff so this may work differently.
This approach gives a lot of the benefits of CVS updating, especially if you're using a patched core, but is convenient if you're not using a CVS version of Drupal (it's a bit complicated to switch it over).
You'll also need to manually copy over any binaries that changed, like for example the file modules/openid/login-bg.png for the example given.
You can also do convenient things like

$ diff drupal-6.13/sites/all/default/default.settings.php drupal-6.14/sites/all/default/default.settings.php | patch $DRUPAL_INSTALL/sites/all/default/settings.php

to apply updates to the default settings file to your site's settings file.

tarzadon’s picture

tarzadon commented
Component: Code » PM (dl, en, up ...)

Thanks for the tips intuited !

On my dev server, I did:
diff -crB drupal-6.19 drupal-6.20 > drupal-6.20.patch
Then, on my production server, I did:
patch -p1 < drupal-6.20.patch

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Just a note that these days, Drush can, in fact, upgrade Drupal core. :)

drush up drupal

Or, if you want to upgrade both core and all contributed projects:

drush up

kevinquillen’s picture

kevinquillen commented

Doing 'drush up drupal' just put drush into an endless loop of checking contributed modules with 5.0-rc2.

kevinquillen’s picture

kevinquillen commented

Odd. On the third try it worked. I had better results with drush pm-update drupal, too.

DocDJ-forum’s picture

DocDJ-forum commented
Issue summary: View changes

I've been trying to apply the Drupal 7-29 security update with "drush pm-update projects drupal-7.29" and am getting an error message that:

drush can't find /modules/entity/includes/entity.inc

although I can see it in Windows Explorer. I've seen a post that I could just extract all the files into their corresponding locations, but that means taking the site offline by hand, etc. Is there a way I can fix this error? My include_path for PEAR is properly set (all the tests worked). Windows, Apache 2.4, PHP 5.6, Drupal 7-28.