Skip to content

add wireguard-tools wg-quick subpackage#78654

Open
skewballfox wants to merge 2 commits intowolfi-dev:mainfrom
skewballfox:wg-tools
Open

add wireguard-tools wg-quick subpackage#78654
skewballfox wants to merge 2 commits intowolfi-dev:mainfrom
skewballfox:wg-tools

Conversation

@skewballfox
Copy link
Copy Markdown

adds a subpackage to wireguard tools for wg-quick.

Fixes:
#78653
Related:

Pre-review Checklist

For new package PRs only

  • This PR is marked as fixing a pre-existing package request bug
    • Alternatively, the PR is marked as related to a pre-existing package request bug, such as a dependency
  • REQUIRED - The package is available under an OSI-approved or FSF-approved license
  • REQUIRED - The version of the package is still receiving security updates
  • This PR links to the upstream project's support policy (e.g. endoflife.date)

For new version streams

  • The upstream project actually supports multiple concurrent versions.
  • Any subpackages include the version string in their package name (e.g. name: ${{package.name}}-compat)
  • The package (and subpackages) provides: logical unversioned forms of the package (e.g. nodejs, nodejs-lts)
  • If non-streamed package names no longer built, open PR to withdraw them (see WITHDRAWING PACKAGES)

For package updates (renames) in the base images

When updating packages part of base images (i.e. cgr.dev/chainguard/wolfi-base or ghcr.io/wolfi-dev/sdk)

  • REQUIRED cgr.dev/chainguard/wolfi-base and ghcr.io/wolfi-dev/sdk images successfully build
  • REQUIRED cgr.dev/chainguard/wolfi-base and ghcr.io/wolfi-dev/sdk contain no obsolete (no longer built) packages
  • Upon launch, does apk upgrade --latest successfully upgrades packages or performs no actions

For security-related PRs

  • The security fix is recorded in the advisories repo

CVE Scanning: This PR will fail if ANY CVEs are found (fail-any mode). To customize:

  • Must-fix specific CVEs only: Add <!--ci-cve-scan:must-fix: CVE-ID--> markers and remove the line below
  • Fail on any CVEs (default): Keep the marker below
<!--ci-cve-scan:fail-any-->

For version bump PRs

  • The epoch field is reset to 0

For PRs that add patches

  • Patch source is documented

@skewballfox
Copy link
Copy Markdown
Author

kind of new to this, and didn't find a contributing.md. what's the epoch-bot about?

Increment epoch to 1 due to changes in build instructions.

Signed-off-by: Joshua Ferguson <joshua.ferguson.273@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant