Danke Spooky für die rasche Antwort. Das habe ich bereits versucht (war mal dein Lösungsvorschlag bei einem ähnlichen Problem in einem anderen Thread), führt aber zum selben Output:
Code:
composer update trilobit-gmbh/contao-cookiebar-bundle terminal42/notification_center richardhj/isotope-klarna-checkout numero2/contao-marketing-suite mpdf/mpdf madeyourday/contao-rocksolid-slider isotope/isotope_documents isotope/isotope-core inszenium/isotope-export heimrichhannot/contao-email2username-bundle dklemmt/contao_dk_mmenu delahaye/dlh_googlemaps cliffparnitzky/tiny-mce-advanced-list christianbarkowsky/contao-tiny-compress-images chillerlan/php-qrcode contao/manager-bundle contao/news-bundle contao/calendar-bundle contao/faq-bundle contao/comments-bundle contao/newsletter-bundle contao/listing-bundle contao/conflicts
> Resolving dependencies using Composer Cloud v3.2.0
!!! Current server is sponsored by: Contao Association !!!
[7.4MiB/0.20s] Loading composer repositories with package information
[75.4MiB/2.90s] Updating dependencies
[1801.0MiB/19.03s] Your requirements could not be resolved to an installable set of packages.
[1801.0MiB/19.04s]
Problem 1
- Root composer.json requires contao/manager-bundle 4.13.* -> satisfiable by contao/manager-bundle[4.13.0-RC1].
- Root composer.json requires richardhj/isotope-klarna-checkout ^2.0 -> satisfiable by richardhj/isotope-klarna-checkout[v2.0.0, ..., v2.0.4].
- Conclusion: don't install contao/conflicts 9999999-dev (conflict analysis result)
- Root composer.json requires contao/conflicts *@dev -> satisfiable by contao/conflicts[dev-main].
[1801.0MiB/19.04s] <warning>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.</warning>
[79.4MiB/21.35s] Memory usage: 79.4MB (peak: 1805.55MB), time: 21.36s.
[79.4MiB/21.35s] Finished Composer Cloud resolving.
# Cloud Job ID MgnbI9p43SKmwCKGotJtCog35VeKRqAkNOCUQ9EvJxbeZ58uZviHfrhnFuy6XpGGSPVdflVcAw1fQJirTWJqtNHpvvalVmPW9C9v3T6cf0S5WarMzDahTO6PrpyGO failed
Gibt's eine Möglichkeit herauszufinden, welches Package die Probleme verursacht?
Lesezeichen