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.
Related
I've installed Magento with sample data on a virtual machine. Now I'm trying to install Live Search for it. I used the instructions from this link. As the instruction says, I run the command below:
composer require magento/live-search
But it gives me an error:
Problem 1
- magento/live-search 2.0.0 requires magento/module-live-search-metrics 2.0.0 -> could not be found in any version, there may be a typo in the package name.
- magento/live-search 2.0.1 requires magento/module-live-search-metrics 2.0.1 -> could not be found in any version, there may be a typo in the package name.
- magento/live-search 2.0.2 requires magento/module-live-search-metrics 2.0.2 -> could not be found in any version, there may be a typo in the package name.
- magento/live-search 2.0.3 requires magento/module-live-search-metrics 2.0.3 -> could not be found in any version, there may be a typo in the package name.
- Root composer.json requires magento/live-search ^2.0 -> satisfiable by magento/live-search[2.0.0, 2.0.1, 2.0.2, 2.0.3].
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.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require magento/live-search:*" to figure out if any version is installable, or "composer require magento/live-search:^2.1" if you know which you need.
As I can see, it says magento/module-live-search-metrics does not exist, but I couldn't find anyone else who has the same problem as mine, which means this is only my problem.
You just have to type:
composer require magento/module-live-search
and that's it =)
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
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
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.
How to set up and use laravel shibboleth package,
supposing that in my organization there are distinct user roles? My version of Laravel Framework is 5.7.26. I initially tried to install it (with composer require razorbacks/laravel-shibboleth via cmd) with no success.
Below is the result of my attempt to install it. Any idea?
" Problem 1
- Installation request for razorbacks/laravel-shibboleth ^3.0
-> satisfiable by razorbacks/laravel-shibboleth[3.0.0].
- Conclusion: remove laravel/framework v5.7.26
- Conclusion: don't install laravel/framework v5.7.26
- razorbacks/laravel-shibboleth 3.0.0 requires laravel/framework 5.4.* || 5.5.*
-> satisfiable by laravel/framework[5.4.x-dev, 5.5.x-dev].
- Can only install one of: laravel/framework[5.4.x-dev, v5.7.26].
- Can only install one of: laravel/framework[5.5.x-dev, v5.7.26].
- Installation request for laravel/framework (locked at v5.7.26, required as 5.7.*)
-> satisfiable by laravel/framework[v5.7.26].
Installation failed, reverting ./composer.json to its original content."
Depending on your project it might be easiest to downgrade your Laravel framework version to 5.5. You'll see on the razorbacks/laravel-shibboleth packagist page that it requires Laravel 5.4 or 5.5. On the package's github profile you'll see that there's an issue logged for Laravel 5.6 support and that the latest commit was on 25 Jan 2018, so it is not very up to date. I recommend always checking these things before deciding on using a package.
To downgrade to Laravel 5.5, you'll need to change your composer.json file to to require "laravel/framework": "5.5.*". You'll also need to check that all your other dependencies are compatible with 5.5. If they are not, you'll also need to downgrade them to compatible versions.
Lastly, consider using uabookstores/laravel-shibboleth or prasad/laravel-shibboleth which are forks of razorbacks/laravel-shibboleth that have Laravel 5.7 support.
You can downgrade laravel. Or you can fork shibboleth, change the composer.json requirements/limits, then start testing to see if the package works with 5.7
fork this into your github account https://github.com/razorbacks/laravel-shibboleth
clone your new forked copy to local work machine
edit composer.json to adjust limits/requirements
commit and push back to your forked copy
Now, in your project that uses the package you'll need to point to your copy/fork instead of the original public version of the package.
add your fork to the "repositories" section of composer.json (NOT the same composer.json ... this is the laravel project composer.json)
run composer update
Your new repositories section in the composer.json file should look something like this...
"repositories": [
{
"type": "vcs",
"url": "https://github.com/YOUR-ACCOUNT-NAME/laravel-shibboleth"
}]