-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot install using pip on Ubuntu 20.04 #1320
Comments
Thank you for reporting! We're looking into this right away! |
Hi @m-decoster , thanks for the report. Can you please post the output of the command |
@jondo2010 Sure, here you go:
|
@m-decoster I reproduced this locally in a 20.04 docker container and can confirm it's an issue with how we're building the wheels. Working on an updated builder now that should do the trick for you. Will report back when I have an updated package to try out. |
Ok, @m-decoster I managed to create a one-off build from an ubuntu 20.04 environment (specifically with glibc-2.31 ABI). It will take a bit more to get this fully integrated into our CI, but I'm curious if this works for you. Download the attached zip, then:
|
Thanks @jleibs, this works perfectly! |
Awesome, thanks for testing, @m-decoster I'll go ahead and figure out how to get these changes into our CI then. |
@jleibs, is
when trying to run the objectron demo with |
@robertbagge That test build wasn't, but I just landed the change to do this in our CI. Looks like I've got one more bug to fix, but should have updated pre-release wheels for you very soon. |
@robertbagge ok, the CI build finally finished. It won't be available via pypi until our next patch-release, but you can grab the wheel from here: https://github.com/rerun-io/rerun/releases/download/latest/rerun_sdk-0.2.0+df920dc.1-cp38-abi3-manylinux_2_31_x86_64.whl
|
Hi @jleibs , I'm still using Ubuntu 18.04 (glibc 2.27) and the same issue happens. Could you also add the CI pipeline to generate whl for glibc 2.27? I'm looking forward to working with your sdk. |
We haven't officially decided what our minimum supported Ubuntu is (see #1346), but Ubuntu 18.04 was released in 2018 and will loose standard support on April 2023, so I'm leaning towards that not making the cut. Have you tried building from source? https://github.com/rerun-io/rerun/tree/main/rerun_py#from-source |
Fair enough. I'll give it a shot. Thank you. |
18.04 also does not ship with python 3.8. Which is currently our minimum required python version, so you'll also need to use a non-system python version. |
@jleibs, do you have any timeline on when the next patch release will be? |
I just tried that, however, I got a couple of problems. The biggest thing is that gtk-sys crate requires I'll consider migration to the latest LTS version (I'd love to do that personally, but it's not an easy choice in the company😕). |
@robertbagge There are a few more things we're hoping to land first. Currently looking like sometime mid- next week. |
@mont1004 yes, that seems likely to cause some problems. I was hoping there might be some way for you to build without the gtk dep, i.e. only using the web-viewer, but this is not currently possible (I just created an issue for this for the future though: #1384). For now I think you're going to be stuck finding a way to work with 20.04 (or 22.04 which is also LTS). |
Cool, that sounds good |
I've created an issue to track the next release: #1386 |
As of rerun-sdk-0.3.0 this is now working. Just confirmed in a new Ubuntu-20.04 docker container. |
After running this, I'm getting below error in Ubuntu 20.04 |
ok, it works after upgrading pip using |
Hi @jondo2010 @Wumpf , I am facing the same issue:
Here are some info about my system:
Do you know where the issue come from? |
@fabienbaradel the Rerun packages require Also, I notice you are using python-3.7. Rerun has a minimum python version of python-3.8, so in addition to upgrading pip you are going to need to upgrade to a more recent python. |
Just updated my pip and python to newer version but I am still facing same issue:
The output is not verbose so it is difficult to know where the issue comes from. |
Interesting. What linux version is this? Our packages are built as manylinux_2_31, which works back to ubuntu 20.04. Looks like on the Fedora side this requires Fedora 32 or later. |
The linux version is Centos. What do you recommend me for installing rerun? Thanks. |
I am facing the same issue as @fabienbaradel on CentOS 7:
I'm guessing it's related to OS's ancient glibc version (2.17). |
I am trying to install rerun sdk on a RHEL system, but it fails. Any suggestions?
|
@ani0075saha our current pypi-hosted wheel depends on glibc 2.31. It looks like RHEL-8.9 is still using glibc-2.28 For older OS's such as redhat 8 I would currently recommend either doing a source install, or using using our |
upgrading the pip should fix this |
@feisuo I've confirmed your exact install command works for me on a modern tegra platform from within the lerobot conda environment.
My guess is that 4.9.337-tegra has too old of a glibc. Our pypi-packaged wheels require glibc >= 2.31. (You can check this by running I believe our conda-forge packages may work with an older glibc. You might try |
this should fix
|
Describe the bug
Despite seemingly meeting the requirements to install the Python version of rerun, I cannot install it using Pip.
The documentation says I need a working version of Python 3.8+. The PyPI website also says >= 3.8. However, this happens when I try to install rerun:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expected behavior is that
pip install rerun-sdk
would install the rerun sdk.Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: