Checking out FTLDEV succeeds and updates AdminLTE to a FTLDEV version instead of master
Actual Behaviour:
$ pihole checkout web FTLDNS
[sudo] password for vlad:
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
I've tried this several times now, and every time I get the git ls-remote usage error. I'm using git version 2.7.4, although I don't think the syntax of ls-remote has changed over versions of git. I'm willing to do the update manually, although I'd prefer it going through the automated system. I was able to update core without any issue whatsoever:
If you are willing, let's move you to the 4.0 release branch. This contains all of the FTLDNS features and some other new features. The devs have also improved some of the install checks.
echo release/v4.0 | sudo tee /etc/pihole/ftlbranch
pihole checkout core release/v4.0
pihole checkout web release/v4.0
FWIW, I tried this and got similar results to the original poster:
$ echo release/v4.0 | sudo tee /etc/pihole/ftlbranch
release/v4.0
$ pihole checkout core release/v4.0
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
$ pihole checkout web release/v4.0
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
Similarly to tekneek, trying to switch to 4.0 also gives me the same error messages, for core as well now:
vlad@linux:/var/www/html/admin$ echo release/v4.0 | sudo tee /etc/pihole/ftlbranch
release/v4.0
vlad@linux:/var/www/html/admin$ pihole checkout core release/v4.0
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
vlad@linux:/var/www/html/admin$ pihole checkout web release/v4.0
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
From your debug log, which versions and branches and commits did you end up with for Core, Web and FTL? This shows more detailed information that may help us diagnose this problem.
Nada, same error and update now says everything is up to date:
vlad@linux:/var/www/html/admin$ echo release/v4.0 | sudo tee /etc/pihole/ftlbranch
release/v4.0
vlad@linux:/var/www/html/admin$ pihole checkout core release/v4.0
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
vlad@linux:/var/www/html/admin$ pihole checkout web release/v4.0
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
I made it over to release/v4.0 successfully, but for some reason lost my adlist completely (ended up with a new file w/ no entries - wish I had backed that up!). I've reconstructed that. Thankfully the local whitelist and blacklist were intact.
