Co-authored-by: ayumi-signal <143036029+ayumi-signal@users.noreply.github.com>
Co-authored-by: Fabian Vilers <fabian.vilers@dev-one.com>
This commit is contained in:
automated-signal 2024-08-30 15:23:32 -05:00 committed by GitHub
parent d77d112a49
commit 7c9ec90e8c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -38,16 +38,16 @@ $ cd Signal-Desktop/
This will download Signal Desktop's source code under the `Signal-Desktop` directory.
Now, select the version/branch you would like to verify. For instance, if you are trying to build `7.18.0`, then do:
Now, select the version/branch you would like to verify. For instance, if you are trying to build `7.22.0`, then do:
```bash
$ git checkout tags/v7.18.0
$ git checkout tags/v7.22.0
```
> [!NOTE]
> This guide uses `v7.18.0` as the placeholder version. You may want to change this version to the most recent one. All the versions are available here: https://github.com/signalapp/Signal-Desktop/tags. Older versions may however not be reproducible.
> This guide uses `v7.22.0` as the placeholder version. You may want to change this version to the most recent one. All the versions are available here: https://github.com/signalapp/Signal-Desktop/tags. Older versions may however not be reproducible.
At this point we are now on the branch of the source code used to build version `v7.18.0`. Before continuing, make sure your shell is in the `reproducible-builds` directory:
At this point we are now on the branch of the source code used to build version `v7.22.0`. Before continuing, make sure your shell is in the `reproducible-builds` directory:
```bash
$ cd reproducible-builds/
@ -67,7 +67,7 @@ $ ./build.sh public
This bash script will create the Docker container where Signal Desktop will be built, then download the required dependencies and start the build inside the container.
After the build is completed, the resulting file will be available in the `Signal-Desktop/release` folder. In our case, the file is named `signal-desktop_7.18.0_amd64.deb`.
After the build is completed, the resulting file will be available in the `Signal-Desktop/release` folder. In our case, the file is named `signal-desktop_7.22.0_amd64.deb`.
### Verifying the build
@ -100,10 +100,10 @@ If the checksums from the official build and your own build match, then the two
> Do not compare your output against the checksums given below! They only serve as a visual example of what the output would look like. Yours will look different!
```bash
$ sha256sum ../release/signal-desktop_7.18.0_amd64-OUR_BUILD.deb signal-desktop_7.18.0_amd64_OFFICIAL_BUILD.deb
$ sha256sum ../release/signal-desktop_7.22.0_amd64-OUR_BUILD.deb signal-desktop_7.22.0_amd64_OFFICIAL_BUILD.deb
0df3d06f74c6855559ef079b368326ca18e144a28ede559fd76648a62ec3eed7 ../release/signal-desktop_7.18.0_amd64-OUR_BUILD.deb
0df3d06f74c6855559ef079b368326ca18e144a28ede559fd76648a62ec3eed7 signal-desktop_7.18.0_amd64_OFFICIAL_BUILD.deb
0df3d06f74c6855559ef079b368326ca18e144a28ede559fd76648a62ec3eed7 ../release/signal-desktop_7.22.0_amd64-OUR_BUILD.deb
0df3d06f74c6855559ef079b368326ca18e144a28ede559fd76648a62ec3eed7 signal-desktop_7.22.0_amd64_OFFICIAL_BUILD.deb
```
### What to do if the checksums don't match