Tor Browser issueshttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues2024-01-25T10:23:09Zhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42293Updater is disabled when tor-browser is run by torbrowser-launcher flatpak2024-01-25T10:23:09ZboklmUpdater is disabled when tor-browser is run by torbrowser-launcher flatpakIt looks like Tor Browser updater is disabled when run from the Flatpak
version of torbrowser-launcher:
- https://github.com/torproject/torbrowser-launcher/issues/721#issuecomment-1824742227
- https://searchfox.org/mozilla-central/source...It looks like Tor Browser updater is disabled when run from the Flatpak
version of torbrowser-launcher:
- https://github.com/torproject/torbrowser-launcher/issues/721#issuecomment-1824742227
- https://searchfox.org/mozilla-central/source/toolkit/mozapps/update/AppUpdater.sys.mjs#404
This is probably what we want when we'll have a Tor Browser Flatpak, but
not for the torbrowser-launcher Flatpak.boklmboklmhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42101Incremental update from 13.0a2 to 13.0a4 fails to apply2023-10-03T17:33:28ZrichardIncremental update from 13.0a2 to 13.0a4 fails to applyJust did a quick test on Linux, the incremental fails then the full update is downloaded and applied.
archive link: https://archive.torproject.org/tor-package-archive/torbrowser/13.0a2/
Have not looked into cause yet.
/cc @pierov @boklmJust did a quick test on Linux, the incremental fails then the full update is downloaded and applied.
archive link: https://archive.torproject.org/tor-package-archive/torbrowser/13.0a2/
Have not looked into cause yet.
/cc @pierov @boklmPier Angelo VendramePier Angelo Vendramehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41531Unable to update to 12.0.1 on Apple Silicon-based Mac2022-12-17T09:07:38ZdonutsUnable to update to 12.0.1 on Apple Silicon-based MacI'm getting this error when I try to update from 12.0 to 12.0.1 on my Apple Silicon-based Mac:
![apple-silicon-incomatible](/uploads/4f0960b9e1cfc91cdc69dd234f68f4e0/apple-silicon-incomatible.png)
Updating on my Intel machine seems to ...I'm getting this error when I try to update from 12.0 to 12.0.1 on my Apple Silicon-based Mac:
![apple-silicon-incomatible](/uploads/4f0960b9e1cfc91cdc69dd234f68f4e0/apple-silicon-incomatible.png)
Updating on my Intel machine seems to work fine, and I can successfully install 12.0.1 on my Apple Silicon-based mac manually too.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41140Review Mozilla 1751366: Disable tab unloading in private windows (Firefox up...2022-10-25T18:21:20ZrichardReview Mozilla 1751366: Disable tab unloading in private windows (Firefox update coupled with tabs unloading can cause loss of tabs in private browsing)## https://bugzilla.mozilla.org/show_bug.cgi?id=1751366
This sent up warning flags since Tor Browser is always in private browsing mode, but there may be nothing for us to worry about here given that we use a different update process.## https://bugzilla.mozilla.org/show_bug.cgi?id=1751366
This sent up warning flags since Tor Browser is always in private browsing mode, but there may be nothing for us to worry about here given that we use a different update process.Sponsor 131 - Phase 3 - Major ESR 102 Migrationma1ma1https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41126Review Mozilla 1734262: Rewrite pingsender as a Gecko Background Task2022-10-24T06:48:45ZrichardReview Mozilla 1734262: Rewrite pingsender as a Gecko Background TaskWe disable building the pingsender executable (part of the vanilla updater iirc) entirely. We should ensure any funcitonality we don't want here is disabled.We disable building the pingsender executable (part of the vanilla updater iirc) entirely. We should ensure any funcitonality we don't want here is disabled.Sponsor 131 - Phase 3 - Major ESR 102 Migrationma1ma1https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41100Add unsupported OS warning UX when tor-browser upgrade cannot happen due to u...2024-03-11T14:40:50ZrichardAdd unsupported OS warning UX when tor-browser upgrade cannot happen due to user's device no longer meeting min-specWe have logic in UpdateService.jsm that detects when the user's OS version is incompatible with a pending update, but we don't have any UX to tell the user about it.
As part of this we should also add a debug pref for exercising this co...We have logic in UpdateService.jsm that detects when the user's OS version is incompatible with a pending update, but we don't have any UX to tell the user about it.
As part of this we should also add a debug pref for exercising this code path (similar to how we use `torbrowser.debug.censorship_level` in TorConnect.jsm)Sponsor 131 - Phase 2 - Privacy Browserhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41045Phantom update notification in Tor Browser Alpha2022-11-30T15:26:53ZninaPhantom update notification in Tor Browser Alpha<!--
* Use this issue template for reporting a new bug.
-->
### Summary
After opening TB Alpha the browser informed about the existing update. However, failed to update automatically. So I deleted existing TB Alpha an re-installed from ...<!--
* Use this issue template for reporting a new bug.
-->
### Summary
After opening TB Alpha the browser informed about the existing update. However, failed to update automatically. So I deleted existing TB Alpha an re-installed from the TP web site. However, I started browser anew I got an update reminder again. Then I checked for updates in Settings. And it said the browser was up to date. The update notification dissipated
But after I restart the update notification showed up again. And it did not disappeared after checking for updates.
I restarted again and got the red screen. Then I restarted again and got new update notification
### Steps to reproduce:
**How one can reproduce the issue - this is very important.**
1. Open TB Alpha
### Environment
MacOS Monterey
TB Alpha 11.5a13
### Relevant logs and/or screenshots
![Screenshot_2022-07-06_at_11.48.10](/uploads/22295fbbcb7521a4c60026b0b6c21e5a/Screenshot_2022-07-06_at_11.48.10.png)
![Screenshot_2022-07-06_at_11.38.20](/uploads/572e815c141108d2e7f04b85b1031039/Screenshot_2022-07-06_at_11.38.20.png)https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40906Update breaking the browser2022-11-08T20:13:38ZmcgiwerUpdate breaking the browser### Environment
- **OS**: Debian 11
- **Browser version**: 91.5.0 esr
- **Downloaded from**: Official website
- **Download form**: Packed with Zip binaries
- **Persistance**: yes, It does appear in newer versions as well
### Summary
Af...### Environment
- **OS**: Debian 11
- **Browser version**: 91.5.0 esr
- **Downloaded from**: Official website
- **Download form**: Packed with Zip binaries
- **Persistance**: yes, It does appear in newer versions as well
### Summary
After the browser restart to apply some settings and a new version is avaliable, the browser self start to update and usually fail's, corrupting the current installation
### Steps to reproduce
1. use the browser
2. when a new version appear, restart the browser that it updates (the autoupdate option in settings need to be turned on)
3. After failed update try to launch again the browser
4. see the errors
### What is the current bug behavior?
Error:
```
Exception ignored in: <_io.TextIIWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
[1]+ Done ./firefox
```
### What is the expected behavior?
TorBrowser application interface
### Relevant logs and/or screenshots
Same as quoted above. Due technical issues, I'm unable to take any screenshoot'shttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40274Create new nightly MAR signing key2021-01-11T21:37:32ZGeorg KoppenCreate new nightly MAR signing keyIn tor-browser-build#40146 we moved to our new signing machine but we
kept for now the old nightly signing key. We baked in a second MAR
signing key which should take over in a couple of days. However, before
that one moves into the firs...In tor-browser-build#40146 we moved to our new signing machine but we
kept for now the old nightly signing key. We baked in a second MAR
signing key which should take over in a couple of days. However, before
that one moves into the first position and onto our signing machine we
want to have a new backup key embeddedTor Browser: 10.5Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40221Adapt nightly update URL2022-07-09T03:56:21ZGeorg KoppenAdapt nightly update URLWe patch the nightly update URL in `tor-browser-build` ad-hoc but we should move that out of `tor-browser-build` into a proper `tor-browser` patch.We patch the nightly update URL in `tor-browser-build` ad-hoc but we should move that out of `tor-browser-build` into a proper `tor-browser` patch.Tor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40018Linux64 10.0a1-10.0a2 incremental update fails2020-07-01T14:02:57ZMatthew FinkelLinux64 10.0a1-10.0a2 incremental update failsIn `Browser/TorBrowser/UpdateInfo/updates/last-update.log`, I see:
```
FINISH PATCH TorBrowser/Tor/tor
backup_restore: cannot get info for backup file: TorBrowser/Tor/tor.moz-backup, err: 2
FINISH PATCH TorBrowser/Docs/ChangeLog.txt
back...In `Browser/TorBrowser/UpdateInfo/updates/last-update.log`, I see:
```
FINISH PATCH TorBrowser/Tor/tor
backup_restore: cannot get info for backup file: TorBrowser/Tor/tor.moz-backup, err: 2
FINISH PATCH TorBrowser/Docs/ChangeLog.txt
backup_restore: cannot get info for backup file: TorBrowser/Docs/ChangeLog.txt.moz-backup, err: 2
FINISH ADD TorBrowser/Data/Browser/profile.default/extensions/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi
backup_restore: cannot get info for backup file: TorBrowser/Data/Browser/profile.default/extensions/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi.moz-backup, err: 2
failed: 2
calling QuitProgressUI
```
The updater logs show the file was successfully downloaded and verified:
```
*** AUS:SVC Downloader:onStartRequest - original URI spec: https://cdn.torproject.org/aus1/torbrowser/10.0a2/tor-browser-linux64-10.0a1-10.0a2_en-US.incremental.mar, final URI spec: https://cdn-fastly.torproject.org/aus1/torbrowser/10.0a2/tor-browser-linux64-10.0a1-10.0a2_en-US.incremental.mar
*** AUS:SVC Downloader:onProgress - progress: 512/4773259
*** AUS:SVC Downloader:onProgress - progress: 27420/4773259
*** AUS:SVC Downloader:onProgress - progress: 67179/4773259
*** AUS:SVC Downloader:onProgress - progress: 163149/4773259
[snip]
*** AUS:SVC Downloader:onProgress - progress: 4512012/4773259
*** AUS:SVC Downloader:onProgress - progress: 4725004/4773259
*** AUS:SVC Downloader:onProgress - progress: 4773259/4773259
*** AUS:SVC Downloader:onStopRequest - downloader: nsIIncrementalDownload, original URI spec: https://cdn.torproject.org/aus1/torbrowser/10.0a2/tor-browser-linux64-10.0a1-10.0a2_en-US.incremental.mar, final URI spec: https://cdn-fastly.torproject.org/aus1/torbrowser/10.0a2/tor-browser-linux64-10.0a1-10.0a2_en-US.incremental.mar, status: 0
*** AUS:SVC Downloader:onStopRequest - status: 0, current fail: 0, max fail: 10, retryTimeout: 2000
*** AUS:SVC Downloader:_verifyDownload called
*** AUS:SVC Downloader:_verifyDownload downloaded size == expected size.
*** AUS:SVC Downloader:_verifyDownload hashes match.
```
However, installing the complete update was successful.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/3436510.0a1 mar update failing2020-06-27T14:31:34ZMatthew Finkel10.0a1 mar update failing```
*** AUS:SVC Creating UpdateService
*** AUS:SVC Logging current UpdateService status:
*** AUS:SVC UpdateService.canCheckForUpdates - able to check for updates
*** AUS:SVC getCanApplyUpdates - testing write access /home/user/tor-browse...```
*** AUS:SVC Creating UpdateService
*** AUS:SVC Logging current UpdateService status:
*** AUS:SVC UpdateService.canCheckForUpdates - able to check for updates
*** AUS:SVC getCanApplyUpdates - testing write access /home/user/tor-browser_en-US/Browser/TorBrowser/UpdateInfo/update.test
*** AUS:SVC getCanApplyUpdates - able to apply updates
*** AUS:SVC getCanStageUpdates - staging updates is disabled by preference app.update.staging.enabled
*** AUS:SVC Elevation required: false
*** AUS:SVC Update being handled by other instance: false
*** AUS:SVC Downloading: false
*** AUS:SVC End of UpdateService status
*** AUS:SVC getCanStageUpdates - staging updates is disabled by preference app.update.staging.enabled
*** AUS:SVC UpdateManager:_loadXMLFileIntoArray - XML file does not exist. path: /home/user/tor-browser_en-US/Browser/TorBrowser/UpdateInfo/active-update.xml
*** AUS:SVC getCanStageUpdates - staging updates is disabled by preference app.update.staging.enabled
*** AUS:SVC Checker: checkForUpdates, force: true
*** AUS:SVC Creating UpdateService
*** AUS:SVC Logging current UpdateService status:
*** AUS:SVC UpdateService.canCheckForUpdates - able to check for updates
*** AUS:SVC getCanApplyUpdates - testing write access /home/user/tor-browser_en-US/Browser/TorBrowser/UpdateInfo/update.test
*** AUS:SVC getCanApplyUpdates - able to apply updates
*** AUS:SVC getCanStageUpdates - staging updates is disabled by preference app.update.staging.enabled
*** AUS:SVC Elevation required: false
*** AUS:SVC Update being handled by other instance: false
*** AUS:SVC Downloading: false
*** AUS:SVC End of UpdateService status
*** AUS:SVC UpdateService.canCheckForUpdates - able to check for updates
*** AUS:SVC Checker:getUpdateURL - update URL: https://aus1.torproject.org/torbrowser/update_3/alpha/Linux_x86_64-gcc3/9.5a13/en-US?force=1
*** AUS:SVC Checker:checkForUpdates - sending request to: https://aus1.torproject.org/torbrowser/update_3/alpha/Linux_x86_64-gcc3/9.5a13/en-US?force=1
*** AUS:SVC Checker:onLoad - request completed downloading document
*** AUS:SVC Checker:onLoad - Getting sslStatus failed.
*** AUS:SVC Checker:onLoad - number of updates available: 1
*** AUS:SVC getCanApplyUpdates - testing write access /home/user/tor-browser_en-US/Browser/TorBrowser/UpdateInfo/update.test
*** AUS:SVC getCanApplyUpdates - able to apply updates
*** AUS:SVC Creating Downloader
*** AUS:SVC UpdateService:_downloadUpdate
*** AUS:SVC readStringFromFile - file doesn't exist: /home/user/tor-browser_en-US/Browser/TorBrowser/UpdateInfo/updates/0/update.status
*** AUS:SVC readStatusFile - status: null, path: /home/user/tor-browser_en-US/Browser/TorBrowser/UpdateInfo/updates/0/update.status
*** AUS:SVC getCanUseBits - Not using BITS because this is not Windows
*** AUS:SVC Downloader:downloadUpdate - Starting nsIIncrementalDownload with url: https://cdn.torproject.org/aus1/torbrowser/10.0a1/tor-browser-linux64-9.5a13-10.0a1_en-US.incremental.mar, path: /home/user/tor-browser_en-US/Browser/TorBrowser/UpdateInfo/updates/0/update.mar, interval: 0
*** AUS:SVC Downloader:onStartRequest - original URI spec: https://cdn.torproject.org/aus1/torbrowser/10.0a1/tor-browser-linux64-9.5a13-10.0a1_en-US.incremental.mar, final URI spec: https://cdn.torproject.org/aus1/torbrowser/10.0a1/tor-browser-linux64-9.5a13-10.0a1_en-US.incremental.mar
*** AUS:SVC Downloader:onStopRequest - downloader: nsIIncrementalDownload, original URI spec: https://cdn.torproject.org/aus1/torbrowser/10.0a1/tor-browser-linux64-9.5a13-10.0a1_en-US.incremental.mar, final URI spec: https://cdn.torproject.org/aus1/torbrowser/10.0a1/tor-browser-linux64-9.5a13-10.0a1_en-US.incremental.mar, status: 2147549183
*** AUS:SVC Downloader:onStopRequest - status: 2147549183, current fail: 0, max fail: 10, retryTimeout: 2000
*** AUS:SVC Downloader:onStopRequest - non-verification failure
*** AUS:SVC getStatusTextFromCode - transfer error: Failed (unknown reason), default code: 2152398849
*** AUS:SVC Downloader:onStopRequest - setting state to: download-failed
*** AUS:SVC Downloader:onStopRequest - verification of patch failed, downloading complete update patch
*** AUS:SVC UpdateService:_downloadUpdate
*** AUS:SVC readStringFromFile - file doesn't exist: /home/user/tor-browser_en-US/Browser/TorBrowser/UpdateInfo/updates/0/update.status
*** AUS:SVC readStatusFile - status: null, path: /home/user/tor-browser_en-US/Browser/TorBrowser/UpdateInfo/updates/0/update.status
*** AUS:SVC Downloader:_selectPatch - found existing patch with state: null
*** AUS:SVC getCanUseBits - Not using BITS because this is not Windows
*** AUS:SVC Downloader:downloadUpdate - Starting nsIIncrementalDownload with url: https://cdn.torproject.org/aus1/torbrowser/10.0a1/tor-browser-linux64-10.0a1_en-US.mar, path: /home/user/tor-browser_en-US/Browser/TorBrowser/UpdateInfo/updates/0/update.mar, interval: 0
*** AUS:SVC Downloader:onStartRequest - original URI spec: https://cdn.torproject.org/aus1/torbrowser/10.0a1/tor-browser-linux64-10.0a1_en-US.mar, final URI spec: https://cdn.torproject.org/aus1/torbrowser/10.0a1/tor-browser-linux64-10.0a1_en-US.mar
*** AUS:SVC Downloader:onStopRequest - downloader: nsIIncrementalDownload, original URI spec: https://cdn.torproject.org/aus1/torbrowser/10.0a1/tor-browser-linux64-10.0a1_en-US.mar, final URI spec: https://cdn.torproject.org/aus1/torbrowser/10.0a1/tor-browser-linux64-10.0a1_en-US.mar, status: 2147549183
*** AUS:SVC Downloader:onStopRequest - status: 2147549183, current fail: 0, max fail: 10, retryTimeout: 2000
*** AUS:SVC Downloader:onStopRequest - non-verification failure
*** AUS:SVC getStatusTextFromCode - transfer error: Failed (unknown reason), default code: 2152398849
*** AUS:SVC Downloader:onStopRequest - setting state to: download-failed
*** AUS:SVC Downloader:onStopRequest - notifying observers of error. topic: update-error, status: download-attempt-failed
*** AUS:SVC UpdateManager:_writeUpdatesToXMLFile - no updates to write. removing file: /home/user/tor-browser_en-US/Browser/TorBrowser/UpdateInfo/active-update.xml
```https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/34319remove symlink support from the updater2023-05-13T09:51:57ZMark Smithremove symlink support from the updaterOur updater patch (legacy/trac#4234) adds support for handling symlinks during MAR file generation and in the updater itself. The original reason for adding this feature was to support meek's use of a second browser for its HTTP tunnel; ...Our updater patch (legacy/trac#4234) adds support for handling symlinks during MAR file generation and in the updater itself. The original reason for adding this feature was to support meek's use of a second browser for its HTTP tunnel; see legacy/trac#12647.
We no longer use symlinks on any platform. Kathy and I think we should remove the symlink portions of the legacy/trac#4234 patch (smaller patches == good).Sponsor 131 - Phase 3 - Major ESR 102 Migrationhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/33803Generate a second mar signing key for nightly2020-12-10T15:53:59ZboklmGenerate a second mar signing key for nightlyWe currently have only one mar signing key accepted by the nightly builds. To plan for rotation of the key, we should generate a second one in advance (offline), and add it as `toolkit/mozapps/update/updater/nightly_aurora_level3_seconda...We currently have only one mar signing key accepted by the nightly builds. To plan for rotation of the key, we should generate a second one in advance (offline), and add it as `toolkit/mozapps/update/updater/nightly_aurora_level3_secondary.der`.Tor Browser: 10.5Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/33521Check if RecommendedTBBVersions is still used2022-02-11T08:01:03ZboklmCheck if RecommendedTBBVersions is still usedAs part of the release process, we are updating RecommendedTBBVersions to put the new versions in it.
However according to GeKo, at least in the alpha, RecommendedTBBVersions is not used anymore. If that is not used in the stable relea...As part of the release process, we are updating RecommendedTBBVersions to put the new versions in it.
However according to GeKo, at least in the alpha, RecommendedTBBVersions is not used anymore. If that is not used in the stable release too, then we should remove that step from the release process.Tor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/33403Add nightly mar key to tor-browser2020-06-27T14:31:59ZboklmAdd nightly mar key to tor-browserIn legacy/trac#31988 I created a mar signing key for nightly builds. We should add it to tor-browser nightly builds.
It seems the path used by nightly build is `toolkit/mozapps/update/updater/nightly_aurora_level3_primary.der` (and `nig...In legacy/trac#31988 I created a mar signing key for nightly builds. We should add it to tor-browser nightly builds.
It seems the path used by nightly build is `toolkit/mozapps/update/updater/nightly_aurora_level3_primary.der` (and `nightly_aurora_level3_secondary.der`).boklmboklmhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/33402Set app.update.url for nightly builds2020-06-27T14:31:59ZboklmSet app.update.url for nightly buildsWe won't use the same `app.update.url` for releases and nightly builds. So we need to change this pref in the nightly builds.
https://nightlies.tbb.torproject.org/nightly-updates/updates/ is where the updates xml for nightly builds are ...We won't use the same `app.update.url` for releases and nightly builds. So we need to change this pref in the nightly builds.
https://nightlies.tbb.torproject.org/nightly-updates/updates/ is where the updates xml for nightly builds are located.boklmboklmhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/33380Add build-infos.json to sha256sums-unsigned-build.txt2020-06-27T14:32:00ZboklmAdd build-infos.json to sha256sums-unsigned-build.txtIn legacy/trac#32768 we added a `build-infos-$os.json` file. To make download of this file easier/safer, I think we should add it to `sha256sums-unsigned-build.txt`.In legacy/trac#32768 we added a `build-infos-$os.json` file. To make download of this file easier/safer, I think we should add it to `sha256sums-unsigned-build.txt`.boklmboklmhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/32805Make creation of downloads.json optional2020-06-27T14:32:13ZboklmMake creation of downloads.json optionalIn `tools/update-responses/update_responses` we generate a `downloads.json` file containing the list of bundles available for download. However we don't need to create that file for nightly builds, and only have the .mar files available ...In `tools/update-responses/update_responses` we generate a `downloads.json` file containing the list of bundles available for download. However we don't need to create that file for nightly builds, and only have the .mar files available when running this script for the nightly updates. So we should add an option to make creation of `downloads.json` optional.boklmboklmhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/32768Create a build-infos.json file containing firefox platform_version and buildid2020-06-27T14:32:14ZboklmCreate a build-infos.json file containing firefox platform_version and buildidTo generate the update-responses xml, we need to know the firefox `platformVersion` and `buildID`.
In standard releases we generate a `config.yml` from `projects/release/update_responses_config.yml` which includes the `platformVersion` ...To generate the update-responses xml, we need to know the firefox `platformVersion` and `buildID`.
In standard releases we generate a `config.yml` from `projects/release/update_responses_config.yml` which includes the `platformVersion` it gets from the rbm config. To get the `buildID` the `update_responses` script will extract a mar file to get it from `application.ini`.
While generating updates-responses xml for nightly builds (in legacy/trac#25102), we don't have easy access to the `platformVersion`. I think we could add it in a `build-infos.json` file. At the same time we can also include the `buildID` in that same file which removes the need to have mar-tools available to extract a mar file.boklmboklm