CyberSource / CyberSource/cybersource-rest-client-php
dependency error with firebase/php-jwt and other packages
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 41
- Forks
- 77
- Avg merge
- 26m
- Merged PRs (30d)
- 1
Description
I am not able to install the package because of dependency version error with many packages.
Problem 1
- cybersource/rest-client-php[dev-december-release-2023, dev-master, dev-adding-disclaimer-in-beta-apis, 0.0.41, ..., 0.0.46] require cache/apcu-adapter >=1.1.0 -> satisfiable by cache/apcu-adapter[1.1.0, 1.1.x-dev, 1.2.0, 1.3.0].
- cybersource/rest-client-php[dev-generator-with-logging-and-masking, 0.0.1, ..., 0.0.16] require firebase/php-jwt 5.0.0 -> found firebase/php-jwt[v5.0.0] but the package is fixed to v6.10.0 (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.
- cybersource/rest-client-php[dev-test-fix-empty-body-param, dev-travis-trial, dev-transient_token, dev-masking-fix, dev-sensitive-logging, dev-logging-issue, 0.0.17, ..., 0.0.40] require firebase/php-jwt ^5.0.0 -> found firebase/php-jwt[v5.0.0, ..., v5.5.1] but the package is fixed to v6.10.0 (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.
- cache/apcu-adapter 1.1.0 requires psr/cache ^1.0 -> found psr/cache[1.0.0, 1.0.1] but the package is fixed to 3.0.0 (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.
- cache/apcu-adapter[1.1.x-dev, ..., 1.3.0] require psr/cache ^1.0 || ^2.0 -> found psr/cache[1.0.0, 1.0.1, 2.0.0] but the package is fixed to 3.0.0 (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.
- Root composer.json requires cybersource/rest-client-php * -> satisfiable by cybersource/rest-client-php[dev-generator-with-logging-and-masking, dev-test-fix-empty-body-param, dev-masking-fix, dev-sensitive-logging, dev-logging-issue, dev-transient_token, dev-travis-trial, dev-december-release-2023, dev-master, dev-adding-disclaimer-in-beta-apis, 0.0.1, ..., 0.0.46, 9999999-dev].
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 cybersource/rest-client-php:*" to figure out if any version is installable, or "composer require cybersource/rest-client-php:^2.1" if you know which you need.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named; start by reproducing the Composer installation failure from the dependency output and inspect the package constraints for firebase/php-jwt, cache/apcu-adapter, and psr/cache. Done would mean documenting or resolving a compatible dependency set that allows cybersource/rest-client-php to install without the reported lock-file conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100