mirror of
https://github.com/pi-hole/pi-hole
synced 2025-08-03 12:58:07 +00:00
6db6c68a4e
Currently, if the FTL update check returns 404, hence the FTL branch does not seem to exist, an error message is printed, but the update continues, only the FTL update is skipped. This can lead to setups with v5 FTL and v6 core/web, failing at config migration, where FTL is invoked with a v6-only command. With this change, the update aborts immediately if the FTL branch is invalid, like it does in case of other FTL update check errors (other HTTP error codes than 404 or other curl errors). Hence it continues only if FTL is up-to-date already, or a new version from the given branch has been found. Signed-off-by: MichaIng <micha@dietpi.com> |
||
|---|---|---|
| .. | ||
| database_migration | ||
| api.sh | ||
| COL_TABLE | ||
| list.sh | ||
| piholeARPTable.sh | ||
| piholeCheckout.sh | ||
| piholeDebug.sh | ||
| piholeLogFlush.sh | ||
| query.sh | ||
| update.sh | ||
| updatecheck.sh | ||
| utils.sh | ||
| version.sh | ||