feat: stop pinning licence contents, refresh version pins - #960
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Needs pkgforge/sbuilder#15.
Licences are no longer content-pinned. Every licence in the tree is fetched from a branch rather than a tag, so an upstream copyright-year edit changed the file and broke its hash. That cost the user their licence file and a warning, for a file that is documentation rather than something that runs. Each licence extra now sets
verify = false, and the 424 of them are recorded without hashes.This is scoped per extra rather than applied to side files as a whole. pueue ships
pueuedas a separate per-architecture binary, and that stays verified.Removing the hashes also drops 424 downloads from every hashfill pass.
Digest table ordering is now consistent. 20 files had their hash tables in a different host order from their
[url]table, an artefact of how the two were written. Every table now follows the url order.Version pins refreshed, with the upstream publication date recorded for each.
Validation is clean at 0 errors and 0 warnings, and hashfill is a no-op on a second run.