Closed (won't fix)
Project:
Drush
Version:
8.x-6.x-dev
Component:
Core Commands
Priority:
Normal
Category:
Feature request
Assigned:
Issue tags:
Reporter:
Created:
15 Nov 2011 at 21:13 UTC
Updated:
25 Feb 2016 at 19:22 UTC
Jump to comment: Most recent
Comments
Comment #1
greg.1.anderson commentedWouldn't it meet your requirements to just run
drush dis updateafter the site install completes?Comment #2
paul kim consulting commentedThat could work. However, there are sometimes very strict requirements around a new install talking to anything on the internet. Drush seems to segment fault when the update module can't talk to updates.drupal.org during installation of the update module. This is what I'm seeing when talking to updates.drupal.org is disabled (by firewall?):
This is what i'm seeing when there is no restriction in place:
Comment #3
greg.1.anderson commentedThis issue was marked
closed (won't fix)because Drush has moved to Github.If this feature is still desired, you may copy it to our Github project. For best results, create a Pull Request that has been updated for the master branch. Post a link here to the PR, and please also change the status of this issue to
closed (duplicate).Please ask support questions on Drupal Answers.
Comment #3.0
greg.1.anderson commentedFix typo.
Comment #4
kenorb commentedPossible workaround:
drush site-install foo_profile install_configure_form.update_status_module='array(FALSE,FALSE)'This also can be overridden in hook_form_FORM_ID_alter, like: