-
Notifications
You must be signed in to change notification settings - Fork 4
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
Missing Release files are not detected by our checks #11
Comments
apyrgio
changed the title
Verify the repo is not in a corrupted state
Missing RELEASE files are not detected by our checks
Dec 11, 2023
apyrgio
added a commit
to apyrgio/apt-tools-prod
that referenced
this issue
Dec 11, 2023
Rerun the ./tools/publish script, after removing the ./repo/db directory, in order to create the missing Release files for Ubuntu Focal. By doing so, we also update the Release files for the rest of the distributions as well. Refs freedomofpress#11
This was referenced Dec 11, 2023
apyrgio
added a commit
to apyrgio/apt-tools-prod
that referenced
this issue
Dec 12, 2023
Make sure to clean up the repo, before publishing artifacts. Starting from scratch is necessary if we want to avoid some edge cases that can lead to a corrupted APT repo. Refs freedomofpress#11
apyrgio
added a commit
to apyrgio/apt-tools-prod
that referenced
this issue
Dec 12, 2023
Make sure to clean up the repo, before publishing artifacts. Starting from scratch is necessary if we want to avoid some edge cases that can lead to a corrupted APT repo. Refs freedomofpress#11
apyrgio
changed the title
Missing RELEASE files are not detected by our checks
Missing Release files are not detected by our checks
Dec 12, 2023
apyrgio
added a commit
to apyrgio/apt-tools-prod
that referenced
this issue
Feb 22, 2024
Make sure to clean up the repo, before publishing artifacts. Starting from scratch is necessary if we want to avoid some edge cases that can lead to a corrupted APT repo. Refs freedomofpress#11
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While releasing Dangerzone 0.5.1, we realized that the Ubuntu Focal repo does not have any
Release
files (see freedomofpress/dangerzone#653)The reason behind this seems to be that
./tools/publish
is not idempotent, if one terminates it abruptly (Ctrl-C) and retries. Worst, the validationsreprepro
performs (invoked by the./tools/publish
script) on the repo are not enough. The following commands complete successfully in our (corrupted in b5730cf) repo:(The
reprepro
version when testing the above commands is 5.4.2)The
deleteunreferenced
/clearvanished
commands are not picking up on the issue as well.Until we have a way to be sure that the repo is not corrupted, the best way forward is to delete the following directories, whenever we "publish" packages:
This is something we've been manually doing after all on every commit, so we will basically make it part of the script.
The text was updated successfully, but these errors were encountered: