Level 102
Can you show your current composer.json file?
Mar 7, 2022
10
Level 6
Upgrade Laravel 8 to Laravel 9
Hi guys, i trying to upgrade a project following the docs, i update laravel version to 9.0, nunomaduro/collision to 6.1 and change from facade/ignition to "spatie/laravel-ignition": "^1.0". the thing is when i try to update the Flysystem get errors but dont say nothing revelant. any idea what could possibly be??
Problem 1 - Root composer.json requires laravel/framework ^9.0, found laravel/framework[v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require. Problem 2 - laravel/sanctum is locked to version v2.14.0 and an update of this package was not requested. - laravel/sanctum v2.14.0 requires illuminate/database ^6.9|^7.0|^8.0|^9.0 -> found illuminate/database[v6.10.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require. Problem 3 - laravel/tinker is locked to version v2.7.0 and an update of this package was not requested. - laravel/tinker v2.7.0 requires illuminate/console ^6.0|^7.0|^8.0|^9.0 -> found illuminate/console[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require. Problem 4 - spatie/laravel-backup is locked to version 7.7.3 and an update of this package was not requested. - spatie/laravel-backup 7.7.3 requires illuminate/console ^8.36 -> found illuminate/console[v8.36.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require. Problem 5 - ukfast/laravel-health-check is locked to version v1.13.2 and an update of this package was not requested. - ukfast/laravel-health-check v1.13.2 requires illuminate/console ^5.4|^6.0|^7.0|^8.0 -> found illuminate/console[v5.4.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 - barryvdh/laravel-ide-helper is locked to version v2.12.1 and an update of this package was not requested. - barryvdh/laravel-ide-helper v2.12.1 requires illuminate/console ^8 || ^9 -> found illuminate/console[v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require. Problem 7 - knuckleswtf/scribe is locked to version 3.22.0 and an update of this package was not requested. - knuckleswtf/scribe 3.22.0 requires illuminate/console ^6.0|^7.0|^8.0|^9.0 -> found illuminate/console[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require. Problem 8 - laravel/breeze is locked to version v1.7.1 and an update of this package was not requested. - laravel/breeze v1.7.1 requires illuminate/filesystem ^8.42|^9.0 -> found illuminate/filesystem[v8.42.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require. Problem 9 - laravel/sail is locked to version v1.13.1 and an update of this package was not requested. - laravel/sail v1.13.1 requires illuminate/console ^8.0|^9.0 -> found illuminate/console[v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require.
Level 6
{
"name": "laravel/laravel",
"type": "project",
"description": "The Laravel Framework.",
"keywords": [
"framework",
"laravel"
],
"license": "MIT",
"require": {
"php": "^7.3|^8.0",
"dariuszp/cli-progress-bar": "^1.0",
"doctrine/dbal": "^3.0",
"elibyy/tcpdf-laravel": "^8.1.2|^9.0",
"ezyang/htmlpurifier": "^4.13",
"fideloper/proxy": "^4.4",
"fruitcake/laravel-cors": "^2.0",
"guzzlehttp/guzzle": "^7.0.1",
"laravel/fortify": "^1.7",
"laravel/framework": "^9.0",
"laravel/sanctum": "^2.9",
"laravel/tinker": "^2.5",
"league/csv": "^9.6",
"league/flysystem-aws-s3-v3": "~1.0",
"maatwebsite/excel": "^3.1",
"mpdf/mpdf": "^8.0",
"php-ds/php-ds": "^1.3",
"phpoffice/phpspreadsheet": "^1.21",
"ramsey/uuid": "^4.1",
"respect/validation": "^2.2",
"spatie/laravel-backup": "^7.7.3|^8.0.9",
"ukfast/laravel-health-check": "^1.10"
},
"require-dev": {
"barryvdh/laravel-ide-helper": "^2.9",
"brianium/paratest": "^6.3",
"spatie/laravel-ignition": "^1.0",
"fakerphp/faker": "^1.9.1",
"friendsofphp/php-cs-fixer": "^3.2",
"knuckleswtf/scribe": "^3.11",
"laravel/breeze": "^1.0",
"laravel/sail": "^1.0.1",
"mockery/mockery": "^1.4.2",
"nunomaduro/collision": "^5.11.0|^6.1",
"phpunit/phpunit": "^9.3.3"
},
"config": {
"optimize-autoloader": true,
"preferred-install": "dist",
"sort-packages": true,
"allow-plugins": {
"composer/package-versions-deprecated": true
}
},
"extra": {
"laravel": {
"dont-discover": []
}
},
"autoload": {
"psr-4": {
"App\": "app/",
"Database\Factories\": "database/factories/",
"Database\Seeders\": "database/seeders/"
}
},
"autoload-dev": {
"psr-4": {
"Tests\": "tests/"
}
},
"minimum-stability": "dev",
"prefer-stable": true,
"scripts": {
"post-autoload-dump": [
"Illuminate\Foundation\ComposerScripts::postAutoloadDump",
"@php artisan package:discover --ansi"
],
"post-root-package-install": [
"@php -r \"file_exists('.env') || copy('.env.example', '.env');\""
],
"post-create-project-cmd": [
"@php artisan key:generate --ansi"
],
"post-update-cmd": [
"Illuminate\Foundation\ComposerScripts::postUpdate",
"@php artisan ide-helper:generate",
"@php artisan ide-helper:meta"
]
}
}
Level 6
@Sinnbeck TY for the advice
Level 102
@hcastillo Can you try running composer update -W
Level 6
@Sinnbeck i dont understand the "conflict analysis", i ran composer update -W
Problem 1
- Conclusion: don't install spatie/laravel-backup 8.0.9 (conflict analysis result)
- Conclusion: don't install spatie/laravel-backup 7.7.3 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.3.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.3.1 (conflict analysis result)
- Conclusion: don't install one of spatie/laravel-backup[8.0.9], league/flysystem-aws-s3-v3[1.0.28], laravel/framework[v9.2.0] | install league/flysystem[3.0.11] (conflict analysis result)
- Conclusion: don't install illuminate/support v8.71.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.0.0-beta.2 (conflict analysis result)
- Conclusion: don't install illuminate/support v8.72.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.0.0-beta.3 (conflict analysis result)
- Conclusion: don't install illuminate/support v8.73.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.0.0-beta.4 (conflict analysis result)
- Conclusion: don't install illuminate/support v8.73.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.0.0-beta.5 (conflict analysis result)
- Conclusion: don't install illuminate/support v8.73.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.0.0 (conflict analysis result)
- Conclusion: don't install illuminate/support v8.74.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.0.1 (conflict analysis result)
- Conclusion: don't install illuminate/support v8.75.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.0.2 (conflict analysis result)
- Conclusion: don't install illuminate/support v8.76.0 (conflict analysis result)
- Conclusion: don't install illuminate/support[v8.76.1] | install one of laravel/framework[v9.1.0, v9.2.0] (conflict analysis result)
- Conclusion: don't install illuminate/support[v8.76.2] | install one of laravel/framework[v9.1.0, v9.2.0] (conflict analysis result)
- Conclusion: don't install illuminate/support[v8.77.0] | install one of laravel/framework[v9.1.0, v9.2.0] (conflict analysis result)
- Conclusion: don't install illuminate/support[v8.77.1] | install one of laravel/framework[v9.1.0, v9.2.0] (conflict analysis result)
- Conclusion: don't install illuminate/support[v8.78.0] | install one of laravel/framework[v9.1.0, v9.2.0] (conflict analysis result)
- Conclusion: don't install illuminate/support[v8.78.1] | install one of laravel/framework[v9.1.0, v9.2.0] (conflict analysis result)
- Conclusion: don't install illuminate/support[v8.79.0] | install one of laravel/framework[v9.1.0, v9.2.0] (conflict analysis result)
- Conclusion: don't install illuminate/support[v8.80.0] | install one of laravel/framework[v9.1.0, v9.2.0] (conflict analysis result)
- Conclusion: don't install illuminate/support[v8.81.0] | install one of laravel/framework[v9.1.0, v9.2.0] (conflict analysis result)
- Conclusion: don't install illuminate/support[v8.82.0] | install one of laravel/framework[v9.1.0, v9.2.0] (conflict analysis result)
- Conclusion: don't install illuminate/support[v8.83.0] | install one of laravel/framework[v9.1.0, v9.2.0] (conflict analysis result)
- Conclusion: don't install illuminate/support[v8.83.1] | install one of laravel/framework[v9.1.0, v9.2.0] (conflict analysis result)
- Conclusion: don't install laravel/framework v9.1.0 (conflict analysis result)
- Conclusion: don't install illuminate/support v8.83.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.2.0 (conflict analysis result)
- Conclusion: don't install illuminate/support v8.83.3 (conflict analysis result)
- Conclusion: don't install one of spatie/laravel-backup[8.0.9], league/flysystem-aws-s3-v3[1.0.27] | install one of league/flysystem[1.1.8, 1.1.9, 3.0.5, ..., 3.0.11] (conflict analysis result)
- Conclusion: don't install one of spatie/laravel-backup[8.0.9], league/flysystem-aws-s3-v3[1.0.26] | install one of league/flysystem[1.1.7, 1.1.8, 1.1.9, 3.0.3, ..., 3.0.11] (conflict analysis result)
- Root composer.json requires spatie/laravel-backup ^7.7.3|^8.0.9 -> satisfiable by spatie/laravel-backup[7.7.3, v7.x-dev, 8.0.9].
- Root composer.json requires league/flysystem-aws-s3-v3 ~1.0 -> satisfiable by league/flysystem-aws-s3-v3[1.0.0, ..., 1.0.x-dev (alias of dev-master)].
- Conclusion: don't install laravel/framework v9.0.0-beta.1 (conflict analysis result)
- spatie/laravel-backup v7.x-dev requires illuminate/support ^8.36 -> satisfiable by illuminate/support[v8.36.0, ..., 8.x-dev].
- Only one of these can be installed: illuminate/support[v5.4.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev], laravel/framework[v9.0.0-beta.1, ..., 9.x-dev]. laravel/framework replaces illuminate/support and thus cannot coexist with it.
- Root composer.json requires laravel/framework ^9.0 -> satisfiable by laravel/framework[v9.0.0-beta.1, ..., 9.x-dev].
Level 102
@hcastillo Can you try setting backup to a specific version
"spatie/laravel-backup": "^8.0",
and then try it again
Level 6
@Sinnbeck i try and get this
Problem 1
- Conclusion: don't install laravel/framework v9.0.0-beta.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.0.0-beta.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.0.0-beta.3 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.0.0-beta.4 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.0.0-beta.5 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.0.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.0.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.0.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.1.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.2.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.3.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.3.1 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.0 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.1 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.2 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.3 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.4 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.5 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.6 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.7 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.8 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.9 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.10 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.11 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.12 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.13 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.15 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.16 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.17 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.18 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.19 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.20 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.21 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.22 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.23 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.24 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.25 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.26 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.27 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.28 (conflict analysis result)
- Conclusion: don't install league/flysystem 3.0.10 (conflict analysis result)
- Conclusion: don't install league/flysystem-aws-s3-v3 1.0.29 (conflict analysis result)
- Conclusion: don't install league/flysystem 3.0.11 (conflict analysis result)
- Root composer.json requires laravel/framework ^9.0 -> satisfiable by laravel/framework[v9.0.0-beta.1, ..., 9.x-dev].
- Conclusion: don't install one of league/flysystem[3.0.9], league/flysystem-aws-s3-v3[dev-master] | install league/flysystem[1.1.9] (conflict analysis result)
- Conclusion: don't install one of league/flysystem[3.0.8], league/flysystem-aws-s3-v3[dev-master] | install league/flysystem[1.1.9] (conflict analysis result)
- Conclusion: don't install one of league/flysystem[3.0.7], league/flysystem-aws-s3-v3[dev-master] | install league/flysystem[1.1.9] (conflict analysis result)
- Conclusion: don't install one of league/flysystem[3.0.6], league/flysystem-aws-s3-v3[dev-master] | install league/flysystem[1.1.9] (conflict analysis result)
- Conclusion: don't install one of league/flysystem[3.0.5], league/flysystem-aws-s3-v3[dev-master] | install league/flysystem[1.1.9] (conflict analysis result)
- Conclusion: don't install one of league/flysystem[3.0.4], league/flysystem-aws-s3-v3[dev-master] | install league/flysystem[1.1.9] (conflict analysis result)
- Conclusion: don't install one of league/flysystem[3.0.3], league/flysystem-aws-s3-v3[dev-master] | install league/flysystem[1.1.9] (conflict analysis result)
- Conclusion: don't install one of league/flysystem[3.0.2], league/flysystem-aws-s3-v3[dev-master] | install league/flysystem[1.1.9] (conflict analysis result)
- Conclusion: don't install one of league/flysystem[3.0.1], league/flysystem-aws-s3-v3[dev-master] | install league/flysystem[1.1.9] (conflict analysis result)
- Conclusion: don't install league/flysystem 1.1.9 (conflict analysis result)
- league/flysystem-aws-s3-v3 1.0.x-dev is an alias of league/flysystem-aws-s3-v3 dev-master and thus requires it to be installed too.
- Root composer.json requires league/flysystem-aws-s3-v3 ~1.0 -> satisfiable by league/flysystem-aws-s3-v3[1.0.0, ..., 1.0.x-dev (alias of dev-master)].
- league/flysystem-aws-s3-v3 dev-master requires league/flysystem ^1.0.40 -> satisfiable by league/flysystem[1.0.40, ..., 1.x-dev].
- You can only install one version of a package, so only one of these can be installed: league/flysystem[1.0.0-alpha1, ..., 1.x-dev, 2.0.0-alpha.1, ..., 2.x-dev, 3.0.0, ..., 3.x-dev].
- laravel/framework 9.x-dev requires league/flysystem ^3.0 -> satisfiable by league/flysystem[3.0.0, ..., 3.x-dev].
- Conclusion: don't install league/flysystem 3.0.0 (conflict analysis result)
so, first i try to update composer require -W league/flysystem-aws-s3-v3 "^3.0" and get
Problem 1
- Root composer.json requires laravel/framework ^9.0, found laravel/framework[v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 2
- Root composer.json requires spatie/laravel-backup ^8.0, found spatie/laravel-backup[8.0.0, ..., 8.0.9] but the package is fixed to 7.7.3 (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.
Problem 3
- laravel/sanctum is locked to version v2.14.0 and an update of this package was not requested.
- laravel/sanctum v2.14.0 requires illuminate/database ^6.9|^7.0|^8.0|^9.0 -> found illuminate/database[v6.10.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 4
- laravel/tinker is locked to version v2.7.0 and an update of this package was not requested.
- laravel/tinker v2.7.0 requires illuminate/console ^6.0|^7.0|^8.0|^9.0 -> found illuminate/console[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 5
- ukfast/laravel-health-check is locked to version v1.13.2 and an update of this package was not requested.
- ukfast/laravel-health-check v1.13.2 requires illuminate/console ^5.4|^6.0|^7.0|^8.0 -> found illuminate/console[v5.4.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
- barryvdh/laravel-ide-helper is locked to version v2.12.1 and an update of this package was not requested.
- barryvdh/laravel-ide-helper v2.12.1 requires illuminate/console ^8 || ^9 -> found illuminate/console[v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 7
- knuckleswtf/scribe is locked to version 3.22.0 and an update of this package was not requested.
- knuckleswtf/scribe 3.22.0 requires illuminate/console ^6.0|^7.0|^8.0|^9.0 -> found illuminate/console[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 8
- laravel/breeze is locked to version v1.7.1 and an update of this package was not requested.
- laravel/breeze v1.7.1 requires illuminate/filesystem ^8.42|^9.0 -> found illuminate/filesystem[v8.42.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require.
Problem 9
- laravel/sail is locked to version v1.13.1 and an update of this package was not requested.
- laravel/sail v1.13.1 requires illuminate/console ^8.0|^9.0 -> found illuminate/console[v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require.
Level 102
@hcastillo Alright. Now try removing "league/flysystem-aws-s3-v3": "~1.0", completely and see if it allows you to update. If so, we can look into installing aws again afterwards
composer require -W league/flysystem-aws-s3-v3 "^3.0"
Level 6
@Sinnbeck that work, thank you so much. i getting other errors about header (Trusted Proxies ) but that is cover in the documentation.
Level 102
@hcastillo Awesome. :) Please mark "best answer" to set the thread as solved.
2 likes
Please or to participate in this conversation.