starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

SABNZBD update fails at line 66, citing thast the updater is trying to mess with the python packages running on the host #280

New Issue
Closed
opened 2026-02-04 17:41:34 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 17:41:34 +03:00
Owner
Copy Link

Originally created by @esworp on GitHub (Jan 6, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

SABNZBD

📂 What was the exact command used to execute the script?

update

📝 Provide a clear and concise description of the issue.

error line 66, exit code 0.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

run the update script.

❌ Paste the full error output (if available).

/ Updating SABnzbd to 4.4.1
[ERROR] in line 66: exit code 0: while executing command python3 -m pip install -r requirements.txt &> /dev/null

root@sabnzbd:~# python3 -m 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.11/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.

🖼️ Additional context (optional).

No response

Originally created by @esworp on GitHub (Jan 6, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? SABNZBD ### 📂 What was the exact command used to execute the script? update ### 📝 Provide a clear and concise description of the issue. error line 66, exit code 0. ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. run the update script. ### ❌ Paste the full error output (if available). / Updating SABnzbd to 4.4.1 [ERROR] in line 66: exit code 0: while executing command python3 -m pip install -r requirements.txt &> /dev/null root@sabnzbd:~# python3 -m 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.11/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. ### 🖼️ Additional context (optional). _No response_
OVERLORD commented 2026-02-04 17:41:53 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 6, 2025):

Search in discussion for Python and you get the Solution.

@MickLesk commented on GitHub (Jan 6, 2025): Search in discussion for Python and you get the Solution.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#280
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?