Fehler bei Upgrade von 4.12.1 auf 4.13.0
Hallo zusammen
Ich kann eine Installation nicht von 12.1 auf 13.0 upgraden. Ich habe alle Erweiterungen auf dem neuesten Stand und die Version 12.1 auch testweise neu installiert. Für das Upgrade habe ich im CM auch "Pakete aktualisieren" aktiviert. Ich erhalte folgende Meldung:
Fehler CM:
Code:
- contao/manager-bundle 4.13.0 requires symfony/console ^5.4 -> found symfony/console[v5.4.0, v5.4.1, v5.4.2, v5.4.3]
but these were not loaded, likely because it conflicts with another require.
[80.7MiB/11.44s] <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.8MiB/11.50s] Memory usage: 13.82MB (peak: 128.9MB), time: 11.51s.
[13.8MiB/11.50s] Finished Composer Cloud resolving.
# Cloud Job ID dyVBZQDBk2Lc5armRMHgSY3ivGGHwTWZHE30oGHuM76LH3HWggoLlLECr376vhLEUT5Sh05wjAlCxyNirxHH2LV2LYLtFIQEvJCpMdpApcLCOLgMj689Fz failed
Composer.json:
Code:
{
"name": "contao/managed-edition",
"type": "project",
"description": "Contao Open Source CMS",
"license": "LGPL-3.0-or-later",
"authors": [
{
"name": "Leo Feyer",
"homepage": "https://github.com/leofeyer"
}
],
"require": {
"contao/conflicts": "*@dev",
"contao/manager-bundle": "4.13.*",
"dklemmt/contao_dk_mmenu": "3.2.5",
"do-while/contao-backupdb-bundle": "1.5.1",
"erdmannfreunde/euf_overlay": "^1.3",
"terminal42/contao-easy_themes": "3.0.2"
},
"conflict": {
"doctrine/dbal": "2.9.1"
},
"require-dev": {
"sensiolabs/security-checker": "^4.1"
},
"extra": {
"branch-alias": {
"dev-4.6": "4.6.x-dev"
},
"contao-component-dir": "assets"
},
"autoload": {
"psr-4": {
"App\": "src/"
}
},
"scripts": {
"post-install-cmd": [
"Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
],
"post-update-cmd": [
"Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
]
}
}
Hätte jemand einen Tip? Vielen Dank!
Bei mir gibt es bei einer Installation auch ein Problem ...
Guten Tag, ich habe 8 CONTAO-Installationen, bei 7 davon konnte ich problemlos auf 4.13.0 updaten.
Eine Installation sperrt sich jedoch.
Hier ein Ausschnitt aus dem LOG:
Code:
[6.9MiB/0.24s] Loading composer repositories with package information
[36.6MiB/14.68s] Updating dependencies
[130.1MiB/15.42s] Your requirements could not be resolved to an installable set of packages.
[130.1MiB/15.42s]
Problem 1
- sensiolabs/security-checker[v4.1.6, ..., v4.1.8] require symfony/console ~2.7|~3.0|~4.0 -> satisfiable by symfony/console[v2.7.0, ..., v2.8.52, v3.0.0, ..., v3.4.47, v4.0.0, ..., v4.4.37].
- sensiolabs/security-checker[v4.1.0, ..., v4.1.5] require symfony/console ~2.7|~3.0 -> satisfiable by symfony/console[v2.7.0, ..., v2.8.52, v3.0.0, ..., v3.4.47].
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v4.4.37.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v4.4.26.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v4.4.20.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v4.4.8.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v4.3.11.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v4.2.12.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v4.2.2.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v4.1.12.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v4.1.10.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v3.4.47.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v3.4.21.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v3.3.18.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v3.3.6.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v3.2.14.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v3.1.4.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v2.8.52.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v2.8.17.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v2.8.11.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v2.7.51.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v2.7.24.
- symfony/yaml[v5.4.0, ..., v5.4.3] conflict with symfony/console v2.7.18.
- contao/calendar-bundle 4.13.0 requires symfony/yaml ^5.4 -> satisfiable by symfony/yaml[v5.4.0, v5.4.2, v5.4.3].
- Root composer.json requires contao/calendar-bundle 4.13.* -> satisfiable by contao/calendar-bundle[4.13.0].
- Root composer.json requires sensiolabs/security-checker ^4.1 -> satisfiable by sensiolabs/security-checker[v4.1.0, ..., v4.1.8].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
[130.1MiB/15.42s] 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.
[18.0MiB/15.51s] Memory usage: 18.01MB (peak: 154.41MB), time: 15.52s.
[18.0MiB/15.52s] Finished Composer Cloud resolving.
Und ja, ich habe "alles updaten" gewählt und im Install-Tool auch ein "Composer-Update" laufen lassen.
Weiß jemand Rat?
Grüße
Contao 4.9 auf 4.13 aktualisieren
Hallo Zusammen.
Ich wollte auch von Contao 4.9 auf 4.13 aktualisieren.
Erst den bitnami mamp in version 7.4.x installiert und dann die Website zum laufen gebracht.
Composer.json angepasst mit
HTML-Code:
"php": "^7.4",
"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",
...
Wenn ich den Update ausführe bekomme ich folgendes Problem:
HTML-Code:
Problem 1
- Root composer.json requires contao/calendar-bundle ^4.13 -> satisfiable by contao/calendar-bundle[4.13.0].
- ixtensa/employee-bundle[v6.0.0, ..., v6.0.4] require symfony/intl ^4.2 -> satisfiable by symfony/intl[v4.2.0, ..., v4.4.38].
- You can only install one version of a package, so only one of these can be installed: symfony/intl[v2.3.0, ..., v2.8.52, v3.0.0, ..., v3.4.47, v4.0.0, ..., v4.4.38, v5.0.0, ..., v5.4.5].
- contao/core-bundle 4.13.0 requires symfony/intl ^5.4 -> satisfiable by symfony/intl[v5.4.0, v5.4.2, v5.4.3, v5.4.5].
- contao/calendar-bundle 4.13.0 requires contao/core-bundle 4.13.0 -> satisfiable by contao/core-bundle[4.13.0].
- Root composer.json requires ixtensa/employee-bundle ^6.0 -> satisfiable by ixtensa/employee-bundle[v6.0.0, ..., v6.0.4].
Liegt das Problem an der Schreibweise, wie ich es in composer.json anegegeben habe contao/calendar-bundle": "^4.13?
Dazu habe ich bei dem einen Bundle die symfony/intl auf ^5.4 geändert, aber es hat keine Auswirkung.
Wenn ich composer run-script post-install-cmd ausführe kommt dabei folgendes raus:
HTML-Code:
Contao\ManagerBundle\Composer\ScriptHandler::initializeApplication
dyld: Library not loaded: /bitnami/mamp74stack-osx-x64/output/common/lib/libldap.2.dylib
Referenced from: /Applications/mampstack-7.4/php/bin/php.bin
Reason: image not found
Script Contao\ManagerBundle\Composer\ScriptHandler::initializeApplication handling the post-install-cmd event terminated with an exception
In Process.php line 441:
The process has been signaled with signal "6".
Was mache ich hier falsch? Ich komme nicht drauf, wo dieser Fehler her kommt.
Fehlermeldung beim Update von contao 4.12.7 auf 4.13.0
Hallo liebes Forum,
auch ich habe ein Problem bei einer meiner Installationen mit dem Update auf das 4.13er conato. Probiere es schon seit ein paar Stunden, und mittlerweile alle Erweiterungen auf den neuesten Stand.
Bei der Suche nach einer Lösung fand ich dann diesen Forumseintrag.
Dann beim 4.13 update steht in der Konsole folgende Fehlermeldung:
Code:
# Process terminated with exit code 0
# Result: OK
> Resolving dependencies using Composer Cloud v3.3.3
!!! Current server is sponsored by: Contao Association !!!
[6.9MiB/0.18s] Loading composer repositories with package information
[29.1MiB/9.99s] Updating dependencies
[61.4MiB/10.29s] Your requirements could not be resolved to an installable set of packages.
[61.4MiB/10.30s]
Problem 1
- Root composer.json requires contao/manager-bundle 4.13.0 -> satisfiable by contao/manager-bundle[4.13.0].
- contao/manager-bundle 4.13.0 requires symfony/filesystem ^5.4 -> found symfony/filesystem[v5.4.0, v5.4.3, v5.4.5] but these were not loaded, likely because it conflicts with another require.
Problem 2
- contao/core-bundle 4.13.0 requires symfony/filesystem ^5.4 -> found symfony/filesystem[v5.4.0, v5.4.3, v5.4.5] but these were not loaded, likely because it conflicts with another require.
- contao/newsletter-bundle 4.13.0 requires contao/core-bundle 4.13.0 -> satisfiable by contao/core-bundle[4.13.0].
- Root composer.json requires contao/newsletter-bundle 4.13.0 -> satisfiable by contao/newsletter-bundle[4.13.0].
[61.4MiB/10.30s] 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.
[13.8MiB/10.34s] Memory usage: 13.76MB (peak: 134.32MB), time: 10.35s.
[13.8MiB/10.34s] Finished Composer Cloud resolving.
# Cloud Job ID WNGpwqP5s3hsRefwnuwKWL8k9rno6wuCi5tWU3npMbbLwHUUtW158YOsuoGT07suCGjA3QSjDHoSD5N6ebw8EBnzKTSuJaRGWoai24P9vTSKc failed
Also habe ich dann die composer.json gesucht und da ist folgendes zu sehen:
Code:
{
"type": "project",
"require": {
"contao-themes-net/nature-theme-bundle": "^1.8",
"contao/calendar-bundle": "^4.12.7",
"contao/comments-bundle": "^4.12.7",
"contao/conflicts": "*@dev",
"contao/faq-bundle": "^4.12.7",
"contao/listing-bundle": "^4.12.7",
"contao/manager-bundle": "^4.12.7",
"contao/news-bundle": "^4.12.7",
"contao/newsletter-bundle": "^4.12.7",
"contao/tcpdf-bundle": "^1.2",
"inszenium/isotope-export": "^2.0.4",
"isotope/isotope-core": "^2.7.4",
"isotope/isotope_documents": "^1.0.3",
"menatwork/registration_info_mailer": "^3.1.1",
"terminal42/contao-changelanguage": "^3.2.8"
},
"extra": {
"contao-component-dir": "assets"
},
"scripts": {
"post-install-cmd": [
"Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
],
"post-update-cmd": [
"Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
]
}
}
auf einer anderen Intsallation lief es reibungslos...
Was habe ich falsch gemacht, oder vergessen?
nette halbverzweifelte Grüße
