The first alpha for Drush 9.x was released 4 weeks ago. Currently, if Drush 9.x is used, provision will fail with the error: "Error: Drush !version is not supported". This is not a duplicate of #2554029: Error: Drush !version is not supported, although they both likely involve similar or related code blocks re: version detection/validation of Drush.

The fix to this is a simple additional case in the select statement at line 87 of platform/drupal/install_7.inc to add the substr(drush_core_version(), 0, 1) = 9 case to fall through to the Drush 8.x case that falls through to the Drush 7.x case.

I'll revise this shortly with a patch against dev, 7.x-3.x.

Comments

JamesAn created an issue. See original summary.

JamesAn’s picture

Issue summary: View changes

Amended tag and branch head targets for this issue's patches. 7.x-4.x is a dev branch without yet much activity; i.e. there's no practical point in patching against it.

JamesAn’s picture

Issue summary: View changes
Status: Active » Needs review
StatusFileSize
new451 bytes

Here's the patch against 7.x-3.x. Applying this patch to either 7.x-3.x or 7.x-3.4 works and in both cases, the patched code can successfully be used to execute a clean hostmaster-install and run various drush-initiated provision commands and hostmaster-initiated tasks including verifying all initial Aegir entities and enabling the hosting daemon along with its backend systemd service.

I don't notice any unexpected side effects, although I haven't been thorough at all. Can someone corroborate this one-liner feature add?

JamesAn’s picture

Version: 7.x-4.x-dev » 7.x-3.x-dev

Correcting the dev version in which this issue is being addressed: 7.x-3.x.

  • helmo committed f868fcd on 7.x-3.x authored by JamesAn
    Issue #2701145 by JamesAn: Add support for Drush 9.x
    
helmo’s picture

Status: Needs review » Fixed

I haven't had a chance to test Drush 9 but this makes perfect sence... committed. Thanks.

colan’s picture

Issue summary: View changes

Added a missing "#" in an issue link in the description.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.