add missing install for hub.sr.ht
Add a dry-run mode to the cleanup script
Add cleanup script for getting rid of old packages after a delay
pkgkit: don't remove old packages on repo-add
Due to the frequency and timing of builds, we're seeing builds.sr.ht
failing to download needed packages on makepkg -s since they were
deleted already. Instead, we will add a cron job to clean up old
pkgkit: generate list of files upfront, then iterate for upload
Because ssh for the first line will swallow stdin for the second+ lines.
pkgkit: do not repo-add "only new packages"
if we have just uploaded a new package, but it shares the same version
as the old one, we are in big trouble if we skip recreating its database
entry. The checksums and PGP signature will be invalid.
We really shouldn't ever have this happen, so it should not make a
difference whether we use --new or not. But in practice, in at least one
case the release pipeline tried releasing the same package twice
(seemingly due to building both a commit push and a tag push, but upon
cloning, both had the tag, so both tried to deploy).
pkgkit: make set -x local to function, avoid printing "set +x" at the end
Although given it is run in a subshell func() ( ... ) it is localized
pkgkit: rely on makepkg --packagelist to find files to upload
core/pacman moved from .xz to .zst which broke the hardcoded logic.
Recent versions of makepkg have --packagelist specifically for this use
pkgkit: handle case where signing key is missing
python-misaka: unused now, drop it from the repo
python-srht migrate from misaka to mistletoe, bump version
python-mistletoe: new package
needed for core.sr.ht
meta: add new graphql API service
Signed-off-by: Eli Schwartz <firstname.lastname@example.org>
[bump versions and redeploy]
packages with compiled go binaries are no longer "any" packages!
remove some packages which are now in archlinux [community]
lists: add email processing services
todo: add email processing service
git.sr.ht: upgrade to latest version and add the API service
Don't use "Unknown Packager" for the official built packages.
Instead, use the identity of the gpg key being used to sign them.