Add support for Fedora 39 #680
Merged
Commits on Jan 31, 2024
-
-
Fedora 39 ships with Python 3.12 by default, which Dangerzone previously did not support due to limitations from the PySide6 package. Now that the PySide6 package has been updated to 6.6.1, and the limitation has lifted, we should to reflect this in pyproject.toml.
-
Build Dangerzone RPM with PySide6 dependency
Update our RPM spec file to include PySide6 as a dependency, for Fedora 39 onward.
-
dev_scripts: Return exit code for failures
The env.py dev script does not return an exit code for failures, so we add the necessary 'return' statements to do so.
-
dev_scripts: Build end-user Fedora env with PySide6
Extend the env.py script to build an end-user, Fedora 39+ environment with PySide6 installed, as a regular RPM package. Previously, this was only possible for development environments with PySide6 downloaded from PyPI. As a way to simplify builds, the env.py script offers the option to download the RPM package itself from FPF's RPM repo [1], if the package has been uploaded. [1]: https://packages.freedom.press/yum-tools-prod
-
Add official support for Fedora 39
Now that we can create a Dangerzone RPM that depends on PySide6, we can officially support Fedora 39 as a platform. Add this platform in our CI tests, as well as our install/release notes. Fixes #606
-
ci: Build and install Dangerzone RPMs
Add some Fedora CI jobs that build RPMs, install them in an end-user environment, and make a simple conversion and GUI import check. These are basically smoke tests for Fedora, similar to the ones we have for Debian.
-
Elaborate on how to add/remove Linux platforms
Explain what's the process behind adding/removing Linux platforms, prior to a release.
-
Explain what happens when PySide6 gets updated
Explain what happens when we bump our `poetry.lock`, and a new Pyside6 version. Also, have a step-by-step guide on how the maintainer should create a new PySide6 RPM and update FPF's repo, so that Dangerzone can be released.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.