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

Composer installation issue #259

Closed
nspyke opened this issue May 18, 2015 · 29 comments
Closed

Composer installation issue #259

nspyke opened this issue May 18, 2015 · 29 comments
Labels
bug

Comments

@nspyke
Copy link

nspyke commented May 18, 2015 

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

  Problem 1
    - Installation request for deployer/deployer ^3.0 -> satisfiable by deployer/deployer[v3.0.0].
    - deployer/deployer v3.0.0 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.

Either switch the require to dev-master or the packages version tag.
@oanhnn
Copy link
Contributor

oanhnn commented May 19, 2015

Please try with this composer.json file:

{
    "require": {
        "php": ">=5.4.0",
        "phpseclib/phpseclib": "dev-master#2c96af214bf1b5e29b707249108504b4e0041a21",
        "deployer/deployer": "~3.0.0"
    },
}

And run composer clear-cache command before composer install command.
Good luck !

@antonmedv antonmedv added the bug label May 19, 2015
@antonmedv
Copy link
Member

This will gone away, when phpseclib do release. Or i will implement ssh in php myself ✊

@gpupo
Copy link

gpupo commented May 21, 2015

It worked with what was said by @oanhnn

@oanhnn oanhnn mentioned this issue May 27, 2015
Closed
@deframe
Copy link

deframe commented May 28, 2015

I don't mean to be "that guy" but a stable package shouldn't really be requiring an unstable dependency, even if it is a specific commit.

@Lynnworld Lynnworld mentioned this issue Jun 1, 2015
Closed
@ZeeCoder
Copy link
Contributor

ZeeCoder commented Jun 2, 2015

I don't quite get this.
The phpseclib package has a lot of releases: https://packagist.org/packages/phpseclib/phpseclib

What do you mean by "when phpseclib do release" @Elfet ?
Are you waiting for a 0.4.x version?

@kenjis
Copy link
Contributor

kenjis commented Jun 2, 2015

See the date of the commit: phpseclib/phpseclib@2c96af2

It is 23 Feb. There is no release containing the commit: https://github.com/phpseclib/phpseclib/releases

@ZeeCoder
Copy link
Contributor

ZeeCoder commented Jun 2, 2015

I see.
Then this solution should be noted on the website until it gets fixed somehow.
Now the tool basically seems broken from an outsider's point of view, if he tries to install it via Composer.
Even if he stumbles upon this thread, it will still leave a bad taste in his mouth, the tool loses some of it's credibility.

@kenjis
Copy link
Contributor

kenjis commented Jun 2, 2015

@ZeeCoder 👍

@kenjis kenjis mentioned this issue Jun 3, 2015
Closed
@antonmedv
Copy link
Member

I thinking about ugly hack, until phpseclib release. Include phpseclib to project. What do you think?
ping @ZeeCoder @oanhnn @kenjis @gordalina @nspyke

@nspyke
Copy link
Author

nspyke commented Jun 4, 2015

I personally wouldn't include a dependent package into this one. That's a short sighted fix for what could become a bigger issue later on.
I tried to track down where this referenced commit was merged into, but have had no luck.

What is in this commit's tree that is required and not in the master branch? Has anyone tried running this using the phpseclib master branch?

@deframe
Copy link

deframe commented Jun 4, 2015

I'm more curious about why Deployer needs such a recent version of phpseclib in the first place. What essential feature was added in 2c96af214bf1b5e29b707249108504b4e0041a2 that isn't available in the 0.3.10 tag?

The phpseclib repository is difficult to grasp - '1.0' and '2.0' branches that are both being merged into master, yet the latest tag is 0.3.10. Ugh.

@ZeeCoder
Copy link
Contributor

ZeeCoder commented Jun 4, 2015

Same questions here.

@kenjis
Copy link
Contributor

kenjis commented Jun 4, 2015

@Elfet 👍

  1. The next release might be next year. Until then all users using Composer have to set the version of phpseclib to composer.json. Or might be github issue will be reported again and again.
  2. dev-master won't work if a bug will be introduced.

@kenjis kenjis mentioned this issue Jun 5, 2015
Closed
@oanhnn
Copy link
Contributor

oanhnn commented Jun 5, 2015

Dear all,
Fix version of phpseclib as a commit is my idea. It is temporary solution for issue #228 .
As commit 2c96af214bf1b5e29b707249108504b4e0041a21, deployer was run good.
I'm not sure a current stable version of phpseclib is good for deployer. it must be tested. I'm happy if someone can do it.
Thank you!

@antonmedv
Copy link
Member

I think fork phpseclob and release it myself, until phpseclib will release.

@ZeeCoder
Copy link
Contributor

ZeeCoder commented Jun 5, 2015

It's better than nothing.
Not an elegant solution but still better than including the whole project in Deployer.

@gpupo
Copy link

gpupo commented Jun 5, 2015

Yep, better than nothing

@kenjis
Copy link
Contributor

kenjis commented Jun 9, 2015

v3.0.5 still has this problem. I hope fixed soon.

@ZeeCoder
Copy link
Contributor

ZeeCoder commented Jun 9, 2015

The fork already exists, I think it will be in the next release.

ZeeCoder referenced this issue Jun 12, 2015
Migrate to deployer/phpseclib.
a569811
@ZeeCoder
Copy link
Contributor

If I'm not mistaken, Deployer v3.0.6 includes the above mentioned fix.
Could you check if it works as expected @kenjis?

@kenjis
Copy link
Contributor

kenjis commented Jun 12, 2015

Good! No problem.

By the way,

Package guzzle/parser is abandoned, you should avoid using it. Use guzzle/guzzle instead.

What's using guzzle/parser?

@kenjis
Copy link
Contributor

kenjis commented Jun 12, 2015

This is it: reactphp/http-client#23

This is it: reactphp/http#24 (comment)

@kenjis kenjis mentioned this issue Jun 16, 2015
Closed
@goreilly
Copy link

goreilly commented Oct 1, 2015

There were some new releases on phpseclib/phpseclib on August 3rd. Is the code you guys wanted in any of their releases now?

@ZeeCoder
Copy link
Contributor

ZeeCoder commented Oct 1, 2015

Hmm, I think so, based on the commit: phpseclib/phpseclib@2c96af2
I think v2.0 should be the thing Deployer needs.

Can you confirm this @Elfet ?

@antonmedv
Copy link
Member

Yes! Can anyone place new release?

2 окт. 2015 г., в 0:28, Hubert Viktor notifications@github.com написал(а):

Hmm, I think so, based on the commit: phpseclib/phpseclib@2c96af2
I think v2.0 should be the thing Deployer needs.

Can you confirm this @Elfet ?

—
Reply to this email directly or view it on GitHub.

@loranger
Copy link

This bug still occurs.
I was not able to install deployer from composer, and the standalone phar version cannot self-update.

@oanhnn
Copy link
Contributor

oanhnn commented Feb 17, 2016

@loranger Can you try run and show ouput to here:

$ composer init
$ composer require deployer/deployer

@ghost
Copy link

ghost commented Feb 24, 2016 

Using version ^3.0 for deployer/deployer
./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
    - 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: don't install deployer/deployer v3.0.10
    - Conclusion: don't install deployer/deployer v3.0.9
    - Conclusion: don't install deployer/deployer v3.0.8
    - Conclusion: don't install deployer/deployer v3.0.7
    - Conclusion: remove symfony/yaml v3.0.2
    - 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].
    - Conclusion: don't install symfony/yaml v3.0.2
    - deployer/deployer v3.0.6 requires symfony/yaml ^2.6 -> satisfiable by symfony/yaml[v2.6.0, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.13, 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.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
    - Can only install one of: symfony/yaml[v2.8.0, v3.0.2].
    - Can only install one of: symfony/yaml[v2.8.1, v3.0.2].
    - Can only install one of: symfony/yaml[v2.8.2, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.0, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.1, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.10, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.11, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.12, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.13, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.2, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.3, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.4, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.5, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.6, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.7, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.8, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.9, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.0, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.1, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.2, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.3, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.4, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.5, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.6, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.7, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.8, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.9, v3.0.2].
    - Installation request for symfony/yaml == 3.0.2.0 -> satisfiable by symfony/yaml[v3.0.2].

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.

Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

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

@oanhnn
Copy link
Contributor

oanhnn commented Feb 25, 2016

@wesleywesley You are using symfony component >= 3.0
Current deployer has problem with symfony 3.x
Please #495

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

No branches or pull requests
9 participants
@loranger @kenjis @gpupo @antonmedv @deframe @nspyke @oanhnn @ZeeCoder @goreilly