Zitat von
mlweb
Du hast mehrere Probleme.
Zum einen hattest Du für den Testlauf wahrscheinlich nicht alle Pakete zum Update ausgewählt. Das sollte man eigentlich immer machen - es sei denn es gibt einen triftigen Grund der dagegen spricht, ist im Moment aber ganz besonders wichtig, da gerade heute auf composer 2 umgestellt worden ist und damit einmal alle Abhängigkeiten mit composer 2 aufgelöst werden sollten, damit es keine Fehler gibt.
Zum anderen hast Du anscheinend die Erweiterung ausi/contao-slug-backport installiert. Die ist inzwischen im Core von Contao enthalten und damit sollte die Erweiterung beim Update auf Contao 4.9 auch deinstalliert werden.
Danke für die schnelle Rückmeldung!
Ah, stimmt: Ich hatte die Pakete alle bei dem 4.4.55 Update aktiviert. Soll ich ausi/contao-slug-backport vor dem Update einfach rausschmeißen oder danach?
Den zweiten Testlauf mit aktivieren AddOns habe ich auch schon gemacht, aber der ist noch länger :-(
Vielleicht ist es trotzdem besser… was denkst du?
Code:
$ /opt/RZphp73/bin/php-cli -q -dmax_execution_time=0 -dmemory_limit=-1 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=CET /mnt/web507/d3/83/59762583/htdocs/xyz-zxy-de/web/contao-manager.phar.php composer require contao/manager-bundle=4.9.* contao/news-bundle=4.9.* contao/calendar-bundle=4.9.* contao/faq-bundle=4.9.* contao/comments-bundle=4.9.* contao/newsletter-bundle=4.9.* contao/listing-bundle=4.9.* --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction
/mnt/web507/d3/83/59762583/htdocs/xyz-zxy-de/composer.json has been updated
# Process terminated with exit code 0
# Result: OK
> Resolving dependencies using Composer Cloud v3.0.0
!!! Current server is sponsored by: Contao Association !!!
[5.9MiB/0.29s] Loading composer repositories with package information
[55.9MiB/1.97s] Updating dependencies
[1118.1MiB/8.29s] Your requirements could not be resolved to an installable set of packages.
[1118.1MiB/8.29s]
Problem 1
- Conclusion: don't install ausi/contao-slug-backport v1.0.1 (conflict analysis result)
- Conclusion: don't install ausi/contao-slug-backport v1.0.2 (conflict analysis result)
- Conclusion: don't install ausi/contao-slug-backport v1.0.3 (conflict analysis result)
- Conclusion: don't install ausi/contao-slug-backport v1.0.4 (conflict analysis result)
- Conclusion: don't install ausi/contao-slug-backport v1.0.5 (conflict analysis result)
- Conclusion: don't install ausi/contao-slug-backport v1.0.6 (conflict analysis result)
- contao/managed-edition 1.0.0+no-version-set conflicts with contao/core-bundle 4.4.7.
- contao/managed-edition 1.0.0+no-version-set conflicts with contao/core-bundle 4.4.6.
- contao/managed-edition 1.0.0+no-version-set conflicts with contao/core-bundle 4.4.5.
- contao/managed-edition 1.0.0+no-version-set conflicts with contao/core-bundle 4.4.4.
- contao/managed-edition 1.0.0+no-version-set conflicts with contao/core-bundle 4.4.3.
- contao/managed-edition 1.0.0+no-version-set conflicts with contao/core-bundle 4.4.2.
- contao/managed-edition 1.0.0+no-version-set conflicts with contao/core-bundle 4.4.1.
- contao/managed-edition 1.0.0+no-version-set conflicts with contao/core-bundle 4.4.0.
- contao/managed-edition is present at version 1.0.0+no-version-set and cannot be modified by Composer
- contao/newsletter-bundle 4.9.2 requires contao/core-bundle 4.9.2 -> satisfiable by contao/core-bundle[4.9.2].
- Conclusion: don't install contao/core-bundle 4.9.2 (conflict analysis result)
- contao/newsletter-bundle 4.9.3 requires contao/core-bundle 4.9.3 -> satisfiable by contao/core-bundle[4.9.3].
- Conclusion: don't install contao/core-bundle 4.9.3 (conflict analysis result)
- contao/newsletter-bundle 4.9.4 requires contao/core-bundle 4.9.4 -> satisfiable by contao/core-bundle[4.9.4].
- Conclusion: don't install contao/core-bundle 4.9.4 (conflict analysis result)
- contao/newsletter-bundle 4.9.5 requires contao/core-bundle 4.9.5 -> satisfiable by contao/core-bundle[4.9.5].
- Conclusion: don't install contao/core-bundle 4.9.5 (conflict analysis result)
- contao/newsletter-bundle 4.9.6 requires contao/core-bundle 4.9.6 -> satisfiable by contao/core-bundle[4.9.6].
- Conclusion: don't install contao/core-bundle 4.9.6 (conflict analysis result)
- contao/newsletter-bundle 4.9.7 requires contao/core-bundle 4.9.7 -> satisfiable by contao/core-bundle[4.9.7].
- Conclusion: don't install contao/core-bundle 4.9.7 (conflict analysis result)
- contao/newsletter-bundle 4.9.8 requires contao/core-bundle 4.9.8 -> satisfiable by contao/core-bundle[4.9.8].
- Conclusion: don't install contao/core-bundle 4.9.8 (conflict analysis result)
- contao/newsletter-bundle 4.9.9 requires contao/core-bundle 4.9.9 -> satisfiable by contao/core-bundle[4.9.9].
- Conclusion: don't install contao/core-bundle 4.9.9 (conflict analysis result)
- contao/newsletter-bundle 4.9.10 requires contao/core-bundle 4.9.10 -> satisfiable by contao/core-bundle[4.9.10].
- Conclusion: don't install contao/core-bundle 4.9.10 (conflict analysis result)
- contao/newsletter-bundle 4.9.11 requires contao/core-bundle 4.9.11 -> satisfiable by contao/core-bundle[4.9.11].
- Conclusion: don't install contao/core-bundle 4.9.11 (conflict analysis result)
- Root composer.json requires ausi/contao-slug-backport ^1.0 -> satisfiable by ausi/contao-slug-backport[v1.0.0, ..., v1.0.6].
- contao/newsletter-bundle 4.9.1 requires contao/core-bundle 4.9.1 -> satisfiable by contao/core-bundle[4.9.1].
- Conclusion: don't install contao/core-bundle 4.9.1 (conflict analysis result)
- ausi/contao-slug-backport v1.0.0 requires contao/core-bundle 4.4.* -> satisfiable by contao/core-bundle[4.4.0, ..., 4.4.55].
- You can only install one version of a package, so only one of these can be installed: contao/core-bundle[4.3.0, ..., 4.10.6].
- contao/newsletter-bundle 4.9.0 requires contao/core-bundle 4.9.0 -> satisfiable by contao/core-bundle[4.9.0].
- Root composer.json requires contao/newsletter-bundle 4.9.* -> satisfiable by contao/newsletter-bundle[4.9.0, ..., 4.9.11].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
[1118.1MiB/8.29s] Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.
[43.5MiB/9.15s] Memory usage: 43.52MB (peak: 1118.77MB), time: 9.16s.
[43.5MiB/9.15s] Finished Composer Cloud resolving.
# Cloud Job ID LpCk4ANbLbfKZfWphzbFct1aWJdhlzp3pVcgLqCzWBmeuLpGWxTHUAHEMxf8TSGnt06WMl4oubKpLz failed
Lesezeichen