Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Hi getting the following error on update from 8.4.13 to 8.4.14 and for new installation of 8.4.14 during composer require command
- Installing drupal/core (8.4.4): Loading from cache
- Applying patches for drupal/core
https://www.drupal.org/files/issues/1356276-408--8.4.4.patch (Issue #1356276: Allow profiles to provide a base_parent profile and load them in the correct order)
Could not apply patch! Skipping. The error was: Cannot apply patch https://www.drupal.org/files/issues/1356276-408--8.4.4.patch
[Exception]
Cannot apply patch Issue #1356276: Allow profiles to provide a base_parent profile and load them in the correct order (https:/
/www.drupal.org/files/issues/1356276-408--8.4.4.patch)!
Any ideas?
regards,
Comments
Comment #2
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot commentedPlease make sure that you have updated your project composer.json
with the latest changes in the following link:
https://github.com/Vardot/varbase-project/blob/8.4.14/composer.json
Have you followed the Varbase Update steps?
https://github.com/Vardot/varbase/blob/8.x-4.x/UPDATE.md
When we delete the "vendor" folder
And we delete the "composer.lock" file
And we run the "composer require vardot/varbase:8.4.14" command
Varbase Procedures to the varbase base code. not in any varbase-project project builders.
We could do this in the other way:
Given that we updated our project composer.json with the latest changes in the following link: https://github.com/Vardot/varbase-project/blob/8.4.14/composer.json and keep all your extra modules or libraries.
When we delete the "vendor" folder
And we delete the "composer.lock" file
And we run the "composer update" command
After that:
Updating the active config and database from Varbase 8.4.13 to Varbase 8.4.14
Then we will have the Varbase site updated to the latest version.
Comment #3
mellowtothemax CreditAttribution: mellowtothemax commentedThanks for the reply.
Yes, I did follow the instructions correctly.
Please note that this also occurs for a new installations of 8.4.14.
This is the full output
regards,
Comment #4
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot commentedI think you had this issue before:
#2931026: Cannot update to 8.4.13
delete the "vendor" folder
delete the "composer.lock" file
and your composer.json should follow:
Please check your php, composer and git versions
php --version
composer --version
to update composer
$ composer self-update
git --version
Comment #5
mellowtothemax CreditAttribution: mellowtothemax commentedOk, so the issue was that my server runs cloudlinux, this adds users to cagefs that causes the problem with composer (as it is currently setup, it will not use system composer that has been updated so composer remains on an old version for cagefs users.)
Removing my user from cagefs allows the user to use the system composer (updated version) and the command to update finishes correctly.
Thank you for the feedback.
I think now I know why there have been issues in past updates too.
regards,
Comment #6
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot commentedGood to know that :)
This issue will be archived in case other Developers face this issue.
Comment #7
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot commented