Update von 4.13.43 auf 5.3.7 scheitert
Hallo in die Runde,
ich habe hier eine sehr schmale contao Installation, deren update von 4.13.43 auf 5.3.7 scheitert.
Ich habe die composer.json entsprechend angepasst und versuche alle Pakete zu aktualisieren.
Vielleicht kann mich jemand in die richtige Richtung schupsen.
Vielen Dank,
Matthias
Consolen-Meldung:
Code:
> Resolving dependencies using Composer Cloud v3.7.0
[7.0MiB/0.22s] Loading composer repositories with package information
[88.7MiB/10.22s] Updating dependencies
[134.0MiB/10.66s] Your requirements could not be resolved to an installable set of packages.
[134.0MiB/10.66s]
Problem 1
- Root composer.json requires contao-themes-net/mate-theme-bundle ^3.3 -> satisfiable by contao-themes-net/mate-theme-bundle[3.3.0, 3.3.1, 3.3.2].
- contao-themes-net/mate-theme-bundle[3.3.0, ..., 3.3.2] require contao/core-bundle ^5.0 -> found contao/core-bundle[5.0.0, ..., 5.3.7] but these were not loaded, likely because it conflicts with another require.
Problem 2
- contao/calendar-bundle 5.3.0 requires contao/core-bundle 5.3.0 -> found contao/core-bundle[5.3.0] but these were not loaded, likely because it conflicts with another require.
- contao/calendar-bundle 5.3.1 requires contao/core-bundle 5.3.1 -> found contao/core-bundle[5.3.1] but these were not loaded, likely because it conflicts with another require.
- contao/calendar-bundle 5.3.2 requires contao/core-bundle 5.3.2 -> found contao/core-bundle[5.3.2] but these were not loaded, likely because it conflicts with another require.
- contao/calendar-bundle 5.3.3 requires contao/core-bundle 5.3.3 -> found contao/core-bundle[5.3.3] but these were not loaded, likely because it conflicts with another require.
- contao/calendar-bundle 5.3.4 requires contao/core-bundle 5.3.4 -> found contao/core-bundle[5.3.4] but these were not loaded, likely because it conflicts with another require.
- contao/calendar-bundle 5.3.5 requires contao/core-bundle 5.3.5 -> found contao/core-bundle[5.3.5] but these were not loaded, likely because it conflicts with another require.
- contao/calendar-bundle 5.3.6 requires contao/core-bundle 5.3.6 -> found contao/core-bundle[5.3.6] but these were not loaded, likely because it conflicts with another require.
- contao/calendar-bundle 5.3.7 requires contao/core-bundle 5.3.7 -> found contao/core-bundle[5.3.7] but these were not loaded, likely because it conflicts with another require.
- Root composer.json requires contao/calendar-bundle ^5.3 -> satisfiable by contao/calendar-bundle[5.3.0, ..., 5.3.7].
[134.0MiB/10.67s] 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.
[54.8MiB/10.72s] Memory usage: 54.85MB (peak: 223.62MB), time: 10.73s.
[54.8MiB/10.72s] Finished Composer Cloud resolving.
# Cloud Job ID iJJPLWzTABNlKRisBICpjvjLFzLRrpli2MEwUOH6eu0Xuj9DHctFxvYcAFxv0bAAzzEl4wgkee2Q02uZMDvEpeOjWiTkNkET2DKme0HG failed
hosted auf alfahosting:
MySql 8.0, php 8.2.16
Packages:
mate-theme 2.20.5
rocksolid-slider 2.2.5
composer.json:
Code:
{
"type": "project",
"require": {
"contao-themes-net/mate-theme-bundle": "^3.3",
"contao/calendar-bundle": "^5.3",
"contao/comments-bundle": "^5.3",
"contao/conflicts": "@dev",
"contao/faq-bundle": "^5.3",
"contao/listing-bundle": "^5.3",
"contao/manager-bundle": "5.3.*",
"contao/news-bundle": "^5.3",
"contao/newsletter-bundle": "^5.3",
"madeyourday/contao-rocksolid-slider": "^2.2"
},
"extra": {
"public-dir": "public",
"contao-component-dir": "assets"
},
"scripts": {
"post-install-cmd": [
"@php vendor/bin/contao-setup"
],
"post-update-cmd": [
"@php vendor/bin/contao-setup"
]
}
}
Problem gelöst: Update von 4.13 auf 5.3 mit nur einer Extension
Ich hatte lediglich erdmannfreunde/contao-onepage-navigation als Extension installiert. Ich konnte das Update durchführen indem ich die Extensio im Manager entfernt, aber die Datenbank NICHT aktualisiert habe (so bleiben alle Einträge erhalten und die Artikel müssen nicht neu zugewiesen werden.)
Danach konnte ich reibungslos auf 5.3 aktualisieren, auch wieder OHNE die Datenbank zu aktualisieren. Danach Onepage-Navigation wieder installiert und zum Abschluss die Datenbank erneuert.
