You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already have msgpack, which is the same. Building a Python env with
`spacy` resulted in a collision between an `.so` provided through both
`msgpack` and `msgpack-python`.
I don't know why `transitional = True` was set. These kind of things
should be documented!
We already have msgpack, which is the same. Building a Python env with
`spacy` resulted in a collision between an `.so` provided through both
`msgpack` and `msgpack-python`.
I don't know why `transitional = True` was set. These kind of things
should be documented!
(cherry picked from commit 22aef72)
dtzWill
pushed a commit
to dtzWill/nixpkgs
that referenced
this issue
Sep 30, 2019
We already have msgpack, which is the same. Building a Python env with
`spacy` resulted in a collision between an `.so` provided through both
`msgpack` and `msgpack-python`.
I don't know why `transitional = True` was set. These kind of things
should be documented!
(cherry picked from commit 22aef72)
Issue description
msgpack-python was renamed to msgpack, but the rename isn't handled properly in release-18.09 yet.
Steps to reproduce
See https://stackoverflow.com/questions/52941074/in-nixos-how-can-i-resolve-a-collision
Technical details
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste theresults.
The text was updated successfully, but these errors were encountered: