Related
I'm updating Laravel from 6.18 to 8. Normally I would simply change the version in composer.json and run composer update.
There are a bunch of additional changes for 6.x to 7 so I'm trying to do this first (as I use the auth scaffolding that changed in 7 but isn't mentioned in the documentation for 8.x upgrades).
I change composer.json accordingly (also dropping some outdated other stuff) and run composer update, but this fails (changing directly to 8 fails too). Using composer update -w doesn't work either.
{
"name": "laravel/laravel",
"description": "The Laravel Framework.",
"keywords": ["framework", "laravel"],
"license": "MIT",
"type": "project",
"require": {
"php": "^7.2.2",
"ajthinking/tinx": "^2.1",
"barryvdh/laravel-debugbar": "^3.2",
"davejamesmiller/laravel-breadcrumbs": "^5.2",
"doctrine/dbal": "^2.10",
"dompdf/dompdf": "^0.8.5",
"facade/ignition": "^1.16",
"fico7489/laravel-pivot": "^3.0",
"fideloper/proxy": "^4.0",
"guzzlehttp/guzzle": "^6.5",
"guzzlehttp/psr7": "^1.6",
"jrean/laravel-user-verification": "^8.0",
"kriswallsmith/buzz": "^1.1",
"laravel/framework": "6.x",
"laravel/helpers": "^1.1",
"laravel/tinker": "^1.0",
"laravelcollective/html": "^6.0",
"maatwebsite/excel": "^3.1",
"mailgun/mailgun-php": "^3.0",
"nunomaduro/phpinsights": "^1.11",
"nyholm/psr7": "^1.2",
"php-http/guzzle6-adapter": "^2.0",
"php-http/message": "^1.8",
"predis/predis": "^1.1",
"simplesoftwareio/simple-qrcode": "~2"
},
"require-dev": {
"filp/whoops": "^2.0",
"fzaninotto/faker": "^1.4",
"mockery/mockery": "^1.0",
"nunomaduro/collision": "^2.0",
"phpunit/phpunit": "^7.0"
},
"autoload": {
"classmap": [
"database/seeds",
"database/factories"
],
"files": [
"app/Http/helpers.php"
],
"psr-4": {
"App\\": "app/"
}
},
"autoload-dev": {
"psr-4": {
"Tests\\": "tests/"
}
},
"extra": {
"laravel": {
"dont-discover": [
]
}
},
"scripts": {
"post-root-package-install": [
"#php -r \"file_exists('.env') || copy('.env.example', '.env');\""
],
"post-create-project-cmd": [
"#php artisan key:generate"
],
"post-autoload-dump": [
"Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
"#php artisan package:discover"
]
},
"config": {
"preferred-install": "dist",
"sort-packages": true,
"optimize-autoloader": true
},
"minimum-stability": "dev",
"prefer-stable": true
}
to
{
"name": "laravel/laravel",
"description": "The Laravel Framework.",
"keywords": ["framework", "laravel"],
"license": "MIT",
"type": "project",
"require": {
"php": "^7.2.2",
"barryvdh/laravel-debugbar": "^3.2",
"davejamesmiller/laravel-breadcrumbs": "^5.2",
"doctrine/dbal": "^2.10",
"dompdf/dompdf": "^0.8.5",
"facade/ignition": "^2.0",
"fico7489/laravel-pivot": "^3.0",
"fideloper/proxy": "^4.0",
"guzzlehttp/guzzle": "^6.5",
"guzzlehttp/psr7": "^1.6",
"kriswallsmith/buzz": "^1.1",
"laravel/framework": "7.x",
"laravel/helpers": "^1.1",
"laravel/tinker": "^2.0",
"laravelcollective/html": "^6.0",
"maatwebsite/excel": "^3.1",
"mailgun/mailgun-php": "^3.0",
"nunomaduro/phpinsights": "^1.11",
"nyholm/psr7": "^1.2",
"php-http/guzzle6-adapter": "^2.0",
"php-http/message": "^1.8",
"predis/predis": "^1.1",
"simplesoftwareio/simple-qrcode": "~2"
},
"require-dev": {
"filp/whoops": "^2.0",
"fzaninotto/faker": "^1.4",
"mockery/mockery": "^1.0",
"nunomaduro/collision": "^4.1",
"phpunit/phpunit": "^8.5"
},
"autoload": {
"classmap": [
"database/seeds",
"database/factories"
],
"files": [
"app/Http/helpers.php"
],
"psr-4": {
"App\\": "app/"
}
},
"autoload-dev": {
"psr-4": {
"Tests\\": "tests/"
}
},
"extra": {
"laravel": {
"dont-discover": [
]
}
},
"scripts": {
"post-root-package-install": [
"#php -r \"file_exists('.env') || copy('.env.example', '.env');\""
],
"post-create-project-cmd": [
"#php artisan key:generate"
],
"post-autoload-dump": [
"Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
"#php artisan package:discover"
]
},
"config": {
"preferred-install": "dist",
"sort-packages": true,
"optimize-autoloader": true
},
"minimum-stability": "dev",
"prefer-stable": true
}
But this is failing (Laravel isn't updated)
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Conclusion: don't install one of phploc/phploc[5.0.0], symfony/console[v5.0.0-BETA1] | install one of symfony/console[v4.1.12, ..., v4.4.30] (conflict analysis result)
- Conclusion: don't install facade/ignition 2.10.0 (conflict analysis result)
- Conclusion: don't install symfony/console[v5.3.0-BETA1] | install one of symfony/console[v4.4.3, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.3 (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.4 (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.0-BETA1] | install one of symfony/console[v4.4.5, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[5.4.x-dev] | install one of symfony/console[v4.4.5, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[5.3.x-dev] | install one of symfony/console[v4.4.5, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[5.1.x-dev] | install one of symfony/console[v4.4.5, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[5.0.x-dev] | install one of symfony/console[v4.4.5, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.5 (conflict analysis result)
- Conclusion: don't install symfony/console[v5.3.0-BETA2] | install one of symfony/console[v4.4.6, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.2.0-BETA3] | install one of symfony/console[v4.4.6, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.2.0-BETA2] | install one of symfony/console[v4.4.6, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.2.0-BETA1] | install one of symfony/console[v4.4.6, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.1.0-BETA1] | install one of symfony/console[v4.4.6, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.0-BETA2] | install one of symfony/console[v4.4.6, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v4.4.6] | install one of laravel/framework[v7.30.2, v7.30.3], symfony/console[v5.0.0-RC1, ..., v5.3.0-RC1] (conflict analysis result)
- Conclusion: don't install laravel/framework v7.30.2 (conflict analysis result)
- Conclusion: don't install facade/ignition 2.10.1 (conflict analysis result)
- Conclusion: don't install symfony/console[v5.1.0-RC1] | install one of symfony/console[v4.4.7, ..., v4.4.15] (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.7 (conflict analysis result)
- Conclusion: don't install symfony/console[v5.3.0-BETA3] | install one of symfony/console[v4.4.8, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.3.0-BETA4] | install one of symfony/console[v4.4.8, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.0-RC1] | install one of symfony/console[v4.4.8, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v4.4.8] | install one of laravel/framework[v7.30.3], symfony/console[v5.0.0, ..., v5.3.0-RC1] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.2.0-RC2] | install one of symfony/console[v4.4.9, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.1.0-RC2] | install one of symfony/console[v4.4.9, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v4.4.10] | install one of laravel/framework[v7.30.3], symfony/console[v5.0.0, ..., v5.3.0-RC1] (conflict analysis result)
- Conclusion: don't install symfony/console[v4.4.9] | install one of laravel/framework[v7.30.3], symfony/console[v5.0.0, ..., v5.3.0-RC1] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.2] | install one of symfony/console[v4.4.11, ..., v4.4.29] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.2.0-RC1] | install one of symfony/console[v4.4.11, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.3] | install one of symfony/console[v4.4.11, ..., v4.4.29] (conflict analysis result)
- Conclusion: don't install symfony/console[v4.4.11] | install one of laravel/framework[v7.30.3], symfony/console[v5.0.0, ..., v5.3.0-RC1] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.0] | install one of symfony/console[v4.4.12, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.1] | install one of symfony/console[v4.4.12, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.3.0-RC1] | install one of symfony/console[v4.4.12, ..., v4.4.17] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.4] | install one of symfony/console[v4.4.12, ..., v4.4.16] (conflict analysis result)
- Conclusion: don't install symfony/console[v4.4.13] | install one of laravel/framework[v7.30.3], symfony/console[v5.0.5, ..., v5.1.0] (conflict analysis result)
- Conclusion: don't install symfony/console[v4.4.12] | install one of laravel/framework[v7.30.3], symfony/console[v5.0.5, ..., v5.1.0] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.6] | install one of symfony/console[v4.4.14, ..., v4.4.30] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.7] | install one of symfony/console[v4.4.14, ..., v4.4.30] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.8] | install one of symfony/console[v4.4.14, ..., v4.4.30] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.5] | install one of symfony/console[v4.4.14, v4.4.15, v4.4.16] (conflict analysis result)
- Conclusion: don't install symfony/console[v4.4.14] | install one of laravel/framework[v7.30.3], symfony/console[v5.0.9, v5.0.10, v5.0.11, v5.1.0] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.9] | install one of symfony/console[v4.4.15, v4.4.16] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.10] | install one of symfony/console[v4.4.15, v4.4.16] (conflict analysis result)
- Conclusion: don't install symfony/console[v4.4.15] | install one of laravel/framework[v7.30.3], symfony/console[v5.0.11] (conflict analysis result)
- Conclusion: don't install laravel/framework v7.30.3 (conflict analysis result)
- Conclusion: don't install facade/ignition 2.10.2 (conflict analysis result)
- Conclusion: don't install facade/ignition 2.11.0 (conflict analysis result)
- Conclusion: don't install symfony/console[v5.0.11] | install symfony/console[v4.4.16] (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.16 (conflict analysis result)
- Conclusion: don't install facade/ignition 2.11.1 (conflict analysis result)
- Conclusion: don't install facade/ignition 2.11.2 (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.17 (conflict analysis result)
- Conclusion: don't install symfony/console v5.1.0 (conflict analysis result)
- Conclusion: don't install symfony/console[v5.1.2] | install one of symfony/console[v4.4.18, ..., v4.4.29] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.1.3] | install one of symfony/console[v4.4.18, ..., v4.4.30] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.1.1] | install one of symfony/console[v4.4.18, ..., v4.4.29] (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.18 (conflict analysis result)
- Conclusion: don't install symfony/console v5.1.4 (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.19 (conflict analysis result)
- Conclusion: don't install symfony/console v5.1.5 (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.20 (conflict analysis result)
- Conclusion: don't install symfony/console v5.1.6 (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.21 (conflict analysis result)
- Conclusion: don't install symfony/console v5.1.7 (conflict analysis result)
- Conclusion: don't install symfony/console[v5.1.10] | install one of symfony/console[v4.4.22, ..., v4.4.30] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.1.11] | install one of symfony/console[v4.4.22, ..., v4.4.30] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.1.9] | install one of symfony/console[v4.4.22, ..., v4.4.29] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.1.8] | install one of symfony/console[v4.4.22, ..., v4.4.29] (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.22 (conflict analysis result)
- Conclusion: don't install symfony/console v5.2.0 (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.23 (conflict analysis result)
- Conclusion: don't install symfony/console v5.2.1 (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.24 (conflict analysis result)
- Conclusion: don't install symfony/console v5.2.2 (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.25 (conflict analysis result)
- Conclusion: don't install symfony/console v5.2.3 (conflict analysis result)
- Conclusion: don't install symfony/console[v5.2.6] | install one of symfony/console[v4.4.26, v4.4.27, v4.4.29, v4.4.30] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.2.7] | install one of symfony/console[v4.4.26, v4.4.27, v4.4.29, v4.4.30] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.2.5] | install one of symfony/console[v4.4.26, v4.4.27, v4.4.29] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.2.4] | install one of symfony/console[v4.4.26, v4.4.27, v4.4.29] (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.26 (conflict analysis result)
- Conclusion: don't install symfony/console v5.2.8 (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.27 (conflict analysis result)
- Conclusion: don't install symfony/console v5.2.10 (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.29 (conflict analysis result)
- Conclusion: don't install symfony/console v5.2.11 (conflict analysis result)
- Conclusion: don't install facade/ignition 2.11.3 (conflict analysis result)
- Conclusion: don't install symfony/console v5.2.12 (conflict analysis result)
- Conclusion: don't install facade/ignition 2.11.4 (conflict analysis result)
- Conclusion: don't install symfony/console v5.2.14 (conflict analysis result)
- Conclusion: don't install symfony/console v5.3.0 (conflict analysis result)
- Conclusion: don't install symfony/console[v5.3.4] | install symfony/console[v4.4.30] (conflict analysis result)
- Conclusion: don't install symfony/console[v5.3.2] | install symfony/console[v4.4.30] (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.30 (conflict analysis result)
- Conclusion: don't install facade/ignition 2.12.0 (conflict analysis result)
- Conclusion: don't install symfony/console v5.3.6 (conflict analysis result)
- Conclusion: don't install one of phploc/phploc[5.0.0], symfony/console[v5.3.7] (conflict analysis result)
- Conclusion: don't install sebastian/version[2.0.1] | install phploc/phploc[5.0.0] (conflict analysis result)
- Conclusion: install sebastian/version 2.0.1 (conflict analysis result)
- Conclusion: don't install one of phploc/phploc[5.0.0], symfony/console[v5.2.4] | install one of symfony/console[v4.4.18, ..., v4.4.30] (conflict analysis result)
- Conclusion: don't install symfony/console v4.4.2 (conflict analysis result)
- Conclusion: don't install one of phploc/phploc[5.0.0], symfony/console[v5.2.5] | install one of symfony/console[v4.4.18, ..., v4.4.30] (conflict analysis result)
- Conclusion: don't install one of phploc/phploc[5.0.0], symfony/console[v5.1.0-BETA1] | install one of symfony/console[v4.2.0, ..., v4.4.30] (conflict analysis result)
- Conclusion: don't install one of phploc/phploc[5.0.0], symfony/console[v5.0.0-BETA2] | install one of symfony/console[v4.1.12, ..., v4.4.30] (conflict analysis result)
- Root composer.json requires laravel/framework 7.x -> satisfiable by laravel/framework[v7.0.0, ..., 7.x-dev].
- Root composer.json requires phpunit/phpunit ^8.5 -> satisfiable by phpunit/phpunit[8.5.0, ..., 8.5.x-dev].
- Root composer.json requires nunomaduro/phpinsights ^1.11 -> satisfiable by nunomaduro/phpinsights[v1.11.0, ..., v1.x-dev].
- facade/ignition[2.0.0, ..., 2.9.1] require symfony/console ^5.0 -> satisfiable by symfony/console[v5.0.0-BETA1, ..., 5.4.x-dev].
- Conclusion: don't install symfony/console[5.2.x-dev] | install one of symfony/console[v4.4.2, ..., v4.4.17] (conflict analysis result)
- Root composer.json requires facade/ignition ^2.0 -> satisfiable by facade/ignition[2.0.0, ..., 2.12.0].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
I have trouble reading what the problem exactly is and have no idea how to solve this (especially since I'm following the steps as laid out by the Laravel update documentation).
I've read about some similar-ish update problems because of different required package versions of symphony/console required by phploc and the require-dev packages? I don't know, nor even how to solve that if it was the case.
Update:
Trying to solve the problem with phploc/phploc, i tried composer update phploc/phploc "6.0.0" -w.
This gives the following error:
Loading composer repositories with package information
Package "6.0.0" listed for update is not locked.
Dependency "laravel/framework" is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency "phpunit/phpunit" is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires facade/ignition ^2.0, found facade/ignition[2.0.0, ..., 2.12.0] but the package is fixed to 1.18.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.
Problem 2
- Root composer.json requires laravel/framework 7.x, found laravel/framework[v7.0.0, ..., 7.x-dev] but the package is fixed to v6.20.33 (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
- Root composer.json requires laravel/tinker ^2.0, found laravel/tinker[v2.0.0, ..., 2.x-dev] but the package is fixed to v1.0.10 (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 4
- laravel/ui[v2.0.0, ..., 2.x-dev] require illuminate/console ^7.0 -> found illuminate/console[v7.0.0, ..., 7.x-dev] but these were not loaded, likely because it conflicts with another require.
- laravel/ui[v2.2.0, ..., v2.3.0] require illuminate/console ^7.0|^8.0 -> found illuminate/console[v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
- Root composer.json requires laravel/ui ^2.0 -> satisfiable by laravel/ui[v2.0.0, ..., 2.x-dev].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Tried composer require phploc/phploc, and update, both with and without -w
All result pretty much in the following:
Problem 1
- nunomaduro/phpinsights is locked to version v1.13.0 and an update of this package was not requested.
- nunomaduro/phpinsights v1.13.0 requires phploc/phploc ^5.0 -> found phploc/phploc[5.0.0] but it conflicts with your root composer.json require (^7.0).
Problem 2
- phploc/phploc 7.0.x-dev is an alias of phploc/phploc dev-master and thus requires it to be installed too.
- phploc/phploc[dev-master, 7.0.0, ..., 7.0.2] require sebastian/version ^3.0 -> satisfiable by sebastian/version[3.0.0, 3.0.1, 3.0.2].
- You can only install one version of a package, so only one of these can be installed: sebastian/version[2.0.1, 3.0.0, 3.0.1, 3.0.2].
- phpunit/phpunit 7.5.20 requires sebastian/version ^2.0.1 -> satisfiable by sebastian/version[2.0.1].
- phpunit/phpunit is locked to version 7.5.20 and an update of this package was not requested.
- Root composer.json requires phploc/phploc ^7.0 -> satisfiable by phploc/phploc[7.0.0, 7.0.1, 7.0.2, 7.0.x-dev (alias of dev-master)].
phploc/phploc is required in v5, which requires symfony/console in v4. Laravel v7 requires Symfony v5.
Solution: update phploc/phploc to at least v6. As this is not listed in your composer.json, maybe as part of "removing outdated stuff": did you use it before? How did you remove it? By simply removing it from your composer.json without using composer remove phploc/phploc?
It could help to rollback all changes in your composer.json, remove what you want to remove package by package and call composer update $packagename after each single removal
I am attempting to install league/flysystem-aws-s3-v3 with laravel but receive the following:
Problem 1
- The requested package league/flysystem (locked at 1.1.3, required as ^2.0) is satisfiable by league/flysystem[1.1.3] but these conflict with your requirements or minimum-stability.
Problem 2
- Conclusion: remove laravel/framework v7.28.4
- Conclusion: don't install laravel/framework v7.28.4
- Conclusion: don't install league/flysystem 2.0.2
- Conclusion: don't install league/flysystem 2.0.1
- Conclusion: don't install league/flysystem 2.0.0
- Conclusion: don't install league/flysystem 2.0.0-RC1
- Conclusion: don't install league/flysystem 2.0.0-beta.3
- Conclusion: don't install league/flysystem 2.0.0-beta.2
- Conclusion: don't install league/flysystem 2.0.0-beta.1
- Conclusion: don't install league/flysystem 2.0.0-alpha.4
- Conclusion: don't install league/flysystem 2.0.0-alpha.3
- Conclusion: don't install league/flysystem 2.0.0-alpha.2
- Installation request for laravel/framework (locked at v7.28.4, required as ^7.24) -> satisfiable by laravel/framework[v7.28.4].
- Conclusion: don't install league/flysystem 2.0.0-alpha.1
- laravel/framework v7.28.4 requires league/flysystem ^1.0.34 -> satisfiable by league/flysystem[1.0.x-dev, 1.x-dev].
- Can only install one of: league/flysystem[2.x-dev, 1.x-dev].
- Can only install one of: league/flysystem[2.x-dev, 1.0.x-dev].
- Installation request for league/flysystem ^2.0 -> satisfiable by league/flysystem[2.0.0, 2.0.0-RC1, 2.0.0-alpha.1, 2.0.0-alpha.2, 2.0.0-alpha.3, 2.0.0-alpha.4, 2.0.0-beta.1, 2.0.0-beta.2, 2.0.0-beta.3, 2.0.1, 2.0.2, 2.x-dev].
When I try to update league/flysystem I receive the following:
Problem 1
- Conclusion: remove laravel/framework v7.28.4
- Conclusion: don't install laravel/framework v7.28.4
- Conclusion: don't install league/flysystem 2.0.2
- Conclusion: don't install league/flysystem 2.0.1
- Conclusion: don't install league/flysystem 2.0.0
- Conclusion: don't install league/flysystem 2.0.0-RC1
- Conclusion: don't install league/flysystem 2.0.0-beta.3
- Conclusion: don't install league/flysystem 2.0.0-beta.2
- Conclusion: don't install league/flysystem 2.0.0-beta.1
- Conclusion: don't install league/flysystem 2.0.0-alpha.4
- Conclusion: don't install league/flysystem 2.0.0-alpha.3
- Conclusion: don't install league/flysystem 2.0.0-alpha.2
- Installation request for laravel/framework (locked at v7.28.4, required as ^7.24) -> satisfiable by laravel/framework[v7.28.
- Conclusion: don't install league/flysystem 2.0.0-alpha.1
- laravel/framework v7.28.4 requires league/flysystem ^1.0.34 -> satisfiable by league/flysystem[1.0.x-dev, 1.x-dev].
- Can only install one of: league/flysystem[2.x-dev, 1.x-dev].
- Can only install one of: league/flysystem[2.x-dev, 1.0.x-dev].
- Installation request for league/flysystem ^2.0 -> satisfiable by league/flysystem[2.0.0, 2.0.0-RC1, 2.0.0-alpha.1, 2.0.0-alp
I am also unable to remove league/flysystem or update laravel
You're using Laravel 7 (although the same is true for Laravel 8), if you take a look at the laravel/framework composer.json file, you will see that it is requiring version 1; "league/flysystem": "^1.1"
Per composer constraints, this will allow any version from 1.1 to less than 2 (>=1.1 <2).
Now it is technically possible to install 2 different versions of a package, but I'd highly advise against it as you have to monkey with the autoloader to change the namespace for one version of the package. This answer covers the details on how to do it if you absolutely must.
If you are using laravel/framework version >= 8. Try running this command in your console. It worked for me.
composer require league/flysystem-aws-s3-v3
I'm trying to regenerate my composer.lock file with composer.phar install, but I'm running into this error:
Problem 1
- Conclusion: don't install laravel/framework v5.4.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.3 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.4 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.5 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.6 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.7 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.8 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.9 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.10 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.11 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.12 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.13 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.14 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.15 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.16 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.17 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.18 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.19 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.20 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.21 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.22 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.23 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.24 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.25 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.26 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.27 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.28 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.29 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.30 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.31 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.32 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.33 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.34 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.35 (conflict analysis result)
- Conclusion: don't install laravel/framework v5.4.36 (conflict analysis result)
- barryvdh/laravel-debugbar[v3.4.0, ..., v3.4.2] require maximebf/debugbar ^1.16.3 -> satisfiable by maximebf/debugbar[v1.16.3, v1.16.4].
- barryvdh/laravel-debugbar[v3.5.0, ..., v3.5.1] require php >=7.2 -> your php version (7.0; overridden via config.platform, actual: 7.2.34) does not satisfy that requirement.
- maximebf/debugbar v1.16.3 requires php ^7.1 -> your php version (7.0; overridden via config.platform, actual: 7.2.34) does not satisfy that requirement.
- maximebf/debugbar v1.16.4 requires php ^7.1|^8 -> your php version (7.0; overridden via config.platform, actual: 7.2.34) does not satisfy that requirement.
- illuminate/support[v5.6.0, ..., v5.8.36] require php ^7.1.3 -> your php version (7.0; overridden via config.platform, actual: 7.2.34) does not satisfy that requirement.
- illuminate/support[v6.0.0, ..., v6.19.1] require php ^7.2 -> your php version (7.0; overridden via config.platform, actual: 7.2.34) does not satisfy that requirement.
- illuminate/support[v6.20.0, ..., v6.20.7, v7.29.0, ..., v7.30.0] require php ^7.2.5|^8.0 -> your php version (7.0; overridden via config.platform, actual: 7.2.34) does not satisfy that requirement.
- illuminate/support[v7.0.0, ..., v7.28.4] require php ^7.2.5 -> your php version (7.0; overridden via config.platform, actual: 7.2.34) does not satisfy that requirement.
- barryvdh/laravel-debugbar[v3.2.9, ..., v3.3.3] require illuminate/support ^5.5|^6|^7 -> satisfiable by illuminate/support[v5.5.0, ..., v5.8.36, v6.0.0, ..., v6.20.7, v7.0.0, ..., v7.30.0].
- barryvdh/laravel-debugbar[v3.2.6, ..., v3.2.8] require illuminate/support ^5.5|^6 -> satisfiable by illuminate/support[v5.5.0, ..., v5.8.36, v6.0.0, ..., v6.20.7].
- barryvdh/laravel-debugbar[v3.2.3, ..., v3.2.5] require illuminate/support 5.5.x|5.6.x|5.7.x|5.8.x -> satisfiable by illuminate/support[v5.5.0, ..., v5.8.36].
- barryvdh/laravel-debugbar[v3.2.0, ..., v3.2.2] require illuminate/support 5.5.x|5.6.x|5.7.x -> satisfiable by illuminate/support[v5.5.0, ..., v5.7.28].
- Only one of these can be installed: illuminate/support[v5.2.43, ..., v5.6.7], laravel/framework[v5.4.0, ..., v5.4.36]. They all replace tightenco/collect and thus cannot coexist.
- Root composer.json requires laravel/framework 5.4.* -> satisfiable by laravel/framework[v5.4.0, ..., v5.4.36].
- Root composer.json requires barryvdh/laravel-debugbar ^3.2 -> satisfiable by barryvdh/laravel-debugbar[v3.2.0, ..., v3.5.1].
composer.json file:
{
"name": "laravel/laravel",
"description": "The Laravel Framework.",
"keywords": ["framework", "laravel"],
"license": "MIT",
"type": "project",
"require": {
"php": ">=5.6.4",
"askedio/laravel5-profanity-filter": "^1.10",
"aws/aws-sdk-php-laravel": "^3.4",
"barryvdh/laravel-dompdf": "0.8.0 as 0.7.0",
"dompdf/dompdf": "0.8.0 as 0.7.0",
"fideloper/proxy": "^4.2",
"intervention/image": "^2.5",
"jrean/laravel-user-verification": "4.1.10",
"laravel/framework": "5.4.*",
"laravel/socialite": "^3.3",
"laravel/tinker": "~1.0",
"league/flysystem-aws-s3-v3": "^1.0",
"nesbot/carbon": "1.36.2",
"owen-it/laravel-auditing": "4.1.1",
"predis/predis": "^1.1",
"tymon/jwt-auth": "^1.0.0-rc.2",
"zizaco/entrust": "^1.9"
},
"require-dev": {
"barryvdh/laravel-debugbar": "^3.2",
"fzaninotto/faker": "~1.4",
"mockery/mockery": "0.9.*",
"phpunit/phpunit": "~5.0"
},
"autoload": {
"classmap": [
"database"
],
"psr-4": {
"App\\": "app/",
"Tests\\": "tests/"
}
},
"scripts": {
"post-root-package-install": [
"php -r \"file_exists('.env') || copy('.env.example', '.env');\""
],
"post-create-project-cmd": [
"php artisan key:generate"
],
"post-install-cmd": [
"Illuminate\\Foundation\\ComposerScripts::postInstall",
"php artisan optimize"
],
"post-update-cmd": [
"Illuminate\\Foundation\\ComposerScripts::postUpdate",
"php artisan optimize"
]
},
"config": {
"preferred-install": "dist",
"sort-packages": true,
"platform": {
"php": "7.0"
}
}
}
The dependencies in your composer.json cannot be resolved. The barryvdh/laravel-debugbar version specified cannot be used with the laravel/framework version specified.
The lowest version of barryvdh/laravel-debugbar allowed as specified is 3.2.0. Looking at its composer.json file, it requires laravel/framework version 5.5.x at a minimum. However, you've specified laravel/framework version 5.4.*.
Since your dependencies can't be resolved, you get the error. You'll need to upgrade your laravel/framework version, or downgrade your barryvdh/laravel-debugbar version.
That's a difficult one: your composer.json requires barryvdh/laravel-debugbar in v3.2, and this has a requirement for Laravel v5.5 or later. Through your own requirement, you restrict Laravel's version to v5.4 (through the line "laravel/framework": "5.4.*").
A quick solution could be to either downgrade barryvdh/laravel-debugbar to v2.4.3 (the latest one compatibel with Laravel 5.4), or upgrade your whole application to Laravel 5.5. You should do such upgrades from time to time - this helps you to manage such upgrades. The longer you wait, the more difficult it is to run upgrades, as your application and the packages you require drifted apart too much.
While you're upgrading: Why do you configure PHP 7.0? Your application should not run on such an outdated version any longer, as even the security support has ended two years ago
I needed to customize a package I found on packagist, so I cloned the repo on github and updated my composer.json file to get the dependency from there instead.
Now when I run composer update I get the following:
[4.5MB/0.34s] Loading composer repositories with package information
[4.8MB/1.57s] Updating dependencies (including require-dev)
[248.7MB/16.88s] - Removing serverfireteam/blog (master)
[113.1MB/17.54s] Writing lock file
[113.1MB/17.55s] Generating autoload files
Fatal error: Class 'PHPExcel_Shared_Font' not found in C:\Users\Tim\Code\Laravel\config\excel.php on line 174
PHP Fatal error: Class 'PHPExcel_Shared_Font' not found in C:\Users\Tim\Code\Laravel\config\excel.php on line 174
[113.4MB/18.22s] Script php artisan clear-compiled handling the post-update-cmd event returned with an error
[RuntimeException]
Error Output: PHP Fatal error: Class 'PHPExcel_Shared_Font' not found in C:\Users\Tim\Code\Laravel\config\excel.php on line 174
I reveresed the change, and ran `composer update' again and get the following message:
[4.4MB/0.33s] Loading composer repositories with package information
[4.7MB/1.48s] Updating dependencies (including require-dev)
[258.9MB/15.11s] Your requirements could not be resolved to an installable set of packages.
[258.9MB/15.11s]
Problem 1
- Conclusion: remove laravel/framework v5.0.33
- Conclusion: don't install laravel/framework v5.0.33
- Conclusion: don't install laravel/framework v5.0.32
- Conclusion: don't install laravel/framework v5.0.31
- Conclusion: don't install laravel/framework 5.0.30
- Conclusion: don't install laravel/framework v5.0.29
- Conclusion: don't install laravel/framework v5.0.28
- Conclusion: don't install laravel/framework v5.0.27
- Conclusion: don't install laravel/framework v5.0.26
- Conclusion: don't install laravel/framework v5.0.25
- Conclusion: don't install laravel/framework v5.0.24
- Conclusion: don't install laravel/framework v5.0.23
- Conclusion: don't install laravel/framework v5.0.22
- Conclusion: don't install laravel/framework v5.0.21
- Conclusion: don't install laravel/framework v5.0.20
- Conclusion: don't install laravel/framework v5.0.19
- Conclusion: don't install laravel/framework v5.0.18
- Conclusion: don't install laravel/framework v5.0.17
- Conclusion: don't install laravel/framework v5.0.16
- Conclusion: don't install laravel/framework v5.0.15
- Conclusion: don't install laravel/framework v5.0.14
- Conclusion: don't install laravel/framework v5.0.13
- Conclusion: don't install laravel/framework v5.0.12
- Conclusion: don't install laravel/framework v5.0.11
- Conclusion: don't install laravel/framework v5.0.10
- Conclusion: don't install laravel/framework v5.0.9
- Conclusion: don't install laravel/framework v5.0.8
- Conclusion: don't install laravel/framework v5.0.7
- Conclusion: don't install laravel/framework v5.0.6
- Conclusion: don't install laravel/framework v5.0.5
- Conclusion: don't install laravel/framework v5.0.4
- Conclusion: don't install laravel/framework v5.0.3
- Conclusion: don't install laravel/framework v5.0.2
- Conclusion: don't install laravel/framework v5.0.1
- serverfireteam/blog master requires illuminate/support ~5.1 -> satisfiable by illuminate/support[v5.1.1, v5.1.2, v5.1.6, v5.1.8].
- serverfireteam/blog dev-master requires illuminate/support ~5.1 -> satisfiable by illuminate/support[v5.1.1, v5.1.2, v5.1.6, v5.1.8].
- don't install illuminate/support v5.1.1|don't install laravel/framework v5.0.0
- don't install illuminate/support v5.1.2|don't install laravel/framework v5.0.0
- don't install illuminate/support v5.1.6|don't install laravel/framework v5.0.0
- don't install illuminate/support v5.1.8|don't install laravel/framework v5.0.0
- Installation request for laravel/framework 5.0.* -> satisfiable by laravel/framework[5.0.30, v5.0.0, v5.0.1, v5.0.10, v5.0.11, v5.0.12, v5.0.13, v5.0.14, v5.0.15, v5.0.16, v5.0.17, v5.0.18, v5.0.19, v5.0.2, v5.0.20, v5.0.21, v5.0.22, v5.0.23, v5.0.24, v5.0.25, v5.0.26, v5.0.27, v5.0.28, v5.0.29, v5.0.3, v5.0.31, v5.0.32, v5.0.33, v5.0.4, v5.0.5, v5.0.6, v5.0.7, v5.0.8, v5.0.9].
- Installation request for serverfireteam/blog dev-master -> satisfiable by serverfireteam/blog[master].
[113.9MB/15.48s] Memory usage: 113.9MB (peak: 259.06MB), time: 15.48s
Does anyone know where I've gone wrong?
delete config/excel.php and re-publish it.
php artisan vendor:publish --provider=Maatwebsite\Excel\ExcelServiceProvider
As per your own comment #TimothyBuktu, serverfireteam/blog requires laravel 5.1.
You'll want to lock the version of serverfireteam/blog to dev-master#c0039d3ade67503d674093f3a56d7b1540ae958d in your composer.json, which is the last commit before the requirement of laravel was bumped to 5.1
Alternatively if you still want to receive updates for the package, you'll need to update your application to laravel 5.1. http://laravel.com/docs/5.1/upgrade
mm Xl's answer is excellent!
But after version 3.1 (included), the command is changed to the following one:
php artisan vendor:publish --provider="Maatwebsite\Excel\ExcelServiceProvider" --tag=config
To see this part on docs: https://github.com/Maatwebsite/laravel-excel-docs/blob/develop/3.1/getting-started/installation.md
I recently tried updating my laravel project using composer, using this in the requirements section:
"require": {
"laravel/framework": "4.0.*",
"way/generators": "dev-master",
"taylorotwell/laravel-oauth2": "0.2.*",
"juy/profiler" : "dev-master",
"cviebrock/eloquent-sluggable": "1.0.*"
},
I received the following error:
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
- Conclusion: remove laravel/framework 4.0.x-dev
- Conclusion: don't install laravel/framework 4.0.x-dev
- Conclusion: don't install laravel/framework v4.0.10
- Conclusion: don't install laravel/framework v4.0.9
- Conclusion: don't install laravel/framework v4.0.8
- Conclusion: don't install laravel/framework v4.0.7
- Conclusion: don't install laravel/framework v4.0.6
- Conclusion: don't install laravel/framework v4.0.5
- Conclusion: don't install laravel/framework v4.0.4
- Conclusion: don't install laravel/framework v4.0.3
- Conclusion: don't install laravel/framework v4.0.2
- Conclusion: don't install laravel/framework v4.0.1
- Conclusion: don't install laravel/framework v4.0.0
- Conclusion: don't install laravel/framework v4.0.0-BETA4
- Conclusion: don't install laravel/framework v4.0.0-BETA3
- way/generators dev-master requires illuminate/support ~4.1 -> satisfiable by laravel/framework[4.1.x-dev, 4.2.x-dev], illuminate/support[4.1.x-dev, 4.2.x-dev, v4.1.0, v4.1.1, v4.1.10, v4.1.11, v4.1.12, v4.1.13, v4.1.14, v4.1.15, v4.1.16, v4.1.17, v4.1.18, v4.1.19, v4.1.2, v4.1.20, v4.1.21, v4.1.22, v4.1.23, v4.1.3, v4.1.4, v4.1.5, v4.1.6, v4.1.7, v4.1.8, v4.1.9].
- way/generators dev-master requires illuminate/support ~4.1 -> satisfiable by laravel/framework[4.1.x-dev, 4.2.x-dev], illuminate/support[4.1.x-dev, 4.2.x-dev, v4.1.0, v4.1.1, v4.1.10, v4.1.11, v4.1.12, v4.1.13, v4.1.14, v4.1.15, v4.1.16, v4.1.17, v4.1.18, v4.1.19, v4.1.2, v4.1.20, v4.1.21, v4.1.22, v4.1.23, v4.1.3, v4.1.4, v4.1.5, v4.1.6, v4.1.7, v4.1.8, v4.1.9].
- don't install illuminate/support 4.1.x-dev|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support 4.2.x-dev|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.0|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.1|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.10|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.11|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.12|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.13|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.14|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.15|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.16|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.17|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.18|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.19|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.2|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.20|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.21|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.22|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.23|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.3|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.4|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.5|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.6|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.7|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.8|don't install laravel/framework v4.0.0-BETA2
- don't install illuminate/support v4.1.9|don't install laravel/framework v4.0.0-BETA2
- Can only install one of: laravel/framework[v4.0.0-BETA2, 4.1.x-dev].
- Can only install one of: laravel/framework[v4.0.0-BETA2, 4.2.x-dev].
- Installation request for laravel/framework 4.0.* -> satisfiable by laravel/framework[4.0.x-dev, v4.0.0, v4.0.0-BETA2, v4.0.0-BETA3, v4.0.0-BETA4, v4.0.1, v4.0.10, v4.0.2, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8, v4.0.9].
- Installation request for way/generators dev-master -> satisfiable by way/generators[dev-master].
I've never seen this before. I tried removing the "cviebrock/eloquent-sluggable": "1.0.*" line (because it was recently added), but I am seeing the same error. Any ideas? Thank you.
way/generators dev-master requires illuminate/support ~4.1
There's your conflict, as laravel 4.0.* will install illuminate/support based on which laravel version you use: https://github.com/laravel/framework/blob/master/composer.json#L61
Edit:
I.e. you'll need to downgrade way/generators to 1.1 as laravel 4.0.* is required by taylorotwell/laravel-oauth2.
Don't use dev-master as a version requirement for long-term (or even short-term) development of your own software if you do not follow the development decisions of that library closely.
What probably happened is that way/generators once was compatible with Laravel 4.0 in that dev-master branch, which lead to the release of version 1.1. And then they went on and switched to depending on Laravel 4.1.
Your own software can only see the most current commit in that branch. There is no way Composer can go back in history to earlier states in dev-master, like the last one that defined Laravel 4.0 as dependency. In such a situation, you cannot update with Composer anymore. If you update the whole setup (composer update), things will conflict. If you only update one component (composer update other/library), which itself depends on the NEWER version of way/generators:dev-master, which you didn't install, it will also not work.
Always use tagged versions. To make it easier with updating, don't only use fixed versions like 4.0.7 (although these will be very stable - but you would be unable to update anything), but use these tilde version requirements: ~4.0 is a shortcut for >=4.0,<5.0. This will allow updating to any compatible version in the 4.x branch (provided that the software follows semantic versioning). In particular, it would allow to update to Laravel 4.1. And if you know you need 4.1.0 as the minimum version: ~4.1 is the shortcut for >=4.1,<5.0.
Additionally, there is a nifty piece of software that generates the dependency graph as a picture including the version requirements and resolved versions: https://github.com/clue/graph-composer This really helps understanding what kind of software is required by whom.