Testing / Legacy Branch Support
Posted: Tue Jan 30, 2024 11:49 am
As we move toward a world of up-to-date firmwares, and up to date DV related binaries, there is clearly a need for some of you to stay put on the older releases - maybe your boards just won't play nice, maybe they are manufacturer locked etc.
To help support you, we now have a "legacy" branch of binaries (and matching 1.5.2 firmware).
You can swap to the legacy branch (and reflash your Hotspot Hat if required).
To swap you need to login over SSH and run some commands:
For the mavericks among you who'd like to live on the bleeding edge, I will also keep the builds in the "testing" branch, these will be right up to date, within a day or so of the work going on in the source repos, I may even fully automate these deployments to testing later.
Finally to return to the normal branch you can just
Once you swap branches, do a normal pistar-update (either on the CLI or on the Dashboard to make sure you're all up-to-date for your branch.
You will see that the update process now shows the branch you are tracking:
Finally if you swap about a lot, you may see the message:
This can be safely ignored; it just means you have used this branch before (you may see this when moving back to "master" from "testing" for example.
To help support you, we now have a "legacy" branch of binaries (and matching 1.5.2 firmware).
You can swap to the legacy branch (and reflash your Hotspot Hat if required).
To swap you need to login over SSH and run some commands:
Code: Select all
pi-star@pi-star(ro):~$ rpi-rw
pi-star@pi-star(rw):~$ sudo git --work-tree=/usr/local/bin/ --git-dir=/usr/local/bin/.git fetch origin
pi-star@pi-star(rw):~$ sudo git --work-tree=/usr/local/bin/ --git-dir=/usr/local/bin/.git checkout legacy
pi-star@pi-star(rw):~$ sudo git --work-tree=/usr/local/bin/ --git-dir=/usr/local/bin/.git checkout -t origin/legacy
For the mavericks among you who'd like to live on the bleeding edge, I will also keep the builds in the "testing" branch, these will be right up to date, within a day or so of the work going on in the source repos, I may even fully automate these deployments to testing later.
Code: Select all
pi-star@pi-star(ro):~$ rpi-rw
pi-star@pi-star(rw):~$ sudo git --work-tree=/usr/local/bin/ --git-dir=/usr/local/bin/.git fetch origin
pi-star@pi-star(rw):~$ sudo git --work-tree=/usr/local/bin/ --git-dir=/usr/local/bin/.git checkout testing
pi-star@pi-star(rw):~$ sudo git --work-tree=/usr/local/bin/ --git-dir=/usr/local/bin/.git checkout -t origin/testing
Code: Select all
pi-star@pi-star(ro):~$ rpi-rw
pi-star@pi-star(rw):~$ sudo git --work-tree=/usr/local/bin/ --git-dir=/usr/local/bin/.git fetch origin
pi-star@pi-star(rw):~$ sudo git --work-tree=/usr/local/bin/ --git-dir=/usr/local/bin/.git checkout master
pi-star@pi-star(rw):~$ sudo git --work-tree=/usr/local/bin/ --git-dir=/usr/local/bin/.git checkout -t origin/master
You will see that the update process now shows the branch you are tracking:
Code: Select all
Updating Pi-Star Binaries...
No updates for /usr/local/sbin (Branch: master) available
Done
Code: Select all
fatal: A branch named 'master' already exists.