-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Make conflict with amphp/file lax #267
Conversation
It makes as much sense as using |
I've added the branch alias to |
@kelunik I tried again but unfortunately it seems it didn't help. Composer is still refusing to install it. |
Works fine for me, how does your |
Yeah, minimal use-case works for me too. But it breaks as soon as I add anything (even totally unrelated) into require-dev: {
"require": {
"amphp/file": "^1.0@dev",
"amphp/http-client": "^4.2"
},
"require-dev": {
"psr/log": "*"
}
}
Honestly I think it's a composer bug. Can you please tell me if this happens for you too? I tried to update composer but it didn't help. |
Confirmed, this pretty much looks like a composer bug. |
Thanks... could you make a stable release of amphp/file with amphp/file@7dc65ff? I'd like to avoid using workarounds. |
@kelunik As you might have noticed the bug won't be fixed in Composer 1.x. Would you consider removing the >=2 conflict for now until Composer 2.0 is stable and commonly used? |
Got the same error as @enumag . My workaround currently is setting amphp/file strict to version v1.0.0 instead of ^v1.0.0. |
Using |
I'm trying to use
"amphp/file": "dev-master as 1.0.1",
in my composer.json because of amphp/file@7dc65ff but composer refuses to install it:Now there are two ways to fix this:
^1.0@dev
. (I'd recommend this for all repos.)Personally I'd recommend doing both.
Please fix this ASAP.