Skip to content

"Could not be resolve to an installable set of packages." #31

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

Closed
chriswgerber opened this issue Jul 16, 2015 · 4 comments
Closed

"Could not be resolve to an installable set of packages." #31

chriswgerber opened this issue Jul 16, 2015 · 4 comments

Comments

@chriswgerber
Copy link

Attempt to install the package is causing my composer installation to fail. No longer able to send test coverage.

User: ~/dir: composer require --dev codeclimate/php-test-reporter dev-master
./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 codeclimate/php-test-reporter dev-master -> satisfiable by codeclimate/php-test-reporter[dev-master].
    - codeclimate/php-test-reporter dev-master requires satooshi/php-coveralls 0.6.* -> satisfiable by satooshi/php-coveralls[v0.6.0, v0.6.1].
    - satooshi/php-coveralls v0.6.0 requires psr/log 1.0.0 -> satisfiable by psr/log[1.0.0].
    - satooshi/php-coveralls v0.6.1 requires psr/log 1.0.0 -> satisfiable by psr/log[1.0.0].
    - Conclusion: don't install psr/log 1.0.0

Running PHP 5.6.11

Other packages are:

"require": {
    "ddeboer/data-import": "@stable"
},
"require-dev": {
    "phpunit/phpunit": "4.6.*",
    "phpdocumentor/phpdocumentor": "dev-master"
},
@ryanwinchester
Copy link

I'm getting the exact same problem.

@ryanwinchester
Copy link

By installing satooshi/php-coveralls:0.6.* separately, first, it worked.

@pbrisbin
Copy link
Contributor

@ThatGerber we've made some pretty broad changes to packaging and dependencies. Can you confirm if this is still an issue as of v0.4.1?

@dblandin
Copy link
Contributor

@ThatGerber I'm going to close this issue for now, but let us know if this is still an issue.

Thanks!

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

4 participants