I'm trying to require JMS/Serializer in a client Symfony 3.4 installation.
Even if I set "minimum-stability":"dev", I can't proceed.
I issued the following command php -d memory_limit=-1 composer.phar -v require jms/serializer-bundle jms/metadata jms/di-extra-bundle hoping to install all dependencies.
But this is the result:
Using version ^3.5#dev for jms/serializer-bundle
Using version ^2.0#dev for jms/metadata
Using version ^1.8#dev for jms/di-extra-bundle
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Dependency resolution completed in 0.623 seconds
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for jms/metadata ^2.0#dev -> satisfiable by jms/metadata[2.0.0, 2.0.0-RC1, 2.0.0-beta1, 2.1.0, 2.x-dev].
- jms/security-extra-bundle 1.6.1 requires jms/metadata ~1.0 -> satisfiable by jms/metadata[1.x-dev].
- jms/security-extra-bundle 1.6.1 requires jms/metadata ~1.0 -> satisfiable by jms/metadata[1.x-dev].
- jms/security-extra-bundle 1.6.1 requires jms/metadata ~1.0 -> satisfiable by jms/metadata[1.x-dev].
- Conclusion: don't install jms/metadata 1.x-dev
- Installation request for jms/security-extra-bundle 1.6.1 -> satisfiable by jms/security-extra-bundle[1.6.1].
Installation failed, reverting ./composer.json to its original content.
Already tried just issuing php -d memory_limit=-1 composer.phar -v require jms/serializer-bundle. Nothing change.
Note I'm using composer.phar at the last version, running with memory_limit=-1 cause composer fill all my 8G ram in seconds.
JMS/Serializer jms/metadata jms/di-extra-bundle, are included into Symfony 3.4 now.
you don't need install this package :)
Serializer for example : https://symfony.com/doc/current/components/serializer.html
Di-Extra-Bundle : https://symfony.com/doc/current/components/dependency_injection.html
Metadata : https://symfony.com/doc/current/components/validator/metadata.html
Related
We try to update from 2.4.2 to 2.4.4. (and tried to 2.4.3 as well) and as mentioned in the official docs, two steps should do it:
composer require magento/product-community-edition 2.4.4
composer update
On our installation, we get the following errors:
root#a9758412c9f0:/opt/bitnami/magento# composer require magento/product-community-edition 2.4.4 --update-with-all-dependencies
./composer.json has been updated
Running composer update magento/product-community-edition --with-all-dependencies
Loading composer repositories with package information
Info from https://repo.packagist.org: #StandWithUkraine
In Laminas\DependencyPlugin\DependencyRewriterV2::onPrePoolCreate
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.4.4 -> satisfiable by magento/product-community-edition[2.4.4].
- magento/magento-coding-standard is locked to version 6 and an update of this package was not requested.
- Conclusion: don't install webonyx/graphql-php v14.11.5 (conflict analysis result)
- Conclusion: don't install webonyx/graphql-php v14.11.6 (conflict analysis result)
- magento/product-community-edition 2.4.4 requires magento/framework 103.0.4 -> satisfiable by magento/framework[103.0.4].
- magento/magento-coding-standard 6 requires webonyx/graphql-php >=0.12.6 <1.0 -> satisfiable by webonyx/graphql-php[v0.12.6, ..., v0.13.9].
- You can only install one version of a package, so only one of these can be installed: webonyx/graphql-php[v0.12.6, ..., v0.13.9, v14.11.3, v14.11.4, v14.11.5, v14.11.6].
- magento/framework 103.0.4 requires webonyx/graphql-php ~14.11.3 -> satisfiable by webonyx/graphql-php[v14.11.3, v14.11.4, v14.11.5, v14.11.6].
- Conclusion: don't install webonyx/graphql-php v14.11.4 (conflict analysis result)
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
We tried to satisfy the dependencies manually by hand, but we saw way more errors at the end. Is there any Howto or Tutorial (apart from https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/implementation/perform-upgrade.html) about the process or does somebody experienced similar issues? Is it meant to be like this, to resolve dependencies by hand? Its pain and maybe we missed the proper way to do it?
I run this command:
COMPOSER_MEMORY_LIMIT=-1 composer require crscheid/php-article-extractor -vvv
Resolving dependencies through SAT
Dependency resolution completed in 0.044 seconds
Reading /root/.composer/cache/repo/https---repo.packagist.org/provider-scotteh$php-goose.json from cache
Reading /root/.composer/cache/repo/https---repo.packagist.org/provider-scotteh$php-goose.json from cache
Your requirements could not be resolved to an installable set of packages.
Problem 1
- crscheid/php-article-extractor 2.5.1 requires scotteh/php-goose dev-master -> satisfiable by scotteh/php-goose[dev-master] but these conflict with your requirements or minimum-stability.
- crscheid/php-article-extractor 2.5 requires scotteh/php-goose dev-master -> satisfiable by scotteh/php-goose[dev-master] but these conflict with your requirements or minimum-stability.
- Installation request for crscheid/php-article-extractor ^2.5 -> satisfiable by crscheid/php-article-extractor[2.5, 2.5.1].
Installation failed, reverting ./composer.json to its original content.
But this package won't be installed because it requires bigger composer version, my version is
Composer version 1.10.24 2021-12-09 20:06:33
can i still install it on this version, any help?
Solution:
Step 1:
COMPOSER_MEMORY_LIMIT=-1 composer require scotteh/php-goose dev-master
Step 2:
COMPOSER_MEMORY_LIMIT=-1 composer require crscheid/php-article-extractor
I'm trying to install domain-availability on the Laravel project but this is the result
PS C:\..\workspace v2> composer require helgesverre/domain-availability
Using version ^1.4 for helgesverre/domain-availability
./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
- helgesverre/domain-availability 1.4.0 requires jeremykendall/php-domain-parser ^3.0 -> satisfiable by jeremykendall/php-domain-parser[3.x-dev].
- helgesverre/domain-availability v1.4.1 requires jeremykendall/php-domain-parser ^3.0 -> satisfiable by jeremykendall/php-domain-parser[3.x-dev].
- Conclusion: don't install jeremykendall/php-domain-parser 3.x-dev
- Installation request for helgesverre/domain-availability ^1.4 -> satisfiable by helgesverre/domain-availability[1.4.0, v1.4.1].
Installation failed, reverting ./composer.json to its original content.
PS C:\..\workspace v2>
I'm using this library
https://github.com/HelgeSverre/Domain-Availability
and i activated extension=intl in php.ini file
and install jeremykendall/php-domain-parser using command
composer require jeremykendall/php-domain-parser
How do I solve this problem?
Having issues installing Google Cloud PHP client using Composer.
Any ideas how to best resolve the issues:
Using version ^0.33.1 for google/cloud
./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: google/auth[v1.0, v0.11.1].
- Can only install one of: google/auth[v1.0, v0.11.1].
- Can only install one of: google/auth[v1.0, v0.11.1].
- google/cloud v0.33.1 requires google/auth ^1.0 -> satisfiable by google/auth[v1.0].
- Installation request for google/cloud ^0.33.1 -> satisfiable by google/cloud[v0.33.1].
- Installation request for google/auth (locked at v0.11.1) -> satisfiable by google/auth[v0.11.1].
Installation failed, reverting ./composer.json to its original content.
sfbstack#villada:~/api/dev$
I try install https://github.com/google/google-api-php-client for my php project via composer.
composer.json:
{
"require": {
"Intervention/image": "~2.3.7",
"intervention/image": "^2.3",
"guzzlehttp/guzzle": "^6.2"
}
}
I run this command:
composer require google/apiclient:^2.0
And result:
./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
- google/apiclient v2.0.0 requires google/auth 0.8 -> satisfiable by google/auth[v0.8].
- Installation request for google/apiclient 2.0 -> satisfiable by google/apiclient[v2.0.0].
- Conclusion: remove guzzlehttp/psr7 1.3.0
- Conclusion: don't install guzzlehttp/psr7 1.3.0
- google/auth v0.8 requires guzzlehttp/psr7 1.2.* -> satisfiable by guzzlehttp/psr7[1.2.0, 1.2.1, 1.2.2, 1.2.3].
- Can only install one of: guzzlehttp/psr7[1.2.0, 1.3.0].
- Can only install one of: guzzlehttp/psr7[1.2.1, 1.3.0].
- Can only install one of: guzzlehttp/psr7[1.2.2, 1.3.0].
- Can only install one of: guzzlehttp/psr7[1.2.3, 1.3.0].
- Installation request for guzzlehttp/psr7 (locked at 1.3.0) -> satisfiable by guzzlehttp/psr7[1.3.0].
Installation failed, reverting ./composer.json to its original content.
Also I installed php composer.phar require guzzlehttp/guzzle before...
I would try removing your project's requirement of guzzlehttp/guzzle and let your Google dependency tell composer what version it wants to pull in. Google's package (for some reason) has a version floor of 1.2 for guzzlehttp/psr7, and composer is complaining that it can't figure out how to satisfy this requirement.
Since your new dependency (the Google package) also requires guzzlehttp/guzzle, you don't need to specifically require it, so I would just remove it and try composer update again.