Guten Morgen zusammen!
"Frisch ans Werk" dachte ich mir und habe die composer.json zuerst geändert in:
Code:
{
"type": "project",
"require": {
"contao/calendar-bundle": "5.3.*",
"contao/comments-bundle": "5.3.*",
"contao/conflicts": "*@dev",
"contao/faq-bundle": "5.3.*",
"contao/listing-bundle": "5.3.*",
"contao/manager-bundle": "5.3.*",
"contao/news-bundle": "5.3.*",
"contao/newsletter-bundle": "5.3.*"
},
...
und versucht, das Upgrade via CLI anzuschubbsen (Wie gesagt: ich will nur die LTS 5.3, keine 5.4 usw.) :
$ composer update contao/manager-bundle contao/news-bundle contao/calendar-bundle contao/faq-bundle contao/comments-bundle contao/newsletter-bundle contao/listing-bundle contao/conflicts contao/core-bundle contao/installation-bundle --no-install
Das lief relativ schnell auf einen Fehler:
Code:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- contao/calendar-bundle[5.3.0, ..., 5.3.28] require symfony/config ^6.4 -> found symfony/config[v6.4.0, ..., v6.4.14] but the package is fixed to v5.4.46 (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 contao/calendar-bundle 5.3.* -> satisfiable by contao/calendar-bundle[5.3.0, ..., 5.3.28].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Also wohl doch was falsch (verstanden) mit dem Caret?
Nochmal alte Beiträge in diesem Thread gelesen und die composer.json erneut geändert, damit es im gelben Bereich https://github.com/contao/managed-ed...er.json#L6-L15 entspricht. Das geht aber genauso schief:
Code:
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- contao/calendar-bundle[5.3.0, ..., 5.3.28] require symfony/config ^6.4 -> found symfony/config[v6.4.0, ..., v6.4.14] but the package is fixed to v5.4.46 (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.
- contao/calendar-bundle[5.4.0, ..., 5.5.3] require friendsofsymfony/http-cache ^3.0 -> found friendsofsymfony/http-cache[3.0.0, 3.1.0] but the package is fixed to 2.16.2 (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 contao/calendar-bundle ^5.3 -> satisfiable by contao/calendar-bundle[5.3.0, ..., 5.5.3].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Nun traue ich mich nicht, dem "Vorschlag" aus der letzten Zeile Folge leisten, weil da was von downgrades und removals steht...
Ich bin der Meinung, auf Basis von https://docs.contao.org/manual/de/migration/ die Zeilen mit ^ oder * richtig gemacht zu haben:
Code:
{
"type": "project",
"require": {
"contao/calendar-bundle": "^5.3",
"contao/comments-bundle": "^5.3",
"contao/conflicts": "*@dev",
"contao/faq-bundle": "^5.3",
"contao/listing-bundle": "^5.3",
"contao/manager-bundle": "5.3.*",
"contao/news-bundle": "^5.3",
"contao/newsletter-bundle": "^5.3"
},
...
Darf ich "gefahrlos" --with-all-dependencies mit an meine $ composer update ... Zeile anhängen?
Zitieren
Zitat von purzel
