Skip to content

docs: keep the Debian suite configurable with a trixie default #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
joshschmelzle merged 2 commits into from
Oct 27, 2026
Merged

docs: keep the Debian suite configurable with a trixie default #51

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3e947e0
docs: keep the Debian suite configurable with a trixie default
joshschmelzle Oct 27, 2026
1770090
docs: single source for Debian suite default on main
joshschmelzle Oct 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions PACKAGING_EXAMPLE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -605,9 +605,9 @@ jobs:
```

The deploy workflow fires when a `debian/changelog` change reaches `main`. A
git tag on its own does not deploy. The `sbuild-deploy-pkg` reusable workflow
builds for the Debian suites in its `distros` input and uploads to the
Packagecloud `dev` repository.
git tag on its own does not deploy. The `sbuild-deploy-pkg` reusable workflow builds for the suites in its
`distros` input (default `["trixie"]`) and uploads to the Packagecloud `dev`
repository.

## Step 9: Complete filesystem structure

Expand Down
2 changes: 1 addition & 1 deletion agents/AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ A forked upstream project versions as `<upstream>+wlanpi<N>`, for example `2.3.0

## CI

CI should keep Debian Trixie packaging jobs, plus compiler builds and tests. Do not add sid, Bookworm, Ubuntu, Arch, or Fedora jobs. WLAN Pi ships Debian packages, so do not maintain an Arch `PKGBUILD` or an RPM spec to track versions.
Packaging CI on `main` follows [Target Debian suite](https://github.com/WLAN-Pi/developers/blob/main/architecture/PACKAGING.md#target-debian-suite), plus compiler builds and tests.

## Documentation

Expand Down
9 changes: 9 additions & 0 deletions architecture/PACKAGING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,15 @@ If you want to create a new package for WLAN Pi:
2. Review this guide and the Packaging Example
3. Check [FHS Policy](FHS.md) for filesystem standards

## Target Debian suite

On `main`, WLAN Pi ships `.deb` packages built for Debian Trixie. CI runs
packaging jobs for that suite. Dockerfiles, build scripts, and workflow inputs
take the target suite as a parameter, with Trixie as the default (for example
a `SUITE` build arg, `DEBIAN_RELEASE`, or a workflow `distros` input).
Adopting the next Debian release updates that default, not the layout of the
build.

## Package structure

All WLAN Pi packages must follow this structure:
Expand Down