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 13 Packages Projects Releases 10 Wiki Activity

MeTube - Installation Failed #1071

New Issue
Closed
opened 2026-02-04 22:53:32 +03:00 by OVERLORD · 7 comments
OVERLORD commented 2026-02-04 22:53:32 +03:00
Owner
Copy Link

Originally created by @SlothStuff on GitHub (Jun 5, 2025).

✅ Have you read and understood the above guidelines?

yes

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

MeTube

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/metube.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

The script fails both in default mode and advanced mode. The issue appears to be permissions related with pip. I have attempted this both in privileged and unprivileged mode. Below is the error output from running default but the output from advanced is similar.

🔄 Steps to reproduce the issue.

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/metube.sh)"

❌ Paste the full error output (if available).

⠋Installing collected packages: distlib, setuptools, platformdirs, packaging, filelock, virtualenv, pipenv
⠹  Attempting uninstall: setuptools
    Found existing installation: setuptools 66.1.1
    Not uninstalling setuptools at /usr/lib/python3/dist-packages, outside environment /usr
    Can't uninstall 'setuptools'. No files were found to uninstall.
 ⠙Successfully installed distlib-0.3.9 filelock-3.18.0 packaging-25.0 pipenv-2025.0.3 platformdirs-4.3.8 setuptools-80.9.0 virtualenv-20.31.2
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
 ⠙Warning: Python 3.13 was not found on your system...
Neither 'pyenv' nor 'asdf' could be found to install Python.
You can specify specific versions of Python with:
$ pipenv --python path/to/python
 ⠹
[ERROR] in line 48: exit code 0: while executing command $STD pipenv install
 ⠧/dev/fd/63: line 74: SPINNER_PID: unbound variable

🖼️ Additional context (optional).

No response

Originally created by @SlothStuff on GitHub (Jun 5, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? MeTube ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/metube.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. The script fails both in default mode and advanced mode. The issue appears to be permissions related with pip. I have attempted this both in privileged and unprivileged mode. Below is the error output from running default but the output from advanced is similar. ### 🔄 Steps to reproduce the issue. bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/metube.sh)" ### ❌ Paste the full error output (if available). ``` ⠋Installing collected packages: distlib, setuptools, platformdirs, packaging, filelock, virtualenv, pipenv ⠹ Attempting uninstall: setuptools Found existing installation: setuptools 66.1.1 Not uninstalling setuptools at /usr/lib/python3/dist-packages, outside environment /usr Can't uninstall 'setuptools'. No files were found to uninstall. ⠙Successfully installed distlib-0.3.9 filelock-3.18.0 packaging-25.0 pipenv-2025.0.3 platformdirs-4.3.8 setuptools-80.9.0 virtualenv-20.31.2 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv ⠙Warning: Python 3.13 was not found on your system... Neither 'pyenv' nor 'asdf' could be found to install Python. You can specify specific versions of Python with: $ pipenv --python path/to/python ⠹ [ERROR] in line 48: exit code 0: while executing command $STD pipenv install ⠧/dev/fd/63: line 74: SPINNER_PID: unbound variable ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 22:53:32 +03:00
OVERLORD commented 2026-02-04 22:53:42 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Jun 6, 2025):

The dev updated dependencies, so it now requires Python 3.13, which is not on Debian stable branch yet.
We need to update the script to either install Python 3.13 from backports repo or try forcing the install on Python 3.11

@tremor021 commented on GitHub (Jun 6, 2025): The dev updated dependencies, so it now requires Python 3.13, which is not on Debian stable branch yet. We need to update the script to either install Python 3.13 from backports repo or try forcing the install on Python 3.11
OVERLORD commented 2026-02-04 22:53:47 +03:00
Author
Owner
Copy Link

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

UV PR

@MickLesk commented on GitHub (Jun 6, 2025): UV PR
OVERLORD commented 2026-02-04 22:53:57 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Jun 6, 2025):

UV PR

PYTHON_VERSION="3.12" setup_uv this won't work, app targets 3.13 in lockfiles

@tremor021 commented on GitHub (Jun 6, 2025): > UV PR `PYTHON_VERSION="3.12" setup_uv` this won't work, app targets 3.13 in lockfiles
OVERLORD commented 2026-02-04 22:54:00 +03:00
Author
Owner
Copy Link

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

Then Change to 13, uv are Up to 14

@MickLesk commented on GitHub (Jun 6, 2025): Then Change to 13, uv are Up to 14
OVERLORD commented 2026-02-04 22:54:08 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Jun 6, 2025):

Pushed

@tremor021 commented on GitHub (Jun 6, 2025): Pushed
OVERLORD commented 2026-02-04 22:54:18 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Jun 6, 2025):

@SlothStuff we will have to wait for #4961 to merge, as we are migrating all python scripts to UV from bare python3 installs.

@MickLesk want me to push updated script to main now or we wait for all to complete?

@tremor021 commented on GitHub (Jun 6, 2025): @SlothStuff we will have to wait for #4961 to merge, as we are migrating all python scripts to UV from bare python3 installs. @MickLesk want me to push updated script to main now or we wait for all to complete?
OVERLORD commented 2026-02-04 22:54:30 +03:00
Author
Owner
Copy Link

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

Wait for all, because there are some Strange Issues and i modify the setup_uv straight to the current issues

You can maybe remove the json (.json.bak) from Frontend and we readd it when UV merged

@MickLesk commented on GitHub (Jun 6, 2025): Wait for all, because there are some Strange Issues and i modify the setup_uv straight to the current issues You can maybe remove the json (.json.bak) from Frontend and we readd it when UV merged
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 bug
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#1071
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?