diff options
Diffstat (limited to 'nixpkgs/pkgs/build-support/php/hooks/php-script-utils.bash')
| -rw-r--r-- | nixpkgs/pkgs/build-support/php/hooks/php-script-utils.bash | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/nixpkgs/pkgs/build-support/php/hooks/php-script-utils.bash b/nixpkgs/pkgs/build-support/php/hooks/php-script-utils.bash index 9b5978865634..bba0242e65d1 100644 --- a/nixpkgs/pkgs/build-support/php/hooks/php-script-utils.bash +++ b/nixpkgs/pkgs/build-support/php/hooks/php-script-utils.bash @@ -21,6 +21,10 @@ checkComposerValidate() { echo -e '\e[31mThe validation of the composer.json failed.\e[0m' echo -e '\e[31mMake sure that the file composer.json is valid.\e[0m' echo + echo -e '\e[31mTo address the issue efficiently, follow one of these steps:\e[0m' + echo -e '\e[31m 1. File an issue in the project'\''s issue tracker with detailed information, and apply any available remote patches as a temporary solution '\('with fetchpatch'\)'.\e[0m' + echo -e '\e[31m 2. If an immediate fix is needed or if reporting upstream isn'\''t suitable, develop a temporary local patch.\e[0m' + echo exit 1 else echo @@ -29,6 +33,10 @@ checkComposerValidate() { echo -e '\e[33mThe validation of the composer.json failed.\e[0m' echo -e '\e[33mMake sure that the file composer.json is valid.\e[0m' echo + echo -e '\e[33mTo address the issue efficiently, follow one of these steps:\e[0m' + echo -e '\e[33m 1. File an issue in the project'\''s issue tracker with detailed information, and apply any available remote patches as a temporary solution with '\('with fetchpatch'\)'.\e[0m' + echo -e '\e[33m 2. If an immediate fix is needed or if reporting upstream isn'\''t suitable, develop a temporary local patch.\e[0m' + echo echo -e '\e[33mThis check is not blocking, but it is recommended to fix the issue.\e[0m' echo fi @@ -42,6 +50,12 @@ checkComposerValidate() { echo -e '\e[31mThe validation of the composer.json and composer.lock failed.\e[0m' echo -e '\e[31mMake sure that the file composer.lock is consistent with composer.json.\e[0m' echo + echo -e '\e[31mThis often indicates an issue with the upstream project, which can typically be resolved by reporting the issue to the relevant project maintainers.\e[0m' + echo + echo -e '\e[31mTo address the issue efficiently, follow one of these steps:\e[0m' + echo -e '\e[31m 1. File an issue in the project'\''s issue tracker with detailed information '\('run '\''composer update --lock --no-install'\'' to fix the issue'\)', and apply any available remote patches as a temporary solution with '\('with fetchpatch'\)'.\e[0m' + echo -e '\e[31m 2. If an immediate fix is needed or if reporting upstream isn'\''t suitable, develop a temporary local patch.\e[0m' + echo exit 1 else echo @@ -50,6 +64,12 @@ checkComposerValidate() { echo -e '\e[33mThe validation of the composer.json and composer.lock failed.\e[0m' echo -e '\e[33mMake sure that the file composer.lock is consistent with composer.json.\e[0m' echo + echo -e '\e[33mThis often indicates an issue with the upstream project, which can typically be resolved by reporting the issue to the relevant project maintainers.\e[0m' + echo + echo -e '\e[33mTo address the issue efficiently, follow one of these steps:\e[0m' + echo -e '\e[33m 1. File an issue in the project'\''s issue tracker with detailed information '\('run '\''composer update --lock --no-install'\'' to fix the issue'\)', and apply any available remote patches as a temporary solution with '\('with fetchpatch'\)'.\e[0m' + echo -e '\e[33m 2. If an immediate fix is needed or if reporting upstream isn'\''t suitable, develop a temporary local patch.\e[0m' + echo echo -e '\e[33mThis check is not blocking, but it is recommended to fix the issue.\e[0m' echo fi |