Neuinstallation und kein Paket Install möglich

Druckbare Version

14.02.2023, 16:58
Tattoo Angestochen

Neuinstallation und kein Paket Install möglich

Hallöchen

habe Testweise mal eine Neuinstallation gemacht und kann kein Theme z.B. Mate installieren. auch einige andere Pakete aus dem Manager sind nicht installierbar.
Ich habe die Version Version 4.9.38 neu aufgesetzt und Datenbank (MySQL8.0) Update durchgeführt. Als erstes wollte ich testweise Das Mate them installieren, und da kommt folgender Fehler mit dem ich nichts anfangen kann.

Code:

composer require contao-themes-net/mate-theme-bundle $ /usr/bin/php8.1-cli -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/Madrid /homepages/36/d685933499/htdocs/testdomain/contao/web/contao-manager.phar.php composer require contao-themes-net/mate-theme-bundle --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction Info from https://repo.packagist.org: #StandWithUkraine Using version ^3.0 for contao-themes-net/mate-theme-bundle /homepages/36/d685933499/htdocs/testdomain/contao/composer.json has been updated # Process terminated with exit code 0 # Result: OK composer update contao-themes-net/mate-theme-bundle contao/conflicts --no-install > Resolving dependencies using Composer Cloud v3.5.1 [6.5MiB/0.18s] Loading composer repositories with package information [64.7MiB/7.58s] Updating dependencies [82.2MiB/7.91s] Your requirements could not be resolved to an installable set of packages. [82.2MiB/7.91s] Problem 1 - Root composer.json requires contao-themes-net/mate-theme-bundle ^3.0 -> satisfiable by contao-themes-net/mate-theme-bundle[3.0.0, ..., 3.0.5]. - contao-themes-net/mate-theme-bundle[3.0.0, ..., 3.0.5] require contao/core-bundle ^5.0 -> found contao/core-bundle[5.0.0, ..., 5.0.9] but these were not loaded, likely because it conflicts with another require. [82.2MiB/7.91s] <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> [36.8MiB/7.93s] Memory usage: 36.81MB (peak: 183.02MB), time: 7.94s. [36.8MiB/7.94s] Finished Composer Cloud resolving. # Cloud Job ID b6kBiRLgAxwPnPj9V6VwRSGuNTvZofQOWtlsr6JhMyX43Gw3KnSAYmUDBucOpJftzRrV0EH3miHR9tFyQrdDC10lQpMdwaeVpn9UYaCA6UE3cBhi7OeCEG failed composer install

nach allen Updates im Manager und alles aktualisieren:
- Prod-Cache erneuern (yes)
- Datenbank Überprüfen (yes)
- Composer Class Loader (yes)
- Composer Abhängigkeiten, Update Installieren (yes)
- Composer Install (yes)
- Composer Cache leeren (yes)

Code:

composer require contao-themes-net/nature-theme-bundle $ /usr/bin/php8.1-cli -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/Madrid /homepages/36/d685933499/htdocs/testdomain/contao/web/contao-manager.phar.php composer require contao-themes-net/nature-theme-bundle --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction Info from https://repo.packagist.org: #StandWithUkraine Using version ^2.1 for contao-themes-net/nature-theme-bundle /homepages/36/d685933499/htdocs/testdomain/contao/composer.json has been updated # Process terminated with exit code 0 # Result: OK composer update --no-install > Resolving dependencies using Composer Cloud v3.5.1 [6.5MiB/0.17s] Loading composer repositories with package information [66.5MiB/6.31s] Updating dependencies [126.9MiB/6.87s] Your requirements could not be resolved to an installable set of packages. [126.9MiB/6.87s] Problem 1 - Root composer.json requires contao-themes-net/nature-theme-bundle ^2.1 -> satisfiable by contao-themes-net/nature-theme-bundle[2.1.0, 2.1.1]. - 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) - contao/newsletter-bundle 4.9.21 requires contao/core-bundle 4.9.21 -> satisfiable by contao/core-bundle[4.9.21]. - Conclusion: don't install contao/core-bundle 4.9.21 (conflict analysis result) - contao/newsletter-bundle 4.9.22 requires contao/core-bundle 4.9.22 -> satisfiable by contao/core-bundle[4.9.22]. - Conclusion: don't install contao/core-bundle 4.9.22 (conflict analysis result) - contao/newsletter-bundle 4.9.23 requires contao/core-bundle 4.9.23 -> satisfiable by contao/core-bundle[4.9.23]. - Conclusion: don't install contao/core-bundle 4.9.23 (conflict analysis result) - contao/newsletter-bundle 4.9.24 requires contao/core-bundle 4.9.24 -> satisfiable by contao/core-bundle[4.9.24]. - Conclusion: don't install contao/core-bundle 4.9.24 (conflict analysis result) - contao/newsletter-bundle 4.9.25 requires contao/core-bundle 4.9.25 -> satisfiable by contao/core-bundle[4.9.25]. - Conclusion: don't install contao/core-bundle 4.9.25 (conflict analysis result) - contao/newsletter-bundle 4.9.26 requires contao/core-bundle 4.9.26 -> satisfiable by contao/core-bundle[4.9.26]. - Conclusion: don't install contao/core-bundle 4.9.26 (conflict analysis result) - contao/newsletter-bundle 4.9.27 requires contao/core-bundle 4.9.27 -> satisfiable by contao/core-bundle[4.9.27]. - Conclusion: don't install contao/core-bundle 4.9.27 (conflict analysis result) - contao/newsletter-bundle 4.9.28 requires contao/core-bundle 4.9.28 -> satisfiable by contao/core-bundle[4.9.28]. - Conclusion: don't install contao/core-bundle 4.9.28 (conflict analysis result) - contao/newsletter-bundle 4.9.29 requires contao/core-bundle 4.9.29 -> satisfiable by contao/core-bundle[4.9.29]. - Conclusion: don't install contao/core-bundle 4.9.29 (conflict analysis result) - contao/newsletter-bundle 4.9.30 requires contao/core-bundle 4.9.30 -> satisfiable by contao/core-bundle[4.9.30]. - Conclusion: don't install contao/core-bundle 4.9.30 (conflict analysis result) - contao/newsletter-bundle 4.9.31 requires contao/core-bundle 4.9.31 -> satisfiable by contao/core-bundle[4.9.31]. - Conclusion: don't install contao/core-bundle 4.9.31 (conflict analysis result) - contao/newsletter-bundle 4.9.32 requires contao/core-bundle 4.9.32 -> satisfiable by contao/core-bundle[4.9.32]. - Conclusion: don't install contao/core-bundle 4.9.32 (conflict analysis result) - contao/newsletter-bundle 4.9.33 requires contao/core-bundle 4.9.33 -> satisfiable by contao/core-bundle[4.9.33]. - Conclusion: don't install contao/core-bundle 4.9.33 (conflict analysis result) - contao/newsletter-bundle 4.9.34 requires contao/core-bundle 4.9.34 -> satisfiable by contao/core-bundle[4.9.34]. - Conclusion: don't install contao/core-bundle 4.9.34 (conflict analysis result) - contao/newsletter-bundle 4.9.35 requires contao/core-bundle 4.9.35 -> satisfiable by contao/core-bundle[4.9.35]. - Conclusion: don't install contao/core-bundle 4.9.35 (conflict analysis result) - contao/newsletter-bundle 4.9.36 requires contao/core-bundle 4.9.36 -> satisfiable by contao/core-bundle[4.9.36]. - Conclusion: don't install contao/core-bundle 4.9.36 (conflict analysis result) - contao/newsletter-bundle 4.9.37 requires contao/core-bundle 4.9.37 -> satisfiable by contao/core-bundle[4.9.37]. - Conclusion: don't install contao/core-bundle 4.9.37 (conflict analysis result) - contao/newsletter-bundle 4.9.38 requires contao/core-bundle 4.9.38 -> satisfiable by contao/core-bundle[4.9.38]. - Conclusion: don't install contao/core-bundle 4.9.38 (conflict analysis result) - contao-themes-net/theme-components-bundle[1.4.0, ..., 1.4.1] require contao-dd/advanced-classes-bundle ^1.4 -> satisfiable by contao-dd/advanced-classes-bundle[1.4.0, 1.5.0]. - contao-themes-net/nature-theme-bundle[2.1.0, ..., 2.1.1] require contao-themes-net/theme-components-bundle ^1.4 -> satisfiable by contao-themes-net/theme-components-bundle[1.4.0, 1.4.1]. - contao/newsletter-bundle[4.9.0, ..., 4.9.9] require php ^7.2 -> your php version (8.1.14.0) does not satisfy that requirement. - 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-dd/advanced-classes-bundle[1.4.0, ..., 1.5.0] require contao/core-bundle ^5.0 -> satisfiable by contao/core-bundle[5.0.0, ..., 5.0.9]. - You can only install one version of a package, so only one of these can be installed: contao/core-bundle[4.9.0, ..., 4.13.15, 5.0.0, ..., 5.0.9]. - contao/newsletter-bundle 4.9.10 requires contao/core-bundle 4.9.10 -> satisfiable by contao/core-bundle[4.9.10]. - Root composer.json requires contao/newsletter-bundle 4.9.* -> satisfiable by contao/newsletter-bundle[4.9.0, ..., 4.9.38]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions. [127.0MiB/6.87s] <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> [38.0MiB/6.92s] Memory usage: 37.97MB (peak: 170.21MB), time: 6.93s. [38.0MiB/6.92s] Finished Composer Cloud resolving. # Cloud Job ID Lp3cOymQ2bDficOlvo8BXsYLJKtjU617d1pCtzrWaFfSUVvVfL5kBKohi46NHfpsuasqFBHfdU3UQOlxr93JnJmRVPaX failed composer install

hatte eine schon einmal dieses Problem, und wie kann ich dem Abhilfe schaffen?

Vielen lieben Dank
14.02.2023, 17:39
lbableck

Du musst Version ^2.0 des Themes installieren. 3.0 ist für Contao 5.
14.02.2023, 18:45
Tattoo Angestochen

re

alter Schwede vielen Dank....

da wäre ich jetzt beim besten willen nicht drauf gekommen. Gibt es das auch mit dem 0.1 und Nature Theme?

welche Versionen wären es da?

Danke Danke Dank
14.02.2023, 18:54
lbableck

Ja, ist da das gleiche, da brauchst du ^1.0 bei beiden.
14.02.2023, 19:31
Tattoo Angestochen

re

das 0.1 mit Vers. 1.0 funktioniert nicht:

Code:

composer require contao-themes-net/zero-one-theme-bundle=1.0 $ /usr/bin/php8.1-cli -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/Madrid /homepages/36/d685933499/htdocs/testdomain/contao/web/contao-manager.phar.php composer require contao-themes-net/zero-one-theme-bundle=1.0 --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction The "1.0" constraint for "contao-themes-net/zero-one-theme-bundle" appears too strict and will likely not match what you want. See https://getcomposer.org/constraints /homepages/36/d685933499/htdocs/testdomain/contao/composer.json has been updated # Process terminated with exit code 0 # Result: OK composer update contao-themes-net/zero-one-theme-bundle contao/conflicts --no-install > Resolving dependencies using Composer Cloud v3.5.1 [6.8MiB/0.36s] Loading composer repositories with package information [65.3MiB/7.72s] Updating dependencies [82.6MiB/7.98s] Your requirements could not be resolved to an installable set of packages. [82.6MiB/7.99s] Problem 1 - Root composer.json requires contao-themes-net/zero-one-theme-bundle 1.0 -> satisfiable by contao-themes-net/zero-one-theme-bundle[1.0.0]. - contao-themes-net/zero-one-theme-bundle 1.0.0 requires php ^5.6 || ^7.0 -> your php version (8.1.14.0) does not satisfy that requirement. [82.6MiB/7.99s] <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> [37.3MiB/8.01s] Memory usage: 37.3MB (peak: 183.88MB), time: 8.02s. [37.3MiB/8.01s] Finished Composer Cloud resolving. # Cloud Job ID 77diJmfXNFFVGzaWWQicx7j9ZafGG4sIdvpOWAXdfhifEIBin33DNroK6DJw4z80TQuhjFFSbBIgz failed composer install

Nature das gleiche:

Code:

composer require contao-themes-net/nature-theme-bundle=1.0 $ /usr/bin/php8.1-cli -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/Madrid /homepages/36/d685933499/htdocs/testdomain/contao/web/contao-manager.phar.php composer require contao-themes-net/nature-theme-bundle=1.0 --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction The "1.0" constraint for "contao-themes-net/nature-theme-bundle" appears too strict and will likely not match what you want. See https://getcomposer.org/constraints /homepages/36/d685933499/htdocs/testdomain/contao/composer.json has been updated # Process terminated with exit code 0 # Result: OK composer update contao-themes-net/nature-theme-bundle contao/conflicts --no-install > Resolving dependencies using Composer Cloud v3.5.1 [6.8MiB/0.18s] Loading composer repositories with package information [65.4MiB/7.29s] Updating dependencies [82.8MiB/7.58s] Your requirements could not be resolved to an installable set of packages. [82.8MiB/7.58s] Problem 1 - Root composer.json requires contao-themes-net/nature-theme-bundle 1.0 -> satisfiable by contao-themes-net/nature-theme-bundle[1.0.0]. - contao-themes-net/nature-theme-bundle 1.0.0 requires php ^5.6 || ^7.0 -> your php version (8.1.14.0) does not satisfy that requirement. [82.8MiB/7.59s] <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> [37.3MiB/7.61s] Memory usage: 37.34MB (peak: 184.4MB), time: 7.62s. [37.3MiB/7.61s] Finished Composer Cloud resolving. # Cloud Job ID HHpClqt8kJFBxPIEAUqD97YZOEBwvtNue6EZuBJua7ocw4bLqTqPfZLDS5MGTvTXlCEXa50KJG2A8BaateZR0toAqMe7r2 failed composer install
14.02.2023, 19:41
lbableck

Neuinstallation und kein Paket Install möglich

Du musst ^1.0 requiren, nicht 1.0.
14.02.2023, 19:59
tab

nicht "1.0", sondern "^1.0", das bedeutet >=1.0.0 < 2.0.0. Wie die Meldung ja schon sagt, ist erscheint die genaue Version 1.0.0 als zu strikt und ist wahrscheinlich nicht das, was du eigentlich willst.
16.02.2023, 11:45
Tattoo Angestochen

re

Hallöchen. habe mich jetzt nach einige herum spielen für das 0.1 Theme inclusive des Isotope entschieden und gestern gekauft. Habe es dann gestern Abend noch nach Anweisung installiert und wundere mich über das Layout, welches nicht so ist, wie in der Demo. Es gibt keinen Warenkorb, Artikel, Produkte. Es ist quasi wie eine Free Version, wo man den Isotope nach installiert. Außer das die Ordnerstruktur nicht so ausgeprägt ist wie in der Demo.
Heute morgen dachte ich mir es gab evl. einen Install Fehler, also habe ich alles noch einmal neu aufgesetzt. Contao 4.13.x und neue Datenbank MySQL8.0.
Beim installieren bringt er mir tatsächlich einen Fehler:

Ein Template importieren
Der Import konnte nicht abgeschlossen werden! Ist die Datenbank aktuell und die Template-Datei kompatibel mit Ihrer Contao-Version?
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '2' for key 'tl_iso_attribute.PRIMARY'

wie kann ich dieses Problem beheben und ist das Theme wirklich ohne Vorkonfigurationen?

<<<
In der Shop-Version des klimafreundlichen "0.1"-Theme steht ein komplett vorkonfigurierter Isotope eCommerce-Shop inkl. optimierter Startseite & typischer Shop-Elemente, wie Themenwelten, Marken und Produktslider im frischen Look zur Verfügung.
>>>

DANKE
16.02.2023, 11:55
mlweb

Wende Dich mit diesen Fragen an den Verkäufer des Themes. Nur er wird Dir hierzu m.E. eine zuverlässige Antwort geben können.

Meine grobe Vermutung geht in Richtung Fehler bei der Demo-Datei (Demo-Template). Warum das aber auftritt, kann ich Dir nicht sagen. Das reicht von falsche Demodatei heruntergeladen über Fehler gemacht beim Einspielen des Themes mit den Demodaten bis zu Fehler in den bereitgestellten Demodaten.
21.04.2023, 14:54
Hoch-3

Manager ist blockiert

Ich hab eine etwas ältere Contao 4 Installation (4.4.38) Ich würde gerne aktualisieren und eine Erweiterung aufschalten. Auf der Pakete Seite gibt es die Erweiterung contao-components/installer als manuell entfernt an. Wenn ich diese Änderung (oder eine neue Erweiterung oder eine Aktualisierung des CMS vorerst auf 4.4.57 machen möchte bricht es mit dieser Fehlermeldung ab.

Code:

> Resolving dependencies using Composer Cloud v3.6.0 2 3 [4.8MiB/0.19s] Loading composer repositories with package information 4 [5.4MiB/0.27s] Updating dependencies 5 [6.3MiB/0.28s] Your requirements could not be resolved to an installable set of packages. 6 [6.3MiB/0.29s] 7 Problem 1 8 - contao/manager-plugin 2.7.0 requires composer-plugin-api ^1.1 -> found composer-plugin-api[2.3.0] but it does not match the constraint. 9 - contao/manager-bundle 4.4.38 requires contao/manager-plugin ^2.1 -> satisfiable by contao/manager-plugin[2.7.0]. 10 - contao/manager-bundle is locked to version 4.4.38 and an update of this package was not requested. 11 12 [6.3MiB/0.29s] <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> 13 [5.5MiB/0.29s] Memory usage: 5.5MB (peak: 6.76MB), time: 0.29s. 14 [5.5MiB/0.29s] Finished Composer Cloud resolving. 15 16 17 # Cloud Job ID 7LTv7iWdD6PPyv3GFbltwBLjc9skuFIGc9pLQWQG3PO9K68EOMELN7psXNIbMeWrTI329OvDo0Nu6wyAh9XmApTHOfG failed

Leider reichen meine Fähigkeiten nicht aus, um das Problem und dann die Lösung zu finden... kann mit jemand helfen?

Die Website (https://noma-hilfe.ch) läuft, immerhin.
21.04.2023, 14:56
Spooky

Die Composer Cloud unterstützt Contao 4.4 nicht.
24.04.2023, 09:56
Hoch-3

Zitat:

Zitat von Spooky

Die Composer Cloud unterstützt Contao 4.4 nicht.

Hallo Spooky. Wie krieg ich das denn weg?

Ich hab versucht auf 4.13 zu aktualisieren. Ähnlicher Fehler und Abbruch.
24.04.2023, 09:59
Spooky

Zitat:

Zitat von Hoch-3

Hallo Spooky. Wie krieg ich das denn weg?

Wenn der Contao Manager startet in der Server Konfiguration die Composer Cloud deaktivieren.

Zitat:

Zitat von Hoch-3

Ich hab versucht auf 4.13 zu aktualisieren. Ähnlicher Fehler und Abbruch.

"Ähnlicher" Fehler? Wenn es nicht der selbe Fehler ist erzeuge einen neuen Thread und beschreibe das Problem genau.
24.04.2023, 11:01
Hoch-3

Zitat:

Zitat von Spooky

Wenn der Contao Manager startet in der Server Konfiguration die Composer Cloud deaktivieren.

Composer Resolver Cloud deaktiviert. Neue Fehlermeldung:

Code:

composer update contao-components/installer contao/conflicts --no-install 1 $ /usr/local/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/Zurich /services/webs/nomahilfe.ch/htdocs/web/contao-manager.phar.php composer update contao-components/installer contao/conflicts --with-dependencies --no-install --no-scripts --no-dev --no-progress --no-ansi --no-interaction --optimize-autoloader 2 3 The "contao-components/installer" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.2.0"). You may need to run composer update with the "--no-plugins" option. 4 The "contao-community-alliance/composer-plugin" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.2.0"). You may need to run composer update with the "--no-plugins" option. 5 The "contao/manager-plugin" plugin was skipped because it requires a Plugin API version ("^1.1") that does not match your Composer installation ("2.2.0"). You may need to run composer update with the "--no-plugins" option. 6 Loading composer repositories with package information 7 Info from https://repo.packagist.org: #StandWithUkraine 8 Updating dependencies 9 Your requirements could not be resolved to an installable set of packages. 10 11 Problem 1 12 - contao/manager-plugin 2.7.0 requires composer-plugin-api ^1.1 -> found composer-plugin-api[2.2.0] but it does not match the constraint. 13 - contao/manager-bundle 4.4.38 requires contao/manager-plugin ^2.1 -> satisfiable by contao/manager-plugin[2.7.0]. 14 - contao/manager-bundle is locked to version 4.4.38 and an update of this package was not requested. 15 16 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. 17 18 # Process terminated with exit code 2 19 # Result: Misuse of shell builtins

Irgendwas ist hier total verknorzt...