- Issue created by @trackleft2
- Merge request !81Issue #3501202 Fix conflict section of composer.json. β (Closed) created by trackleft2
- πΊπΈUnited States trackleft2 Tucson, AZ πΊπΈ
After removing the conflict section and running composer require drupal/viewsreferennce I did see that there was an old project with that name.
β viewsreference-2922687 git:(2922687-preselect-views-by) β lando composer require drupal/viewsreferennce ./composer.json has been updated Running composer update drupal/viewsreferennce No patches supplied. Loading composer repositories with package information Updating dependencies Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires drupal/viewsreferennce * -> satisfiable by drupal/viewsreferennce[1.0.0-alpha1, 1.0.0-alpha2]. - drupal/viewsreferennce[1.0.0-alpha1, ..., 1.0.0-alpha2] require drupal/core ~8.0 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev] but the package is fixed to 10.3.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. 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 drupal/viewsreferennce:*" to figure out if any version is installable, or "composer require drupal/viewsreferennce:^2.1" if you know which you need.
So, I'm going to close this issue as closed works as designed.
- π¬π§United Kingdom scott_euser
I think I went through the same thing when I first started helping out with the module :)