Ergebnis 1 bis 2 von 2

Thema: codefog/contao-news_categories PROBLEM mit Update auf Version 3.5

  1. #1
    Alter Contao-Hase
    Registriert seit
    12.10.2010.
    Beiträge
    1.026

    Standard codefog/contao-news_categories PROBLEM mit Update auf Version 3.5

    Hallo,

    ich führe gerade ein Update durch und die Erweiterung codefog/contao-news_categories macht nicht so richtig mit.


    Code:
    > Resolving dependencies using Composer Cloud v3.6.0-1-g9d9036c
    
    [7.1MiB/0.40s] Loading composer repositories with package information
    [78.1MiB/9.20s] Updating dependencies
    [179.7MiB/9.91s] Your requirements could not be resolved to an installable set of packages.
    [179.7MiB/9.91s] 
      Problem 1
        - Root composer.json requires terminal42/contao-leads ^1.4 -> satisfiable by terminal42/contao-leads[1.4.0, ..., 1.4.33].
        - codefog/contao-news_categories[3.5.0, ..., 3.5.5] require codefog/contao-haste ^5.0 -> satisfiable by codefog/contao-haste[5.0.0, ..., 5.1.9].
        - Conclusion: don't install codefog/contao-haste 5.1.9 (conflict analysis result)
        - Root composer.json requires codefog/contao-news_categories ^3.5 -> satisfiable by codefog/contao-news_categories[3.5.0, ..., 3.5.5].
    
    Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
    [179.7MiB/9.91s] 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.
    [44.6MiB/9.99s] Memory usage: 44.63MB (peak: 204.21MB), time: 9.99s.
    [44.6MiB/9.99s] Finished Composer Cloud resolving.

    Versuche ich dann, Contao Haste zu inastallieren, kommt diese Fehlermeldung:
    Code:
    $ /usr/bin/php -q -dmax_execution_time=0 -dmemory_limit=-1 -ddisplay_errors=0 -ddisplay_startup_errors=0 -derror_reporting=0 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /html/cto/cto_413_23/web/contao-manager.phar.php composer require codefog/contao-haste --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction
    
    Info from https://repo.packagist.org: #StandWithUkraine
    Using version ^5.1 for codefog/contao-haste
    /html/cto/cto_413_23/composer.json has been updated
    
    # Process terminated with exit code 0
    # Result: OK
    
    
    > Resolving dependencies using Composer Cloud v3.6.0-1-g9d9036c
    
    [7.1MiB/0.18s] Loading composer repositories with package information
    [77.4MiB/9.26s] Updating dependencies
    [177.7MiB/10.04s] Your requirements could not be resolved to an installable set of packages.
    [177.7MiB/10.04s] 
      Problem 1
        - terminal42/contao-leads[1.4.0, ..., 1.4.33] require codefog/contao-haste ^4.10.0 -> found codefog/contao-haste[4.10.0, ..., 4.25.25] but it conflicts with your root composer.json require (^5.1).
        - terminal42/contao-leads[1.4.7, ..., 1.4.20] require php ^5.3.2 || ^7.0 -> your php version (8.1.13.0) does not satisfy that requirement.
        - Root composer.json requires terminal42/contao-leads ^1.4 -> satisfiable by terminal42/contao-leads[1.4.0, ..., 1.4.33].
    
    Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
    [177.7MiB/10.04s] 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.
    [44.4MiB/10.11s] Memory usage: 44.4MB (peak: 202.81MB), time: 10.12s.
    [44.4MiB/10.12s] Finished Composer Cloud resolving.
    
    
    # Cloud Job ID YbB4eJhSgzTsEv8EGTRz7fTrIZlbmUb1qxRAtV69YyCNDYUS6do062T9MIUx5adYu9k6KGn3GKxvxn2Ex3q1aFIPdKIAS1yhfsZfCb5PpDrBeCK5Si9m6 failed

    Meine Contao-Version: 4.13.23
    PHP 8.13.13


    composer.json:

    Code:
    {
        "name": "contao/managed-edition",
        "type": "project",
        "description": "Contao Open Source CMS",
        "license": "LGPL-3.0+",
        "authors": [
            {
                "name": "Leo Feyer",
                "homepage": "https://github.com/leofeyer"
            }
        ],
        "require": {
            "php": "^8.1",
            "codefog/contao-cookiebar": "^1.4",
            "codefog/contao-mobile_menu": "^2.7",
            "codefog/contao-news_categories": "^3.5",
            "contao/calendar-bundle": "4.13.*",
            "contao/comments-bundle": "4.13.*",
            "contao/conflicts": "*@dev",
            "contao/faq-bundle": "4.13.*",
            "contao/listing-bundle": "4.13.*",
            "contao/manager-bundle": "4.13.*",
            "contao/news-bundle": "4.13.*",
            "contao/newsletter-bundle": "4.13.*",
            "do-while/contao-backupdb-bundle": "^1.5",
            "jrgregory/m17-sticky-backend-footer": "^2.0",
            "madeyourday/contao-rocksolid-frontend-helper": "^2.2",
            "mathcontao/be_piwikcharts": "^1.8",
            "numero2/contao-marketing-suite": "^1.0",
            "numero2/contao-opengraph3": "^4.2",
            "terminal42/contao-easy_themes": "^2.2",
            "terminal42/contao-leads": "^1.4",
            "terminal42/contao-rte_table": "^1.0",
            "terminal42/notification_center": "^1.6"
        },
    	"extra": {
            "contao-component-dir": "assets",
    		"symfony": {
    			"require": "^4.2"
    		}
        },
        "conflict": {
            "contao/core-bundle": "<4.4.1"
        },
        "config": {
            "component-dir": "assets"
        },
        "scripts": {
            "post-install-cmd": [
                "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
            ],
            "post-update-cmd": [
                "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
            ]
        }
    }
    Hat jemand eine Idee, was da genau falsch läuft bzw. was wo wie eingestellt werden muß?

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

    Standard

    Du musst wenn dann eine vollständige Paketaktualisierung durchführen. Es kann aber sein, dass du nicht auf die neueste Version aktualisieren kannst, aufgrund deiner anderen Abhängigkeiten.
    » sponsor me via GitHub or PayPal or Revolut

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
  •