csisnett
Hi everyone!
I’m trying to install the Calecto library but when I run mix deps.get I get the following:
Failed to use “ecto” (version 3.1.7) because
calecto (version 0.17.0) requires ~> 2.1
ecto_sql (version 3.1.6) requires ~> 3.1.0
phoenix_ecto (version 4.0.0) requires ~> 3.0
mix.lock specifies 3.1.7
** (Mix) Hex dependency resolution failed, change the version requirements of your dependencies or unlock them (by using mix deps.update or mix deps.unlock). If you are unable to resolve the conflicts you can try overriding with {:dependency, “~> 1.0”, override: true}
I’ve tried overriding like: {:calecto, “~> 0.17.0”, override: true} but is not working as I keep getting the same error, I’m guessing I have to override calecto’s depedency not the calecto dependency
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Practical resources that improve the lives of professional developers.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
NobbZ
You need to
:overridethe dependency that can’t be resolved,:ectoin your case.Sometimes this leads to adding dependencies that usually would just be added transiently.
csisnett
Yes, but how can I do that? What would I write instead of
{:calendar, "~> 0.17.6"}or in addition to that
Edit: Solved it by adding
{:ecto, "~> 3.1.7", override: true}in the begginning of the dependency list
NobbZ
It’s not important whether you do this at the end, the beginning or in the middle of the list, dependency resolution is an overall process.
But be aware that overriding into another major version might cause issues due to incompatible API between those versions.
Perhaps file an issue with the library to update the dependencies?
csisnett
Thanks!
I’ll do that to be sure it works (at least the Calendar.DateTime type) with this version of ecto