SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-11 00:22:37 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

HomeBox update script fails from 0.19.0 -> 0.20.2 #1656

New Issue
Closed
opened 2025-11-20 05:14:19 -05:00 by saavagebueno · 5 comments
saavagebueno commented 2025-11-20 05:14:19 -05:00
Owner
Copy Link

Originally created by @jamespeek on GitHub (Aug 8, 2025).

✅ Have you read and understood the above guidelines?

yes

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

HomeBox

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

update

⚙️ 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.

Running the update script fails because it says there is no HomeBox installation, which there is as it is running. This appears to be due to the change last week in the update script which checks if the /opt/homebox exists and is a directory where as previously it was a file.

🔄 Steps to reproduce the issue.

Run update script on 0.19.0 installation.

❌ Paste the full error output (if available).

No HomeBox Installation Found!

🖼️ Additional context (optional).

Change was in this commit: ab6f2dd24f

if [[ ! -f /opt/homebox ]]; then

to

if [[ ! -d /opt/homebox ]]; then

Originally created by @jamespeek on GitHub (Aug 8, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? HomeBox ### 📂 What was the exact command used to execute the script? update ### ⚙️ 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. Running the update script fails because it says there is no HomeBox installation, which there is as it is running. This appears to be due to the change last week in the update script which checks if the `/opt/homebox` exists and is a *directory* where as previously it was a file. ### 🔄 Steps to reproduce the issue. Run update script on 0.19.0 installation. ### ❌ Paste the full error output (if available). No HomeBox Installation Found! ### 🖼️ Additional context (optional). Change was in this commit: https://github.com/community-scripts/ProxmoxVE/commit/ab6f2dd24f512faa307db19bd26d9abef689b852 `if [[ ! -f /opt/homebox ]]; then` to `if [[ ! -d /opt/homebox ]]; then`
saavagebueno added the bug label 2025-11-20 05:14:19 -05:00
saavagebueno commented 2025-11-20 05:14:20 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 8, 2025):

Correct, it should check for existing service file anyway. Fixed in #6677 . Try after the merge

@tremor021 commented on GitHub (Aug 8, 2025): Correct, it should check for existing service file anyway. Fixed in #6677 . Try after the merge
saavagebueno commented 2025-11-20 05:14:20 -05:00
Author
Owner
Copy Link

@jamespeek commented on GitHub (Aug 8, 2025):

Thanks for the speedy fix @tremor021, will try once merged.

@jamespeek commented on GitHub (Aug 8, 2025): Thanks for the speedy fix @tremor021, will try once merged.
saavagebueno commented 2025-11-20 05:14:20 -05:00
Author
Owner
Copy Link

@jamespeek commented on GitHub (Aug 8, 2025):

@tremor021 got further after the fix merge (did a restore to a couple o days ago to ensure it was unaltered from previous attempts):

⠋ Stopping HomeBoxWarning: The unit file, source configuration file or drop-ins of homebox.service changed on disk. Run 'systemctl daemon-reload' to reload units.
  ✔️   HomeBox Stopped
⠋ Fetching GitHub release: homebox (0.20.2)mkdir: cannot create directory ‘/opt/homebox’: File exists
⠏ Fetching GitHub release: homebox (0.20.2)
[ERROR] in line 976: exit code 0: while executing command mkdir -p "$target"

After this, I tried renaming /opt/homebox manually renaming to /opt/homebox_bak and re-running:

⠋ Stopping HomeBoxWarning: The unit file, source configuration file or drop-ins of homebox.service changed on disk. Run 'systemctl daemon-reload' to reload units.
  ✔️   HomeBox Stopped
  ✔️   Deployed: homebox (0.20.2)
⠋ Starting HomeBoxWarning: The unit file, source configuration file or drop-ins of homebox.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Job for homebox.service failed because of unavailable resources or another system error.
See "systemctl status homebox.service" and "journalctl -xeu homebox.service" for details.
⠦ Starting HomeBox
[ERROR] in line 45: exit code 0: while executing command systemctl start homebox
@jamespeek commented on GitHub (Aug 8, 2025): @tremor021 got further after the fix merge (did a restore to a couple o days ago to ensure it was unaltered from previous attempts): ``` ⠋ Stopping HomeBoxWarning: The unit file, source configuration file or drop-ins of homebox.service changed on disk. Run 'systemctl daemon-reload' to reload units. ✔️ HomeBox Stopped ⠋ Fetching GitHub release: homebox (0.20.2)mkdir: cannot create directory ‘/opt/homebox’: File exists ⠏ Fetching GitHub release: homebox (0.20.2) [ERROR] in line 976: exit code 0: while executing command mkdir -p "$target" ``` After this, I tried renaming `/opt/homebox` manually renaming to `/opt/homebox_bak` and re-running: ``` ⠋ Stopping HomeBoxWarning: The unit file, source configuration file or drop-ins of homebox.service changed on disk. Run 'systemctl daemon-reload' to reload units. ✔️ HomeBox Stopped ✔️ Deployed: homebox (0.20.2) ⠋ Starting HomeBoxWarning: The unit file, source configuration file or drop-ins of homebox.service changed on disk. Run 'systemctl daemon-reload' to reload units. Job for homebox.service failed because of unavailable resources or another system error. See "systemctl status homebox.service" and "journalctl -xeu homebox.service" for details. ⠦ Starting HomeBox [ERROR] in line 45: exit code 0: while executing command systemctl start homebox ```
saavagebueno commented 2025-11-20 05:14:20 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 9, 2025):

Oops yes, i forgot to delete the old binary. Fix incoming. Please try again after #6702 merges. I hope i didn't miss anything more, i had very little sleeep when i did the first fix :) Sorry about that

@tremor021 commented on GitHub (Aug 9, 2025): Oops yes, i forgot to delete the old binary. Fix incoming. Please try again after #6702 merges. I hope i didn't miss anything more, i had very little sleeep when i did the first fix :) Sorry about that
saavagebueno commented 2025-11-20 05:14:20 -05:00
Author
Owner
Copy Link

@jamespeek commented on GitHub (Aug 10, 2025):

Thanks, that has fixed it, update went through successfully. Cheers @tremor021

@jamespeek commented on GitHub (Aug 10, 2025): Thanks, that has fixed it, update went through successfully. Cheers @tremor021
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1656
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?