Contao-Camp 2024
Ergebnis 1 bis 6 von 6

Thema: Schaffe es nicht BackupDB lokal zu installieren

  1. #1
    Contao-Fan
    Registriert seit
    08.03.2010.
    Beiträge
    451

    Frage Schaffe es nicht BackupDB lokal zu installieren

    hallo,
    ich versuche gerade die BackupDB extension bei mir lokal zu installieren. Auf dem Live Server habe ich es problemlos installieren können, nur lokal will es mir nicht gelingen.

    ich bekomme folgende meldung:

    Code:
    $ /Applications/MAMP/bin/php/php7.4.20/bin/php -q -dmax_execution_time=0 -dmemory_limit=-1 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /Users/atomie/Sites/localhost/Manual/web/contao-manager.phar.php composer require do-while/contao-backupdb-bundle --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction
    
    Using config.component-dir has been deprecated. Please use extra.contao-component-dir instead.
    Using version ^1.4 for do-while/contao-backupdb-bundle
    /Users/atomie/Sites/localhost/Manual/composer.json has been updated
    
    # Process terminated with exit code 0
    # Result: OK
    
    
    > Resolving dependencies using Composer Cloud v3.2.0
    !!! Current server is sponsored by: Contao Association !!!
    
    
    [6.6MiB/0.19s] Loading composer repositories with package information
    [57.0MiB/1.74s] Updating dependencies
    [1432.2MiB/21.76s] Your requirements could not be resolved to an installable set of packages.
    [1432.2MiB/21.77s] 
      Problem 1
        - Root composer.json requires do-while/contao-backupdb-bundle ^1.4 -> satisfiable by do-while/contao-backupdb-bundle[1.4.0, 1.4.1, 1.4.2].
        - Conclusion: don't install symfony/http-kernel v5.2.2 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.2.3 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.2.4 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.2.5 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.2.6 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.10] | install one of symfony/framework-bundle[v4.4.24, v4.4.25, v4.4.26, v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.9] | install one of symfony/framework-bundle[v4.4.22, ..., v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.8] | install one of symfony/framework-bundle[v4.4.21, ..., v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.7] | install one of symfony/framework-bundle[v4.4.21, ..., v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v4.4.21] | install one of symfony/framework-bundle[v5.1.10, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v4.4.22] | install one of symfony/framework-bundle[v5.1.10, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v4.4.24] | install one of symfony/framework-bundle[v5.1.10, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.11] | install one of symfony/framework-bundle[v4.4.25, v4.4.26, v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.12] | install one of symfony/framework-bundle[v4.4.25, v4.4.26, v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.13] | install one of symfony/framework-bundle[v4.4.26, v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v5.1.10] | install one of symfony/framework-bundle[v4.4.25, v4.4.26, v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v5.1.11] | install one of symfony/framework-bundle[v4.4.25, v4.4.26, v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.14] | install one of symfony/framework-bundle[v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v4.4.27] | install one of symfony/framework-bundle[v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v4.4.26] | install one of symfony/framework-bundle[v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v4.4.25] | install one of symfony/framework-bundle[v5.2.0, ..., v5.2.12] (conflict analysis result)
        - symfony/framework-bundle[v5.2.0, ..., v5.2.12] require symfony/routing ^5.2 -> satisfiable by symfony/routing[v5.2.0, ..., v5.3.4].
        - Conclusion: don't install symfony/routing v5.2.0 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.1 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.2 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.3 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.4 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.6 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.7 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.9 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.10 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.12 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.3.0 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.3.0 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.3.1 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.3.2 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.3.3 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.3.4 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.3.4 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.3.5 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.3.6 (conflict analysis result)
        - contao/manager-bundle 4.11.6 requires contao/installation-bundle 4.11.6 -> satisfiable by contao/installation-bundle[4.11.6].
        - contao/manager-bundle 4.11.6 requires symfony/web-profiler-bundle 4.4.* || 5.2.* -> satisfiable by symfony/web-profiler-bundle[v5.2.13].
        - contao/manager-bundle is locked to version 4.11.6 and an update of this package was not requested.
        - contao/installation-bundle 4.11.6 requires symfony/framework-bundle 4.4.* || 5.2.* -> satisfiable by symfony/framework-bundle[v4.4.0, ..., v4.4.27, v5.2.0, ..., v5.2.12].
        - symfony/framework-bundle[v4.4.0, ..., v4.4.20] require symfony/http-kernel ^4.4 -> satisfiable by symfony/http-kernel[v4.4.0, ..., v4.4.29].
        - You can only install one version of a package, so only one of these can be installed: symfony/http-kernel[v2.1.0, ..., v2.8.52, v3.0.0, ..., v3.4.49, v4.0.0, ..., v4.4.29, v5.0.0, ..., v5.3.6].
        - symfony/web-profiler-bundle v5.2.13 requires symfony/http-kernel ^5.2 -> satisfiable by symfony/http-kernel[v5.2.0, ..., v5.3.6].
        - Conclusion: don't install symfony/http-kernel v5.2.1 (conflict analysis result)
    
    [1432.2MiB/21.77s] 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.
    [76.4MiB/23.23s] Memory usage: 76.42MB (peak: 1434.09MB), time: 23.23s.
    [76.4MiB/23.23s] Finished Composer Cloud resolving.
    
    
    # Cloud Job ID juNYmr7DM6AlifPUEo3DFkEgEaZDg9DVS0pZgHf3Wkhyja8XbcsoiKsQfYTjiFI50Bf2YEgL9NrsKDervlPRAfsxNJ2wQwMVcB3YpviNl8wEIoAjAeKzD7GqItos3 failed
    Im Bereich Maintance habe ich, glaube ich, jeden Button gedrückt den es dort gibt. Geholfen hat es aber leider nicht.

    Danke schonmal!

  2. #2
    Contao-Urgestein Avatar von do_while
    Registriert seit
    15.06.2009.
    Ort
    Berlin | Deutschland
    Beiträge
    3.612
    Partner-ID
    1081
    User beschenken
    Wunschliste
    Contao-Projekt unterstützen

    Support Contao

    Standard

    Du musst eine komplette Paketaktualisierung machen.

  3. #3
    Contao-Fan
    Registriert seit
    08.03.2010.
    Beiträge
    451

    Frage

    meinst du den button oben "Pakete aktualisieren"? den habe ich auch schon gedrückt. dann kommt dann die meldung von oben.

    was mich wundert ist das es zuerst richtig läuft (grüner haken):
    Code:
    composer require do-while/contao-backupdb-bundle
    $ /Applications/MAMP/bin/php/php7.4.20/bin/php -q -dmax_execution_time=0 -dmemory_limit=-1 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /Users/atomie/Sites/localhost/Manual/web/contao-manager.phar.php composer require do-while/contao-backupdb-bundle --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction
    Using config.component-dir has been deprecated. Please use extra.contao-component-dir instead.
    Using version ^1.4 for do-while/contao-backupdb-bundle
    /Users/atomie/Sites/localhost/Manual/composer.json has been updated
    # Process terminated with exit code 0
    # Result: OK
    aber dann im zweiten abschnitt sagt er mir (rotes Kreuz):
    Code:
    composer update do-while/contao-backupdb-bundle contao/conflicts
    > Resolving dependencies using Composer Cloud v3.2.0
    !!! Current server is sponsored by: Contao Association !!!
    [6.6MiB/0.17s] Loading composer repositories with package information
    [57.0MiB/2.10s] Updating dependencies
    [1432.2MiB/23.61s] Your requirements could not be resolved to an installable set of packages.
    [1432.2MiB/23.61s] 
      Problem 1
        - Root composer.json requires do-while/contao-backupdb-bundle ^1.4 -> satisfiable by do-while/contao-backupdb-bundle[1.4.0, 1.4.1, 1.4.2].
        - Conclusion: don't install symfony/http-kernel v5.2.2 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.2.3 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.2.4 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.2.5 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.2.6 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.10] | install one of symfony/framework-bundle[v4.4.24, v4.4.25, v4.4.26, v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.9] | install one of symfony/framework-bundle[v4.4.22, ..., v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.8] | install one of symfony/framework-bundle[v4.4.21, ..., v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.7] | install one of symfony/framework-bundle[v4.4.21, ..., v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v4.4.21] | install one of symfony/framework-bundle[v5.1.10, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v4.4.22] | install one of symfony/framework-bundle[v5.1.10, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v4.4.24] | install one of symfony/framework-bundle[v5.1.10, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.11] | install one of symfony/framework-bundle[v4.4.25, v4.4.26, v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.12] | install one of symfony/framework-bundle[v4.4.25, v4.4.26, v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.13] | install one of symfony/framework-bundle[v4.4.26, v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v5.1.10] | install one of symfony/framework-bundle[v4.4.25, v4.4.26, v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v5.1.11] | install one of symfony/framework-bundle[v4.4.25, v4.4.26, v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel[v5.2.14] | install one of symfony/framework-bundle[v4.4.27, v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v4.4.27] | install one of symfony/framework-bundle[v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v4.4.26] | install one of symfony/framework-bundle[v5.2.0, ..., v5.2.12] (conflict analysis result)
        - Conclusion: don't install symfony/framework-bundle[v4.4.25] | install one of symfony/framework-bundle[v5.2.0, ..., v5.2.12] (conflict analysis result)
        - symfony/framework-bundle[v5.2.0, ..., v5.2.12] require symfony/routing ^5.2 -> satisfiable by symfony/routing[v5.2.0, ..., v5.3.4].
        - Conclusion: don't install symfony/routing v5.2.0 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.1 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.2 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.3 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.4 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.6 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.7 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.9 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.10 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.2.12 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.3.0 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.3.0 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.3.1 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.3.2 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.3.3 (conflict analysis result)
        - Conclusion: don't install symfony/routing v5.3.4 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.3.4 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.3.5 (conflict analysis result)
        - Conclusion: don't install symfony/http-kernel v5.3.6 (conflict analysis result)
        - contao/manager-bundle 4.11.6 requires contao/installation-bundle 4.11.6 -> satisfiable by contao/installation-bundle[4.11.6].
        - contao/manager-bundle 4.11.6 requires symfony/web-profiler-bundle 4.4.* || 5.2.* -> satisfiable by symfony/web-profiler-bundle[v5.2.13].
        - contao/manager-bundle is locked to version 4.11.6 and an update of this package was not requested.
        - contao/installation-bundle 4.11.6 requires symfony/framework-bundle 4.4.* || 5.2.* -> satisfiable by symfony/framework-bundle[v4.4.0, ..., v4.4.27, v5.2.0, ..., v5.2.12].
        - symfony/framework-bundle[v4.4.0, ..., v4.4.20] require symfony/http-kernel ^4.4 -> satisfiable by symfony/http-kernel[v4.4.0, ..., v4.4.29].
        - You can only install one version of a package, so only one of these can be installed: symfony/http-kernel[v2.1.0, ..., v2.8.52, v3.0.0, ..., v3.4.49, v4.0.0, ..., v4.4.29, v5.0.0, ..., v5.3.6].
        - symfony/web-profiler-bundle v5.2.13 requires symfony/http-kernel ^5.2 -> satisfiable by symfony/http-kernel[v5.2.0, ..., v5.3.6].
        - Conclusion: don't install symfony/http-kernel v5.2.1 (conflict analysis result)
    [1432.2MiB/23.61s] <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>
    [76.4MiB/24.95s] Memory usage: 76.42MB (peak: 1434.09MB), time: 24.96s.
    [76.4MiB/24.96s] Finished Composer Cloud resolving.
    # Cloud Job ID 2ZET51DhUXW1365mzLnHlUCyRyKqivyl4LCriIO21BxCEMeDXyqNxM05iIF4IMOBqFf1MU1 failed

  4. #4
    Contao-Urgestein Avatar von do_while
    Registriert seit
    15.06.2009.
    Ort
    Berlin | Deutschland
    Beiträge
    3.612
    Partner-ID
    1081
    User beschenken
    Wunschliste
    Contao-Projekt unterstützen

    Support Contao

    Standard

    BackupDB läuft noch nicht in Symfony 5, daher wird bei der Installation das Contao zurückgestuft auf Symfony 4, was normal auch funktioniert.
    Wenn Du jetzt andere Erweiterungen nutzt, die Symfony 5 fordern, kommt es zum Konflikt und kann nicht installiert werden.

    Ansich sollte es mit "Alle Pakete aktualisieren" dann auch funktionieren (war jedenfalls bisher immer so).

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

    Standard

    Du musst zuerst alle Pakete zum Update markieren, dann das neue Paket hinzufügen, dann die Änderungen anwenden.
    » sponsor me via GitHub or PayPal or Revolut

  6. #6
    Contao-Fan
    Registriert seit
    08.03.2010.
    Beiträge
    451

    Daumen hoch Danke!

    Zitat Zitat von Spooky Beitrag anzeigen
    Du musst zuerst alle Pakete zum Update markieren, dann das neue Paket hinzufügen, dann die Änderungen anwenden.
    Tatsächlich. genau so hat es funktioniert. Da muss man erstmal drauf kommen.
    Danke schön!

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
  •