Code:
$ /usr/bin/php74 -q -dmax_execution_time=0 -dmemory_limit=-1 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /usr/www/users/baslerd/Droplimits2019/web/contao-manager.phar.php composer require contao/manager-bundle=4.13.* contao/news-bundle=4.13.* contao/calendar-bundle=4.13.* contao/faq-bundle=4.13.* contao/comments-bundle=4.13.* contao/newsletter-bundle=4.13.* contao/listing-bundle=4.13.* --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction
/usr/www/users/baslerd/Droplimits2019/composer.json has been updated
# 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.20s] Loading composer repositories with package information
[34.4MiB/11.01s] Updating dependencies
[96.6MiB/11.54s] Your requirements could not be resolved to an installable set of packages.
[96.6MiB/11.54s]
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.38].
- 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.38.
- 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.
[96.6MiB/11.54s] 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.
[16.1MiB/11.61s] Memory usage: 16.09MB (peak: 142.54MB), time: 11.62s.
[16.1MiB/11.61s] Finished Composer Cloud resolving.
# Cloud Job ID 8776uqrHZ3sRJxmkBng7M8eBCQWKQ6lvrJHO834stUb4del1iz1XXOKhqkEVlDmOD7u7TWi failed
Lesezeichen