... | ... | @@ -205,6 +205,8 @@ Otherwise, please check that you are using the correct hashes, and then consider |
|
|
|
|
|
For desktop builds, we produce also smaller, incremental archives (`make incrementals-{release,alpha,nightly}`): their hashes are in `sha256sums-unsigned-build.incrementals.txt`, instead, but they should match as well.
|
|
|
|
|
|
If you are a TPO dev verifying a build, you can use the `make` targets `$browser-upload-sha256sumes-$channel` to sign and upload the hashes to people.torproject.org, assuming you've set a `tpo_user` in `rmb.local.conf`. Example command: `make torbrowser-upload-sha256sums-release`.
|
|
|
|
|
|
## Cleaning the artifacts
|
|
|
|
|
|
Since we often switch git branches, `make clean` tries to remove old artifacts in a smart way.
|
... | ... | |