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.

Sign up for GitHub

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

Jump to bottom

Symfony 3.0: dependencies are incompatible #495

Closed
dvzzz opened this issue Dec 8, 2015 · 12 comments · Fixed by #593
Closed

Symfony 3.0: dependencies are incompatible #495

dvzzz opened this issue Dec 8, 2015 · 12 comments · Fixed by #593
Labels
bug

Comments

@dvzzz
Copy link

dvzzz commented Dec 8, 2015

Composer log:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - deployer/deployer v3.0.5 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - deployer/deployer v3.0.4 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - deployer/deployer v3.0.3 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - deployer/deployer v3.0.2 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - deployer/deployer v3.0.1 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - deployer/deployer v3.0.0 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - Conclusion: remove symfony/symfony v3.0.0
    - deployer/deployer v3.0.10 requires symfony/finder ~2.6 -> satisfiable by symfony/finder[v2.6.0, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.8.0].
    - deployer/deployer v3.0.6 requires symfony/finder ~2.6 -> satisfiable by symfony/finder[v2.6.0, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.8.0].
    - deployer/deployer v3.0.7 requires symfony/finder ~2.6 -> satisfiable by symfony/finder[v2.6.0, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.8.0].
    - deployer/deployer v3.0.8 requires symfony/finder ~2.6 -> satisfiable by symfony/finder[v2.6.0, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.8.0].
    - deployer/deployer v3.0.9 requires symfony/finder ~2.6 -> satisfiable by symfony/finder[v2.6.0, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.8.0].
    - don't install symfony/finder v2.6.0|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.6.1|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.6.10|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.6.11|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.6.12|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.6.2|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.6.3|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.6.4|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.6.5|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.6.6|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.6.7|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.6.8|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.6.9|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.7.0|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.7.1|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.7.2|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.7.3|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.7.4|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.7.5|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.7.6|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.7.7|don't install symfony/symfony v3.0.0
    - don't install symfony/finder v2.8.0|don't install symfony/symfony v3.0.0
    - Installation request for symfony/symfony 3.0.* -> satisfiable by symfony/symfony[v3.0.0].
    - Installation request for deployer/deployer ~3.0 -> satisfiable by deployer/deployer[v3.0.0, v3.0.1, v3.0.10, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9].
@oanhnn oanhnn added the bug label Dec 9, 2015
@oanhnn
Copy link
Contributor

oanhnn commented Dec 9, 2015

Thank you for report issue.
You can use deployer.phar to work with symfony 3.x
We will fix this issue as soon as possible.

@antonmedv
Copy link
Member

Yes! We need to support Symfony 3.0.

@whyte624
Copy link
Contributor

👍

@jonasdw
Copy link

jonasdw commented Dec 24, 2015

I already made a pull request that should fix the outdated dependencies in "elfet/purephp". This repo is still active so the outdated dependencies will be fixed in the near future.

As for "kherge/amend", i'm guessing this will never get fixed sees the latest activity is more than a year old. Another pull request is already open for more than 200 days, no feedback or comment from the owner or nothing.

Maybe u guys should fork that repo and fix it yourself, there's only one outdated dependency to the symfony/console. Or if you're willing i will fork and fix it, than update your composer.json and PR it..

If you guys do that, you can re-open #505. And we can all start using deployer in symfony3.0 projects!

@zupolgec
Copy link
Contributor

zupolgec commented Jan 5, 2016

This makes deployer incompatible with Laravel 5.2 too

@zupolgec
Copy link
Contributor

zupolgec commented Jan 5, 2016

@oanhnn the problem with the phar is that is many months old!! why no release has been tagged since?

@oanhnn
Copy link
Contributor

oanhnn commented Jan 5, 2016

  1. This problem only user add Deployer to Symfony project. Current Deployer don't support this work (maybe have conflict function name). We waiting Deployer v4.0
  2. I will testing and release new version on this weekend. Now, i haven't free time. If any @deployphp/maintainer have free time, please do it. ;)

@antonmedv
Copy link
Member

Try start moving 4.0 release next week.

@alxsad
Copy link

alxsad commented Feb 3, 2016

👍 I'd like to use symfony/process ~3.0 but

Problem 1
    - deployer/deployer v3.0.9 requires symfony/process ~2.6 -> no matching package found.
    - deployer/deployer v3.0.8 requires symfony/process ~2.6 -> no matching package found.
    - deployer/deployer v3.0.7 requires symfony/process ~2.6 -> no matching package found.
    - deployer/deployer v3.0.6 requires symfony/process ~2.6 -> no matching package found.
    - deployer/deployer v3.0.5 requires symfony/process ~2.6 -> no matching package found.
    - deployer/deployer v3.0.4 requires symfony/process ~2.6 -> no matching package found.
    - deployer/deployer v3.0.3 requires symfony/process ~2.6 -> no matching package found.
    - deployer/deployer v3.0.2 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - deployer/deployer v3.0.10 requires symfony/process ~2.6 -> no matching package found.
    - deployer/deployer v3.0.1 requires symfony/process ~2.6 -> no matching package found.
    - deployer/deployer v3.0.0 requires symfony/process ~2.6 -> no matching package found.
    - deployer/deployer v3.0.10 requires symfony/process ~2.6 -> no matching package found.
    - Installation request for deployer/deployer ~3.0 -> satisfiable by deployer/deployer[v3.0.0, v3.0.1, v3.0.10, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9].

@oanhnn
Copy link
Contributor

oanhnn commented Feb 3, 2016

You can use deployer.phar to work with symfony 3.x

@andrewtch
Copy link

Bump, can you please use ~2.6 | 3.0 as a constraint?

@oanhnn oanhnn mentioned this issue Feb 25, 2016
Closed
@kbsali
Copy link

kbsali commented Feb 25, 2016

Has anybody managed to get this to work?

@cedricziel cedricziel mentioned this issue Mar 13, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Symfony 3 compatibility
9 participants
@kbsali @antonmedv @zupolgec @dvzzz @alxsad @andrewtch @oanhnn @whyte624 @jonasdw