Skip to content
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

query re: compatibility with symfony/console:^5 #98

Closed
SignpostMarv opened this issue Dec 3, 2019 · 7 comments
Closed

query re: compatibility with symfony/console:^5 #98

SignpostMarv opened this issue Dec 3, 2019 · 7 comments

Comments

@SignpostMarv
Copy link

I've a general preference for using composer require --dev rather than using global installs/phar builds.

Are there any plans to nudge up compatibility with symfony/console, i.e. symfony/console:^4.0|^5.0 ?

@exussum12
Copy link
Collaborator

Ideally you would use the phar for a global install. I can take a look at bumping these though

@SignpostMarv
Copy link
Author

I've a general preference for not installing things globally, which can at times get a little troublesome when upstream dependencies (like symfony/console) get updated :s

@juliangut
Copy link
Contributor

This would have been a great addition to v2.2.0

@badmansan
Copy link

Seems it not work.
composer.json

{
    "require": {
        "symfony/console": "^5.0"
    }
}

$ composer require --dev povils/phpmnd
Using version ^2.2 for povils/phpmnd
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Installation request for povils/phpmnd ^2.2 -> satisfiable by povils/phpmnd[v2.2.0].
- povils/phpmnd v2.2.0 requires symfony/console ^4.0 -> satisfiable by symfony/console[4.0.x-dev, 4.1.x-dev, 4.2.x-dev, 4.3.x-dev, 4.4.x-dev, v4.0.0, v4.0.0-BETA1, v4.0.0-BETA2, v4.0.0-BE
TA3, v4.0.0-BETA4, v4.0.0-RC1, v4.0.0-RC2, v4.0.1, v4.0.10, v4.0.11, v4.0.12, v4.0.13, v4.0.14, v4.0.15, v4.0.2, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8, v4.0.9, v4.1.0, v4.1.0-BETA1,
v4.1.0-BETA2, v4.1.0-BETA3, v4.1.1, v4.1.10, v4.1.11, v4.1.12, v4.1.2, v4.1.3, v4.1.4, v4.1.5, v4.1.6, v4.1.7, v4.1.8, v4.1.9, v4.2.0, v4.2.0-BETA1, v4.2.0-BETA2, v4.2.0-RC1, v4.2.1, v4.2.10,
v4.2.11, v4.2.12, v4.2.2, v4.2.3, v4.2.4, v4.2.5, v4.2.6, v4.2.7, v4.2.8, v4.2.9, v4.3.0, v4.3.0-BETA1, v4.3.0-BETA2, v4.3.0-RC1, v4.3.1, v4.3.10, v4.3.11, v4.3.2, v4.3.3, v4.3.4, v4.3.5, v4
.3.6, v4.3.7, v4.3.8, v4.3.9, v4.4.0, v4.4.0-BETA1, v4.4.0-BETA2, v4.4.0-RC1, v4.4.1, v4.4.2, v4.4.3, v4.4.4, v4.4.5, v4.4.6] but these conflict with your requirements or minimum-stability.

Installation failed, reverting ./composer.json to its original content.

@exussum12
Copy link
Collaborator

run composer why symfony/console that will say what else is blocking it

@badmansan
Copy link

sorry, i read

Update Symfony packages to version 5 #103

and think that it is a commit, but it was mentioned only :)

@sidz
Copy link
Collaborator

sidz commented Oct 28, 2021

phpmnd is compatible with symfony ^5.0 since 2.3.0.
So closed.

@sidz sidz closed this as completed Oct 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants