Move the following scenario to the CI (except for Windows and macOS where testing the scenario is implicit and easier).
10. Updating Dangerzone handles external state correctly.
(Applies to Linux/Windows/MacOS. For MacOS/Windows, it requires an installer
for the new version)
Install the previous version of Dangerzone system-wide:
For MacOS/Windows, use the version from the website.
For Linux, uninstall Dangerzone from your test environment, and install the
previous version using our installation instructions. Also,
keep in mind the following:
In order to run commands as root, execute into the container as root with
podman exec -it -u root <container ID> bash.
If you encounter a GPG error, run the dirmngr command to create the
necessary directories.
Open the Dangerzone application and enable some non-default settings. Close the
Dangerzone application and get the container image for that version. For
example:
$ podman images dangerzone.rocks/dangerzone:latest
REPOSITORY TAG IMAGE ID CREATED SIZE
dangerzone.rocks/dangerzone latest <image ID> <date> <size>
(use docker on Windows/MacOS)
Install the new version of Dangerzone system-wide. For Linux, copy the package
back into the container. Open the Dangerzone application and make sure that the
previously enabled settings still show up. Also, ensure that Dangerzone reports
that the new image has been installed, and verify that it's different from the
old one by doing:
$ podman images dangerzone.rocks/dangerzone:latest
REPOSITORY TAG IMAGE ID CREATED SIZE
dangerzone.rocks/dangerzone latest <different ID> <newer date> <different size>
Move the following scenario to the CI (except for Windows and macOS where testing the scenario is implicit and easier).
10. Updating Dangerzone handles external state correctly.
(Applies to Linux/Windows/MacOS. For MacOS/Windows, it requires an installer for the new version)
Install the previous version of Dangerzone system-wide:
podman exec -it -u root <container ID> bash.dirmngrcommand to create the necessary directories.Open the Dangerzone application and enable some non-default settings. Close the Dangerzone application and get the container image for that version. For example:
(use
dockeron Windows/MacOS)Install the new version of Dangerzone system-wide. For Linux, copy the package back into the container. Open the Dangerzone application and make sure that the previously enabled settings still show up. Also, ensure that Dangerzone reports that the new image has been installed, and verify that it's different from the old one by doing: