search

lochmueller / seocli

SEO CLI Tool
8 stars 2 forks source link

Bump league/uri from ^5.3 to ^6.3 to prevent deprecation notices #4

Closed Patta closed 3 years ago

Patta commented 3 years ago

Please update league/uri from ^5.3 to ^6.3. Version 5.3 requires the no longer maintained package league/uri-schemes ^1.2 which cause deprecation notices with every composer update command.

Class League\Uri\Schemes\AbstractUri located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
Class League\Uri\Schemes\Data located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
Class League\Uri\Schemes\File located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
Class League\Uri\Schemes\Ftp located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
Class League\Uri\Schemes\Http located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
Class League\Uri\Schemes\Uri located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
Class League\Uri\Schemes\UriException located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
Class League\Uri\Schemes\Ws located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
lochmueller commented 3 years ago

Done and publish new release 0.2.0

Patta commented 3 years ago

@lochmueller thanks for the fast update! But now composer fails during update with seocli 0.2.0 due to package conflicts.

Composer 2.0.2 TYPO3 9.5.22 seocli 0.2.0

$ composer update
Gathering patches for root package.
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 removedvendor/removed-sitepackage dev-master -> satisfiable by removedvendor/removed-sitepackage[dev-master].
    - Conclusion: don't install guzzlehttp/guzzle[6.3.2] | install one of guzzlehttp/guzzle[7.0.0, ..., 7.2.0] (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle[6.3.1] | install one of guzzlehttp/guzzle[7.0.0, ..., 7.2.0] (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle[6.3.0] | install one of guzzlehttp/guzzle[7.0.0, ..., 7.2.0] (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle[7.0.1] | install one of guzzlehttp/guzzle[6.4.0, ..., 6.5.4, 7.2.0] (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle[7.0.0] | install one of guzzlehttp/guzzle[6.4.0, ..., 6.5.5, 7.2.0] (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle[6.5.1] | install one of guzzlehttp/guzzle[7.1.0, 7.1.1, 7.2.0] (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle[6.4.0] | install one of guzzlehttp/guzzle[7.1.0, 7.1.1, 7.2.0] (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle[6.4.1] | install one of guzzlehttp/guzzle[7.1.0, 7.1.1, 7.2.0] (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle[7.1.1] | install one of guzzlehttp/guzzle[6.5.2, 6.5.3, 6.5.4, 7.2.0] (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle[6.5.2] | install one of guzzlehttp/guzzle[7.1.0, 7.2.0] (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle[7.1.0] | install one of guzzlehttp/guzzle[6.5.0, 6.5.3, 6.5.4, 6.5.5, 7.2.0] (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle[6.5.4] | install guzzlehttp/guzzle[7.2.0] (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle[6.5.3] | install guzzlehttp/guzzle[7.2.0] (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle 7.2.0 (conflict analysis result)
    - Conclusion: don't install guzzlehttp/guzzle 6.5.5 (conflict analysis result)
    - typo3/cms-core 9.5.x-dev conflicts with guzzlehttp/guzzle 6.5.0.
    - removedvendor/removed-sitepackage dev-master requires typo3/cms-core ^9.5.22 -> satisfiable by typo3/cms-core[v9.5.22, 9.5.x-dev].
    - Conclusion: don't install typo3/cms-core v9.5.22 (conflict analysis result)
    - lochmueller/seocli 0.2.0 requires paquettg/php-html-parser ^3.1 -> satisfiable by paquettg/php-html-parser[3.1.0].
    - removedvendor/removed-sitepackage dev-master requires lochmueller/seocli ^0.2 -> satisfiable by lochmueller/seocli[0.2.0].
    - paquettg/php-html-parser 3.1.0 requires guzzlehttp/guzzle ^7.0 -> satisfiable by guzzlehttp/guzzle[7.0.0-beta.1, ..., 7.2.0].
    - guzzlehttp/guzzle 7.1.x-dev is an alias of guzzlehttp/guzzle dev-master and thus requires it to be installed too.
    - You can only install one version of a package, so only one of these can be installed: guzzlehttp/guzzle[dev-master, 6.3.0, ..., 6.5.x-dev, 7.0.0-beta.1, ..., 7.2.0].
    - typo3/cms-core 9.5.x-dev requires guzzlehttp/guzzle ^6.3.0 -> satisfiable by guzzlehttp/guzzle[6.3.0, ..., 6.5.x-dev].
    - Conclusion: don't install guzzlehttp/guzzle[6.3.3] | install one of guzzlehttp/guzzle[7.0.0, ..., 7.2.0] (conflict analysis result)

(removedvendor/removed-sitepackage is a replacement for the actual sitepackage name)

Removing the composer.lock file did not help.

It seems that paquettg/php-html-parser ^3.1 requires only guzzlehttp/guzzle ^7.0 which is not allowed by typo3 9.5.22. paquettg/php-html-parser ^3.0 could work.