Opened 9 months ago

Closed 9 months ago

#29971 closed defect (fixed)

obfs4 fails to build in nightly builds

Reported by: boklm Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-rbm, TorBrowserTeam201903R
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


The build of obfs4 fails to build with the following error:

Starting build: Sun Mar 31 01:47:41 2019
/var/tmp/dist/gopath/src/ undefined: "".HelloFirefox_65
/var/tmp/dist/gopath/src/ undefined: "".HelloChrome_72
/var/tmp/dist/gopath/src/ undefined: "".HelloIOS_12_1
/var/tmp/dist/gopath/src/ undefined: "".EnableVartimeAES

This is probably fixed by updating the utls tag.

Child Tickets

Change History (5)

comment:1 Changed 9 months ago by boklm

Keywords: TorBrowserTeam201903R added; TorBrowserTeam201903 removed
Status: newneeds_review

comment:2 Changed 9 months ago by yawning

Whoops, sorry, forgot to give a heads up when I did that. Yes that looks fine.

At some point I'm thinking of tagging 0.0.10 because it has a pile of utls related fixes (upstream, in my fork, and to the transport)...

comment:3 in reply to:  1 Changed 9 months ago by gk

Replying to boklm:

There is a patch for review in branch bug_29971_v2:

I think are usually doing something like version: '[% c("abbrev") %]' in case we don't have a tag we can build from but provide a sha1 commit hash. Why are we doing here

+version: 0.0.0
+git_hash: 26d1add596b6d800bdeeb3bc3b2c7b316c056b6d


comment:4 Changed 9 months ago by boklm

Ah, yes, having the commit in the output filename would be better than 0.0.0 (although var/build_id is already changing when the commit is changing), so I changed that in branch bug_29971_v3:

comment:5 Changed 9 months ago by gk

Resolution: fixed
Status: needs_reviewclosed

Looks good. Merged to master (commit 893a4825b1a430ef955812248ebba8017a5c05d7).

Note: See TracTickets for help on using tickets.