Fimeg/SouveraineOS
Watch
1
0
Fork
You've already forked SouveraineOS
 0
Code Releases Activity

distribution: declare blueline audio policy

Browse source 
Add the package to the blueline profile before Pixel3Arch builds it.\nIt owns the existing WirePlumber policy; historical ALSA state stays out.
This commit is contained in:
Fimeg 2026-08-14 11:22:07 -04:00
commit caf8f0af00
3 changed files with 20 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

7
PAF/audio.md
View file

@ -23,9 +23,10 @@ pin. It did **not** remove kernel commit `cd7758eae`'s sysclk + MICB2 hold; that
similar noun is the likely source of the remembered “we resolved it.”
The implementation lives in Pixel3Arch under `pkgs/souveraine-ucm-blueline`,
`pkgs/blueline-callaudio` (package name `souveraine-callaudio`),
`pkgs/souveraine-callaudiod`, and `pkgs/q6voiced` (package name
`souveraine-q6voiced`).
`pkgs/souveraine-wireplumber-blueline` (which packages the canonical
WirePlumber policy from `rootfs-overlay/`), `pkgs/blueline-callaudio` (package
name `souveraine-callaudio`), `pkgs/souveraine-callaudiod`, and
`pkgs/q6voiced` (package name `souveraine-q6voiced`).
Everything below is the evidence ledger. Headings such as “still open” describe
the date beneath them unless the current block above repeats the defect.

3
distribution/manifest.toml
View file

@ -43,6 +43,7 @@ linux-blueline-headers = { producer = "pixel3arch", architectures = ["aarch64"],
souveraine-callaudio = { producer = "pixel3arch", architectures = ["aarch64"], state = "managed" }
souveraine-callaudiod = { producer = "pixel3arch", architectures = ["aarch64"], state = "managed" }
souveraine-ucm-blueline = { producer = "pixel3arch", architectures = ["aarch64"], state = "managed" }
souveraine-wireplumber-blueline = { producer = "pixel3arch", architectures = ["aarch64"], state = "managed" }
souveraine-q6voiced = { producer = "pixel3arch", architectures = ["aarch64"], state = "managed" }
hexagonrpc-blueline = { producer = "pixel3arch", architectures = ["aarch64"], state = "managed" }
tqftpserv-blueline = { producer = "pixel3arch", architectures = ["aarch64"], state = "managed" }
@ -69,7 +70,7 @@ blockers = ["generic ARM provisioning has no completed installer"]
[profiles.blueline]
status = "blocked"
architectures = ["aarch64"]
packages = ["souveraine", "upower-souveraine", "souveraine-updater", "souveraine-viewtop", "linux-blueline", "souveraine-callaudio", "souveraine-callaudiod", "souveraine-ucm-blueline", "souveraine-q6voiced", "hexagonrpc-blueline", "tqftpserv-blueline", "blueline-edge-sense", "souveraine-squeekboard", "souveraine-stt", "blueline-camera", "blueline-usb-gadget", "blueline-fingerprintd", "blueline-boot-promote", "hyprgrass", "smoo", "usb-signaller"]
packages = ["souveraine", "upower-souveraine", "souveraine-updater", "souveraine-viewtop", "linux-blueline", "souveraine-callaudio", "souveraine-callaudiod", "souveraine-ucm-blueline", "souveraine-wireplumber-blueline", "souveraine-q6voiced", "hexagonrpc-blueline", "tqftpserv-blueline", "blueline-edge-sense", "souveraine-squeekboard", "souveraine-stt", "blueline-camera", "blueline-usb-gadget", "blueline-fingerprintd", "blueline-boot-promote", "hyprgrass", "smoo", "usb-signaller"]
blockers = ["linux-blueline is not published to the shared archive", "rootfs overlay content still needs package ownership"]
[profiles.x86-laptop]

14
docs/tasks/27-gitea-pipeline-audit.md
View file

@ -28,6 +28,20 @@ neither is on the device.
Deciding what owns the overlay — a `blueline-rootfs` package, or per-component
packages that each own their own units — is the first real decision here.
### First package repair — 2026-08-14
`souveraine-wireplumber-blueline` now owns the known-good blueline
WirePlumber policy: `51-blueline-audio-s16.conf` and `90-blueline.conf` under
`/etc/wireplumber/wireplumber.conf.d/`. Its sole source remains the matching
`Pixel3Arch/rootfs-overlay/` paths, so a fresh provision and a normal package
update use identical policy rather than two copies.
Pixel3Arch CI builds the package when either source changes and asserts both
paths in the artifact. The distribution graph includes it in the blueline
profile. This is package-source wiring until Gitea publishes it and the phone
adopts the files as owned paths. Do not package the historical `asound.state`:
its RX1/TX7 baseline is diagnostic evidence, not a restore source.
## Pipeline census, measured from the Gitea API 2026-07-25
61 repos on `gitea.wiuf.net` (= `10.10.20.120:4455`; same box, three URL forms