Repository navigation
fix: ship Colony Firewall Control 0.9.1 - #11
Merged
Merged
Conversation
Fourteen upstream commits since 0.8.0. None of them touch pkg/ or systemd/, only Cargo.lock, so the recipe is unchanged apart from pkgver and the checksum, which was verified against the v0.9.1 archive.
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
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.
Bumps colony-firewall-control and colony-firewall-control-ebpf from 0.8.0 to 0.9.1.
Upstream has 14 commits between v0.8.0 and v0.9.1. None touch
pkg/orsystemd/; onlyCargo.lockchanges, so the PKGBUILD changes arepkgverandsha256sums. The checksum was checked withmakepkg --verifysourceagainst the v0.9.1 archive, and.SRCINFOis regenerated.