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

wger - Update script failed #845

New Issue
Closed
opened 2026-02-04 21:52:18 +03:00 by OVERLORD · 8 comments
OVERLORD commented 2026-02-04 21:52:18 +03:00
Owner
Copy Link

Originally created by @h0mesmart on GitHub (Apr 23, 2025).

✅ Have you read and understood the above guidelines?

yes

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

wger

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/wger.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.

Hi there,
First of all, thank you for the quick fix for issue 3972
I tried to update once again and still got an error. exit code 0: while executing command python3 manage.py migrate &> /dev/null
Thank you for your help

🔄 Steps to reproduce the issue.

type update in the wger lxc console

❌ Paste the full error output (if available).

 ✔️   Stopped wger

⠙ Updating wger to v2.3
[ERROR] in line 42: exit code 0: while executing command python3 manage.py migrate &> /dev/null

🖼️ Additional context (optional).

No response

Originally created by @h0mesmart on GitHub (Apr 23, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? wger ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/wger.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Hi there, First of all, thank you for the quick fix for issue [3972](https://github.com/community-scripts/ProxmoxVE/issues/3972) I tried to update once again and still got an error. `exit code 0: while executing command python3 manage.py migrate &> /dev/null` Thank you for your help ### 🔄 Steps to reproduce the issue. type update in the wger lxc console ### ❌ Paste the full error output (if available). ``` ✔️ Stopped wger ⠙ Updating wger to v2.3 [ERROR] in line 42: exit code 0: while executing command python3 manage.py migrate &> /dev/null ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the not a script issueexternal labels 2026-02-04 21:52:18 +03:00
OVERLORD commented 2026-02-04 21:52:33 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 23, 2025):

Run in verbose, nobody know what failed here

@MickLesk commented on GitHub (Apr 23, 2025): Run in verbose, nobody know what failed here
OVERLORD commented 2026-02-04 21:52:43 +03:00
Author
Owner
Copy Link

@h0mesmart commented on GitHub (Apr 23, 2025):

These lines are the output when running the update in verbose mode:

 _      ______ ____  _____
| | /| / / __ `/ _ \/ ___/
| |/ |/ / /_/ /  __/ /    
|__/|__/\__, /\___/_/     
       /____/             

  ✔️   Stopped wger
⠧ Updating wger to v2.3
[ERROR] in line 42: exit code 0: while executing command python3 manage.py migrate &> /dev/null
@h0mesmart commented on GitHub (Apr 23, 2025): These lines are the output when running the update in verbose mode: ``` _ ______ ____ _____ | | /| / / __ `/ _ \/ ___/ | |/ |/ / /_/ / __/ / |__/|__/\__, /\___/_/ /____/ ✔️ Stopped wger ⠧ Updating wger to v2.3 [ERROR] in line 42: exit code 0: while executing command python3 manage.py migrate &> /dev/null ```
OVERLORD commented 2026-02-04 21:52:48 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Apr 23, 2025):

@h0mesmart what is your current running version?

@tremor021 commented on GitHub (Apr 23, 2025): @h0mesmart what is your current running version?
OVERLORD commented 2026-02-04 21:52:57 +03:00
Author
Owner
Copy Link

@h0mesmart commented on GitHub (Apr 24, 2025):

The current version is 2.2

@h0mesmart commented on GitHub (Apr 24, 2025): The current version is 2.2
OVERLORD commented 2026-02-04 21:53:03 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Apr 24, 2025):

@h0mesmart can you do:

cd /home/wger/src
pip install -r requirements.txt
python3 manage.py migrate --all

and tell me if it errors out for you

@tremor021 commented on GitHub (Apr 24, 2025): @h0mesmart can you do: ``` cd /home/wger/src pip install -r requirements.txt python3 manage.py migrate --all ``` and tell me if it errors out for you
OVERLORD commented 2026-02-04 21:53:07 +03:00
Author
Owner
Copy Link

@h0mesmart commented on GitHub (Apr 25, 2025):

Alright, so the command
pip install -r requirements.txt
result in

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
wger 2.3.0a1 requires celery[redis]==5.3.6, but you have celery 5.4.0 which is incompatible.
wger 2.3.0a1 requires crispy-bootstrap5==2023.10, but you have crispy-bootstrap5 2024.10 which is incompatible.
wger 2.3.0a1 requires Django==4.2.6, but you have django 4.2.20 which is incompatible.
wger 2.3.0a1 requires django-axes==6.1.1, but you have django-axes 7.0.2 which is incompatible.
wger 2.3.0a1 requires django-cors-headers==4.3.1, but you have django-cors-headers 4.7.0 which is incompatible.
wger 2.3.0a1 requires django-environ==0.11.2, but you have django-environ 0.12.0 which is incompatible.
wger 2.3.0a1 requires django-filter==23.4, but you have django-filter 25.1 which is incompatible.
wger 2.3.0a1 requires djangorestframework-simplejwt[crypto]==5.3.1, but you have djangorestframework-simplejwt 5.5.0 which is incompatible.
wger 2.3.0a1 requires drf-spectacular[sidecar]==0.26.5, but you have drf-spectacular 0.28.0 which is incompatible.
wger 2.3.0a1 requires easy-thumbnails==2.8.5, but you have easy-thumbnails 2.10 which is incompatible.
wger 2.3.0a1 requires fontawesomefree~=6.4.2, but you have fontawesomefree 6.6.0 which is incompatible.
wger 2.3.0a1 requires icalendar==5.0.11, but you have icalendar 6.1.2 which is incompatible.
wger 2.3.0a1 requires openfoodfacts==0.1.12, but you have openfoodfacts 2.5.0 which is incompatible.
wger 2.3.0a1 requires pillow==10.1.0, but you have pillow 11.1.0 which is incompatible.
wger 2.3.0a1 requires reportlab==4.0.7, but you have reportlab 4.3.1 which is incompatible.
wger 2.3.0a1 requires requests==2.31.0, but you have requests 2.32.3 which is incompatible.
wger 2.3.0a1 requires tzdata==2023.3, but you have tzdata 2025.2 which is incompatible.

and the command
python3 manage.py migrate --all
result in

/home/wger/src# python3 manage.py migrate --all
usage: manage.py migrate [-h] [--noinput] [--database DATABASE] [--fake] [--fake-initial] [--plan]
                         [--run-syncdb] [--check] [--prune] [--version] [-v {0,1,2,3}]
                         [--settings SETTINGS] [--pythonpath PYTHONPATH] [--traceback] [--no-color]
                         [--force-color] [--skip-checks]
                         [app_label] [migration_name]
manage.py migrate: error: unrecognized arguments: --all
@h0mesmart commented on GitHub (Apr 25, 2025): Alright, so the command `pip install -r requirements.txt` result in ``` ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. wger 2.3.0a1 requires celery[redis]==5.3.6, but you have celery 5.4.0 which is incompatible. wger 2.3.0a1 requires crispy-bootstrap5==2023.10, but you have crispy-bootstrap5 2024.10 which is incompatible. wger 2.3.0a1 requires Django==4.2.6, but you have django 4.2.20 which is incompatible. wger 2.3.0a1 requires django-axes==6.1.1, but you have django-axes 7.0.2 which is incompatible. wger 2.3.0a1 requires django-cors-headers==4.3.1, but you have django-cors-headers 4.7.0 which is incompatible. wger 2.3.0a1 requires django-environ==0.11.2, but you have django-environ 0.12.0 which is incompatible. wger 2.3.0a1 requires django-filter==23.4, but you have django-filter 25.1 which is incompatible. wger 2.3.0a1 requires djangorestframework-simplejwt[crypto]==5.3.1, but you have djangorestframework-simplejwt 5.5.0 which is incompatible. wger 2.3.0a1 requires drf-spectacular[sidecar]==0.26.5, but you have drf-spectacular 0.28.0 which is incompatible. wger 2.3.0a1 requires easy-thumbnails==2.8.5, but you have easy-thumbnails 2.10 which is incompatible. wger 2.3.0a1 requires fontawesomefree~=6.4.2, but you have fontawesomefree 6.6.0 which is incompatible. wger 2.3.0a1 requires icalendar==5.0.11, but you have icalendar 6.1.2 which is incompatible. wger 2.3.0a1 requires openfoodfacts==0.1.12, but you have openfoodfacts 2.5.0 which is incompatible. wger 2.3.0a1 requires pillow==10.1.0, but you have pillow 11.1.0 which is incompatible. wger 2.3.0a1 requires reportlab==4.0.7, but you have reportlab 4.3.1 which is incompatible. wger 2.3.0a1 requires requests==2.31.0, but you have requests 2.32.3 which is incompatible. wger 2.3.0a1 requires tzdata==2023.3, but you have tzdata 2025.2 which is incompatible. ``` and the command `python3 manage.py migrate --all` result in ``` /home/wger/src# python3 manage.py migrate --all usage: manage.py migrate [-h] [--noinput] [--database DATABASE] [--fake] [--fake-initial] [--plan] [--run-syncdb] [--check] [--prune] [--version] [-v {0,1,2,3}] [--settings SETTINGS] [--pythonpath PYTHONPATH] [--traceback] [--no-color] [--force-color] [--skip-checks] [app_label] [migration_name] manage.py migrate: error: unrecognized arguments: --all ```
OVERLORD commented 2026-02-04 21:53:10 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Apr 25, 2025):

Image
I guess their official update instructions are broken....

Nothing i can do about that. Restore from backup and don't update until next version

@tremor021 commented on GitHub (Apr 25, 2025): ![Image](https://github.com/user-attachments/assets/40215570-3a84-4b82-99ab-f0cd4c21c48b) I guess their official update instructions are broken.... Nothing i can do about that. Restore from backup and don't update until next version
OVERLORD commented 2026-02-04 21:53:26 +03:00
Author
Owner
Copy Link

@h0mesmart commented on GitHub (Apr 25, 2025):

Ok, got it. thank you

@h0mesmart commented on GitHub (Apr 25, 2025): Ok, got it. thank you
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 external not a script issue
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#845
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?