#19528: The build id stays the same with every Firefox update -----------------------------------------------+--------------------------- Reporter: gk | Owner: tbb-team Type: defect | Status: | needs_information Priority: Medium | Milestone: Component: Applications/Tor Browser | Version: Severity: Normal | Resolution: Keywords: tbb-gitian, TorBrowserTeam201608R | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -----------------------------------------------+---------------------------
Comment (by boklm): Replying to [comment:19 gk]: > So, hrm. I am not so happy with keeping an extra buildid.txt file around. Can't we extract this info once from one of the full MAR files just before we are creating the update response files? Yes, I think we can do that if we want to avoid adding a buildid.txt file. > > I am not sure I understand the need for a hard-coded oldest supported ESR version? Could you elaborate? > > I am interested in getting rid of hard-coding the year as well but have not looked at how we could do that yet. When `MOZ_BUILD_DATE` is not set, the buildid is the current date. With the changes from this ticket we are converting the firefox version to a number that looks like a date, that we set in `MOZ_BUILD_DATE`. However the ESR branch (currently 45) is used as the month in the buildid number, but 45 is not a valid month so we need to subtract something if we want it to look like a valid date. If we don't care about `MOZ_BUILD_DATE` containing an invalid date, we could stop adding a year and subtracting something to the ESR version. But I don't know if some part of the build would break if `MOZ_BUILD_DATE` is not a valid date, or if it can work with any number. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19528#comment:20> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs