Problem Update 4.9.42 auf 4.13

[pinda]

Hallo zusammen,

mein update von Contao 4.9.42 auf 4.13 schlägt leider fehl.
Die verwendete php-Version ist 7.4.33.

Hat jemand einen Tipp für mich?
1.000 Dank im voraus!

Folgende Meldung wird angezeigt

> Resolving dependencies using Composer Cloud v3.7.0
[6.8MiB/0.24s] Loading composer repositories with package information
[96.6MiB/15.97s] Updating dependencies
[218.6MiB/17.55s] Your requirements could not be resolved to an installable set of packages.
[218.6MiB/17.55s] 
  Problem 1
    - contao/newsletter-bundle 4.13.37 requires contao/core-bundle 4.13.37 -> satisfiable by contao/core-bundle[4.13.37].
    - contao/newsletter-bundle 4.13.36 requires contao/core-bundle 4.13.36 -> satisfiable by contao/core-bundle[4.13.36].
    - contao/newsletter-bundle 4.13.35 requires contao/core-bundle 4.13.35 -> satisfiable by contao/core-bundle[4.13.35].
    - contao/newsletter-bundle 4.13.34 requires contao/core-bundle 4.13.34 -> satisfiable by contao/core-bundle[4.13.34].
    - contao/newsletter-bundle 4.13.33 requires contao/core-bundle 4.13.33 -> satisfiable by contao/core-bundle[4.13.33].
    - contao/newsletter-bundle 4.13.32 requires contao/core-bundle 4.13.32 -> satisfiable by contao/core-bundle[4.13.32].
    - contao/newsletter-bundle 4.13.31 requires contao/core-bundle 4.13.31 -> satisfiable by contao/core-bundle[4.13.31].
    - contao/newsletter-bundle 4.13.30 requires contao/core-bundle 4.13.30 -> satisfiable by contao/core-bundle[4.13.30].
    - contao/newsletter-bundle 4.13.29 requires contao/core-bundle 4.13.29 -> satisfiable by contao/core-bundle[4.13.29].
    - contao/newsletter-bundle 4.13.28 requires contao/core-bundle 4.13.28 -> satisfiable by contao/core-bundle[4.13.28].
    - contao/newsletter-bundle 4.13.27 requires contao/core-bundle 4.13.27 -> satisfiable by contao/core-bundle[4.13.27].
    - contao/newsletter-bundle 4.13.26 requires contao/core-bundle 4.13.26 -> satisfiable by contao/core-bundle[4.13.26].
    - contao/newsletter-bundle 4.13.25 requires contao/core-bundle 4.13.25 -> satisfiable by contao/core-bundle[4.13.25].
    - contao/newsletter-bundle 4.13.24 requires contao/core-bundle 4.13.24 -> satisfiable by contao/core-bundle[4.13.24].
    - contao/newsletter-bundle 4.13.23 requires contao/core-bundle 4.13.23 -> satisfiable by contao/core-bundle[4.13.23].
    - contao/newsletter-bundle 4.13.22 requires contao/core-bundle 4.13.22 -> satisfiable by contao/core-bundle[4.13.22].
    - contao/newsletter-bundle 4.13.21 requires contao/core-bundle 4.13.21 -> satisfiable by contao/core-bundle[4.13.21].
    - contao/newsletter-bundle 4.13.20 requires contao/core-bundle 4.13.20 -> satisfiable by contao/core-bundle[4.13.20].
    - contao/newsletter-bundle 4.13.19 requires contao/core-bundle 4.13.19 -> satisfiable by contao/core-bundle[4.13.19].
    - contao/newsletter-bundle 4.13.18 requires contao/core-bundle 4.13.18 -> satisfiable by contao/core-bundle[4.13.18].
    - contao/newsletter-bundle 4.13.17 requires contao/core-bundle 4.13.17 -> satisfiable by contao/core-bundle[4.13.17].
    - contao/newsletter-bundle 4.13.16 requires contao/core-bundle 4.13.16 -> satisfiable by contao/core-bundle[4.13.16].
    - contao/newsletter-bundle 4.13.15 requires contao/core-bundle 4.13.15 -> satisfiable by contao/core-bundle[4.13.15].
    - contao/newsletter-bundle 4.13.14 requires contao/core-bundle 4.13.14 -> satisfiable by contao/core-bundle[4.13.14].
    - contao/newsletter-bundle 4.13.13 requires contao/core-bundle 4.13.13 -> satisfiable by contao/core-bundle[4.13.13].
    - contao/newsletter-bundle 4.13.12 requires contao/core-bundle 4.13.12 -> satisfiable by contao/core-bundle[4.13.12].
    - contao/newsletter-bundle 4.13.11 requires contao/core-bundle 4.13.11 -> satisfiable by contao/core-bundle[4.13.11].
    - contao/newsletter-bundle 4.13.10 requires contao/core-bundle 4.13.10 -> satisfiable by contao/core-bundle[4.13.10].
    - contao/newsletter-bundle 4.13.9 requires contao/core-bundle 4.13.9 -> satisfiable by contao/core-bundle[4.13.9].
    - contao/newsletter-bundle 4.13.8 requires contao/core-bundle 4.13.8 -> satisfiable by contao/core-bundle[4.13.8].
    - contao/newsletter-bundle 4.13.7 requires contao/core-bundle 4.13.7 -> satisfiable by contao/core-bundle[4.13.7].
    - contao/newsletter-bundle 4.13.6 requires contao/core-bundle 4.13.6 -> satisfiable by contao/core-bundle[4.13.6].
    - contao/newsletter-bundle 4.13.5 requires contao/core-bundle 4.13.5 -> satisfiable by contao/core-bundle[4.13.5].
    - contao/newsletter-bundle 4.13.4 requires contao/core-bundle 4.13.4 -> satisfiable by contao/core-bundle[4.13.4].
    - contao/newsletter-bundle 4.13.3 requires contao/core-bundle 4.13.3 -> satisfiable by contao/core-bundle[4.13.3].
    - contao/newsletter-bundle 4.13.2 requires contao/core-bundle 4.13.2 -> satisfiable by contao/core-bundle[4.13.2].
    - contao/newsletter-bundle 4.13.1 requires contao/core-bundle 4.13.1 -> satisfiable by contao/core-bundle[4.13.1].
    - contao/newsletter-bundle 4.13.0 requires contao/core-bundle 4.13.0 -> satisfiable by contao/core-bundle[4.13.0].
    - contao/core-bundle[4.13.0, ..., 4.13.37] require monolog/monolog ^2.0 -> satisfiable by monolog/monolog[2.0.0, ..., 2.9.2].
    - __root__ 1.0.0+no-version-set conflicts with monolog/monolog 2.9.2.
    - __root__ 1.0.0+no-version-set conflicts with monolog/monolog 2.3.3.
    - __root__ 1.0.0+no-version-set conflicts with monolog/monolog 2.3.2.
    - __root__ 1.0.0+no-version-set conflicts with monolog/monolog 2.0.2.
    - __root__ is present at version 1.0.0+no-version-set and cannot be modified by Composer
    - Root composer.json requires contao/newsletter-bundle 4.13.* -> satisfiable by contao/newsletter-bundle[4.13.0, ..., 4.13.37].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
[218.6MiB/17.55s] <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>
[59.7MiB/17.68s] Memory usage: 59.7MB (peak: 232.27MB), time: 17.69s.
[59.7MiB/17.68s] Finished Composer Cloud resolving.

Meine composer.json sieht folgendermaßen aus

{
    "type": "project",
    "require": {
        "contao/calendar-bundle": "4.9.*",
        "contao/comments-bundle": "4.9.*",
        "contao/conflicts": "*@dev",
        "contao/faq-bundle": "4.9.*",
        "contao/listing-bundle": "4.9.*",
        "contao/manager-bundle": "4.9.*",
        "contao/news-bundle": "4.9.*",
        "contao/newsletter-bundle": "4.9.*",
        "madeyourday/contao-rocksolid-columns": "^2.0",
        "madeyourday/contao-rocksolid-custom-elements": "2.2.*",
        "terminal42/contao-changelanguage": "^3.1",
        "terminal42/notification_center": "^1.5"
    },
    "conflict": {
        "doctrine/dbal": "2.9.* <2.9.3",
        "doctrine/doctrine-migrations-bundle": "<1.1",
        "doctrine/orm": "<2.4",
        "knplabs/knp-time-bundle": "1.9.0",
        "lexik/maintenance-bundle": "2.1.4",
        "monolog/monolog": ">=2",
        "symfony/finder": "3.4.7 || 4.0.7",
        "symfony/framework-bundle": "4.2.7",
        "symfony/security": "3.3.17 || 3.4.7 || 3.4.8 || 3.4.11",
        "symfony/swiftmailer-bundle": "2.6.* <2.6.2",
        "symfony/twig-bundle": "4.1.0",
        "twig/twig": "2.7.0"
    },
    "scripts": {
        "post-install-cmd": [
            "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
        ],
        "post-update-cmd": [
            "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
        ]
    }
}

1.000 Dank im voraus für Eure Hilfe!

[Spooky]

Die Contao Versionen musst du alle auf 4.13.* ändern. Die Version von den Custom Elements musst du von 2.2.* auf ^2.2 ändern.

Und den "monolog/monolog": ">=2" Conflict musst du auch entfernen. Warum hast du den drin?

[pinda]

Hallo Spooky,

Und den "monolog/monolog": ">=2" Conflict musst du auch entfernen. Warum hast du den drin?

Ich habe die Installation von einem anderen Dienstleister übernommen …
Ich habe keine Ahnung warum monolog verwendet wurde.

Danke!

[Spooky]

Ich habe keine Ahnung warum monolog verwendet wurde.

monolog wird nicht "verwendet" in dem Sinn, sondern es wurde ein Conflict eingetragen. Also da müsstest du schon nachfragen oder die Code-Basis prüfen.

[pinda]

Hallo Spooky,

ich hatte direkt nach Deiner ersten Antwort "monolog/monolog": ">=2" Conflict entfernt und mit dem Update begonnen.

Dann erst sah ich Deine zweite Antwort.

Das Update hat reibungslos funktioniert.

Die Website arbeitet, soweit ich sehe, fehlerfrei.

Gibt es evtl. bestimmte Punkte, die ich speziell prüfen sollte, die mit monolog zu tun haben?

Besten Dank für Deine Antwort!