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

Debian 12 changed how pip works #236

Open
crowtrobot opened this issue Jan 8, 2024 · 0 comments
Open

Debian 12 changed how pip works #236

crowtrobot opened this issue Jan 8, 2024 · 0 comments

Comments

@crowtrobot
Copy link
Contributor

In Debian 12 (and I think some other Linux distributions) changes were made to the way pip works to discourage installing things in a way that might conflict with the versions installed by apt-get. AFAIK (and I am not an expert, so feel free to correct me) you now have to create a python virtual environment, have pip install the packages there, and then run your program from that virtual environment so it can see the packages.

I just finished re-installing my Seafile Server on a Debian 12 VM using a python venv, and so far it seems to work. I made some notes on what I had to do different from the steps in the manual. The differences are pretty small. Just make the venv, activate it before running pip, and made a script to start the seahub and seafile scripts with the venv. I will submit a pull request with edits to the relevant sections.

I've never done this before, so please tell me if I've done anything wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant