Skip to content
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

Latest repodata.json causes issues with pip / libffi.so.6 #9884

Closed
SSchott opened this issue Apr 26, 2020 · 4 comments
Closed

Latest repodata.json causes issues with pip / libffi.so.6 #9884

SSchott opened this issue Apr 26, 2020 · 4 comments
Labels
locked [bot] locked due to inactivity source::community catch-all for issues filed by community members stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity type::packaging indicates a request regarding a package

Comments

@SSchott
Copy link

SSchott commented Apr 26, 2020

Current Behavior

Under OpenSuse 42.3, latest Miniconda fails to update properly, causing:

`The following packages will be REMOVED:

pip-19.3.1-py27_0
wheel-0.33.6-py27_0`

And at the end:
ImportError: libffi.so.6: cannot open shared object file: No such file or directory

Steps to Reproduce

./Miniconda2-latest-Linux-x86_64.sh
......
./conda update conda -y
./conda install pip

Expected Behavior

This happens after the latest change in repodata.json. I guess there is the problem. It worked before last Thursday 23.04.2020

@kalefranz
Copy link
Contributor

CC @mingwandroid

@kalefranz kalefranz added source::community catch-all for issues filed by community members type::packaging indicates a request regarding a package labels Apr 26, 2020
@ruanimal
Copy link

ruanimal commented May 7, 2020

same issues with miniconda

@ruanimal
Copy link

ruanimal commented May 8, 2020

use base env can bypass this problem. And virtualenv can be used as an alternative to conda env.

@github-actions
Copy link

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Jul 12, 2022
@github-actions github-actions bot added the stale::closed [bot] closed after being marked as stale label Aug 12, 2022
@github-actions github-actions bot added the locked [bot] locked due to inactivity label Aug 12, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity source::community catch-all for issues filed by community members stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity type::packaging indicates a request regarding a package
Projects
None yet
Development

No branches or pull requests

3 participants