Ergebnis 1 bis 11 von 11

Thema: Während Paketinstallation Composer-Fehler

  1. #1
    Contao-Nutzer
    Registriert seit
    13.02.2012.
    Beiträge
    26

    Trauriges Gesicht Während Paketinstallation Composer-Fehler

    Hallo zusammen,

    während einer Paketinstallation bricht der Task im Contao-Manager mit einem roten X bei Composer install ab.

    Hier die Log-Datei:

    Code:
    $ /opt/RZphp74/bin/php-cli -q -dmax_execution_time=0 -dmemory_limit=-1 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=CET /mnt/web519/c0/33/5540233/htdocs/c4/web/contao-manager.phar.php composer install --prefer-dist --no-dev --no-progress --no-ansi --no-interaction --optimize-autoloader
    Installing dependencies from lock file
    Verifying lock file contents can be installed on current platform.
    Nothing to install, update or remove
    Package contao-components/compass is abandoned, you should avoid using it. No replacement was suggested.
    Package crossjoin/browscap is abandoned, you should avoid using it. No replacement was suggested.
    Package doctrine/doctrine-cache-bundle is abandoned, you should avoid using it. No replacement was suggested.
    Package doctrine/reflection is abandoned, you should avoid using it. Use roave/better-reflection instead.
    Package kmielke/calendar_extended is abandoned, you should avoid using it. No replacement was suggested.
    Package leafo/scssphp is abandoned, you should avoid using it. Use scssphp/scssphp instead.
    Package league/uri-hostname-parser is abandoned, you should avoid using it. No replacement was suggested.
    Package league/uri-manipulations is abandoned, you should avoid using it. No replacement was suggested.
    Package league/uri-schemes is abandoned, you should avoid using it. No replacement was suggested.
    Package menatwork/contao-multicolumnwizard is abandoned, you should avoid using it. Use menatwork/contao-multicolumnwizard-bundle instead.
    Package oyejorge/less.php is abandoned, you should avoid using it. No replacement was suggested.
    Package patchwork/utf8 is abandoned, you should avoid using it. Use symfony/polyfill-mbstring or symfony/string instead.
    Package phpunit/php-token-stream is abandoned, you should avoid using it. No replacement was suggested.
    Package symfony/inflector is abandoned, you should avoid using it. Use use `EnglishInflector` from the String component instead instead.
    Generating optimized autoload files
    Class Sensio\Bundle\FrameworkExtraBundle\Tests\DependencyInjection\AddExpressionLanguageProvidersPassTest located in ./vendor/sensio/framework-extra-bundle/Tests/DependencyInjection/Compiler/AddExpressionLanguageProvidersPassTest.php does not comply with psr-4 autoloading standard. Skipping.
    Class Sensio\Bundle\FrameworkExtraBundle\Tests\DependencyInjection\AddParamConverterPassTest located in ./vendor/sensio/framework-extra-bundle/Tests/DependencyInjection/Compiler/AddParamConverterPassTest.php does not comply with psr-4 autoloading standard. Skipping.
    Class Sensio\Bundle\FrameworkExtraBundle\Tests\Request\ParamConverter\ArgumentNameConverterTest located in ./vendor/sensio/framework-extra-bundle/Tests/Request/ArgumentNameConverterTest.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\AbstractUri located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\Data located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\File located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\Ftp located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\Http located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\Uri located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\UriException located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    Class League\Uri\Schemes\Ws located in ./vendor/league/uri-schemes/src/Schemes/deprecated.php does not comply with psr-4 autoloading standard. Skipping.
    composer/package-versions-deprecated: Generating version class...
    composer/package-versions-deprecated: ...done generating version class
    66 packages you are using are looking for funding.
    Use the `composer fund` command to find out more!
    contao/manager-plugin: Generating plugin class...
    contao/manager-plugin: ...done generating plugin class
    > Contao\ManagerBundle\Composer\ScriptHandler::initializeApplication
    PHP Fatal error:  Could not check compatibility between Symfony\Bridge\ProxyManager\LazyProxy\PhpDumper\LazyLoadingValueHolderGenerator::generate(ReflectionClass $originalClass, Zend\Code\Generator\ClassGenerator $classGenerator) and ProxyManager\ProxyGenerator\LazyLoadingValueHolderGenerator::generate(ReflectionClass $originalClass, Laminas\Code\Generator\ClassGenerator $classGenerator), because class Zend\Code\Generator\ClassGenerator is not available in /mnt/web519/c0/33/5540233/htdocs/c4/vendor/symfony/proxy-manager-bridge/LazyProxy/PhpDumper/LazyLoadingValueHolderGenerator.php on line 25
    Script Contao\ManagerBundle\Composer\ScriptHandler::initializeApplication handling the post-install-cmd event terminated with an exception
    In ScriptHandler.php line 87:
                                                                                   
      An error occurred while executing the "contao:install-web-dir" command: PHP  
       Fatal error:  Could not check compatibility between Symfony\Bridge\ProxyMa  
      nager\LazyProxy\PhpDumper\LazyLoadingValueHolderGenerator::generate(Reflect  
      ionClass $originalClass, Zend\Code\Generator\ClassGenerator $classGenerator  
      ) and ProxyManager\ProxyGenerator\LazyLoadingValueHolderGenerator::generate  
      (ReflectionClass $originalClass, Laminas\Code\Generator\ClassGenerator $cla  
      ssGenerator), because class Zend\Code\Generator\ClassGenerator is not avail  
      able in /mnt/web519/c0/33/5540233/htdocs/c4/vendor/symfony/proxy-manager-br  
      idge/LazyProxy/PhpDumper/LazyLoadingValueHolderGenerator.php on line 25      
                                                                                   
    install [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--dry-run] [--dev] [--no-suggest] [--no-dev] [--no-autoloader] [--no-scripts] [--no-progress] [--no-install] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--] [<packages>...]
    # Process terminated with exit code 1
    # Result: General error
    Ich weiß ihr leider nicht mehr weiter.
    Contao-Version: 4.7

    Gruß Böhmi

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

    Standard

    Zitat Zitat von boehmi89 Beitrag anzeigen
    Contao-Version: 4.7
    Diese Contao Version hat schon lange das Lebensende erreicht. Du musst auf Contao 4.9 oder 4.12 aktualisieren.
    » sponsor me via GitHub or PayPal or Revolut

  3. #3
    Contao-Nutzer
    Registriert seit
    13.02.2012.
    Beiträge
    26

    Standard

    Hallo Spooky,

    beim Versuch auf Version 4.9 über den Contao Manager im abgesicherten Modus upzudaten kommt folgende Fehlermeldung:

    Ein Hintergrund-Prozess wurde unerwartet beendet. Bitte prüfe die Konsolen-Ausgabe.

    Code:
    > Resolving dependencies using Composer Cloud v3.2.0
    !!! Current server is sponsored by: Contao Association !!!
    [6.0MiB/0.17s] Loading composer repositories with package information
    [64.9MiB/1.55s] Updating dependencies
    [1520.2MiB/9.25s] Your requirements could not be resolved to an installable set of packages.
    [1520.2MiB/9.25s] 
      Problem 1
        - bugbuster/contao-dlstats-bundle is locked to version 1.0.4 and an update of this package was not requested.
        - 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)
        - contao/newsletter-bundle 4.9.12 requires contao/core-bundle 4.9.12 -> satisfiable by contao/core-bundle[4.9.12].
        - Conclusion: don't install contao/core-bundle 4.9.12 (conflict analysis result)
        - contao/newsletter-bundle 4.9.13 requires contao/core-bundle 4.9.13 -> satisfiable by contao/core-bundle[4.9.13].
        - Conclusion: don't install contao/core-bundle 4.9.13 (conflict analysis result)
        - contao/newsletter-bundle 4.9.14 requires contao/core-bundle 4.9.14 -> satisfiable by contao/core-bundle[4.9.14].
        - Conclusion: don't install contao/core-bundle 4.9.14 (conflict analysis result)
        - contao/newsletter-bundle 4.9.15 requires contao/core-bundle 4.9.15 -> satisfiable by contao/core-bundle[4.9.15].
        - Conclusion: don't install contao/core-bundle 4.9.15 (conflict analysis result)
        - contao/newsletter-bundle 4.9.16 requires contao/core-bundle 4.9.16 -> satisfiable by contao/core-bundle[4.9.16].
        - Conclusion: don't install contao/core-bundle 4.9.16 (conflict analysis result)
        - contao/newsletter-bundle 4.9.17 requires contao/core-bundle 4.9.17 -> satisfiable by contao/core-bundle[4.9.17].
        - Conclusion: don't install contao/core-bundle 4.9.17 (conflict analysis result)
        - contao/newsletter-bundle 4.9.18 requires contao/core-bundle 4.9.18 -> satisfiable by contao/core-bundle[4.9.18].
        - Conclusion: don't install contao/core-bundle 4.9.18 (conflict analysis result)
        - contao/newsletter-bundle 4.9.19 requires contao/core-bundle 4.9.19 -> satisfiable by contao/core-bundle[4.9.19].
        - Conclusion: don't install contao/core-bundle 4.9.19 (conflict analysis result)
        - contao/newsletter-bundle 4.9.20 requires contao/core-bundle 4.9.20 -> satisfiable by contao/core-bundle[4.9.20].
        - Conclusion: don't install contao/core-bundle 4.9.20 (conflict analysis result)
        - bugbuster/contao-dlstats-bundle 1.0.4 requires bugbuster/contao-botdetection-bundle >=0.2.1,<2 -> satisfiable by bugbuster/contao-botdetection-bundle[1.5.0].
        - 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)
        - bugbuster/contao-botdetection-bundle 1.5.0 requires contao/core-bundle >=4.6,<4.9 -> satisfiable by contao/core-bundle[4.6.0, ..., 4.8.8].
        - Only one of these can be installed: contao/core[2.10.0, ..., 2.11.17, 3.0.0, ..., 3.5.40], contao/core-bundle[4.1.0, ..., 4.12.1]. contao/core replaces contao/core-bundle and thus cannot coexist with it.
        - 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.20].
    [1520.2MiB/9.25s] <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>
    [77.1MiB/10.53s] Memory usage: 77.12MB (peak: 1520.92MB), time: 10.54s.
    [77.1MiB/10.53s] Finished Composer Cloud resolving.
    # Cloud Job ID HczYpEAzUJHfZS4fzMBECJsfNBPqh0lHLGc9xIK7T5GE9h8wbZK1cAPbZspDGM1xw6HyEN2YV6LJicMqoW6hnjvZguuJDofcT2JOO6pxQyS6jwCT failed
    Was ist jetzt das Problem?

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

    Standard

    Poste deine composer.json.
    » sponsor me via GitHub or PayPal or Revolut

  5. #5
    Contao-Nutzer
    Registriert seit
    13.02.2012.
    Beiträge
    26

    Standard

    Hier meine Composer.json:

    Code:
    {
        "type": "project",
        "require": {
            "bugbuster/contao-dlstats-bundle": "^1.0",
            "bugbuster/contao-visitors-bundle": "^1.5",
            "contao/calendar-bundle": "^4.6",
            "contao/comments-bundle": "^4.6",
            "contao/faq-bundle": "^4.6",
            "contao/listing-bundle": "^4.6",
            "contao/manager-bundle": "4.6.*",
            "contao/news-bundle": "^4.6",
            "contao/newsletter-bundle": "^4.6",
            "kmielke/calendar_extended": "^3.7"
        },
        "extra": {
            "contao-component-dir": "assets"
        },
        "scripts": {
            "post-install-cmd": [
                "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
            ],
            "post-update-cmd": [
                "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
            ]
        }
    }
    Geändert von Spooky (28.08.2021 um 11:19 Uhr) Grund: added [code] tags

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

    Standard

    Laut dieser composer.json hast du aber noch Contao 4.6 installiert, nicht 4.7?
    » sponsor me via GitHub or PayPal or Revolut

  7. #7
    Contao-Nutzer
    Registriert seit
    13.02.2012.
    Beiträge
    26

    Standard

    Im Backend wurde mir 4.7 angezeigt ?!

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

    Standard

    Ändere deine composer.json manuell auf
    Code:
    {
        "type": "project",
        "require": {
            "bugbuster/contao-dlstats-bundle": "^1.0",
            "bugbuster/contao-visitors-bundle": "^1.5",
            "contao/calendar-bundle": "^4.9",
            "contao/comments-bundle": "^4.9",
            "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",
            "kmielke/calendar_extended": "^3.7"
        },
        "extra": {
            "contao-component-dir": "assets"
        },
        "scripts": {
            "post-install-cmd": [
                "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
            ],
            "post-update-cmd": [
                "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
            ]
        }
    }
    Gehe dann in die Systemwartung des Contao Managers und klicke auf "Composer Update ausführen" (siehe den Screenshot hier).
    » sponsor me via GitHub or PayPal or Revolut

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

    Standard

    Statt kmielke/calendar_extended solltest du aber kmielke/calendar-extended-bundle einsetzen.
    » sponsor me via GitHub or PayPal or Revolut

  10. #10
    Contao-Nutzer
    Registriert seit
    13.02.2012.
    Beiträge
    26

    Standard

    Hallo Spooky,

    danke erstmal für die Hilfe. Die Seite läuft wieder.

    Sobald ich aber die Erweiterung "kmielke/calendar-extended-bundle" wieder installieren möchte, kommt im Backend, sowie Frontend nur noch eine weiße Seite.
    Liegt dass dann an der Erweiterung?

    Gruß Böhmi89

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

    Standard

    Welcher Fehler dann vorliegt, musst du mit Error Logs prüfen.
    » 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
  •