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

Package dependency conflict with Jetstream 5.0 and Laravel 11.0 #39

Open
dsbilling opened this issue May 21, 2024 · 0 comments · May be fixed by #40
Open

Package dependency conflict with Jetstream 5.0 and Laravel 11.0 #39

dsbilling opened this issue May 21, 2024 · 0 comments · May be fixed by #40

Comments

@dsbilling
Copy link

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 akaunting/laravel-language ^1.0 -> satisfiable by akaunting/laravel-language[1.0.0, ..., 1.0.22].
    - You can only install one version of a package, so only one of these can be installed: mobiledetect/mobiledetectlib[2.7.6, ..., 2.8.45, 4.8.01, ..., 4.8.06].
    - Conclusion: don't install one of mobiledetect/mobiledetectlib[2.8.45], laravel/jetstream[v5.1.0] (conflict analysis result)
    - Conclusion: install mobiledetect/mobiledetectlib 2.8.45 (conflict analysis result)
    - laravel/jetstream v5.0.0 requires mobiledetect/mobiledetectlib ^4.8 -> satisfiable by mobiledetect/mobiledetectlib[4.8.01, ..., 4.8.06].
    - Root composer.json requires laravel/jetstream ^5.0 -> satisfiable by laravel/jetstream[v5.0.0, ..., v5.1.0].

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

This is caused by the jenssegers/agent dependency and it is not being updated to fix this ref: jenssegers/agent#212

dsbilling added a commit to dsbilling/laravel-language that referenced this issue Sep 19, 2024
@dsbilling dsbilling linked a pull request Sep 19, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant