Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ignoreCollisions... ignored?

See original GitHub issue

Hello,

When using mkPython in the following way:

let
  mach-nix = import (builtins.fetchGit {
    url = "https://github.com/DavHau/mach-nix/";
    ref = "refs/tags/3.0.2";
  }) {};
in
(mach-nix.mkPython {
    requirements = ''
      rasa[spacy]
    '';
}).override (_: { ignoreCollisions = true; })

I run into the following collision:

building '/nix/store/i6vyh6hij93z7wqnqk5qykd39vw39q3q-python3-3.8.5-env.drv'...
collision between `/nix/store/sn8ws24ws7wx1s90dh97rjy6crbl78kg-python3.8-rasa-sdk-2.0.0/lib/python3.8/site-packages/README.md' and `/nix/store/xwbc3fdjaxfqvz1w5igak4v9wxdshibb-python3.8-rasa-2.0.2/lib/python3.8/site-packages/README.md'

I was hoping that the ignoreCollisions = true; bit would be respected, therefore not erroring out because of a simple README collision, but it seemingly isn’t. Am I missing something obvious? And is there any way to workaround that kind of problem with mach-nix powered environments?

Issue Analytics

State:
Created 3 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

DavHaucommented, Oct 29, 2020

It should be fixed with 22da85eae4bdd829b772952f72bc0a269a1819d0 I stopped using buildEnv and instead override makeWrapperArgs to include the extra packages into the PATH.

We could add a general ignoreCollisions option to mach-nix. But what’s currently holding me from it, is that I don’t want people becoming used to setting this option. A collision indicates a bug most of the time and should be reported/fixed rather than ignored.

0reactions

alpmestancommented, Oct 30, 2020

Thanks!