I am new to the whole composer situation.
i am using laravel5.1, and i am trying to upgrade to laravel 5.2
I have updated the composer.json file to reflect as such, i then run
composer update
I get the following error
rappasoft/vault dev-master requires illuminate/support 5.1.* -> satisfiable by laravel/framework[v5.1.40], illuminate/support[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.6, v5.1.8].
- rappasoft/vault dev-master requires illuminate/support 5.1.* -> satisfiable by laravel/framework[v5.1.40], illuminate/support[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.6, v5.1.8].
So i understand the package doesn't support laravel 5.2, so i went to the vendor/rappasoft/vault/composer.json file and updated that to say it could support 5.2 but that didn't work.
Whats the best way to move forward? the rappasoft/vault package is no longer supported, but its heavily embedded in the project i am working on, so i will be upgrading it myself.. i just don't know what the best move forward is.
Thoughts?
Related
I'm trying to run composer require symfony/mailer to use it in Symfony 4 project, but it returns an error :
Your requirements could not be resolved to an installable set of packages.
Problem 1
- symfony/mailer[v5.4.0, ..., v5.4.8] require symfony/mime ^5.2.6|^6.0 -> found symfony/mime[v5.2.6, ..., v5.4.9, v6.0.0, ..., v6.1.1] but the package is fixed to v4.4.42 (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 symfony/mailer ^5.4 -> satisfiable by symfony/mailer[v5.4.0, ..., v5.4.8].
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.
And when I run composer -vvv --no-plugins require --no-scripts -W symfony/mailer I got this :
Problem 1
- symfony/mailer[v5.4.0, v5.4.2, v5.4.3, v5.4.5, v5.4.7, v5.4.8] require
symfony/mime ^5.2.6|^6.0 -> satisfiable by symfony/mime[v5.2.6,
v5.2.7, v5.2.9, v5.2.10, v5.2.11, v5.2.12, v5.3.0, v5.3.2, v5.3.4,
v5.3.7, v5.3.8, v5.3.11
, v5.3.13, v5.3.14, v5.4.0, v5.4.2, v5.4.3, v5.4.7, v5.4.8, v5.4.9,
v6.0.0, v6.0.1, v6.0.2, v6.0.3, v6.0.7, v6.0.8, v6.0.9, v6.1.0,
v6.1.1].
- __root__ dev-develop conflicts with symfony/mime v5.3.7.
- __root__ dev-develop conflicts with symfony/mime v5.3.8.
- __root__ dev-develop conflicts with symfony/mime v5.3.2.
- __root__ dev-develop conflicts with symfony/mime v5.3.4.
- __root__ dev-develop conflicts with symfony/mime v5.3.0.
- __root__ dev-develop conflicts with symfony/mime v5.2.12.
- __root__ dev-develop conflicts with symfony/mime v5.2.11.
- __root__ dev-develop conflicts with symfony/mime v5.2.10.
- __root__ dev-develop conflicts with symfony/mime v5.4.9.
- __root__ dev-develop conflicts with symfony/mime v5.4.7.
- __root__ dev-develop conflicts with symfony/mime v5.4.8.
- __root__ dev-develop conflicts with symfony/mime v5.4.2.
- __root__ dev-develop conflicts with symfony/mime v5.4.3.
- __root__ dev-develop conflicts with symfony/mime v5.4.0.
- __root__ dev-develop conflicts with symfony/mime v5.2.7.
- __root__ dev-develop conflicts with symfony/mime v5.2.9.
- __root__ dev-develop conflicts with symfony/mime v5.2.6.
- __root__ dev-develop conflicts with symfony/mime v5.3.11.
- __root__ dev-develop conflicts with symfony/mime v5.3.13.
- __root__ dev-develop conflicts with symfony/mime v5.3.14.
- symfony/mime[v6.0.0, v6.0.1, v6.0.2, v6.0.3, v6.0.7, v6.0.8, v6.0.9] require php >=8.0.2 -> your php version (7.3.21) does not satisfy that requirement.
- symfony/mime[v6.1.0, v6.1.1] require php >=8.1 -> your php version (7.3.21) does not satisfy that requirement.
- __root__ is present at version dev-develop and cannot be modified by Composer
- Root composer.json requires symfony/mailer ^5.4 -> satisfiable by symfony/mailer[v5.4.0, v5.4.2, v5.4.3, v5.4.5, v5.4.7, v5.4.8].
Any idea how to solve it ?
symfony/mailer is fixed/locked to v4.4.42 in your project.
Run the Composer require command with --with-all-dependencies (-W) to see if it solves your problem:
composer require -W symfony/mailer
symfony/mailer is the only problem you have with your (current) lock file.
I am trying to install the hyn/multi-tenant package in a Laravel 8 project. However when executing the composer require hyn/multi-tenant command, the following error is shown:
Problem 1
- Installation request for laravel/framework (locked at v8.11.2, required as ^8.0) -> satisfiable by laravel/framework[v8.11.2].
- hyn/multi-tenant 5.6.0 requires laravel/framework ^7.0 -> satisfiable by laravel/framework[7.x-dev].
- hyn/multi-tenant 5.6.1 requires laravel/framework ^7.0 -> satisfiable by laravel/framework[7.x-dev].
- hyn/multi-tenant 5.6.2 requires laravel/framework ^7.0 -> satisfiable by laravel/framework[7.x-dev].
- hyn/multi-tenant 5.6.3 requires laravel/framework ^7.0 -> satisfiable by laravel/framework[7.x-dev].
- hyn/multi-tenant 5.6.4 requires laravel/framework ^7.0 -> satisfiable by laravel/framework[7.x-dev].
- hyn/multi-tenant 5.x-dev requires laravel/framework ^7.0 -> satisfiable by laravel/framework[7.x-dev].
- Conclusion: don't install laravel/framework 7.x-dev
- Installation request for hyn/multi-tenant ^5.6 -> satisfiable by hyn/multi-tenant[5.6.0, 5.6.1, 5.6.2, 5.6.3, 5.6.4, 5.x-dev].
Does anyone have an idea how to solve?
This means that the project is not supporting Laravel 8 yet. If you were to look at the source code in GitHub you can also see that the latest commit was months ago. https://github.com/tenancy/multi-tenant
I would suggest using an another package for your tenancy needs, since this one doesn't seem to be maintained well.
Lately I've been doing some testing with https://tenancyforlaravel.com/, it look pretty promising.
In my Laravel 5.6 application I tried to install laravel-setup-wizard
plugin and got error :
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for marvinlabs/laravel-setup-wizard ^0.2.1 -> satisfiable by marvinlabs/laravel-setup-wizard[0.2.1].
- Conclusion: remove laravel/framework v5.6.33
- Conclusion: don't install laravel/framework v5.6.33
- marvinlabs/laravel-setup-wizard 0.2.1 requires illuminate/support 5.4.* -> satisfiable by illuminate/support[5.4.x-dev, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9].
- illuminate/support 5.4.x-dev conflicts with laravel/framework[v5.6.33].
- illuminate/support v5.4.0 conflicts with laravel/framework[v5.6.33].
- illuminate/support v5.4.13 conflicts with laravel/framework[v5.6.33].
- illuminate/support v5.4.17 conflicts with laravel/framework[v5.6.33].
- illuminate/support v5.4.19 conflicts with laravel/framework[v5.6.33].
- illuminate/support v5.4.27 conflicts with laravel/framework[v5.6.33].
- illuminate/support v5.4.36 conflicts with laravel/framework[v5.6.33].
- illuminate/support v5.4.9 conflicts with laravel/framework[v5.6.33].
- Installation request for laravel/framework (locked at v5.6.33, required as 5.6.*) -> satisfiable by laravel/framework[v5.6.33].
Installation failed, reverting ./composer.json to its original content.
I have :
$ php artisan --version
Laravel Framework 5.6.33
1) Does it mean that this plugin is not suitable for laravel 5.6 project?
If there is a way to install it somehow?
2) Can you advice some plugin/script compatible with bootstrap 4.1 ?
Thanks!
Yes this means it is compatible with Laravel 5.4 and not with 5.6.
I scrolled through the readme, didn't really do any real research, but i found this:
Credits:
Some code is taken from another similar project: RachidLaasri/LaravelInstaller
Maybe take a look there?
EDIT: I see now that the code has not been updated for over a year. Maybe it is not the best decision to look at libraries which are not in active development. Try to look for something more active. Also, someone opened an issue on the repo almost a year ago that it is not compatible with Laravel 5.5 (So you can conclude altogether it also wont work with Laravel 5.6). To which the author replied that Pull Requests are welcome and that was it, it seems the repo owner wont put any effort in it anymore.
I'm trying to install Ionic Push Notifications Channel for Laravel package in Laravel 5.2 project using :
composer require laravel-notification-channels/ionic-push-notifications
as it's in the package documentation
but it seems like this package isn't compatible with Laravel 5.2
I tried also to install an old version using :
composer require laravel-notification-channels/ionic-push-notifications 1.0.0
but also it results in these errors :
Your requirements could not be resolved to an installable set of packages.
[275.5MB/1227.19s]
Problem 1
- Installation request for laravel-notification-channels/ionic-push-notifications 1.0.0 -> satisfiable by laravel-notification-channels/ionic-push-notifications[1.0.0].
- Conclusion: remove laravel/framework v5.2.45
- Conclusion: don't install laravel/framework v5.2.45
- laravel-notification-channels/ionic-push-notifications 1.0.0 requires illuminate/notifications 5.3.* -> satisfiable by illuminate/notifications[v5.3.0, v5.3.16, v5.3.23, v5.3.4].
- illuminate/notifications v5.3.0 requires illuminate/bus 5.3.* -> satisfiable by illuminate/bus[v5.3.0, v5.3.16, v5.3.23, v5.3.4].
- illuminate/notifications v5.3.16 requires illuminate/bus 5.3.* -> satisfiable by illuminate/bus[v5.3.0, v5.3.16, v5.3.23, v5.3.4].
- illuminate/notifications v5.3.23 requires illuminate/bus 5.3.* -> satisfiable by illuminate/bus[v5.3.0, v5.3.16, v5.3.23, v5.3.4].
- illuminate/notifications v5.3.4 requires illuminate/bus 5.3.* -> satisfiable by illuminate/bus[v5.3.0, v5.3.16, v5.3.23, v5.3.4].
- don't install illuminate/bus v5.3.0|don't install laravel/framework v5.2.45
- don't install illuminate/bus v5.3.16|don't install laravel/framework v5.2.45
- don't install illuminate/bus v5.3.23|don't install laravel/framework v5.2.45
- don't install illuminate/bus v5.3.4|don't install laravel/framework v5.2.45
- Installation request for laravel/framework (locked at v5.2.45, required as 5.2.*) -> satisfiable by laravel/framework[v5.2.45].
So, is there any version to install with Laravel 5.2 or have I to upgrade to Laravel 5.3 to use this package ??
You have to install
composer require laravel-notification-channels/ionic-push-notifications
Setting up the Ionic Push service
Add your Ionic Push Authentication Token to your config/services.php
Now you can use the channel in your via() method inside the notification:
You can easily set different settings for iOS and Android individually
In order to let your Notification know which device token to send to, add the routeNotificationForIonicPush method to your Notifiable model.
For details see this link :
https://github.com/laravel-notification-channels/ionic-push-notifications
I'm trying to update Laravel 5.3 to Laravel 5.4 that was released yesturday, and I get this message:
Problem 1
- laravelcollective/html 5.3.x-dev requires illuminate/view 5.3.* -> satisfiable by laravel/framework[v5.3.20], illuminate/view[v5.3.0, v5.3.16, v5.3.23, v5.3.4].
- laravelcollective/html 5.3.x-dev requires illuminate/view 5.3.* -> satisfiable by laravel/framework[v5.3.20], illuminate/view[v5.3.0, v5.3.16, v5.3.23, v5.3.4].
- laravelcollective/html 5.3.x-dev requires illuminate/view 5.3.* -> satisfiable by laravel/framework[v5.3.20], illuminate/view[v5.3.0, v5.3.16, v5.3.23, v5.3.4].
- Can only install one of: laravel/framework[v5.4.0, v5.3.20].
- don't install illuminate/view v5.3.0|don't install laravel/framework v5.4.0
- don't install illuminate/view v5.3.16|don't install laravel/framework v5.4.0
- don't install illuminate/view v5.3.23|don't install laravel/framework v5.4.0
- don't install illuminate/view v5.3.4|don't install laravel/framework v5.4.0
- Installation request for laravel/framework 5.4.0 -> satisfiable by laravel/framework[v5.4.0].
- Installation request for laravelcollective/html 5.3.*-dev -> satisfiable by laravelcollective/html[5.3.x-dev].
Thing is I don't see laravelcollective has release a 5.4 version.
Do I need to wait for them to release new version or am I missing something?
Why isn't it in the upgrade guide, it is a quite important lib in Laravel.
You have some options. Laravel Collective is a popular package, so people are already applying the fixes required for it to work on 5.4. Check out the following thread on a pull request.
https://github.com/LaravelCollective/html/pull/276
So, in order to use the package with 5.4, based on comments in the thread, you'll need to change your composer.json to look like this.
"laravel/collective": "5.4.x-dev",
Then run composer update
If you want you can also use a specific commit. In this case, to use the commit on this pull request, your composer.json would look like so.
"laravelcollective/html": "dev-master#92f3ba71c5c11c752ddd68d614f5f0665e759220",