[tor-commits] [Git][tpo/applications/tor-browser-build][main] Bug 41114: Mullvad Browser 13.5a7-build2

[richard (@richard)]

richard pushed to branch main at The Tor Project / Applications / tor-browser-build


Commits:
5059b98c by Nicolas Vigier at 2024-04-25T17:01:35+02:00
Bug 41114: Mullvad Browser 13.5a7-build2

Update pkg_revision to force rebuild of linux-packages. Having
var/browser_release_date being in the past should solve the
reproducibility problem of the deb file.

- - - - -


5 changed files:

- .gitlab/issue_templates/Release Prep - Mullvad Browser Alpha.md
- .gitlab/issue_templates/Release Prep - Mullvad Browser Stable.md
- .gitlab/issue_templates/Release Prep - Tor Browser Alpha.md
- .gitlab/issue_templates/Release Prep - Tor Browser Stable.md
- rbm.conf


Changes:

=====================================
.gitlab/issue_templates/Release Prep - Mullvad Browser Alpha.md
=====================================
@@ -39,7 +39,7 @@ Mullvad Browser Alpha (and Nightly) are on the `main` branch
 - [ ] Update `rbm.conf`
   - [ ] `var/torbrowser_version` : update to next version
   - [ ] `var/torbrowser_build` : update to `$(MULLVAD_BROWSER_BUILD_N)`
-  - [ ] `var/browser_release_date` : update to build date
+  - [ ] `var/browser_release_date` : update to build date. For the build to be reproducible, the date should be in the past when building.
   - [ ] `var/torbrowser_incremental_from` : update to previous Desktop version
     - **NOTE**: We try to build incrementals for the previous 3 desktop versions except in the case of a watershed update
     - **IMPORTANT**: Really *actually* make sure this is the previous Desktop version or else the `make mullvadbrowser-incrementals-*` step will fail


=====================================
.gitlab/issue_templates/Release Prep - Mullvad Browser Stable.md
=====================================
@@ -39,7 +39,7 @@ Mullvad Browser Stable lives in the various `maint-$(MULLVAD_BROWSER_MAJOR).$(MU
 - [ ] Update `rbm.conf`
   - [ ] `var/torbrowser_version` : update to next version
   - [ ] `var/torbrowser_build` : update to `$(MULLVAD_BROWSER_BUILD_N)`
-  - [ ] `var/browser_release_date` : update to build date
+  - [ ] `var/browser_release_date` : update to build date. For the build to be reproducible, the date should be in the past when building.
   - [ ] `var/torbrowser_incremental_from` : update to previous Desktop version
     - **NOTE**: We try to build incrementals for the previous 3 desktop versions except in the case of a watershed update
     - **IMPORTANT**: Really *actually* make sure this is the previous Desktop version or else the `make mullvadbrowser-incrementals-*` step will fail


=====================================
.gitlab/issue_templates/Release Prep - Tor Browser Alpha.md
=====================================
@@ -38,7 +38,7 @@ Tor Browser Alpha (and Nightly) are on the `main` branch
 - [ ] Update `rbm.conf`
   - [ ] `var/torbrowser_version` : update to next version
   - [ ] `var/torbrowser_build` : update to `$(TOR_BROWSER_BUILD_N)`
-  - [ ] `var/browser_release_date` : update to build date
+  - [ ] `var/browser_release_date` : update to build date. For the build to be reproducible, the date should be in the past when building.
   - [ ] ***(Desktop Only)***`var/torbrowser_incremental_from` : update to previous Desktop version
     - **NOTE**: We try to build incrementals for the previous 3 desktop versions except in the case of a watershed update
     - **IMPORTANT**: Really *actually* make sure this is the previous Desktop version or else the `make torbrowser-incrementals-*` step will fail


=====================================
.gitlab/issue_templates/Release Prep - Tor Browser Stable.md
=====================================
@@ -38,7 +38,7 @@ Tor Browser Stable lives in the various `maint-$(TOR_BROWSER_MAJOR).$(TOR_BROWSE
 - [ ] Update `rbm.conf`
   - [ ] `var/torbrowser_version` : update to next version
   - [ ] `var/torbrowser_build` : update to `$(TOR_BROWSER_BUILD_N)`
-  - [ ] `var/browser_release_date` : update to build date
+  - [ ] `var/browser_release_date` : update to build date. For the build to be reproducible, the date should be in the past when building.
   - [ ] ***(Desktop Only)***`var/torbrowser_incremental_from` : update to previous Desktop version
     - **NOTE**: We try to build incrementals for the previous 3 desktop versions except in the case of a watershed update
     - **IMPORTANT**: Really *actually* make sure this is the previous Desktop version or else the `make torbrowser-incrementals-*` step will fail


=====================================
rbm.conf
=====================================
@@ -74,11 +74,13 @@ buildconf:
 
 var:
   torbrowser_version: '13.5a7'
-  torbrowser_build: 'build1'
+  torbrowser_build: 'build2'
   torbrowser_incremental_from:
     - '13.5a6'
     - '13.5a5'
     - '13.5a4'
+  # This should be the date of when the build is started. For the build
+  # to be reproducible, browser_release_date should always be in the past.
   browser_release_date: '2024/04/25 12:00:00'
   browser_release_date_timestamp: '[% USE date; date.format(c("var/browser_release_date"), "%s") %]'
   updater_enabled: 1



View it on GitLab: https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/commit/5059b98cb13b31f91976073bdffbc74f6d20c08b

-- 
This project does not include diff previews in email notifications.
View it on GitLab: https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/commit/5059b98cb13b31f91976073bdffbc74f6d20c08b
You're receiving this email because of your account on gitlab.torproject.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-commits/attachments/20240425/52990690/attachment-0001.htm>