--refresh (-r) generates Packages(.gz), then Release, and Release.gpg
finally, for each target directory. It requires access to
one of the GPG keys listed in the pirogue.gpg keyring
file (also shipped in the pirogue-archive-keyring
package).
--check (-c) generates Packages.check, and checks it's identical to
the existing Packages, for each target directory. It
exits with an error if at least one difference is
spotted.
Both actions can be combined, in which case refresh runs before check.
One can pass pirogue and/or pirogue-3rd party as arguments to pick which one(s) to operate on. By default, both are considered.
Hey @U039b, here's a reworked reindex script, renamed into ppa, supporting both --refresh and --check.
The former requires a pirogue.gpg keyring file to operate (see https://github.com/PiRogueToolSuite/debian-12/pull/7); the latter doesn't need it and can be used right away, e.g. in GitHub Actions to spot inconsistencies.
I'll leave it up to you to decide between merging that right away, or waiting after pirogue.gpg is in place.
For now it supports two operations:
--refresh (-r) generates Packages(.gz), then Release, and Release.gpg finally, for each target directory. It requires access to one of the GPG keys listed in the pirogue.gpg keyring file (also shipped in the pirogue-archive-keyring package).
--check (-c) generates Packages.check, and checks it's identical to the existing Packages, for each target directory. It exits with an error if at least one difference is spotted.
Both actions can be combined, in which case refresh runs before check.
One can pass pirogue and/or pirogue-3rd party as arguments to pick which one(s) to operate on. By default, both are considered.
Hey @U039b, here's a reworked
reindex
script, renamed intoppa
, supporting both--refresh
and--check
.The former requires a
pirogue.gpg
keyring file to operate (see https://github.com/PiRogueToolSuite/debian-12/pull/7); the latter doesn't need it and can be used right away, e.g. in GitHub Actions to spot inconsistencies.I'll leave it up to you to decide between merging that right away, or waiting after
pirogue.gpg
is in place.