Closed MCDELTAT closed 5 years ago
Closing: User error. Apparently the two servers in question somehow didn't have the patch
utility installed, so it obviously couldn't call it.
Perhaps as part of this issue, I might look into how to throw a more meaningful error, I.E. that patch
isn't installed, but not sure how to do that.
I am trying to debug a similar issue on AWS Elastic Beanstalk. I am a neophyte when it comes to servers and infrastructure and trying to resolve an issue where composer can't apply any patches on Elastic Beanstalk. On our local environments, we have no issues and the patching is successful.
Can you say how you found and verified that your 'patch' utility was not installed? If there was a specific packages you were looking for and then installed, may you drop that here?
I appreciate any extra detail that you could provide (I realize this thread is essentially 3-4 years old but thematically seemingly relevant).
Edit: This thread was illustrative to the issue: https://github.com/cweagans/composer-patches/issues/172. Also, when mucking around SSH'ed into our server, it looks like the deployed code is not a git repository when typing 'git status', which might explain why git can't apply the patch in composer install (confirmed that git was installed on the server however.) I'll just leave this here to possibly guide others. I have a few items to run down.
I'm having a strange one that I'll have to track down. I have a script to pull down our git repo, perform composer install, etc. When pulling it onto our live servers that are 100% the same (slight assumption) it worked on the first 4, and then fails to apply the patch on two specific servers. Spun up an AWS instance very quickly with nothing besides composer and it also worked, so not sure what these two specific servers have that's stopping
composer install
.Composer is same 1.8.6 across servers, git is same, php is same (7.2.18)
With
composer install -vvv
:composer.json: