-
-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new explicit migration command #2139
base: development
Are you sure you want to change the base?
Conversation
This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there: https://discourse.pi-hole.net/t/broken-installation/74638/25 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I can see no functional changes but only putting code into new functions
Tested on two virtual machines to do what it should. The latest commit ensures we log the migration process to the user so they can quickly review if everything went the way they'd expect it to. |
…d in the help output as it is solely meant to be used internally by the installer script once from v5 -> v6 Signed-off-by: DL6ER <[email protected]>
Signed-off-by: DL6ER <[email protected]>
The most recent commit adds code to ensure a broken (or too new) database is not used when we know that all the SQL statements against it will fail anyway |
Rebased on latest |
…is not available (e.g. broken or more recent than this particular FTL binary can handle (like checking out a very old branch)) Signed-off-by: DL6ER <[email protected]>
Signed-off-by: DL6ER <[email protected]>
…nly mention it when debug.config is true. Signed-off-by: DL6ER <[email protected]>
What does this implement/fix?
pihole-FTL migrate v6
is intentionally not included in the help output as it is solely meant to be used internally by the installer script once from v5 -> v6Related to pi-hole/pi-hole#5830
Related issue or feature (if applicable): N/A
Pull request in docs with documentation (if applicable): N/A
By submitting this pull request, I confirm the following:
git rebase
)Checklist:
developmental
branch.