UpdateProbleme von Contao 4.4 auf 4.13
Hallo Zusammen,
gerade möchte ich eine Seite auf 4.13 Updaten und komme nicht weiter und bekomme folgende Meldung
HTML-Code:
> Resolving dependencies using Composer Cloud v3.6.0-1-g9d9036c
[7.5MiB/0.18s] Loading composer repositories with package information
[86.2MiB/9.73s] Updating dependencies
[122.9MiB/10.27s] Your requirements could not be resolved to an installable set of packages.
[122.9MiB/10.27s]
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 contao/core-bundle 4.13.0 -> found contao/core-bundle[4.13.0] but these were not loaded, likely because it conflicts with another require.
[122.9MiB/10.27s] <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>
[53.5MiB/10.32s] Memory usage: 53.46MB (peak: 212.45MB), time: 10.33s.
[53.5MiB/10.32s] Finished Composer Cloud resolving.
# Cloud Job ID QLmilk7ll9wfSwpmrsJmXiZEgRYnl1XxgGTIvzKzpM4UPo5Oauc5iTuorFdt7vproaPmdcGEpRWzOropGIZTvls7DAdtDz914faeH5y2sZl failed
Auf 4.13.* hatte ich auch schon versucht. Da war die Meldung dann natürlich länger.
Die Composer.json sieht so aus:
HTML-Code:
{
"type": "project",
"require": {
"asconsulting/flexslider": "^1.0",
"contao/conflicts": "*@dev",
"contao/manager-bundle": "4.9.*",
"do-while/contao-mpdf-template-bundle": "1.3.0",
"fritzmg/contao-youtube-iframe": "^2.2",
"madeyourday/contao-rocksolid-antispam": "^2.0",
"madeyourday/contao-rocksolid-columns": "^2.0",
"madeyourday/contao-rocksolid-custom-elements": "^2.2",
"madeyourday/contao-rocksolid-frontend-helper": "^2.0",
"madeyourday/contao-rocksolid-icon-picker": "^2.0",
"madeyourday/contao-rocksolid-mega-menu": "^2.0",
"madeyourday/contao-rocksolid-slider": "^2.0",
"madeyourday/contao-rocksolid-theme-assistant": "^2.0",
"metamodels/attribute_file": "2.2.0",
"metamodels/attribute_select": "2.2.0",
"metamodels/attribute_tabletext": "2.2.0",
"metamodels/attribute_text": "2.2.0",
"metamodels/attribute_timestamp": "2.2.0",
"metamodels/bundle_start": "2.2.0",
"metamodels/core": "2.2.0",
"metamodels/filter_checkbox": "2.2.0",
"metamodels/filter_perimetersearch": "2.2.0",
"metamodels/filter_select": "2.2.0",
"metamodels/filter_text": "2.2.0"
},
"extra": {
"contao-component-dir": "assets"
},
"scripts": {
"post-install-cmd": [
"Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
],
"post-update-cmd": [
"Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
]
}
}
Wenn ich contao/manager-bundle auf 4.13 hochstelle und den Composer update bekomme ich folgende Meldung:
HTML-Code:
> Resolving dependencies using Composer Cloud v3.6.0-1-g9d9036c
[7.5MiB/0.19s] Loading composer repositories with package information
[92.0MiB/9.05s] Updating dependencies
[189.0MiB/9.83s] Your requirements could not be resolved to an installable set of packages.
[189.0MiB/9.83s]
Problem 1
- Root composer.json requires metamodels/bundle_start 2.2.0 -> satisfiable by metamodels/bundle_start[2.2.0].
- contao/manager-bundle[4.13.0, ..., 4.13.29] require symfony/web-profiler-bundle ^5.4 -> satisfiable by symfony/web-profiler-bundle[v5.4.0, ..., v5.4.26].
- Conclusion: don't install symfony/web-profiler-bundle v5.4.26 (conflict analysis result)
- Root composer.json requires contao/manager-bundle 4.13.* -> satisfiable by contao/manager-bundle[4.13.0, ..., 4.13.29].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
[189.0MiB/9.84s] <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>
[57.3MiB/9.92s] Memory usage: 57.26MB (peak: 216.4MB), time: 9.92s.
[57.3MiB/9.92s] Finished Composer Cloud resolving.
# Cloud Job ID eyZaq2qnLlPqkuDZc3FqStVqRUz3zuWs2oC4z9A1fXUh9XqDiB0XpdXbYmvtUzk4BuHz58mmrblFoNa failed
Was muss ich jetzt machen?
