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

Problems with installing library on Laravel 6.0 #2

Open
ramicbenjamin opened this issue Nov 11, 2019 · 3 comments
Open

Problems with installing library on Laravel 6.0 #2

ramicbenjamin opened this issue Nov 11, 2019 · 3 comments

Comments

@ramicbenjamin
Copy link

Hello,

I'm using "laravel/framework": "^6.0".

I wanted to try out how this library works and went with installing it using:

composer require vanderb/laravel-blinky

Even though I saw there is a commit a few days ago that updates this library for use on Laravel 6.0 it will not allow me to install it.

The error that I'm getting is:

Problem 1
    - Installation request for vanderb/laravel-blinky ^0.1.0 -> satisfiable by vanderb/laravel-blinky[0.1].
    - Conclusion: don't install laravel/framework v6.4.1
    - vanderb/laravel-blinky 0.1 requires illuminate/support 5.* -> satisfiable by illuminate/support[5.0.x-dev, 5.1.x-dev, 5.2.x-dev, 5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8, v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.4, v5.8.8, v5.8.9], laravel/framework[5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.x-dev, 5.8.x-dev].

Can you please take a look at it and see what the issue might be?

Thank you!

@ramicbenjamin
Copy link
Author

@vanderb did you get the chance to take a look at this issue? Thank you!

@vanderb
Copy link
Member

vanderb commented Nov 14, 2019

Hi @ramicbenjamin sorry, forgot to react on your question.

I changed the package-namespace to frogbob/laravel-blinky and published a new version 0.0.2 to handle Laravel 6.0

Sorry for change, but we've decided to reorganize our packages to our organization-namespace.

So you have to change your composer.json to
"frogbob/laravel-blinky": "0.0.2"

Change all namespaces in your laravel-application (Vanderb -> Frogbob) which may be in config/app.php

@ramicbenjamin
Copy link
Author

Thanks for looking into this issue @vanderb .

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

2 participants