8000 Your requirements could not be resolved to an installable set of packages. · Issue #75 · sendgrid/sendgrid-php · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

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

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
Closed
claudiumstoica opened this issue Mar 4, 2014 · 5 comments
Closed

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

claudiumstoica opened this issue Mar 4, 2014 · 5 comments

Comments

@claudiumstoica
Copy link

https://github.com/sendgrid/sendgrid-php/blob/v1.1.4/composer.json
line 8-11
mashape/unirest-php needs to be an uppercase M
since composer is seeing everything strict now
as mentioned in this github issue of composer: composer/composer#2690

This is the error our users are receiving when attempting to install SendGrid PHP with the new version of composer : Your requirements could not be resolved to an installable set of packages.
@ThomasVdBerge
Copy link

The problem lies with the swiftmailer/swiftmailer package and with the mashape/unirest-php package.

This issue only appears with the latest composer version (which has a security update)

This is the full error log:
Your requirements could not be resolved to an installable set of packages.

Problem 1

  • sendgrid/sendgrid 2.0.3 requires mashape/unirest-php dev-master -> no matching package found.
  • sendgrid/sendgrid 2.0.2 requires mashape/unirest-php dev-master -> no matching package found.
  • sendgrid/sendgrid 2.0.1 requires mashape/unirest-php dev-master -> no matching package found.
  • sendgrid/sendgrid 1.1.7 requires swiftmailer/swiftmailer ~5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.1.6 requires swiftmailer/swiftmailer ~5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.1.5 requires swiftmailer/swiftmailer ~5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.1.4 requires swiftmailer/swiftmailer ~5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.1.3 requires swiftmailer/swiftmailer ~5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.1.2 requires swiftmailer/swiftmailer ~5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.1.1 requires swiftmailer/swiftmailer ~5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.1.0 requires swiftmailer/swiftmailer ~5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.0.9 requires swiftmailer/swiftmailer ~5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.0.8 requires swiftmailer/swiftmailer v5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.0.7 requires swiftmailer/swiftmailer v5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.0.6 requires swiftmailer/swiftmailer v5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.0.5 requires swiftmailer/swiftmailer v5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.0.4 requires swiftmailer/swiftmailer v5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.0.3 requires swiftmailer/swiftmailer v5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.0.2 requires swiftmailer/swiftmailer v5.0.1 -> no matching package found.
  • sendgrid/sendgrid 1.0.1 requires swiftmailer/swiftmailer v5.0.0 -> no matching package found.
  • Installation request for sendgrid/sendgrid-php ~1.1.4 -> satisfiable by sendgrid/sendgrid[1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 2.0.1, 2.0.2, 2.0.3].

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 for more details.

To Reproduce:
Update composer
Remove composer cache
Remove sendgrid library
run composer update

@motdotla
Copy link
Contributor
motdotla commented Mar 5, 2014

Thanks for this. I did the following:

/usr/local/Cellar/composer/1.0.0-alpha7/libexec/composer.phar self-update

That put me at version: Composer version fff913d6de5ec8c4315f466cf203c3e0acc3218a 2014-03-01 20:25:32

Then I ran the following:

sudo rm -rf ~/.composer/cache/
sudo rm -rf vendor
composer update

I'm not getting the same error. What composer version are you each on?

@ThomasVdBerge
Copy link

Using the same composer version.

The only difference we probably have is which version of sendgrid-php we are trying to install.

This is what my composer.json looks like to install sendgrid:

"require": {
    "sendgrid/sendgrid": "~1.1.4",
},

Which gives this output:

    sudo /usr/local/bin/composer.phar self-update
    You are already using composer version fff913d6de5ec8c4315f466cf203c3e0acc3218a.

    rm -rf vendors/sendgrid/
    sudo rm -rf ~/.composer/cache/
    composer.phar update
    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
    - sendgrid/sendgrid 1.1.7 requires mashape/unirest-php dev-master -> no matching package found.
    - sendgrid/sendgrid 1.1.6 requires mashape/unirest-php dev-master -> no matching package found.
    - sendgrid/sendgrid 1.1.5 requires mashape/unirest-php dev-master -> no matching package found.
     - sendgrid/sendgrid 1.1.4 requires mashape/unirest-php dev-master -> no matching package found.
    - Installation request for sendgrid/sendgrid ~1.1.4 -> satisfiable by sendgrid/sendgrid[1.1.4, 1.1.5, 1.1.6, 1.1.7].

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://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> for more details.

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

It does work when we add minimum-stability : dev to composer. (didn't have to do that in the past)

But it should work just as good without (hate adding min. stab. dev for prod. env.)

@motdotla
Copy link
Contributor
motdotla commented Mar 6, 2014

Ok, cool. So the fix here is to move to: minimum-stability : dev in your package.json.

And you also can update to 2.x.x version of the library. The 2.0 versions are much improved - but there were method name breaking changes.

@motdotla motdotla closed this as completed Mar 6, 2014
@NoahTwine
Copy link

@motdotla You are a gentlemen and a scholar. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@motdotla @ThomasVdBerge @claudiumstoica @NoahTwine
0