Console task terminated! The background task has stopped unexpectedly.

[Preetz]

Hallo zusammen,

ich versuche gerade ein Update von 4.6.x auf 4.7 durchzuführen. Leider erhalte ich immer diesen Fehler:

> Resolving dependencies using Composer Cloud v2.0.8

[425.9MiB/6.76s] Loading composer repositories with package information
[426.3MiB/6.85s] Updating dependencies
[2045.1MiB/53.74s] Your requirements could not be resolved to an installable set of packages.
[2045.1MiB/53.75s] 
  Problem 1
    - The requested package contao/calendar-bundle (locked at 4.6.14, required as ^4.7) is satisfiable by contao/calendar-bundle[4.6.14] but these conflict with your requirements or minimum-stability.
  Problem 2
    - The requested package contao/comments-bundle (locked at 4.6.14, required as ^4.7) is satisfiable by contao/comments-bundle[4.6.14] but these conflict with your requirements or minimum-stability.
  Problem 3
    - The requested package contao/faq-bundle (locked at 4.6.14, required as ^4.7) is satisfiable by contao/faq-bundle[4.6.14] but these conflict with your requirements or minimum-stability.
  Problem 4
    - The requested package contao/listing-bundle (locked at 4.6.14, required as ^4.7) is satisfiable by contao/listing-bundle[4.6.14] but these conflict with your requirements or minimum-stability.
  Problem 5
    - The requested package contao/news-bundle (locked at 4.6.14, required as ^4.7) is satisfiable by contao/news-bundle[4.6.14] but these conflict with your requirements or minimum-stability.
  Problem 6
    - The requested package contao/newsletter-bundle (locked at 4.6.14, required as ^4.7) is satisfiable by contao/newsletter-bundle[4.6.14] but these conflict with your requirements or minimum-stability.

[2045.1MiB/53.75s] <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>
[719.8MiB/61.83s] Memory usage: 719.79MB (peak: 2773.15MB), time: 61.83s.
[719.8MiB/61.83s] Finished Composer Cloud resolving.


# Cloud Job ID LVkSL0SMXggyTOvaS8ncxFMLfzWNEngwZONmIpmiI6PZcaR6C17eYdCt7PAYzYWaREEeCGoL3kZboUr5EYW0kIwBB failed

---

### The background task has stopped unexpectedly ### 

Jemand einen Tipp für mich?

Vielen Dank,
Preetz

[xchs]

Poste mal Deine composer.json.

[Preetz]

gerne:

{
    "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": {
        "php": "^7.1",
        "contao-themes-net/mate-theme-bundle": "^1.5.8",
        "contao/calendar-bundle": "^4.7",
        "contao/comments-bundle": "^4.7",
        "contao/conflicts": "*@dev",
        "contao/faq-bundle": "^4.7",
        "contao/listing-bundle": "^4.7",
        "contao/manager-bundle": "4.7.*",
        "contao/news-bundle": "^4.7",
        "contao/newsletter-bundle": "^4.7"
    },
    "config": {
        "component-dir": "assets"
    },
    "extra": {
        "branch-alias": {
            "dev-4.6": "4.6.x-dev"
        }
    },
    "scripts": {
        "post-install-cmd": [
            "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
        ],
        "post-update-cmd": [
            "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
        ]
    }
} 

[xchs]

Hast Du alle Pakete zum Update ausgewählt und anschließend das Update ausgeführt?

[Preetz]

Im ersten Schritt hatte ich nur Core auf 4.7 geändert und aktualisiert. Dann im 2. Schritt - als ein Fehler kam - auch die Module.

[xchs]

Du musst wie schon gesagt alle gleichzeitig auswählen und dann den Updatejob starten.

Du könntest auch Deine aktuelle composer.lock z. B. in composer.lock.bak umbenennen und den Vorgang wiederholen.