phase1: satisfy getver.sh requirements

[f00b4r0]

scripts/getver.sh requires upstream branch tracking to correctly compute revision number. Buildbot Git() step does not set branch tracking as it checks out individual commits and then reset the target branch to it, so in order for getver.sh to work, this workaround forcefully sets the upstream branch.

This fixes malformed version code in filenames as observed on openwrt-23.05:

r23001+3-38c150612c
instead of:
r23004-7f0db09513

[Ansuel]

@hnyman tada :D

[hnyman]

@Ansuel
great that the bug (apparently related to the new buildbot config code) and a fix was found. ;-)

Like I earlier said to you, it seemed to be related to the buildbot only, as local build env showed the correct versioning.

[f00b4r0]

it was indeed done in old code, "hidden" in the gitcheckout step which was removed:

buildbot/phase1/master.cfg

Line 808 in ab75514

command = "if [ -d .git ]; then git checkout -f %s && git branch --set-upstream-to origin/%s || rm -fr .git; else exit 0; fi" %(repo_branch, repo_branch),

So I think this is indeed the correct fix; assuming it doesn't explode elsewhere of course ;P

[ynezz]

The build queue is quite long, I've applied this changes manually and it seems to be fine, thanks!

[ynezz]

And first build with that fix https://downloads.openwrt.org/releases/23.05-SNAPSHOT/targets/apm821xx/sata/

[aparcar]

Nice work everyone

[hnyman]

Ps. the mirror https://git.openwrt.org/?p=buildbot.git;a=summary strangely shows the tag "v6" but not the actual commit in the log of master. This commit can only be seen if the v6 tag is opened and then looked at the log from that perspective.