laravel version is 5.8, When I write this command in cmd,
composer require guzzlehttp/guzzle
I get the below problems:
Using version ^7.5 for guzzlehttp/guzzle
./composer.json has been updated
Running composer update guzzlehttp/guzzle
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 guzzlehttp/guzzle ^7.5, found guzzlehttp/guzzle[dev-master, 7.5.0, 7.5.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 2
- Root composer.json requires netflie/whatsapp-cloud-api ^1.3 -> satisfiable by netflie/whatsapp-cloud-api[1.3.0].
- netflie/whatsapp-cloud-api 1.3.0 requires guzzlehttp/guzzle ^7.0 -> found guzzlehttp/guzzle[dev-master, 7.0.0-beta.1, ..., 7.5.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 3
- php-http/guzzle6-adapter v1.1.1 requires guzzlehttp/guzzle ^6.0 -> found guzzlehttp/guzzle[6.0.0, ..., 6.5.x-dev] but it conflicts with your root composer.json require (^7.5).
- nexmo/laravel 1.1.2 requires nexmo/client ^1.0 -> satisfiable by nexmo/client[1.9.1].
- nexmo/client 1.9.1 requires php-http/guzzle6-adapter ^1.0 -> satisfiable by php-http/guzzle6-adapter[v1.1.1].
- nexmo/laravel is locked to version 1.1.2 and an update of this package was not requested.
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require guzzlehttp/guzzle:*" to figure out if any version is installable, or "composer require guzzlehttp/guzzle:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
It's troublesome, and it seems like a catch22 situation and I cannot figure out the problem.
Related
Hello guys i try to use Laravel notification package But When I Run This command in terminal
composer require marjose/laravel-bootstrap-notify
Here I Have This Error
C:\xampp\htdocs\EShop>composer require marjose/laravel-bootstrap-notify
Using version ^1.0 for marjose/laravel-bootstrap-notify
./composer.json has been updated
Running composer update marjose/laravel-bootstrap-notify
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 marjose/laravel-bootstrap-notify ^1.0 -> satisfiable by marjose/laravel-bootstrap-notify[v1.0.0].
- marjose/laravel-bootstrap-notify v1.0.0 requires illuminate/contracts ~6.0|~7.0|~8.0 -> found illuminate/contracts[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-de
v] but these were not loaded, likely because it conflicts with another require.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require marjose/laravel-bootstrap-notify:*" to figure out if any version is installable
, or "composer require marjose/laravel-bootstrap-notify:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
I Try to use These Commands But Doesn't Work
composer require marjose/laravel-bootstrap-notify:*
composer require marjose/laravel-bootstrap-notify:^2.1"
i am having this error when running composer require nesk/puphpeteer
Problem 1
- Root composer.json requires nesk/puphpeteer 2.0 -> satisfiable by nesk/puphpeteer[2.0.0].
- nesk/puphpeteer 2.0.0 requires psr/log ^1.0 -> found psr/log[1.0.0, ..., 1.1.4] but the package is fixed to 3.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions
The composer logs has already detailed the necessary changes you might need –
The nesk/puphpeteer:2.0 requires that the psr/log be at version 1.0.*.
You can try the following to lower your psr/log requirement:
composer require psr/log "^1.0"
Your requirements could not be resolved to an installable set of packages.
Problem 1
- chumper/zipper v1.0.0 requires illuminate/support 5.x -> found illuminate/support[v5.0.0, ..., 5.8.x-dev] but these were not loaded, likely because it conflicts with another require.
- chumper/zipper[v1.0.1, ..., v1.0.3] require illuminate/support ^5.0 -> found illuminate/support[v5.0.0, ..., 5.8.x-dev] but these were not loaded, likely because it conflicts with another require.
- Root composer.json requires chumper/zipper ^1.0 -> satisfiable by chumper/zipper[v1.0.0, v1.0.1, v1.0.2, v1.0.3].
You can also try re-running composer require with an explicit version constraint, e.g. "composer require maatwebsite/excel:*" to figure out if any version is installable, or "composer require maatwebsite/excel:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
I have php verison "PHP 7.4.27", composer version "2.2.4" and laravel version"4.2.9". And my error messages:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires laravelista/comments ^4.5 ->
satisfiable by laravelista/comments[4.5.0].
- laravelista/comments 4.5.0 requires illuminate/database ^8.0 ->
found illuminate/database[v8.0.0, ..., v8.79.0] but these were not loaded, likely because it
conflicts with another require.
You can also try re-running composer require with an explicit version constraint,
e.g. "composer require laravelista/comments:*" to figure out if any version is installable, or
"composer require laravelista/comments:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
According laravel manual https://laravel.com/docs/8.x/redis for install predis, need run: composer require predis/predis. When that command is running (for laravel 8) - appear next Error:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- facade/ignition is locked to version 2.4.2 and an update of this package was not requested.
- facade/ignition 2.4.2 requires php ^7.2.5 -> your php version (8.0.0) does not satisfy that requirement.
Problem 2
- facade/ignition-contracts 1.0.1 requires php ^7.1 -> your php version (8.0.0) does not satisfy that requirement.
- nunomaduro/collision v4.3.0 requires facade/ignition-contracts ^1.0 -> satisfiable by facade/ignition-contracts[1.0.1].
- nunomaduro/collision is locked to version v4.3.0 and an update of this package was not requested.
In my composer.json: "php": "^7.2.5|^8.0",
What here is wrong))?
You need to update facade/ignition and nunomaduro/collision first to support PHP 8 in your project.
Running the following commands should update them accordingly.
composer require --dev facade/ignition nunomaduro/collision
composer require predis/predis
i run comand: composer require --dev facade/ignition nunomaduro/collision and have got new Error: Your requirements could not be resolved to an installable set of packages.
Problem 1
- facade/ignition[2.10.0, ..., 2.10.2] require facade/ignition-contracts ^1.0.2 -> found facade/ignition-contracts[1.0.2] but the package is fixed to 1.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires facade/ignition ^2.10 -> satisfiable by facade/ignition[2.10.0, 2.10.1, 2.10.2].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
I have new laravel 8 project (blog) && use new Vagrant Homestead (with all updates) && i use laravel 8 manual)) may be laravel developers is a little busy and is a little tired to give full instruction in manual). I think may be for Laravel8 Homestead allready is not suitable and need Docker and Sail... But project work (with the exception of predis) Now i use phpredis. May be will try use docker... As for Vagrant&&Homestead - https://laravel.com/docs/8.x/homestead#introduction i don't understand what is problem to use that technology .... god with they)...