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

Gitea Update Failing #734

New Issue
Closed
opened 2026-02-04 21:09:46 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-04 21:09:46 +03:00
Owner
Copy Link

Originally created by @piliener on GitHub (Apr 2, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Gitea

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

update

📝 Provide a clear and concise description of the issue.

Trying to update gitea from an older version fails on the move command. Afterward gitea will no longer run and must be restored from a backup.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

type update
start the process
coming from version 1.22.3

❌ Paste the full error output (if available).

Updating Gitea to 1.23.6mv: target '/usr/local/bin/gitea': No such file or directory
⠏ Updating Gitea to 1.23.6
[ERROR] in line 35: exit code 0: while executing command mv gitea* /usr/local/bin/gitea

🖼️ Additional context (optional).

Image

Originally created by @piliener on GitHub (Apr 2, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Gitea ### 📂 What was the exact command used to execute the script? update ### 📝 Provide a clear and concise description of the issue. Trying to update gitea from an older version fails on the move command. Afterward gitea will no longer run and must be restored from a backup. ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. type update start the process coming from version 1.22.3 ### ❌ Paste the full error output (if available). Updating Gitea to 1.23.6mv: target '/usr/local/bin/gitea': No such file or directory ⠏ Updating Gitea to 1.23.6 [ERROR] in line 35: exit code 0: while executing command mv gitea* /usr/local/bin/gitea ### 🖼️ Additional context (optional). ![Image](https://github.com/user-attachments/assets/14989d91-26c1-4b83-a75e-b2f891bb566b)
OVERLORD added the bug label 2026-02-04 21:09:46 +03:00
OVERLORD commented 2026-02-04 21:09:58 +03:00
Author
Owner
Copy Link

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

this is weird, i'm looking at the code and i tried doing all commands manually, it should work...

@tremor021 commented on GitHub (Apr 2, 2025): this is weird, i'm looking at the code and i tried doing all commands manually, it should work...
OVERLORD commented 2026-02-04 21:10:06 +03:00
Author
Owner
Copy Link

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

cant reproduce. Do it manually

dd4af32587/ct/gitea.sh (L30-L37)

@MickLesk commented on GitHub (Apr 2, 2025): cant reproduce. Do it manually https://github.com/community-scripts/ProxmoxVE/blob/dd4af3258706a45f2d8674a0029ef05293ee4981/ct/gitea.sh#L30-L37
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#734
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?