Composer update Fehlermeldung - Contao 4.9.13
Hallo,
ich bekomme folgende Fehlermeldung wenn ich composer update durchführen will!
Code:
composer install
$ /usr/bin/php7.4 -q -dmax_execution_time=0 -dmemory_limit=-1 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /var/customers/webs/id42/xyz.de/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.
Your lock file does not contain a compatible set of packages. Please run composer update.
Problem 1
- ocramius/proxy-manager is locked to version 2.13.0 and an update of this package was not requested.
- ocramius/proxy-manager 2.13.0 requires composer-runtime-api ^2.1.0 -> found composer-runtime-api[2.0.0] but it does not match the constraint.
Problem 2
- ocramius/proxy-manager 2.13.0 requires composer-runtime-api ^2.1.0 -> found composer-runtime-api[2.0.0] but it does not match the constraint.
- symfony/proxy-manager-bridge v4.4.18 requires ocramius/proxy-manager ~2.1 -> satisfiable by ocramius/proxy-manager[2.13.0].
- symfony/proxy-manager-bridge is locked to version v4.4.18 and an update of this package was not requested.
# Process terminated with exit code 2
# Result: Misuse of shell builtins
Da steht das ich ein Composer Update durchführen soll, aber genau das mache ich, und dann kommt eben diese Fehlermeldung!
habe eine komplette Paketaktualisierung auch versucht, da kommt die gleiche Fehlermeldung bei "composer install"
PHP Ver. 7.416
Contao 4.9.13
Gleiches Problem mit einer 4.4.45 Installation
Ich wollte das Updaten -- Nach Aktualisierung des Managers wollte ich den Composer aktualisieren:
Fehlermeldung:
Code:
Verifying lock file contents can be installed on current platform.
Your lock file does not contain a compatible set of packages. Please run composer update.
Problem 1
- contao-community-alliance/composer-plugin is locked to version 3.0.9 and an update of this package was not requested.
- contao-community-alliance/composer-plugin 3.0.9 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.6.0] but it does not match the constraint.
Problem 2
- contao/manager-plugin is locked to version 2.7.1 and an update of this package was not requested.
- contao/manager-plugin 2.7.1 requires composer-plugin-api ^1.1 -> found composer-plugin-api[2.6.0] but it does not match the constraint.
Problem 3
- contao-community-alliance/composer-plugin 3.0.9 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.6.0] but it does not match the constraint.
- terminal42/notification_center 1.5.8 requires contao-community-alliance/composer-plugin ~2.4 || ~3.0 -> satisfiable by contao-community-alliance/composer-plugin[3.0.9].
- terminal42/notification_center is locked to version 1.5.8 and an update of this package was not requested.
# Process terminated with exit code 2
# Result: Misuse of shell builtins
Contao Manager 1.8.4
HilfeProbleme melden
Die Json sieht aus wie folgt:
Code:
"type": "project",
"require": {
"chrmue/cm_maps": "^1.1",
"chrmue/cm_membermaps": "^1.1",
"cliffparnitzky/form-dependent-mandatory-field": "^2.1",
"contao/calendar-bundle": "4.4.*",
"contao/comments-bundle": "4.4.*",
"contao/conflicts": "*@dev",
"contao/faq-bundle": "4.4.*",
"contao/listing-bundle": "4.4.*",
"contao/manager-bundle": "4.4.*",
"contao/news-bundle": "4.4.*",
"contao/newsletter-bundle": "4.4.*",
"hschottm/tags": "^4.0",
"jrgregory/m17-sticky-backend-footer": "^2.0",
"mvo/contao-facebook-import": "^3.1",
"terminal42/contao-conditionalformfields": "^2.2",
"terminal42/contao-countryselect": "^1.4",
"terminal42/notification_center": "^1.5"
},
"extra": {
"contao-component-dir": "assets"
},
"scripts": {
"post-install-cmd": [
"Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
],
"post-update-cmd": [
"Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
]
}
Kann da jemand helfen?? Danke Euch
Liste der Anhänge anzeigen (Anzahl: 1)
Ahhh .. ich habe jetzt mal auf abgesicherten Modus geklickt .. und da kann ich das nun einstellen. bin sonst nie weiter als bis hierhin gekommen.
Ist ja eigentlich logisch, dass man im abgesicherten Modus weitermacht...Anhang 27234