Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.So this commit to drush HEAD completely broke site installs in the primary platform. All site installs fail with "site already installed".
The problem is that drush now tries to bootstrap drupal as much as possible. In the primary platform, that means that it will bootstrap the hostmaster install itself (in default/) and then say that the site is already installed (which is true, in some way).
I see two ways out of this:
1. specify a "maximum bootstrap level" that drush should use (hackish, I attach a trivial patch)
2. do not install anything in sites/default
I would prefer the latter.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | drush_max_bootstrap.patch | 803 bytes | anarcat |
Comments
Comment #1
anarcat commentedComment #2
anarcat commentedTo have provision working again, we used:
...in drush.
Unfortunatly, we haven't been able to figure out the proper way to fix this. The problem is that drush bootstraps as much as it can now, but provision install needs no bootstrapping (and indeed it should prevent it). So I have experimented with my max_boostrap patch but I haven't been able to make hosting call it.
Comment #3
adrian commentedI reverted to that last working date.
I think we have enough issues in the code that proves we need to take a closer look at it.
Will do so on monday.
Setting this to needs more info until we resolve the parent issue properly.
Comment #4
Macronomicus commentedI had to revert back to 1.44 to get my rig running again.
Sorry for multiple posts in diff places... is this (provision issue cue) the best place to post stuff?
Comment #5
adrian commentedMarking this as closed, the reverted patch is being reworked to take into account some of the issues this brought out.
Comment #6
adrian commented