Ergebnis 1 bis 5 von 5

Thema: Update schlägt fehlt

  1. #1
    Contao-Nutzer
    Registriert seit
    04.06.2021.
    Beiträge
    17

    Standard Update schlägt fehlt

    Hallo,

    ich bin aktuell auf Versionen

    Contao 4.9.5
    Contao Manager 1.6.1
    PHP Version 7.4.33 heute aktualisiert auf 8.2

    und wollte das update auf 5.0.8 machen. Nur leider kann ich aus irgendeinen Grund weder updates machen, noch irgend ein Paket entfernen.

    Sobald ich versuche etwas zu aktualisieren, bekomme ich diesen Fehler:

    Code:
    $ /usr/bin/php8.2 -q -dmax_execution_time=0 -dmemory_limit=-1 -ddisplay_errors=0 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /srv/www/ff-mor-homepage/public/ff-mor/web/contao-manager.phar.php composer require contao/manager-bundle=^5.0.8 contao/news-bundle=^5.0.8 contao/calendar-bundle=^5.0.8 contao/faq-bundle=^5.0.8 contao/comments-bundle=^5.0.8 contao/newsletter-bundle=^5.0.8 contao/listing-bundle=^5.0.8 --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction
    
    /srv/www/ff-mor-homepage/public/ff-mor/composer.json has been updated
    
    # Process terminated with exit code 0
    # Result: OK
    
    
    > Resolving dependencies using Composer Cloud v3.5.1
    
    [7.2MiB/0.18s] Loading composer repositories with package information
    [68.9MiB/8.62s] Updating dependencies
    [108.6MiB/9.16s] Your requirements could not be resolved to an installable set of packages.
    [108.6MiB/9.16s] 
      Problem 1
        - Root composer.json requires contao/calendar-bundle ^5.0.8 -> satisfiable by contao/calendar-bundle[5.0.8].
        - contao/calendar-bundle 5.0.8 requires contao/core-bundle 5.0.8 -> found contao/core-bundle[5.0.8] but these were not loaded, likely because it conflicts with another require.
      Problem 2
        - Root composer.json requires contao/comments-bundle ^5.0.8 -> satisfiable by contao/comments-bundle[5.0.8].
        - contao/comments-bundle 5.0.8 requires contao/core-bundle 5.0.8 -> found contao/core-bundle[5.0.8] but these were not loaded, likely because it conflicts with another require.
      Problem 3
        - Root composer.json requires contao/faq-bundle ^5.0.8 -> satisfiable by contao/faq-bundle[5.0.8].
        - contao/faq-bundle 5.0.8 requires contao/core-bundle 5.0.8 -> found contao/core-bundle[5.0.8] but these were not loaded, likely because it conflicts with another require.
      Problem 4
        - Root composer.json requires contao/listing-bundle ^5.0.8 -> satisfiable by contao/listing-bundle[5.0.8].
        - contao/listing-bundle 5.0.8 requires contao/core-bundle 5.0.8 -> found contao/core-bundle[5.0.8] but these were not loaded, likely because it conflicts with another require.
      Problem 5
        - Root composer.json requires contao/manager-bundle ^5.0.8 -> satisfiable by contao/manager-bundle[5.0.8].
        - contao/manager-bundle 5.0.8 requires contao/core-bundle 5.0.8 -> found contao/core-bundle[5.0.8] but these were not loaded, likely because it conflicts with another require.
      Problem 6
        - Root composer.json requires contao/news-bundle ^5.0.8 -> satisfiable by contao/news-bundle[5.0.8].
        - contao/news-bundle 5.0.8 requires contao/core-bundle 5.0.8 -> found contao/core-bundle[5.0.8] but these were not loaded, likely because it conflicts with another require.
      Problem 7
        - Root composer.json requires contao/newsletter-bundle ^5.0.8 -> satisfiable by contao/newsletter-bundle[5.0.8].
        - contao/newsletter-bundle 5.0.8 requires contao/core-bundle 5.0.8 -> found contao/core-bundle[5.0.8] but these were not loaded, likely because it conflicts with another require.
    
    [108.6MiB/9.16s] 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.
    [39.6MiB/9.20s] Memory usage: 39.61MB (peak: 186.57MB), time: 9.21s.
    [39.6MiB/9.20s] Finished Composer Cloud resolving.
    
    
    # Cloud Job ID cVGvbzERkJr1JGaVSYcQJdjgIRUzn6WwAMq2XC82QuS2hpivmocumpm16B5x1TNRXBzvY3oQRDuYubTHBpgZSIXVkWFC7i9YiBb8i0j0DlIB6h3vE0YdJ failed

    Hier steht hinter jedem Problem dieser Satz: but these were not loaded, likely because it conflicts with another require.

    Wie bekomme ich nun heraus, was diese zusätzlichen Anforderungen sind? Das Problem tritt auch auf wenn ich versuche auf 4.13.0 versuche zu aktualisiere.

    Hier noch die aktuelle Version von der composer.json
    Code:
    {
        "type": "project",
        "require": {
            "codefog/contao-cookiebar": "^2.5.1",
            "contao-themes-net/mate-theme-bundle": "2.9",
            "contao/calendar-bundle": "4.9.5",
            "contao/comments-bundle": "4.9.5",
            "contao/conflicts": "*@dev",
            "contao/faq-bundle": "4.9.5",
            "contao/listing-bundle": "4.9.5",
            "contao/manager-bundle": "4.9.5",
            "contao/news-bundle": "4.9.5",
            "contao/newsletter-bundle": "4.9.5",
            "erdmannfreunde/euf_overlay": "^1.3.0",
            "pdir/social-feed-bundle": "^2.8.3",
            "phpoffice/phpspreadsheet": "^1.18",
            "terminal42/contao-leads": "^1.4",
            "terminal42/notification_center": "^1.5"
        },
        "extra": {
            "contao-component-dir": "assets",
            "public-dir": "web"
        },
        "scripts": {
            "post-install-cmd": [
                "@php vendor/bin/contao-setup"
            ],
            "post-update-cmd": [
                "@php vendor/bin/contao-setup"
            ]
        }
    }

  2. #2
    Community-Moderator
    Wandelndes Contao-Lexikon
    Avatar von Spooky
    Registriert seit
    12.04.2012.
    Ort
    Scotland
    Beiträge
    34.195
    Partner-ID
    10107

    Standard

    https://docs.contao.org/manual/de/mi...n/#allgemeines
    Bei einem solchen Update ist generell zu beachten, dass man zuerst immer auf die neueste Version der aktuell verwendeten Major-Version aktualisieren muss, bevor man auf die nächsthöhere Major-Version aktualisiert. Man kann auch keine Major-Versionen überspringen. Befindet man sich z. B. auf Contao 3.2.10 muss man zuerst auf Contao 3.5.40 aktualisieren, bevor man auf Contao 4.13.x aktualisieren kann. Befindet man sich z. B. auf Contao 4.10.2 muss man zuerst auf Contao 4.13.x aktualisieren, bevor man auf Contao 5.x aktualisieren kann, usw. Nur so ist sichergestellt, dass auch alle automatisierten Migrationen die Contao Version korrekt anheben (hauptsächlich die Datenbank betreffend).
    » sponsor me via GitHub or PayPal or Revolut

  3. #3
    Contao-Nutzer
    Registriert seit
    04.06.2021.
    Beiträge
    17

    Standard

    Ja, wie oben geschrieben bekomme ich den selben Fehler wenn ich versuche auf 4.13 zu aktualisieren.

    Code:
    $ /usr/bin/php7.4 -q -dmax_execution_time=0 -dmemory_limit=-1 -ddisplay_errors=0 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /srv/www/ff-mor-homepage/public/ff-mor/web/contao-manager.phar.php composer require contao/manager-bundle=4.13.15 contao/news-bundle=4.13.15 contao/calendar-bundle=4.13.15 contao/faq-bundle=4.13.15 contao/comments-bundle=4.13.15 contao/newsletter-bundle=4.13.15 contao/listing-bundle=4.13.15 --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction
    
    /srv/www/ff-mor-homepage/public/ff-mor/composer.json has been updated
    
    # Process terminated with exit code 0
    # Result: OK
    
    
    > Resolving dependencies using Composer Cloud v3.5.1
    
    [7.2MiB/0.18s] Loading composer repositories with package information
    [68.8MiB/8.02s] Updating dependencies
    [108.1MiB/8.67s] Your requirements could not be resolved to an installable set of packages.
    [108.1MiB/8.67s] 
      Problem 1
        - Root composer.json requires contao/calendar-bundle 4.13.15 -> satisfiable by contao/calendar-bundle[4.13.15].
        - contao/calendar-bundle 4.13.15 requires symfony/config ^5.4 -> found symfony/config[v5.4.0, ..., v5.4.11] but these were not loaded, likely because it conflicts with another require.
      Problem 2
        - Root composer.json requires contao/comments-bundle 4.13.15 -> satisfiable by contao/comments-bundle[4.13.15].
        - contao/comments-bundle 4.13.15 requires symfony/http-kernel ^5.4 -> found symfony/http-kernel[v5.4.0, ..., v5.4.18] but these were not loaded, likely because it conflicts with another require.
      Problem 3
        - Root composer.json requires contao/faq-bundle 4.13.15 -> satisfiable by contao/faq-bundle[4.13.15].
        - contao/faq-bundle 4.13.15 requires symfony/config ^5.4 -> found symfony/config[v5.4.0, ..., v5.4.11] but these were not loaded, likely because it conflicts with another require.
      Problem 4
        - Root composer.json requires contao/listing-bundle 4.13.15 -> satisfiable by contao/listing-bundle[4.13.15].
        - contao/listing-bundle 4.13.15 requires symfony/http-kernel ^5.4 -> found symfony/http-kernel[v5.4.0, ..., v5.4.18] but these were not loaded, likely because it conflicts with another require.
      Problem 5
        - Root composer.json requires contao/manager-bundle 4.13.15 -> satisfiable by contao/manager-bundle[4.13.15].
        - contao/manager-bundle 4.13.15 requires doctrine/dbal ^3.1 -> found doctrine/dbal[3.1.0, ..., 3.5.3] but these were not loaded, likely because it conflicts with another require.
      Problem 6
        - Root composer.json requires contao/news-bundle 4.13.15 -> satisfiable by contao/news-bundle[4.13.15].
        - contao/news-bundle 4.13.15 requires symfony/config ^5.4 -> found symfony/config[v5.4.0, ..., v5.4.11] but these were not loaded, likely because it conflicts with another require.
      Problem 7
        - Root composer.json requires contao/newsletter-bundle 4.13.15 -> satisfiable by contao/newsletter-bundle[4.13.15].
        - contao/newsletter-bundle 4.13.15 requires symfony/http-kernel ^5.4 -> found symfony/http-kernel[v5.4.0, ..., v5.4.18] but these were not loaded, likely because it conflicts with another require.
    
    [108.1MiB/8.67s] 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.
    [39.5MiB/8.72s] Memory usage: 39.52MB (peak: 186.27MB), time: 8.72s.
    [39.5MiB/8.72s] Finished Composer Cloud resolving.
    
    
    # Cloud Job ID 4B7gMpUwZZr563a2j60CJp3U85pGdFUsGcOdCknjTCYG6WXoZwZeFvv6bUuTpNLhzDRM failed

  4. #4
    Community-Moderator
    Wandelndes Contao-Lexikon
    Avatar von Spooky
    Registriert seit
    12.04.2012.
    Ort
    Scotland
    Beiträge
    34.195
    Partner-ID
    10107

    Standard

    Du musst die composer.json manuell auf 4.13.* ändern und dann über die Systemwartung "Composer Update ausführen".
    » sponsor me via GitHub or PayPal or Revolut

  5. #5
    Contao-Nutzer
    Registriert seit
    04.06.2021.
    Beiträge
    17

    Standard

    Alles klar, Danke

Aktive Benutzer

Aktive Benutzer

Aktive Benutzer in diesem Thema: 1 (Registrierte Benutzer: 0, Gäste: 1)

Lesezeichen

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •