Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Drupal core 8.4.3 was just released. Unfortunately, this patch provided by Lightning no longer applies cleanly:
https://www.drupal.org/files/issues/1356276-408--8.4.x.patch
This produces errors on any composer-based build of a Lightning project that tries to upgrade to 8.4.3.
Long-term, it might be better for Lightning to pin core to a specific version as long as it's being patched, even though this limits the flexibility of downstream projects somewhat.
Comment | File | Size | Author |
---|---|---|---|
#2 | 1356276-408--8.4.3.patch | 66.59 KB | phenaproxima |
Comments
Comment #2
phenaproximaOkay. Here's a reroll against HEAD of 8.4.x, as of today.
Comment #3
balsamaCurrently blocked on https://www.drupal.org/project/drupal/issues/2929211
Comment #4
balsamahttps://github.com/acquia/lightning/pull/535
Comment #5
phenaproximaLooks good to me. RTBC once the tests pass on Pipelines and Travis CI.
Comment #6
sylus CreditAttribution: sylus commentedI also had this problem, and solved it by pinning on sub profile to 8.4.2.
Comment #7
balsamaFixed in cd52b8c3a6fdf8ae97d5ae626f527c6896bb0b50
Comment #9
BXMurphy CreditAttribution: BXMurphy commentedI get this error, too, when I issue composer create-project --no-interaction acquia/blt-project my-project.
I've been doing pretty good... Drupal, Drupal VM, VirtualBox, Vagrant, Ubuntu WSL with reverse-mount shares. I even nailed a Triple Lutz (Russian judge gave me an 8.2).
And all I wanted was a nice website that I could maintain some PHP and MySQL pages in. I didn't even get a t-shirt.
How is this fixed? Somebody said, "Fixed in cd52b8c3a6fdf8ae97d5ae626f527c6896bb0b50." I don't get it.
I'm trying to do jgeerling's thing at https://www.jeffgeerling.com/blog/2017/set-blt-and-drupal-vm-entirely-wi...
I went to the Forum for help but I don't see a search function to look for an answer. Can someone point me in the right direction? Is this a Composer issue? A "well, you really can't run Drupal on a Windows box" thing? Please help. I'd hate to admit defeat and be boxed in by Wordpress yet again.
Sorry for venting..
Comment #10
casc-or CreditAttribution: casc-or as a volunteer commentedBXMurphy, you're not the only one - I'm following the exact path you are and got the same error this morning (but not yesterday).
If I find a solution/workaround I'll message.
Comment #11
Dane Powell CreditAttribution: Dane Powell at Acquia commented@BXMurphy and @casc-or, it's hard to say for sure since you didn't post any clear error messages or output from composer install, but based on the timing I expect you are actually hitting a new version of this bug.
This bug applied to Drupal core 8.4.3. If you check your composer output, it's probably trying to install 8.4.4.
The Lightning team is aware of this problem, I think this is the right issue to follow: #2934239: Update to core 8.4.4
As a workaround, you should be able to pin your version of Drupal core to 8.4.3 in your own composer.json.
Comment #12
casc-or CreditAttribution: casc-or as a volunteer commentedNote that this is a BLT install.
Composer command
composer create-project --no-interaction acquia/blt-project casc-blt
Composer output excerpt
Comment #13
techwolf12 CreditAttribution: techwolf12 at Unc Inc commentedThis could happen because of the docroot folder. Composer patches has a pull request for this: https://github.com/cweagans/composer-patches/pull/204
:)