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

[5.1] fix doctrine/inflector version to pull 1.1.0 #20241

Closed
wants to merge 1 commit into from

Conversation

janhartigan
Copy link
Contributor

This is a clone of #20227 for the 5.1 branch.

@gmsantos
Copy link
Contributor

I guess composer will stop on 1.1 with the current constraint

@janhartigan
Copy link
Contributor Author

^1.0 will take you all the way up to <2.0.0

@gmsantos
Copy link
Contributor

Only if all constraints is satisfied... In a system with PHP 5.6 the version will be 1.1... In PHP 7.0 the version will be 1.2 and finally in PHP 7.2 the version will be 1.3 (or newer)

@janhartigan
Copy link
Contributor Author

Interesting...any documentation on that? I just ran into this problem in a local environment running php7.0 and laravel 5.2. The specific issue was:

[Composer\DependencyResolver\SolverProblemsException]
    Problem 1
      - Installation request for laravel/framework 5.2.* -> satisfiable by laravel/framework[5.2.x-dev].
      - laravel/framework 5.2.x-dev requires doctrine/inflector ~1.0 -> no matching package found.
  ].

Maybe I'm just reading the error wrong?

@janhartigan
Copy link
Contributor Author

Could it be that it's based on the php version in the require block rather than the local environment php version?

@gmsantos
Copy link
Contributor

gmsantos commented Jul 24, 2017

I ran a test on this travis build

See the output for each PHP version:

image

image

image

My composer.json

λ cat composer.json
{
    "name": "gmsantos/inflector",
    "license": "MIT",
    "authors": [
        {
            "name": "gmsantos",
            "email": "gabriel.ms1@hotmail.com"
        }
    ],
    "require": {
        "doctrine/inflector": "~1.0"
    }
}

@janhartigan
Copy link
Contributor Author

Yeah ok I think this is my problem. I just ran a bare-bones test on 5.1 and got the same results as you. Thanks for helping me poke around @gmsantos

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

Successfully merging this pull request may close these issues.

2 participants