Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure that distros have Release files #13

Closed
wants to merge 5 commits into from

Conversation

apyrgio
Copy link
Contributor

@apyrgio apyrgio commented Dec 12, 2023

Ensure that every distro under ./dangerzone has a corresponding Release file, by doing the following:

  1. Cleaning up the repo before publishing packages.
  2. Adding a CI job that checks if there are missing Release files.

Fixes #11

@apyrgio
Copy link
Contributor Author

apyrgio commented Dec 12, 2023

To test the CI job, and simulate the error condition of #11, I temporarily removed a Release file from Debian Bullseye. The CI check catches this omission and fails accordingly:

$ for i in $(ls dangerzone); do ls -l ./repo/public/dists/${i}/Release{,.gpg}; done
-rw-r--r-- 1 root root 1425 Dec 12 15:59 ./repo/public/dists/bookworm/Release
-rw-r--r-- 1 root root  833 Dec 12 15:59 ./repo/public/dists/bookworm/Release.gpg
ls: cannot access './repo/public/dists/bullseye/Release': No such file or directory
-rw-r--r-- 1 root root 833 Dec 12 15:59 ./repo/public/dists/bullseye/Release.gpg

Exited with code exit status 2

Allow users to build a Debian image with `reprepro` installed. The goal
is to use the resulting image, and run the `./tools/publish` script in
a container.
Update our publish instruction to take advantage of the Dockerfile that
we offer in this repo. More specifically, offer instructions on how to
build the necessary container image, and how to run the
`./tools/publish` in a container.
Replace the Dangerzone 0.6.0 package with 0.6.1.
Run `./tools/publish` to update the local Debian repo, and then
`./tools/publish --sign`, to sign the Release files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Missing Release files are not detected by our checks
1 participant