[GH-ISSUE #2] Python dependecy error on installation #3

New issue

Closed

opened 2026-03-02 15:47:06 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 15:47:06 +03:00

Owner

Originally created by @proxforge on GitHub (Jan 25, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/2

This is the output of deploy.sh when installing it on a debian 13 vm:

`[1/6] Installing system dependencies...
W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details
✓ System dependencies installed

[2/6] Creating service user...
✓ User 'pegaprox' already exists

[3/6] Setting up installation directory...
✓ Directory structure created at /opt/PegaProx

[4/6] Installing Python dependencies...
error: uninstall-no-record-file

× Cannot uninstall cryptography 43.0.0
╰─> The package's contents are unknown: no RECORD file was found for cryptography.

hint: The package was installed by debian. You should check if it can uninstall the package. `

when trying manually via pip install it says:

`root@js-analyzer-01:~/project-pegaprox# pip install -r requirements.txt
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.

If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.

If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.

See /usr/share/doc/python3.13/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
root@js-analyzer-01:~/project-pegaprox#`

what should be done, cant we have docker support, so setting it up is easier for newcomers?

Originally created by @proxforge on GitHub (Jan 25, 2026). Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/2 This is the output of deploy.sh when installing it on a debian 13 vm: `[1/6] Installing system dependencies... W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details ✓ System dependencies installed [2/6] Creating service user... ✓ User 'pegaprox' already exists [3/6] Setting up installation directory... ✓ Directory structure created at /opt/PegaProx [4/6] Installing Python dependencies... error: uninstall-no-record-file × Cannot uninstall cryptography 43.0.0 ╰─> The package's contents are unknown: no RECORD file was found for cryptography. hint: The package was installed by debian. You should check if it can uninstall the package. ` when trying manually via pip install it says: `root@js-analyzer-01:~/project-pegaprox# pip install -r requirements.txt error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you are trying to install. If you wish to install a non-Debian-packaged Python package, create a virtual environment using python3 -m venv path/to/venv. Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make sure you have python3-full installed. If you wish to install a non-Debian packaged Python application, it may be easiest to use pipx install xyz, which will manage a virtual environment for you. Make sure you have pipx installed. See /usr/share/doc/python3.13/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. root@js-analyzer-01:~/project-pegaprox#` what should be done, cant we have docker support, so setting it up is easier for newcomers?

kerem closed this issue

2026-03-02 15:47:06 +03:00

kerem commented

2026-03-02 15:47:07 +03:00

Author

Owner

@phantium commented on GitHub (Jan 25, 2026):

I have already made a pull request, which creates a virtualenv for Python instead of installing system wide.
Welcome to try using my fork in the meantime until it's merged.

@phantium commented on GitHub (Jan 25, 2026): I have already made a pull request, which creates a virtualenv for Python instead of installing system wide. Welcome to try using my fork in the meantime until it's merged.

kerem commented

2026-03-02 15:47:07 +03:00

Author

Owner

@MrMasterbay commented on GitHub (Jan 25, 2026):

Pull request apporved updated the docs.

@MrMasterbay commented on GitHub (Jan 25, 2026): Pull request apporved updated the docs.

kerem commented

2026-03-02 15:47:07 +03:00

Author

Owner

@mkellermann97 commented on GitHub (Jan 25, 2026):

This seems to be solved, so I'm closing it. @MrMasterbay Could you also close the related issues on your end?
Regards,
Marcus

@mkellermann97 commented on GitHub (Jan 25, 2026): This seems to be solved, so I'm closing it. @MrMasterbay Could you also close the related issues on your end? Regards, Marcus

kerem referenced this issue

2026-03-02 15:47:49 +03:00

[PR #3] [MERGED] Use virtualenv for python packages installation in deploy.sh, give correct user instructions for index.html copy #82