Open TechnerdsDev-zz opened 3 years ago
I had a similar issue and the only way I solved this was allowing "dev" libraries in composer.json
"minimum-stability": "dev",
"minimum-stability": "dev",
does have this line in my composer.json still facing the same issue
"minimum-stability": "dev",
does have this line in my composer.json still facing the same issue
yeah, its doesnt help
I tried to install laravel voyager in a new project and everything worked, so I then checked what I have installed on my old project and found that the problem was barryvdh/laravel-ide-helper.
After removing this package I was able to install laravel voyager with no problems.
Then I tried to install laravel-ide-helper and it actually removed laravel voyager
So then I removed laravel-ide-helper, removed composer.lock, installed laravel voyager and then installed laravel-ide-helper but without the dev option and fixed my problem. Check if by deleting composer.lock and then installing voyager fixes for you. If not try what I just said above
I have the problem of cloning it, when it is downloading at the section of cloning it says " Install of tcg/voyager failed 0 [>---------------------------] Installation failed, reverting ./composer.json and ./composer.lock to their original content.
[Symfony\Component\Process\Exception\ProcessTimedOutException] The process "git clone --no-checkout "https://github.com/the-control-group/voyager.git" "D:\bast\vendor\tcg\voyager " && cd /D "D:\bast\vendor\tcg\voyager" && git remote add composer "https://github.com/the-control-group/voyager.gi t" && git fetch composer && git remote set-url origin "https://github.com/the-control-group/voyager.git" && git rem ote set-url composer "https://github.com/the-control-group/voyager.git"" exceeded the timeout of 300 seconds. " gives me the error and I installed git and downloaded new project but still give me the error. Every thing is updated
Similar issue for me:
sscotti@iMac-Catalina PortalRads % composer require tcg/voyager Using version ^1.4 for tcg/voyager ./composer.json has been updated Running composer update tcg/voyager Loading composer repositories with package information Updating dependencies Your requirements could not be resolved to an installable set of packages.
Problem 1
- tcg/voyager[1.4.x-dev, ..., 1.x-dev] require doctrine/dbal ^2.5 -> found doctrine/dbal[v2.5.0-BETA2, ..., 2.13.x-dev] 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.
- tcg/voyager[v1.4.0, ..., v1.4.2] require illuminate/support ~6.0|~7.0 -> found illuminate/support[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev] but these were not loaded, likely because it conflicts with another require.
- Root composer.json requires tcg/voyager ^1.4 -> satisfiable by tcg/voyager[v1.4.0, ..., 1.x-dev].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
"minimum-stability": "dev", is in my composer.json file.
I do have a couple barryvdh packages, laravel-debugbar & laravel-snappy. Not sure really how to proceed yet.
If I use --with-all-dependencies
sscotti@iMac-Catalina PortalRads % composer require tcg/voyager --with-all-dependencies
Using version ^1.4 for tcg/voyager
./composer.json has been updated
Running composer update tcg/voyager --with-all-dependencies
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 laravel/framework ^8.0, found laravel/framework[v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 2
- laravel/sanctum is locked to version v2.9.4 and an update of this package was not requested.
- laravel/sanctum v2.9.4 requires illuminate/database ^6.9|^7.0|^8.0 -> found illuminate/database[v6.10.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 3
- livewire/livewire is locked to version v2.4.3 and an update of this package was not requested.
- livewire/livewire v2.4.3 requires illuminate/database ^7.0|^8.0 -> found illuminate/database[v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 4
- spatie/laravel-cookie-consent is locked to version 2.12.13 and an update of this package was not requested.
- spatie/laravel-cookie-consent 2.12.13 requires illuminate/cookie ^6.0|^7.0|^8.0 -> found illuminate/cookie[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 5
- spatie/laravel-csp is locked to version 2.6.4 and an update of this package was not requested.
- spatie/laravel-csp 2.6.4 requires illuminate/http ~5.8.0|^6.0|^7.0|^8.0 -> found illuminate/http[v5.8.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 6
- spatie/laravel-permission is locked to version 4.0.1 and an update of this package was not requested.
- spatie/laravel-permission 4.0.1 requires illuminate/auth ^6.0|^7.0|^8.0 -> found illuminate/auth[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 7
- yajra/laravel-datatables-oracle is locked to version v9.18.0 and an update of this package was not requested.
- yajra/laravel-datatables-oracle v9.18.0 requires illuminate/database 5.8.*|^6|^7|^8 -> found illuminate/database[v5.8.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 8
- barryvdh/laravel-debugbar is locked to version v3.5.5 and an update of this package was not requested.
- barryvdh/laravel-debugbar v3.5.5 requires illuminate/routing ^6|^7|^8 -> found illuminate/routing[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 9
- krlove/eloquent-model-generator is locked to version 1.3.7 and an update of this package was not requested.
- krlove/eloquent-model-generator 1.3.7 requires illuminate/database ^5.0 || ^6.0 || ^7.0 || ^8.0 -> found illuminate/database[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] but these were not loaded, likely because it conflicts with another require.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
Any luck with that @sscotti I am facing the same issue.
same problem
I'm seeing an issue with Laravel 9. I have also installed jetstream but was surprised to see the installation fail:
sail composer require tcg/voyager -W
./composer.json has been updated Running composer update tcg/voyager --with-all-dependencies Loading composer repositories with package information Updating dependencies Your requirements could not be resolved to an installable set of packages.
Problem 1
You can also try re-running composer require with an explicit version constraint, e.g. "composer require tcg/voyager:*" to figure out if any version is installable, or "composer require tcg/voyager:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
So I noticed a pull request in https://github.com/larapack/doctrine-support/pull/16/files - I am suspecting that is at least one of the issues as it seems to be trying to get version 2.0 and blueprint (another package I have installed requires 3.3). What is concerning is that it appears that the larapack doctrine-support package is no longer being actively maintained. I am wondering if it is really required for voyager to work. It may be worthwhile removing the requirement or possibly finding a replacement if it is really needed.
I'm also facing the same issue changing "stable" to "dev" in composer.json resolve this.
"minimum-stability": "dev",
I had a similar issue and the only way I solved this was allowing "dev" libraries in composer.json
"minimum-stability": "dev",
It works my larvel version is 10.6. Thanks
I deleted the file "composer.lock" , then launched my cmd again and it worked
stable
i delete composer.lock and reinstal it work for mee
I deleted the file "composer.lock" , then launched my cmd again and it worked
This worked for me toooo!
Version information
Description:
Problem 1