problem installing with akeneo v2.3.28

[travnewmatic]

tried installing via

composer.phar require flagbit/product-cloner-bundle

but got

Reading composer.json of akeneo/pim-community-dev (v3.0.18)GitHub API limit (60 calls/hr) is exhausted, could not fetch https://api.github.com/repos/akeneo/pim-community-dev/commits/c7ff0e5258d2e8af6c82972f73598c415a66e0fa. Create a GitHub OAuth token to go over the API rate limit. You can also wait until 2019-07-12 07:38:38 for the rate limit to reset.                                                                    

Head to https://github.com/settings/tokens/new?scopes=repo&description=Composer+on+dev-44+2019-07-12+0638
to retrieve a token. It will be stored in "/root/.config/composer/auth.json" for future use by Composer.
Token (hidden):
Token stored successfully.
Using version ^3.0 for flagbit/product-cloner-bundle
./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
    - Installation request for flagbit/product-cloner-bundle ^3.0 -> satisfiable by flagbit/product-cloner-bundle[v3.0.0].                                                                                         
    - flagbit/product-cloner-bundle v3.0.0 requires akeneo/pim-community-dev ^3.0 -> satisfiable by akeneo/pim-community-dev[3.0.x-dev, 3.1.x-dev, 3.2.x-dev, v3.0.0, v3.0.1, v3.0.10, v3.0.11, v3.0.12, v3.0.13, v3.0.14, v3.0.15, v3.0.16, v3.0.17, v3.0.18, v3.0.19, v3.0.2, v3.0.20, v3.0.21, v3.0.22, v3.0.23, v3.0.24, v3.0.25, v3.0.26, v3.0.27, v3.0.28, v3.0.29, v3.0.3, v3.0.30, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.0-BETA1, v3.1.1, v3.1.10, v3.1.11, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9] but these conflict with your requirements or minimum-stability.                                 


Installation failed, reverting ./composer.json to its original content.

is there a different method i should be using for akeneo v2.3.28?

Thanks!

[amansilla]

Will close this issue is not related to the extension. You just need to generate a github token as indicated in the error.

Head to https://github.com/settings/tokens/new?scopes=repo&description=Composer+on+dev-44+2019-07-12+0638 to retrieve a token.

Then just try again.

Please don't forget to 🌟 the repo if you like it!

[travnewmatic]

It is not related to an access token.

A good token was provided. It says 'token stored successfully'

The issue has to do with a version mismatch, or at least it's not properly installing with our current akeneo version.

[amansilla]

Hi @travnewmatic, sorry my error, didn't notice it. I'll take care why isn't that working I'm not sure if is our issue or a composer issue.

In the mean time you can try installing the module with composer.phar require flagbit/product-cloner-bundle:^1.1 and let me know if it's working.

[travnewmatic]

thanks so much for the response, that appears to have completed without error.

i'll have my teammate check in the backend to see if things are showing up properly.

[gldt-arandazzo]

Came here as I had the same problem. May want to update the listing in the Akeneo extension store for users on 2.3.

[amansilla]

@glo-arandazzo what is exactly the command you used for updating the module? It's interesting for me, since I'm not 100% sure if the issue is related to our extension or composer itself. I must go a bit deeper to find what exactly the issue is.