- Issue created by @trickfun
- Status changed to Needs review
4 months ago 12:50pm 9 August 2024 - 🇮🇹Italy aronne
Hi @trickfun and thank you for opening this issue.
Could you please try again after applying this patch?Regards,
aronne - Status changed to RTBC
3 months ago 4:51pm 14 August 2024 - 🇧🇪Belgium gorkagr
Hi!
I think trying to apply a patch for a composer.json and then trying to do smth related with composer is smth that always fails (at least for me)
However, if i edit by hand my composer.lock with @aronne modification and also (just in case) the http_client_manager composer.json, and then i runcomposer require drush/drush:^13.0
, then all good:- Installing illuminate/macroable (v11.20.0): Extracting archive - Installing psr/simple-cache (3.0.0): Extracting archive - Installing illuminate/contracts (v11.20.0): Extracting archive - Installing illuminate/conditionable (v11.20.0): Extracting archive - Installing illuminate/collections (v11.20.0): Extracting archive - Installing laravel/prompts (v0.1.24): Extracting archive - Upgrading drush/drush (12.5.3 => 13.0.1): Extracting archive
I also think that in the patch doing
^12|^13
could workBest
- 🇺🇸United States wrd-oaitsd
Yeah, I've run into this as well. It's primarily a problem because the new core Recipes feature only works with Drush 13. Recipes can be applied using core/scripts/drupal, but I can't seem to get that working for a remote site.
- 🇺🇸United States wrd-oaitsd
For the moment, my workaround is to use an alias to install Drush:
composer require drush/drush:"13.1.1 as 12.5.3"
This seems to be working, although it breaks site creation in Acquia Cloud Site Factory.
- First commit to issue fork.
- 🇮🇹Italy aronne
@emanuelrighetto MR merged,
thank you guys for your contribution.Regards,
aronne Automatically closed - issue fixed for 2 weeks with no activity.