Aegir 3 is incompatible with Drush 9+

Anybody by chance have Aegir 3 working with Drupal 10? We were able to get Drupal 9, but I've tried to apply some of the above solutions to Drupal 10 and not having any luck.

TL;DR BOA supports Drupal 10 while running slightly modified Drush 8. We don’t need newer Drush versions and we shouldn’t.

Longer version follows.

Aegir 3 can work only with Drush 8 because it’s the only still supported Drush version which can be reliably used as standalone Drush.

All post-8 Drush versions up to 11 could theoretically be used as standalone (on command line but not with Aegir) if their dependencies matched the managed Drupal site code, which in practice happens rarely and thus should be used as site-local only.

Composer doesn’t care about possible versions conflicts between Drush and Drupal and you could get pretty different versions of the same Drush release installed depending on when you have installed it. This makes using them as standalone a completely unpredictable mess.

That’s why Drush 12 has been officially announced as the first version which can’t be used as standalone at all — no matter how hard you would try.

The only question was therefore: can we make the old good Drush 8 able to avoid conflicts despite aggressive deprecation coming with Drupal 10?

It seemed impossible initially, so we at Omega8.cc launched a complete rewrite of our BOA stack to make it use Aegir 3 without Drush — at least without the way it was always used, based on bootstrapping Drupal directly, with the intention to use it as a bridge with our own backend code, not affected by any Drush and Drupal compatibility issues.

It turned into serious rabbit hole and we have realized we couldn’t make it a mature enough project before Drupal 9 EOL, which in turn got us back in the dirty hacking and trying to make things work, removing obstacles as we go through tedious and frustrating debugging and testing cycles.

We didn’t believe it was possible, really, but we just wanted to give it a try before taking the risk of switching horses completely and without option to go back.

Guess what.. it worked! We are planning to release it tonight and upgrade all hosted Aegir systems later this night. More details are coming once we have more free time.

Take a look: https://github.com/omega8cc/boa/issues/1678#issuecomment-1778803057

Hey @memtkmcc glad you got it figured out! Would you mind sharing what would work for those of us not on the BOA stack? I tried installing the BOA drush 8 fork and using your D10 patch posted on your github, but I must be missing something still as my site install task still contains errors. Are you installing drush 11/12 on the site level? Any help or direction would be greatly appreciated. Thanks for all your efforts!

Hey @porchlight, we are currently preparing to backport our patches to all relevant parts of Aegir and will also post a how-to to list requirements and changes normally automated in BOA but requiring some simple manual work for standalone Aegir. New issues will be opened to track this process.

@memtkmcc AMAZING! Looking forward to it! Thanks for the quick reply

DevShop runs hosting 4.x and provision 4.x in a composer platform, which includes drush8.

Then, drush 10/11 is installed globally.

Running drush @hostmaster works, properly passes from drush 11 to site-local drush8 in hostmaster.

https://github.com/opendevshop/devshop/blob/1.x/src/DevShop/Control/comp...

It uses provision 4.x and hosting 4.x branch, which is just a stopgap for current generation. Lots of hacks to get DevShop more stable. I added drush9+ yml alias ge eration so "drush sa" works with both drush 8 and 9+.

If someone wants to take this back to aegir, feel free.

It works.

Trying to use your composer file @jon-pugh
"The `url` supplied for the path (../../../devmaster) repository does not exist"

The file is for devshop, it will need to be updated for aegir.

I'll try to set aside some time this week to do this.