Support the ongoing development of Laravel.io →
posted 4 years ago
Laravel

Hi, sorry if I don't include the needed info but ime new to Laravel. Ime trying to get a old project running writern by someone who has become rather unhelpfull ;(. Tried a load of googeling buy no joy. It seems to be something with a dev-master generator dependency, I think.

Any help greatfully aprecuiated.c

`$ COMPOSER_MEMORY_LIMIT=-1 composer update --no-plugins Loading composer repositories with package information Updating dependencies Your requirements could not be resolved to an installable set of packages.

Problem 1 - Root composer.json requires laracasts/generators dev-master -> satisfiable by laracasts/generators[dev-master]. - Conclusion: don't install laravel/framework v5.8.1 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.2 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.3 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.4 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.5 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.6 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.7 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.8 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.9 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.10 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.11 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.12 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.13 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.14 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.15 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.16 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.17 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.18 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.19 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.20 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.21 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.22 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.23 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.24 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.25 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.26 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.27 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.28 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.29 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.30 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.31 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.32 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.33 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.34 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.35 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.36 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.37 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.38 (conflict analysis result) - Conclusion: don't install laravel/framework v5.8.0 (conflict analysis result) - laracasts/generators dev-master requires illuminate/support ~6.0|~7.0|~8.0 -> satisfiable by illuminate/support[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev]. - Only one of these can be installed: illuminate/support[dev-master, v4.0.0-BETA2, ..., 4.2.x-dev, v5.0.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev], laravel/framework[v5.8.0, ..., 5.8.x-dev]. laravel/framework replaces illuminate/support and thus cannot coexist with it. - Root composer.json requires laravel/framework 5.8.* -> satisfiable by laravel/framework[v5.8.0, ..., 5.8.x-dev]. `

Last updated 3 years ago.
0
moderator

Do you have an explicit reason to start with a composer update and not a composer install?

A composer install will use the composer.lock file to install the same versions as used before. A composer update will try to get the latest versions available matching the requirements. With a dev-master version it means the latest commit from the master branch.

My advice is to start with the install if possible try to remove the dev-master version as soon as possible before any other upgrade. (If I'm correct you can see the commit hash after installing to find out what the installed version is form the dev-master branch)

0

Sign in to participate in this thread!

PHPverse

Your banner here too?

Ben Edwards ben-tvpp Joined 24 Oct 2020

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2025 Laravel.io - All rights reserved.