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

[PR #2676] Fix: Homarr - Manually correct db-migration wrong-folder #3774

New Issue
Closed
opened 2026-02-05 05:56:10 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 05:56:10 +03:00
Owner
Copy Link

Original Pull Request: https://github.com/community-scripts/ProxmoxVE/pull/2676

State: closed
Merged: Yes

✍️ Description

Out of any weird reason, homarr outputs the migration into a seperate subolder /migration, which then ends up with /opt/homarr_db/migration/migration instead of /opt/homarr_db/migration a sinple cp with recursive did not work, unless manually executed.

Will talk to homarr-devs and inform them about this bug in the migration.

🔗 Related PR / Discussion / Issue

Link: #

✅ Prerequisites

Before this PR can be reviewed, the following must be completed:

  • Self-review performed – Code follows established patterns and conventions.
  • Testing performed – Changes have been thoroughly tested and verified.

🛠️ Type of Change

Select all that apply:

  • [] 🆕 New script – A fully functional and tested script or script set.
  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • [] ✨ New feature – Adds new, non-breaking functionality.
  • [] 💥 Breaking change – Alters existing functionality in a way that may require updates.

📋 Additional Information (optional)

**Original Pull Request:** https://github.com/community-scripts/ProxmoxVE/pull/2676 **State:** closed **Merged:** Yes --- ## ✍️ Description <!-- Provide a clear and concise description of your changes. --> Out of any weird reason, homarr outputs the migration into a seperate subolder /migration, which then ends up with /opt/homarr_db/migration/migration instead of /opt/homarr_db/migration a sinple cp with recursive did not work, unless manually executed. Will talk to homarr-devs and inform them about this bug in the migration. ## 🔗 Related PR / Discussion / Issue Link: # ## ✅ Prerequisites Before this PR can be reviewed, the following must be completed: - [x] **Self-review performed** – Code follows established patterns and conventions. - [x] **Testing performed** – Changes have been thoroughly tested and verified. ## 🛠️ Type of Change Select all that apply: - [] 🆕 **New script** – A fully functional and tested script or script set. - [x] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [] ✨ **New feature** – Adds new, non-breaking functionality. - [] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. ## 📋 Additional Information (optional) <!-- Provide extra context, screenshots, or references if needed. -->
OVERLORD added the pull-request label 2026-02-05 05:56:10 +03:00
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 pull-request
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#3774
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?