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

composer update with lumen framework does not work #447

Closed
catalinux opened this issue Jun 3, 2015 · 21 comments
Closed

composer update with lumen framework does not work #447

catalinux opened this issue Jun 3, 2015 · 21 comments

Comments

@catalinux
Copy link
Contributor

  "require": {
    "laravel/lumen-framework": "5.0.*@dev",
    "vlucas/phpdotenv": "~1.0",
    "dingo/api": "0.9.*@dev",
    "league/fractal": "*",
    "fzaninotto/faker": "1.4.*"
  },

composer 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
- remove dingo/api 0.9.x-dev|keep dingo/api dev-develop
- dingo/api 0.9.x-dev requires illuminate/routing 5.1.* -> no matching package found.
- dingo/api dev-develop requires illuminate/routing 5.1.* -> no matching package found.
- Installation request for dingo/api 0.9.*@dev -> satisfiable by dingo/api[0.9.x-dev].

Potential causes:

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

@vinkla
Copy link
Contributor

vinkla commented Jun 3, 2015

Try using "laravel/lumen-framework": "5.1.*@dev" instead.

@GrahamCampbell
Copy link
Contributor

"league/fractal": "*", wildcard version constraints are always a bad idea

@catalinux
Copy link
Contributor Author

with:

   "laravel/lumen-framework": "5.1.*@dev",

Problem 1
- Installation request for laravel/lumen-framework 5.1.@dev -> satisfiable by laravel/lumen-framework[5.1.x-dev].
- laravel/lumen-framework 5.1.x-dev requires illuminate/auth 5.1.
-> no matching package found.
Problem 2
- remove dingo/api 0.9.x-dev|keep dingo/api dev-develop
- dingo/api 0.9.x-dev requires illuminate/routing 5.1.* -> no matching package found.
- dingo/api dev-develop requires illuminate/routing 5.1.* -> no matching package found.
- Installation request for dingo/api 0.9.*@dev -> satisfiable by dingo/api[0.9.x-dev].

@jrm2k6
Copy link

jrm2k6 commented Jun 3, 2015

Same thing with Laravel 5.0:

"laravel/framework": "5.0.*",
"illuminate/html": "~5.0",

Is there a way to work around that? As we don't want to upgrade from 5.0 to 5.1 yet.

@vinkla
Copy link
Contributor

vinkla commented Jun 3, 2015

@jrm2k6 This package no longer supports Laravel 5.0 as of #440. Though, you could update to Laravel 5.1 today. They've said it will be released right after Symfony 2.7 which was some days ago.

@jrm2k6
Copy link

jrm2k6 commented Jun 3, 2015

That's interesting. So the package supports 4.2, and supports 5.1 but not 5.0. It would have been sweet to know about this plan before. Will see what I can do

@vinkla
Copy link
Contributor

vinkla commented Jun 3, 2015

The transition between Laravel 5.0 and 5.1 is almost none existing, you should check it out.

@jrm2k6
Copy link

jrm2k6 commented Jun 3, 2015

Cool thanks!

@slovenianGooner
Copy link

Yeah, even if changing to 5.1.*@dev it still returns an error. Any ideas?

@GrahamCampbell
Copy link
Contributor

Yeah, even if changing to 5.1.*@dev it still returns an error. Any ideas?

You need to correctly set the GLOBAL minimum stability.

@slovenianGooner
Copy link

Yes, seems to do the trick. Was just having the GLOBAL preferred-install set to dev. Thanks!

@GrahamCampbell
Copy link
Contributor

"preferred-install" isn't right...

@GrahamCampbell
Copy link
Contributor

"preferred-install": "dist"

@GrahamCampbell
Copy link
Contributor

    "minimum-stability": "dev",
    "prefer-stable": true

@GrahamCampbell
Copy link
Contributor

preferred-install

That's telling composer to download zips, or clone the repo.

@catalinux
Copy link
Contributor Author

It works. Tx @GrahamCampbell

@slovenianGooner
Copy link

Are there any changes on how the API routes are registered? Can't seem to get it to work after the update.

@catalinux
Copy link
Contributor Author

Same question here, such route does not work any more:

$api->version('v1', ['prefix' => 'api'], function ($api) {

    $api->resource('contact', 'App\Http\Controllers\ContactController');

});
GET /api/contact/1 HTTP/1.1

NotFoundHttpException in Application.php line 1116:

@jasonlewis
Copy link
Contributor

Looking at Lumen it seems some changes that made it to 5.0 haven't been merged into the master branch yet, not sure if they will any time soon. I'll raise this issue with Taylor. Hopefully then routing is restored for Lumen.

@jasonlewis
Copy link
Contributor

https://twitter.com/jasonclewis/status/607019177065353216

I'll check shortly but it should be fine now if you're using Lumen. Just run an update.

@jasonlewis
Copy link
Contributor

Can confirm, all should be sweet now folks. Let me know if you're still having dramas.

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

6 participants