Here is the code I run in my bash script:
for site in ${sitelist}; do
sudo -u www-data drush upc --no-core -l http://dev.$site \
--backup-dir="${webroot}/drush-backups"
done
On the first site, a module is found to need an update, and therefore it is updated. Drupal core is not updated. Great, Drush respects my --no-core parameter! On the second site, --no-core is not respected and it asks if I want to update Drupal core. If I choose yes, it performs the update.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | debug.txt | 49.24 KB | Tor Arne Thune |
Comments
Comment #1
moshe weitzman commentedWe need --debug output from when you run against the problem site alone.
Comment #2
Tor Arne Thune commentedSorry about that. Had to redo the updates to save the debug output. Attachment is the output of the 2 sites updated by the script.
As can be seen, the first update respects --no-core, when an update to Drupal core is available. The second update finds 1 update to Drupal core, and does not respect --no-core, as it asks if I want to update it (as I do just to show more debug info).
Comment #3
jonhattanFixed in master.
Comment #4
jonhattancherry pick http://drupalcode.org/project/drush.git/commit/e32e44e
Comment #5
Tor Arne Thune commentedI've noticed that this only happens when there are no updates available other than Drupal core. That is, when there are other updates, Drush respects --no-core, but when the only update available is Drupal core, it does not respect --no-core.
Comment #6
msonnabaum commentedBackported.