Jose, I just upgraded the version of hex and am still seeing the problem. My suspicion is that some number of the elixir packages in hex do not include a mix.lock. That said, the optimal course for me is that mix simply doesn't try to manage dependencies, regardless of whether there is a lock file or not. In the worst case, I can have the nix infrastructure generate a lock file.
Sent from [ProtonMail](https://protonmail.com), encrypted email based in Switzerland. -------- Original Message -------- Subject: Re: [elixir-talk:13437] no-deps-check no longer respected in Mix 1.3.1? Local Time: July 6, 2016 10:43 AM UTC Time: July 6, 2016 5:43 PM From: [email protected] To: [email protected] Eric, after a quick conversation with Eric MJ, he mentioned this should work with the same flags as parameters as long as you have a mix.lock file, as Hex no longer requires a registry for locked dependencies. I was able to verify such in a project like Plug. Which Hex version are you using? Have you tried the latest? José Valim [www.plataformatec.com.br](http://www.plataformatec.com.br/) Skype: jv.ptec Founder and Director of R&D On Wed, Jul 6, 2016 at 7:02 PM, Eric Merritt <[email protected]> wrote: Jose, That's perfectly acceptable. My main concern is that there is a way to tell mix that dependencies are already taken care of and it doesn't need to reach out to the network. How it goes about that, as long as its documented, isn't that big a deal. I will wait to upgrade until you guys release a fix. Eric Sent from [ProtonMail](https://protonmail.com), encrypted email based in Switzerland. -------- Original Message -------- Subject: Re: [elixir-talk:13434] no-deps-check no longer respected in Mix 1.3.1? Local Time: July 6, 2016 9:54 AM UTC Time: July 6, 2016 4:54 PM From: [email protected] To: [email protected] Thank you Eric. I can confirm this is broken. Unfortunately we introduced this regression when fixing another bug. I will discuss a fix with Eric MJ and let you know. If we introduce a new flag or an environment option, would that be acceptable? Since it will only be checked with future versions, it should not affect previous versions and effectively fix the issue for future ones. José Valim [www.plataformatec.com.br](http://www.plataformatec.com.br/) Skype: jv.ptec Founder and Director of R&D On Wed, Jul 6, 2016 at 6:41 PM, Eric Merritt <[email protected]> wrote: Guys, I am working on upgrading elixir support for nixos to Elixir 1.3. There seems to be a change in how Mix responds to the `--no-deps-check` flag. Previously, mix wouldn't try to do anything with deps. Now it blows up with an error when running the following. ``` HEX_OFFLINE=1 mix compile --no-deps-check ``` The error that I see is: ``` * (Mix) Failed to open Hex registry (file does not exist, run `mix hex.info` to fetch it) ``` Previosly This is new behavior between the previous version of Mix and the new version. This problem essentially breaks elixir support on nixos, so I would love to get it fixed. Eric -- You received this message because you are subscribed to the Google Groups "elixir-lang-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit [https://groups.google.com/d/msgid/elixir-lang-talk/e743d7dd-0808-467a-9963-754e611d22fe%40googlegroups.com](https://groups.google.com/d/msgid/elixir-lang-talk/e743d7dd-0808-467a-9963-754e611d22fe%40googlegroups.com?utm_medium=email&utm_source=footer). For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "elixir-lang-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit [https://groups.google.com/d/msgid/elixir-lang-talk/CAGnRm4%2BjAdweauep-PXz7mfg1iqS%3Ds_RbOp-UeBi5Wdr_C0vjA%40mail.gmail.com](https://groups.google.com/d/msgid/elixir-lang-talk/CAGnRm4%2BjAdweauep-PXz7mfg1iqS%3Ds_RbOp-UeBi5Wdr_C0vjA%40mail.gmail.com?utm_medium=email&utm_source=footer). For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "elixir-lang-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit [https://groups.google.com/d/msgid/elixir-lang-talk/JyXKrpMQOisFenZyvqRjZZW1wAj2vve0IA8ivc9edcWChfDrndyOuR0-2pgGtrKLoWtAWmX-PFB6FeITi4ywMw%3D%3D%40merritt.tech](https://groups.google.com/d/msgid/elixir-lang-talk/JyXKrpMQOisFenZyvqRjZZW1wAj2vve0IA8ivc9edcWChfDrndyOuR0-2pgGtrKLoWtAWmX-PFB6FeITi4ywMw%3D%3D%40merritt.tech?utm_medium=email&utm_source=footer). For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "elixir-lang-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit [https://groups.google.com/d/msgid/elixir-lang-talk/CAGnRm4%2Bo%2BPP6h6k1myBCGtpOu1b0%2BrDp6qDA_k0hLfed%2B%2BZC1Q%40mail.gmail.com](https://groups.google.com/d/msgid/elixir-lang-talk/CAGnRm4%2Bo%2BPP6h6k1myBCGtpOu1b0%2BrDp6qDA_k0hLfed%2B%2BZC1Q%40mail.gmail.com?utm_medium=email&utm_source=footer). For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "elixir-lang-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-talk/dTVRCb_Dd-Mlbj4hwxMJCR0EtyG1TMAW-OgNvvho2lhUvxXm0PW-l1-2iAAj3h_5LHqKU5LlBVj7nxgI32v34w%3D%3D%40merritt.tech. For more options, visit https://groups.google.com/d/optout.
