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

dioscouri/omnipay-cybersource #22

Open
NarKarapetyan93 opened this issue Sep 30, 2016 · 5 comments
Open

dioscouri/omnipay-cybersource #22

NarKarapetyan93 opened this issue Sep 30, 2016 · 5 comments

Comments

@NarKarapetyan93
Copy link

I have some issues with integrating dioscouri/omnipay-cybersource in my laravel project.
I'm using laravel 5.1.*
I get this error.
screenshot_1

Here is my composer.json content

{ "name": "laravel/laravel", "description": "The Laravel Framework.", "keywords": ["framework", "laravel"], "license": "MIT", "type": "project", "require": { "php": ">=5.5.9", "laravel/framework": "5.1.*", "dioscouri/omnipay-cybersource": "~2.0" }, "require-dev": { "fzaninotto/faker": "~1.4", "mockery/mockery": "0.9.*", "phpunit/phpunit": "~4.0", "phpspec/phpspec": "~2.1" }, "autoload": { "classmap": [ "database" ], "psr-4": { "App\\": "app/" } }, "autoload-dev": { "classmap": [ "tests/TestCase.php" ] }, "scripts": { "post-root-package-install": [ "php -r \"copy('.env.example', '.env');\"" ], "post-create-project-cmd": [ "php artisan key:generate" ], "post-install-cmd": [ "Illuminate\\Foundation\\ComposerScripts::postInstall", "php artisan optimize" ], "post-update-cmd": [ "Illuminate\\Foundation\\ComposerScripts::postUpdate", "php artisan optimize" ] }, "config": { "preferred-install": "dist" } }

@kirkbushell
Copy link

You can't install due to your dependency settings. The "tag" is pointing to dev-master.

@sf71
Copy link

sf71 commented Jul 24, 2019

if anyone else is having this problem, you can bypass the stability requirements for a single package by adding @dev to the version number,
i.e.:
php composer.phar require dioscouri/omnipay-cybersource:~3.0@dev

(i don't like to edit the composer.json directly but that should work, too, just use ~3.0@dev instead of ~3.0)

@eileenmcnaughton
Copy link
Contributor

I added a release on github - not sure if that helps - oh - it should be 3.0.0 from the looks maybe?

@sf71
Copy link

sf71 commented Jul 24, 2019

my understanding (which is admittedly not very much) is that composer uses packagist.org to get the package. and if there is no "stable" release there then composer needs the @dev flag.

@eileenmcnaughton
Copy link
Contributor

ah of course!

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

4 participants