forked from marfrit/marfrit-packages
marfrit
5feab57b6f
The previous commit used `debian-aarch64-bohr` for the runs-on label, but the actual registered label is the full `actrunner-debian-aarch64-bohr` (per @marfrit on the PR thread). Without the `actrunner-` prefix the job would have sat in the queue forever waiting for a runner that doesn't exist. Renames the label in three places: - .gitea/workflows/build.yml — the runs-on directive itself. - debian/.../build-deb.sh — the comment referencing the expected runner, and the error message printed when the ABI sanity check trips (so a future debug session lands on the right runner name). - debian/.../changelog — the -2 entry's prose description. Pure label rename; no behavioral or build-graph change. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
49 lines
2.5 KiB
Plaintext
49 lines
2.5 KiB
Plaintext
libva-v4l2-request-fourier (1.0.0+r378+gc332d34-2) bookworm trixie; urgency=medium
|
|
|
|
* Rebuild on a native Debian trixie runner (actrunner-debian-aarch64-bohr) so
|
|
the driver picks up trixie's libva-dev (2.22) and exports
|
|
__vaDriverInit_1_22 — the symbol trixie's libva runtime looks up.
|
|
Previous -1 build used the Arch CI runner (libva 2.23.0) and
|
|
exported __vaDriverInit_1_23, which trixie's loader cannot bind:
|
|
vaInitialize() returns -1 ("has no function __vaDriverInit_1_0")
|
|
and ffmpeg -hwaccel vaapi fails on startup.
|
|
* No source change; pure build-env fix. CI workflow's
|
|
libva-v4l2-request-fourier-debian job moved from runs-on:
|
|
arch-aarch64 to runs-on: actrunner-debian-aarch64-bohr; build-deps installed
|
|
via apt-get instead of pacman.
|
|
* Hard sanity check kept in build-deb.sh: build fails if the
|
|
resulting .so doesn't export __vaDriverInit_1_22 (preempts the
|
|
silent install-then-refuse-to-load failure mode).
|
|
|
|
-- Markus Fritsche <mfritsche@reauktion.de> Wed, 20 May 2026 18:00:00 +0000
|
|
|
|
libva-v4l2-request-fourier (1.0.0+r378+gc332d34-1) bookworm trixie; urgency=medium
|
|
|
|
* Bump to c332d34 — LIBVA-1 per-codec dispatch close. Pi 5 mixed
|
|
deployment (rpi-hevc-dec + daedalus_v4l2 both loaded) now correctly
|
|
opens BOTH decoders: VP9/AV1/H.264 route to daedalus via new 'd'
|
|
kind, HEVC stays on 'p' (rpi-hevc-dec). Before this commit
|
|
find_codec_device picked rpi-hevc-dec as the sole primary and the
|
|
daedalus_v4l2 slot stayed -1, so VP9/AV1/H.264 frames failed.
|
|
* Also closes a small fd leak in RequestTerminate (daedalus pair).
|
|
* Backward-compatible: new branches gated by HAVE_DAEDALUS_V4L2
|
|
*and* video_fd_daedalus >= 0 — RK3399/RK3588 boxes unaffected.
|
|
|
|
-- Markus Fritsche <mfritsche@reauktion.de> Wed, 20 May 2026 17:30:00 +0000
|
|
|
|
libva-v4l2-request-fourier (1.0.0+r376+gde27e95-1) bookworm trixie; urgency=medium
|
|
|
|
* Initial Debian packaging (sibling to existing
|
|
arch/libva-v4l2-request-fourier).
|
|
* Pinned to fork tip de27e95: "v4l2: log error_idx + failing ctrl id
|
|
on S_EXT_CTRLS failure" — Phase 8.13 diagnostic that surfaced the
|
|
real root cause of the libva→daedalus_v4l2 request-completion
|
|
timeout.
|
|
* Includes daedalus_v4l2 probe slot (b5b3acf) and meson option gate
|
|
(2146341) for the Pi 5 daemon-backed decoder shim.
|
|
* Backward-compatible on rkvdec / hantro / cedrus / rpi-hevc-dec
|
|
hosts — daedalus probe is off by default unless the kernel module
|
|
is present.
|
|
|
|
-- Markus Fritsche <mfritsche@reauktion.de> Mon, 18 May 2026 23:00:00 +0000
|