echo "release/v5.0" | sudo tee /etc/pihole/ftlbranch
pihole checkout core release/v5.0
pihole checkout web release/v5.0
I did not get errors, but it did not seem to update me to the beta. If I run pihole version, I get:
pi@raspberrypi:~ $ pihole version
Pi-hole version is v4.3.5-467-g413fa94 (Latest: v4.4)
AdminLTE version is v4.3.2-462-g8e51f75 (Latest: v4.3.3)
FTL version is vDev-853261b (Latest: v4.3.1)
And if I run pihole -up
pi@raspberrypi:~ $ pihole -up
[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] Web Interface: up to date
[i] FTL: up to date
[i] Warning: You are using FTL from a custom branch (release/v5.0) and might be missing future releases.
Per your debug log, you are on the release/v5.0 branches, but as version 5 has not yet been tagged, the version string shows the latest tag it knows about. The important part on the dev/beta branches is the 7 character hash at the end of the string, which points to the commit your install is currently at.
As noted, the debug log has more version information than the version command from the command line. The log includes the branch where applicable. As of the time of your post and this reply, this is the latest available for beta 5.0.
I don't really understand why, but two out of three of my Pi-hole instances (one Ubuntu 18.04.4 LTS VM & one Raspbian GNU/Linux 10 (buster) Lite on RPi3B+) are both stuck at Pi-hole version is v4.3.5-460-g413fa94 -- both were initially just upgraded to v5.0 last evening and multiple attempts at further updates (just now, which both claimed success)...
the Ubuntu Server 20.04 Focal Fossa VM which was spun up last week is showing the newer/latest version:
Pi-hole version is v4.3.5-467-g413fa94 (Latest: v4.4)
AdminLTE version is v4.3.2-462-g8e51f75 (Latest: v4.3.3)
FTL version is vDev-853261b (Latest: v4.3.1)
Not a huge deal, just wondering what I could possibly be doing wrong, as identical upgrade process was used in all three places. Thanks for a great release, team.
These are all on the same version. The hash code for the version is the same. The 460 or 467 is the number of commits ahead.
v4.3.5-460-g413fa94
This means the base is version 3.5 plus 460 commits to the code with a git identifying hash of 413fa94. Even if the commits ahead is different, if they have the same hash they are the same release.