almet/dangerzone
1
0
Fork 0
mirror of https://github.com/freedomofpress/dangerzone.git synced 2025-05-04 20:51:49 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 7

Update fedora installation / release instructions

Browse source 
Changes instructions from the packagecloud setup to
packages.freedom.press
This commit is contained in:
deeplow 2023-04-06 09:49:18 +01:00
parent 1c0dfb45f5
commit e61a9e7783
No known key found for this signature in database
GPG key ID: 577982871529A52A
2 changed files with 75 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

43
INSTALL.md
View file

@ -53,18 +53,53 @@ sudo apt install -y dangerzone
### Fedora
Add our repository following [these instructions](https://packagecloud.io/firstlookmedia/code/install#manual-rpm), or by running this script:
### 1. Add our repository
Start by installing our repository. This allows you to
Open a terminal window and type the following commands:
```
curl -s https://packagecloud.io/install/repositories/firstlookmedia/code/script.rpm.sh | sudo bash
gpg --keyserver hkps://keys.openpgp.org --recv-key "DE28 AB24 1FA4 8260 FAC9 B8BA A7C9 B385 2260 4281"
gpg --export --armor A7C9B38522604281 | sudo tee /etc/pki/rpm-gpg/RPM-GPG-dangerzone.pub > /dev/null
sudo yum-config-manager --add-repo=https://packages.freedom.press/yum-tools-prod/dangerzone/dangerzone.repo
```
Install Dangerzone:
### 2. Install Dangerzone
```
sudo dnf install -y dangerzone
sudo dnf install dangerzone
```
<details>
<summary>Importing GPG key 0x22604281: ... Is this ok [y/N]:</summary>
After some minutes of running the above command (depending on your internet speed) you'll be asked to confirm the fingerprint of our signing key. This is to make sure that in the case our servers are compromized your computer stays safe. It should look like this:
```console
--------------------------------------------------------------------------------
Total 389 kB/s | 732 MB 32:07
Dangerzone repository 3.8 MB/s | 3.8 kB 00:00
Importing GPG key 0x22604281:
Userid : "Dangerzone Release Key <dangerzone-release-key@freedom.press>"
Fingerprint: DE28 AB24 1FA4 8260 FAC9 B8BA A7C9 B385 2260 4281
From : /etc/pki/rpm-gpg/RPM-GPG-dangerzone.pub
Is this ok [y/N]:
```
> **Note**: If it does not show this fingerprint confirmation or the fingerprint does not match, it is possible that our servers were compromized. Be distrustful and reach our to us.
The `Fingerprint` should be `DE28 AB24 1FA4 8260 FAC9 B8BA A7C9 B385 2260 4281`. For extra security, you should confirm matches the one at the bottom of our website ([dangerzone.rocks](https://dangerzone.rocks)) and our [mastodon account](https://fosstodon.org/@dangerzone) bio.
After confirming that it matches, type `y` (for yes) and the installation should proceed.
</details>
## Build from source
If you'd like to build from source, follow the [build instructions](https://github.com/freedomofpress/dangerzone/blob/master/BUILD.md).

36
RELEASE.md
View file

@ -212,6 +212,42 @@ Rename `Dangerzone.msi` to `Dangerzone-$VERSION.msi`.
Linux binaries are automatically built and deployed to repositories when a new tag is pushed.
### Fedora
Because the Fedora packages do not contain compiled Python code for a specific
Python version, we can create a single Debian package and use it for all of our
Debian-based distros.
> **NOTE**: This procedure will have to be done for every supported Fedora version.
>
> In this example, we'll use Fedora 37 as an example.
Create a Fedora development environment. You can [follow the
instructions in our build section](https://github.com/freedomofpress/dangerzone/blob/main/BUILD.md#fedora),
or create your own locally with:
```sh
./dev_scripts/env.py --distro fedora --version 37 build-dev
./dev_scripts/env.py --distro fedora --version 37 run --dev bash
cd dangerzone
```
Build the latest container:
```sh
./install/linux/build-image.sh
```
Create a .rpm:
```sh
./install/linux/build-rpm.py
```
Publish the .rpm under `./dist` to the
[`freedomofpress/yum-tools-prod`](https://github.com/freedomofpress/yum-tools-prod) repo, but sending a PR. Follow the instructions in that repo on how to do so.
## Publishing the release
To publish the release: