Skip to content

Unable to install composer require typicms/pages and composer require typicms/menus and maybe so on #272

@verontheservant

Description

@verontheservant

With laravel 10.10
composer require typicms/menus
./composer.json has been updated
Running composer update typicms/menus
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- typicms/menus[1.8.0, ..., v1.8.6] require typicms/core ~1.8.0 -> found typicms/core[1.8.0, ..., v1.8.7] but it conflicts with your root composer.json require (^11.0.0).
- typicms/menus[v2.0.0, ..., v2.0.20] require typicms/core ~2.0.0 -> found typicms/core[v2.0.0, ..., v2.0.30] but it conflicts with your root composer.json require (^11.0.0).
- typicms/menus[v2.1.0, ..., v2.1.2] require typicms/core ~2.1.0 -> found typicms/core[v2.1.0, ..., v2.1.8] but it conflicts with your root composer.json require (^11.0.0).
- typicms/menus[v2.2.0, ..., v2.2.1] require typicms/core ~2.2.0 -> found typicms/core[v2.2.0, v2.2.1, v2.2.2] but it conflicts with your root composer.json require (^11.0.0).
- typicms/menus v2.3.0 requires typicms/core ~2.3.0 -> found typicms/core[v2.3.0, v2.3.1, v2.3.2] but it conflicts with your root composer.json require (^11.0.0).
- typicms/menus[v2.4.0, ..., v2.4.7] require typicms/core ~2.4.0 -> found typicms/core[v2.4.0, ..., v2.4.27] but it conflicts with your root composer.json require (^11.0.0).
- typicms/menus[2.5.0, ..., 2.5.5] require typicms/core ~2.5.0 -> found typicms/core[2.5.0, ..., 2.5.13] but it conflicts with your root composer.json require (^11.0.0).
- typicms/menus 2.6.0 requires typicms/core ~2.6.0 -> found typicms/core[2.6.0, ..., 2.6.6] but it conflicts with your root composer.json require (^11.0.0).
- typicms/menus[2.7.0, ..., 2.7.1] require typicms/core ~2.7.0 -> found typicms/core[2.7.0, ..., 2.7.33] but it conflicts with your root composer.json require (^11.0.0).
- typicms/menus[2.8.0, ..., 2.8.2] require typicms/core ~2.8.0 -> found typicms/core[2.8.0, ..., 2.8.9] but it conflicts with your root composer.json require (^11.0.0).
- typicms/menus[2.9.0, ..., 2.9.2] require typicms/core ~2.9.0 -> found typicms/core[2.9.0, 2.9.1, 2.9.2, 2.9.3] but it conflicts with your root composer.json require (^11.0.0).
- typicms/menus[3.0.0, ..., 3.0.5, 4.0.0, ..., 4.0.2] require laravel/framework ~5.5.0 -> found laravel/framework[v5.5.0, ..., v5.5.50] but it conflicts with your root composer.json require (^10.10).
- typicms/menus[5.0.0, ..., 5.0.8] require laravel/framework ~5.7.0 -> found laravel/framework[v5.7.0, ..., v5.7.29] but it conflicts with your root composer.json require (^10.10).
- typicms/menus[6.0.0, ..., 6.0.3] require laravel/framework ~5.8.0 -> found laravel/framework[v5.8.0, ..., v5.8.38] but it conflicts with your root composer.json require (^10.10).
- typicms/menus[7.0.0, ..., 7.0.6] require laravel/framework ~6.0 -> found laravel/framework[v6.0.0, ..., v6.20.44] but it conflicts with your root composer.json require (^10.10).
- typicms/menus[8.0.0, ..., 8.0.2, 9.0.0, ..., 9.0.12] require laravel/framework ~8.0 -> found laravel/framework[v8.0.0, ..., v8.83.27] but it conflicts with your root composer.json require (^10.10).
- Root composer.json requires typicms/menus * -> satisfiable by typicms/menus[1.8.0, 1.8.1, v1.8.5, v1.8.6, v2.0.0, ..., 2.9.2, 3.0.0, ..., 3.0.5, 4.0.0, 4.0.1, 4.0.2, 5.0.0, ..., 5.0.8, 6.0.0, 6.0.1, 6.0.2, 6.0.3, 7.0.0, ..., 7.0.6, 8.0.0, 8.0.1, 8.0.2, 9.0.0, ..., 9.0.12].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require typicms/menus:*" to figure out if any version is installable, or "composer require typicms/menus:^2.1" if you know which you need.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions