-
-
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
symfont/console dependency conflicts with other packages #57
Comments
Thanks! I'm just confused why the Drush test passed in global. See: https://circleci.com/gh/mglaman/drupal-check/68
Then drupal-check installs without a problem. 🤔 would ~3 be fine? so Also, according to https://semver.mwl.be/#?package=symfony%2Fconsole&version=~3.2%20%7C%7C%20~4.0&minimum-stability=stable there should be no conflict against 3.4 Can you provide a failing scenario? |
Yes! Actually using ~3 would be best unless there was some reason you needed to pin to >3.2 for some reason. My failing scenario is just having a composer.json that has I don't still have the composer log since it failed as drupal-check is only a "nice to have" right now and I had to move to higher-priority tasks. But the composer errors pointed to the ^3.2 in drupal-check conflicting with the existing 3.4 version that was in our composer.lock (from before we added drupal-check to the project) Your semver output above makes sense, so maybe this is also just some composer issue. But I expect others will run into this since literally all I tried to do in my project was: |
Yeah. When the .lock has data and adding something new... It gets freaky sometimes. That's the issue with Drupal sites first created <8.5. Drush was installed and added v3 of the parser and now v4 is valid. Fun times! |
Got a failing test!
|
I think I just need to tag 1.0.9. Looking at: https://packagist.org/packages/mglaman/drupal-check 1.0.8 - |
This is split from #23 that was closed.
Basically, the:
"symfony/console": "~3.2 || ~4.0",
in composer.json is causing drupal-check to conflict with some popular packages when trying to install locally within a project.
Some packages that require ^3.4 are:
drush/drush: "symfony/console": "^3.4",
behat/behat: "symfony/console": "~2.7.40||^2.8.33||~3.3.15||^3.4.3||^4.0.3"
Unless there is a specific reason 3.4 is being excluded from drupal-check, I recommend changing the composer.json to:
"symfony/console": "~3.2 || ~3.4 || ~4.0"
The more compatibility we can get here, the more we can encourage people to start checking their existing code to make projects ready for Drupal 9.
The text was updated successfully, but these errors were encountered: