Can't install/update modules on Drupal 8.9.6 with composer 2.0 - composer-php

I'm trying to install a module on a Drupal 8.9.6 using composer 2.0 but I get the next error:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- cweagans/composer-patches 1.6.7 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.
- drupal/varbase_heroslider_media 7.13.0 requires cweagans/composer-patches ~1.0 -> satisfiable by cweagans/composer-patches[1.6.7].
- drupal/varbase_heroslider_media is locked to version 7.13.0 and an update of this package was not requested.
You are using Composer 2, which some of your plugins seem to be incompatible with. Make sure you update your plugins or report a plugin-issue to ask them to support Composer 2.
Then, I've tried to update cweagans/composer-patches to 1.7 because this issue was solved here. But I get the next error:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- drupal/drupal-library-installer-plugin 0.3 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.
- drupal/varbase_heroslider_media 7.13.0 requires drupal/drupal-library-installer-plugin ^0.3 -> satisfiable by drupal/drupal-library-installer-plugin[0.3].
- drupal/varbase_heroslider_media is locked to version 7.13.0 and an update of this package was not requested.
You are using Composer 2, which some of your plugins seem to be incompatible with. Make sure you update your plugins or report a plugin-issue to ask them to support Composer 2.
Ok, then, I've tried to update drupal/drupal-library-installer-plugin I get again the first error. It is a circle and I can't update Drupal.
How could I do it?

drupal/drupal-library-installer-plugin has not seen any updates since more than five years(!). Either search for an alternative, or downgrade Composer to v1

Related

Trying to configure MAMP for Magento

I'm working to install Magento 2 on my Mac so I can develop with JetBrains PhpStorm and exchange with my company's server.
I've got MAMP installed and but in working to install Magento 2.3.5-p1, I needs some php extensions set and I'm not certain how to do this.
I need intl, ext-zip and possibly others on. This is what I'm seeing:
composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition=2.3.5-p1
Creating a "magento/project-community-edition=2.3.5-p1" project at "./project-community-edition"
Installing magento/project-community-edition (2.3.5-p1)
Installing magento/project-community-edition (2.3.5-p1): Extracting archive
Created project in /Applications/MAMP/htdocs/project-community-edition
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 magento/product-community-edition 2.3.5-p1 -> satisfiable by magento/product-community-edition[2.3.5-p1].
- magento/product-community-edition 2.3.5-p1 requires ext-intl * -> it is missing from your system. Install or enable PHP's intl extension.
Problem 2
- Root composer.json requires dealerdirect/phpcodesniffer-composer-installer ^0.5.0 -> satisfiable by dealerdirect/phpcodesniffer-composer-installer[v0.5.0].
- dealerdirect/phpcodesniffer-composer-installer v0.5.0 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.
Problem 3
- magento/magento2-functional-testing-framework[2.6.4, ..., 2.6.6] require php-webdriver/webdriver ^1.8.0 -> satisfiable by php-webdriver/webdriver[1.8.0, ..., 1.10.0].
- php-webdriver/webdriver[1.8.0, ..., 1.10.0] require ext-zip * -> it is missing from your system. Install or enable PHP's zip extension.
- Root composer.json requires magento/magento2-functional-testing-framework ~2.6.4 -> satisfiable by magento/magento2-functional-testing-framework[2.6.4, 2.6.5, 2.6.6].
You are using Composer 2, which some of your plugins seem to be incompatible with. Make sure you update your plugins or report a plugin-issue to ask them to support Composer 2.
Thanks.

Cyber-duck Installation failed, reverting in Laravel-8

I had earlier installed maatwebsite/excel-3.1, and it was okay. I have Laravel-8 and PHP-7.3 and I am trying to install cyber-duck:
composer require cyber-duck/laravel-excel
But I got this error:
Your requirements could not be resolved to an installable set of packages.
Problem 1
Root composer.json requires cyber-duck/laravel-excel ^2.1 -> >satisfiable by cyber-duck/laravel-excel[2.1.0].
cyber-duck/laravel-excel 2.1.0 requires illuminate/database >^6.0.0|^7.0.0 -> found illuminate/database[v6.0.0, ..., 6.x-dev, v7.0.0, >..., 7.x-dev] but these were not loaded, likely because it conflicts with >another require.
How do I resolve this?
Thanks
As far as release versions of cyber-duck/laravel-excel are concerned, the latest version of the package (commit: b98ad4d) is only supporting Laravel version 7.x.
https://github.com/Cyber-Duck/laravel-excel/releases
So, either you have to downgrade your Laravel version or wait for the latest release version which supports Laravel version 8.x.

Problem in installing elasticsearch for Laravel

When I tried to install Elasticsearch for my Laravel instance using the following command:
composer require elasticsearch/elasticsearch
I got this error:
Problem 1
- elasticsearch/elasticsearch v7.6.0 requires guzzlehttp/ringphp dev-fork-elasticsearch -> no matching package found.
- tamayo/laravel-scout-elastic 5.0.0 requires elasticsearch/elasticsearch ^5.0 -> satisfiable by
elasticsearch/elasticsearch[5.0.x-dev].
- tamayo/laravel-scout-elastic 5.0.0 requires elasticsearch/elasticsearch ^5.0 -> satisfiable by
elasticsearch/elasticsearch[5.0.x-dev].
- tamayo/laravel-scout-elastic 5.0.0 requires elasticsearch/elasticsearch ^5.0 -> satisfiable by
elasticsearch/elasticsearch[5.0.x-dev].
- Can only install one of: elasticsearch/elasticsearch[v7.6.1, 5.0.x-dev].
- Installation request for elasticsearch/elasticsearch ^7.6 -> satisfiable by elasticsearch/elasticsearch[v7.6.0, v7.6.1].
- Installation request for tamayo/laravel-scout-elastic ^5.0 -> satisfiable by tamayo/laravel-scout-elastic[5.0.0].
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting see
https://getcomposer.org/doc/04-schema.md#minimum-stability for more
details.
- It's a private package and you forgot to add a custom repository to find it
Read https://getcomposer.org/doc/articles/troubleshooting.md for
further common problems.
Installation failed, reverting ./composer.json to its original
content.
then I tried to install the package mentioned in the error using the following command:
composer require guzzlehttp/ringphp
and I got the following warning:
Package guzzlehttp/ringphp is abandoned, you should avoid using it. No
replacement was suggested. Package guzzlehttp/streams is abandoned,
you should avoid using it. No replacement was suggested
Then I tried to install it again, and I got the same error.
What can I do to address the problem?
Please simply try installing it again - according to Packagist, there is a version 7.6.1 available that does not depend on such packages any more. This is something you can also find on https://github.com/elastic/elasticsearch-php/releases

How to fix 'Your requirements could not be resolved to an installable set of packages.' in laravel boiler templage

I am going to develop laravel project with boiler template.
I want to have multiple themes.
So, I try to install shipu/themevel package. However composer require shipu/themevel, this command has error like this. Please help me.
Using version ^1.6 for `shipu/themevel
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Can only install one of: hassankhan/config[0.11.2, 0.10.0].
- Can only install one of: hassankhan/config[0.10.0, 0.11.2].
- Can only install one of: hassankhan/config[0.10.0, 0.11.2].
- shipu/themevel v1.6 requires hassankhan/config ^0.10.0 -> satisfiable by hassankhan/config[0.10.0].
- Installation request for shipu/themevel ^1.6 -> satisfiable by shipu/themevel[v1.6].
- Installation request for hassankhan/config (locked at 0.11.2) -> satisfiable by hassankhan/config[0.11.2].
Installation failed, reverting ./composer.json to its original content.
you have to update the higher version of shipu/themevel. please update v2.1 or higher.

issue with Userfrosting & Composer - no matching packages

Just working my way through the Userfrosting 4 tutorial. The basic app is up and running and am now creating the first sprinkle under "Your First UserFrosting Site".
On running composer update I get the following:
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- userfrosting/config dev-master requires userfrosting/support ^4.0.0 -> no matching package found.
- userfrosting/config dev-master requires userfrosting/support ^4.0.0 -> no matching package found.
- Installation request for userfrosting/config dev-master -> satisfiable by userfrosting/config[dev-master].
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
I've replaced my code with the copied / pasted code from the tutorial and still get the errors. I've absolutely no idea where to go from here - any pointers would be appreciated.
Make sure you have the latest version (4.0.11-alpha as of now) since the component versioning was changed/fixed in a recent version.
The core composer.json file shoudn't use the dev-master version of userfrosting/config component anymore, but one of the 4.0.x version. See : https://github.com/userfrosting/UserFrosting/blob/master/app/sprinkles/core/composer.json#L31. If you have a custom ^composer.json` file in your sprinkle, you don't need to add the packages define in the core composer file again.
That being said, if you're still having some issues, you can try running composer clear-cache as composer might have cached some outdated info.

Resources