Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

please supprt php8.2 #169

Open
phpmac opened this issue Apr 30, 2023 · 4 comments
Open

please supprt php8.2 #169

phpmac opened this issue Apr 30, 2023 · 4 comments

Comments

@phpmac
Copy link

phpmac commented Apr 30, 2023

➜  wallet git:(main) ✗ composer require iexbase/tron-api

Info from https://repo.packagist.org: #StandWithUkraine
./composer.json has been updated
Running composer update iexbase/tron-api
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 laravel/framework ^10.8, found laravel/framework[v10.8.0, v10.9.0, 10.x-dev] but the package is fixed to v9.52.7 (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.
  Problem 2
    - Root composer.json requires laravel/sanctum ^3.2, found laravel/sanctum[v3.2.0, ..., 3.x-dev] but the package is fixed to v2.15.1 (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.
  Problem 3
    - Root composer.json requires nunomaduro/collision ^7.0, found nunomaduro/collision[v7.0.0, ..., v7.x-dev] but the package is fixed to v6.4.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.
  Problem 4
    - Root composer.json requires phpunit/phpunit ^10.1, found phpunit/phpunit[dev-main, 10.1.0, ..., 10.2.x-dev (alias of dev-main)] but the package is fixed to 9.6.7 (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.
  Problem 5
    - Root composer.json requires spatie/laravel-ignition ^2.0, found spatie/laravel-ignition[2.0.0, 2.1.0] but the package is fixed to 1.6.4 (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.
  Problem 6
    - Root composer.json requires laravel/breeze ^1.20 -> satisfiable by laravel/breeze[v1.20.0, v1.20.1, v1.20.2, 1.x-dev].
    - laravel/breeze[v1.20.0, ..., 1.x-dev] require illuminate/console ^10.0 -> found illuminate/console[v10.0.0, ..., 10.x-dev] but these were not loaded, likely because it conflicts with another require.
  Problem 7
    - iexbase/tron-api[dev-master, v5.0] require comely-io/data-types ^1.0 -> satisfiable by comely-io/data-types[1.0.10, ..., 1.0.34].
    - iexbase/tron-api[dev-revert-35-fix_triggersmartcontract, v1.0, ..., v1.3.7, v2.0.1, ..., v2.0.7, v3.0, ..., v3.1.1] require php ^7.1 -> your php version (8.2.5) does not satisfy that requirement.
    - comely-io/data-types[1.0.10, ..., 1.0.33] require php ^7.1 -> your php version (8.2.5) does not satisfy that requirement.
    - iexbase/tron-api[dev-revert-79-master, v3.1.2] require php ^7.2 -> your php version (8.2.5) does not satisfy that requirement.
    - comely-io/data-types 1.0.34 require php ^7.2 -> your php version (8.2.5) does not satisfy that requirement.
    - iexbase/tron-api 4.0 requires php ^7.3 -> your php version (8.2.5) does not satisfy that requirement.
    - iexbase/tron-api 4.0.1 requires php ^7.4 -> your php version (8.2.5) does not satisfy that requirement.
    - Root composer.json requires iexbase/tron-api * -> satisfiable by iexbase/tron-api[dev-master, dev-revert-35-fix_triggersmartcontract, dev-revert-79-master, v1.0, ..., v1.3.7, v2.0.1, ..., v2.0.7, v3.0, v3.1.1, v3.1.2, 4.0, 4.0.1, v5.0, 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 iexbase/tron-api:*" to figure out if any version is installable, or "composer require iexbase/tron-api:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.
➜  wallet git:(main) ✗ composer require iexbase/tron-api:*
zsh: no matches found: iexbase/tron-api:*
➜  wallet git:(main) ✗ composer require "iexbase/tron-api:*"
./composer.json has been updated
Running composer update iexbase/tron-api
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 laravel/framework ^10.8, found laravel/framework[v10.8.0, v10.9.0, 10.x-dev] but the package is fixed to v9.52.7 (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.
  Problem 2
    - Root composer.json requires laravel/sanctum ^3.2, found laravel/sanctum[v3.2.0, ..., 3.x-dev] but the package is fixed to v2.15.1 (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.
  Problem 3
    - Root composer.json requires nunomaduro/collision ^7.0, found nunomaduro/collision[v7.0.0, ..., v7.x-dev] but the package is fixed to v6.4.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.
  Problem 4
    - Root composer.json requires phpunit/phpunit ^10.1, found phpunit/phpunit[dev-main, 10.1.0, ..., 10.2.x-dev (alias of dev-main)] but the package is fixed to 9.6.7 (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.
  Problem 5
    - Root composer.json requires spatie/laravel-ignition ^2.0, found spatie/laravel-ignition[2.0.0, 2.1.0] but the package is fixed to 1.6.4 (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.
  Problem 6
    - Root composer.json requires laravel/breeze ^1.20 -> satisfiable by laravel/breeze[v1.20.0, v1.20.1, v1.20.2, 1.x-dev].
    - laravel/breeze[v1.20.0, ..., 1.x-dev] require illuminate/console ^10.0 -> found illuminate/console[v10.0.0, ..., 10.x-dev] but these were not loaded, likely because it conflicts with another require.
  Problem 7
    - iexbase/tron-api[dev-master, v5.0] require comely-io/data-types ^1.0 -> satisfiable by comely-io/data-types[1.0.10, ..., 1.0.34].
    - iexbase/tron-api[dev-revert-35-fix_triggersmartcontract, v1.0, ..., v1.3.7, v2.0.1, ..., v2.0.7, v3.0, ..., v3.1.1] require php ^7.1 -> your php version (8.2.5) does not satisfy that requirement.
    - comely-io/data-types[1.0.10, ..., 1.0.33] require php ^7.1 -> your php version (8.2.5) does not satisfy that requirement.
    - iexbase/tron-api[dev-revert-79-master, v3.1.2] require php ^7.2 -> your php version (8.2.5) does not satisfy that requirement.
    - comely-io/data-types 1.0.34 require php ^7.2 -> your php version (8.2.5) does not satisfy that requirement.
    - iexbase/tron-api 4.0 requires php ^7.3 -> your php version (8.2.5) does not satisfy that requirement.
    - iexbase/tron-api 4.0.1 requires php ^7.4 -> your php version (8.2.5) does not satisfy that requirement.
    - Root composer.json requires iexbase/tron-api * -> satisfiable by iexbase/tron-api[dev-master, dev-revert-35-fix_triggersmartcontract, dev-revert-79-master, v1.0, ..., v1.3.7, v2.0.1, ..., v2.0.7, v3.0, v3.1.1, v3.1.2, 4.0, 4.0.1, v5.0, 9999999-dev].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.
➜  wallet git:(main) ✗ composer require "iexbase/tron-api:*"
./composer.json has been updated
Running composer update iexbase/tron-api
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - iexbase/tron-api[dev-master, v5.0] require comely-io/data-types ^1.0 -> satisfiable by comely-io/data-types[1.0.10, ..., 1.0.34].
    - iexbase/tron-api[dev-revert-35-fix_triggersmartcontract, v1.0, ..., v1.3.7, v2.0.1, ..., v2.0.7, v3.0, ..., v3.1.1] require php ^7.1 -> your php version (8.2.5) does not satisfy that requirement.
    - comely-io/data-types[1.0.10, ..., 1.0.33] require php ^7.1 -> your php version (8.2.5) does not satisfy that requirement.
    - iexbase/tron-api[dev-revert-79-master, v3.1.2] require php ^7.2 -> your php version (8.2.5) does not satisfy that requirement.
    - comely-io/data-types 1.0.34 require php ^7.2 -> your php version (8.2.5) does not satisfy that requirement.
    - iexbase/tron-api 4.0 requires php ^7.3 -> your php version (8.2.5) does not satisfy that requirement.
    - iexbase/tron-api 4.0.1 requires php ^7.4 -> your php version (8.2.5) does not satisfy that requirement.
    - Root composer.json requires iexbase/tron-api * -> satisfiable by iexbase/tron-api[dev-master, dev-revert-35-fix_triggersmartcontract, dev-revert-79-master, v1.0, ..., v1.3.7, v2.0.1, ..., v2.0.7, v3.0, v3.1.1, v3.1.2, 4.0, 4.0.1, v5.0, 9999999-dev].


Installation failed, reverting ./composer.json to its original content.
➜  wallet git:(main) ✗ composer require iexbase/tron-api --ignore-platform-reqs
./composer.json has been updated
Running composer update iexbase/tron-api
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - iexbase/tron-api[dev-master, v5.0] require iexbase/web3.php ^2.0.1 -> satisfiable by iexbase/web3.php[2.0.1].
    - iexbase/tron-api[dev-revert-35-fix_triggersmartcontract, v1.0, ..., v1.3.7, v2.0.1, ..., v2.0.7] require guzzlehttp/guzzle ^6.3 -> found guzzlehttp/guzzle[6.3.0, ..., 6.5.x-dev] but it conflicts with your root composer.json require (^7.2).
    - iexbase/tron-api[dev-revert-79-master, v3.0, ..., v3.1.2, 4.0, ..., 4.0.1] require kornrunner/secp256k1 ^0.1.2 -> found kornrunner/secp256k1[0.1.2] but it conflicts with your root composer.json require (^0.2.0).
    - iexbase/web3.php 2.0.1 requires phpseclib/phpseclib ~2.0.11 -> found phpseclib/phpseclib[2.0.11, ..., 2.0.x-dev] but it conflicts with your root composer.json require (^3.0).
    - Root composer.json requires iexbase/tron-api * -> satisfiable by iexbase/tron-api[dev-master, dev-revert-35-fix_triggersmartcontract, dev-revert-79-master, v1.0, ..., v1.3.7, v2.0.1, ..., v2.0.7, v3.0, v3.1.1, v3.1.2, 4.0, 4.0.1, v5.0, 9999999-dev].

You can also try re-running composer require with an explicit version constraint, e.g. "composer require iexbase/tron-api:*" to figure out if any version is installable, or "composer require iexbase/tron-api:^2.1" if you know which you need.

Installation failed, reverting ./composer.json to its original content.
➜  wallet git:(main) ✗ composer require iexbase/tron-api:^2.1
./composer.json has been updated
Running composer update iexbase/tron-api
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 iexbase/tron-api ^2.1, found iexbase/tron-api[dev-master, dev-revert-35-fix_triggersmartcontract, dev-revert-79-master, v1.0, ..., v1.3.7, v2.0.1, ..., v2.0.7, v3.0, v3.1.1, v3.1.2, 4.0, 4.0.1, v5.0] but it does not match the constraint.


Installation failed, reverting ./composer.json to its original content.
➜  wallet git:(main) ✗ 

@phpmac phpmac closed this as completed May 7, 2023
@phpmac phpmac reopened this May 7, 2023
@farshidpg
Copy link

I have same issue

@skyfiress
Copy link

skyfiress commented Aug 12, 2023

I have same issue +1

2 similar comments
@mr-mr7
Copy link

mr-mr7 commented Jun 17, 2024

I have same issue +1

@samehdoush
Copy link

I have same issue +1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants