-
-
Notifications
You must be signed in to change notification settings - Fork 4
Dependencies packaged as manylinux1 wheels cannot be installed on Nix #352
Comments
@RealOrangeOne This looks like it might be a |
Absolutely none. The version definitely exists on PyPI. @kierdavis is the package installable through |
This might be an upstream bug in poetry. https://circleci.com/workflow-run/899e500a-d9c9-4075-a550-9bfc64210b1d |
We're not the only ones python-poetry/poetry#1256 |
The package's FAQ on PyPI suggests the problem may be due to an outdated pip, but I still experience the issue with the latest version available (19.2.1). |
Interesting. Looks like poetry might be swallowing errors or something, which is definitely strange. Have to monitor this one. Installation works fine for me, so I assume it's something either non-determinstic, or environment-related. |
Temporary fix for |
It seems to be a conflict between |
Same problem occurs using pip directly, so I don't think it's a poetry issue (EDIT: to be specific, there may be multiple causes of this symptom, and not all of them involve poetry):
As above, but with |
Well that's certainly different, but you're right that's definitely not a |
We could do something similar to 9172f2f and pin |
Perhaps. @kierdavis Can you try installing some older versions, and see which is the most recent version you can install successfully. I'd be down for downgrading a couple versions if it helps make things more stable! https://pypi.org/project/opencv-contrib-python-headless/#history |
Unfortunately it appears this problem occurs independently of the version of
I also tried a few specific versions from the link @RealOrangeOne shared, no change. |
pip seems to work fine for other packages:
|
tl;dr: the available wheels and my system use incompatible versions of manylinux After doing some digging I've found that the From the verbose log posted earlier I identified a wheel that I'd expect to be considered compatible with my system (
As it turns out there's two (presumably incompatible) versions of manylinux. It appears my system only supports manylinux 2010, but |
Can confirm that if I convince pip that my platform is manylinux1 instead of manylinux2010 then it finds and installs the package as expected. This is sort of a hack and I haven't checked if the package will actually work if installed in this manner, so I don't intend to use this as a solution.
I'm pretty confident this isn't a j5-specific issue anymore, so I'll close this issue. |
Nix is not manylinux1-compatible. @trickeydan do you think this is a relevant portability issue? AFAIK we have no plans to deploy j5 on Nix, this is just for my personal development purposes. However we've already set a precedent by maintaining support for j5 on Windows. Also, support for manylinux1 on Nix is in development, and based on this work I've made a start on modifying the Nix environment definition (shell.nix) to provide manylinux1 compatibility and allow this problematic package to be installed in my |
The fact there's currently a nix configuration in the repo makes it look like it's a supported platform. My suggestion is that either said file is fixed, or it's removed. Personally i'd consider it fine to keep support for Nix, once NixOS/nixpkgs#55812 ships. What to do now I don't know. Windows support feels reasonable, as it's a common platform, and will be very useful when a simulator is created. |
I see no reason why not, but it's a low priority. |
@kierdavis How did you get this working in your environment? When I try to run shell.nix (https://github.com/j5api/j5/blob/nix-manylinux1/shell.nix) I am getting dozen of errors like "GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference". Solving this problem would help me on RHEL7 when there is no possibility to use this solution https://sid-kap.github.io/posts/2018-03-08-nix-pipenv.html due to old kernel. |
I haven't, yet. I'm expecting to see errors like those once I get round to finishing this (it's low priority for me at the moment). |
NixOS/nixpkgs#71935 was merged, although I'm still experiencing this issue. Will need to investigate further. |
Branch removed for cleanup. Changes on branch were:
|
closing due to inactivity; will reopen if this becomes a relevant problem again. |
The text was updated successfully, but these errors were encountered: