-
Notifications
You must be signed in to change notification settings - Fork 937
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
D7: Error about not being able to apply patch on composer install #498
Comments
You are applying this patch to the 1.6.6 tagged release of the package. But this patch needs to be applied to the 1.x branch of its repo. The code between both states is different, that's why it's not applying the patch. You need to require 1.x first:
Link to patch: cweagans/composer-patches#257 |
Well I'm not applying anything explicitly, it's just the default behavior after setting up a project. So I'm assuming that the composer.json has wrong cweagans/composer-patches reference. |
Hum, I cannot reproduce this. Neither with a fresh setup nor with requiring What exactly you have done that the |
Well in this case, it was probably just me trying 1.6.5 version before. This is the verbose output I just tried:
|
Actually it might be git related: cweagans/composer-patches#148 . |
Oh yes, good catch. Seems likely. What's your Git version then? |
I think I figured it out, see this: cweagans/composer-patches#159 (comment) I'm running composer in Alpine docker container. I think we just have to wait for cweagans/composer-patches#184 merge unfortunately :( . |
I will try also to update my Alpine version and let you know, as it seems that it might fix it. |
You can also try to apply the mentioned PR to your version of cweagans/composer-patches. Maybe they get through. Just change https://github.com/cweagans/composer-patches/pull/184/files to https://github.com/cweagans/composer-patches/pull/184.patch to get the patch URL. |
I can confirm that it works on alpine 3.10 assuming that patch package has been explicitly installed (only this seems to guarantee the newest, unaffected version), so that's good enough for me. |
First
composer install
works fine, but the consecutive ones give:The text was updated successfully, but these errors were encountered: