tor-browser-build issueshttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues2024-01-11T13:11:35Zhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/41054No 13.0.6-13.0.7 incrementals for mullvadbrowser2024-01-11T13:11:35ZboklmNo 13.0.6-13.0.7 incrementals for mullvadbrowserIt looks like we don't have 13.0.6-13.0.7 incrementals for
Mullvad Browser. However we have them for Tor Browser.
In 090f2219b789140838ff748cfc779e8921541ae4 the `Prepare Tor+Mullvad
Browser Stable 13.0.7` commit updated `var/torbrowser...It looks like we don't have 13.0.6-13.0.7 incrementals for
Mullvad Browser. However we have them for Tor Browser.
In 090f2219b789140838ff748cfc779e8921541ae4 the `Prepare Tor+Mullvad
Browser Stable 13.0.7` commit updated `var/torbrowser_incremental_from`
to include `13.0.6`, however there is a separate
`mullvadbrowser/var/torbrowser_incremental_from` which was not updated.boklmboklmhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40149Remove patching of nightly update URL2023-10-03T16:40:59ZGeorg KoppenRemove patching of nightly update URLWhile we are moving the nightly signing key into tor-browser (#40138) we should do so as well for the update URL change.While we are moving the nightly signing key into tor-browser (#40138) we should do so as well for the update URL change.Pier Angelo VendramePier Angelo Vendramehttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40936Revert tor-browser-build#409332023-12-01T08:49:02ZrichardRevert tor-browser-build#40933Once we are no longer building incrmentals from the 12.5 series, we should revert a21969281d18941b69a94b994b0797f8b88ad45f in `main`Once we are no longer building incrmentals from the 12.5 series, we should revert a21969281d18941b69a94b994b0797f8b88ad45f in `main`richardrichard2023-12-01https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40688Disable updater in base-browser2022-11-17T08:58:06ZboklmDisable updater in base-browserIt seems base-browser nightly currently gets updated to firefox nightly.
Until we have base-browser updates working, I think we should disable the updater.
Removing the line `--enable-update-channel=[% c("var/channel") %]` in `projects...It seems base-browser nightly currently gets updated to firefox nightly.
Until we have base-browser updates working, I think we should disable the updater.
Removing the line `--enable-update-channel=[% c("var/channel") %]` in `projects/firefox/build` should do that.Sponsor 131 - Phase 2 - Privacy Browserhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/18497Check that MAR signing is done properly on the files available in the update ...2023-01-31T20:39:12ZboklmCheck that MAR signing is done properly on the files available in the update responsesIn legacy/trac#18405 we are adding a script to be used during the release process to check that the MAR files are properly signed. We could have an other one that is doing the same things on the files currently proposed as an update. Thi...In legacy/trac#18405 we are adding a script to be used during the release process to check that the MAR files are properly signed. We could have an other one that is doing the same things on the files currently proposed as an update. This would allow someone to easily check (maybe as a cron job) that the updates currently available are the same as the ones in the sha256sums-unsigned-build files.
In tools/update-responses/check_update_responses_deployement we have a script that currently check that the update responses xml provides the expected version. I think I could extend it to also download the mar files it provides, unsign them and check that they match sha256sums-unsigned-build.txt.https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/18326Creating incremental MAR files should not include Tor Browser version in meta...2023-01-05T13:59:01ZGeorg KoppenCreating incremental MAR files should not include Tor Browser version in meta dataWhile trying to build the incrementals for 5.5.2 on a machine that had older mar-tools I ended up with them not matching incrementals built on other machines. Upon investigation it turned out that the browser versions gets embedded in th...While trying to build the incrementals for 5.5.2 on a machine that had older mar-tools I ended up with them not matching incrementals built on other machines. Upon investigation it turned out that the browser versions gets embedded in the MAR files' metadata. There is no need for doing that actually.https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/18867Ship auto-updates for Tor Browser nightly channel2020-10-25T12:54:44ZGeorg KoppenShip auto-updates for Tor Browser nightly channelWe want to get more users to test our nightly builds. The main hurdle currently is the missing auto-update. This is the parent ticket that tracks this task.We want to get more users to test our nightly builds. The main hurdle currently is the missing auto-update. This is the parent ticket that tracks this task.https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40138Move nightly signing key to tor-browser2022-04-04T17:53:05ZGeorg KoppenMove nightly signing key to tor-browserWhen fixing tor-browser#33803 we should make sure that the current nightly signing key is moved out of `tor-browser-build` as well (see: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/33803#note_2671931).When fixing tor-browser#33803 we should make sure that the current nightly signing key is moved out of `tor-browser-build` as well (see: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/33803#note_2671931).Tor Browser: 10.5Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/25102Add script to sign nightly build mar files, generate update-responses xml and...2020-10-25T12:48:01ZboklmAdd script to sign nightly build mar files, generate update-responses xml and publish the new versionWe need a script that will fetch the latest nightly build from the build machine, then sign the mar files and publish them.
Later we can improve it to fetch builds from multiple builders and only do the signing if they match.We need a script that will fetch the latest nightly build from the build machine, then sign the mar files and publish them.
Later we can improve it to fetch builds from multiple builders and only do the signing if they match.https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40100Make sure all older bundles are downloaded for incremental creation or fail hard2022-12-08T15:15:30ZGeorg KoppenMake sure all older bundles are downloaded for incremental creation or fail hardIf previous versions of Tor Browser needed for incremental .mar creation
are not available they will get downloaded first, which is great.
However, we should make sure that we have really all bundles downloaded
before proceeding to the ....If previous versions of Tor Browser needed for incremental .mar creation
are not available they will get downloaded first, which is great.
However, we should make sure that we have really all bundles downloaded
before proceeding to the .mar creation step. If not, we should fail hard.
Right now neither is happening which is a bad combination. :)https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40716Unable to update to 12.0.1 on Apple Silicon-based Mac2022-12-19T12:07:51ZdonutsUnable 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/a88e89de30bc07e1769780dcbc59ea88/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/a88e89de30bc07e1769780dcbc59ea88/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.