diff --git a/debian/libva-v4l2-request-fourier/build-deb.sh b/debian/libva-v4l2-request-fourier/build-deb.sh
index 0642a3f93..503da3af8 100755
--- a/debian/libva-v4l2-request-fourier/build-deb.sh
+++ b/debian/libva-v4l2-request-fourier/build-deb.sh
@@ -10,15 +10,21 @@
 # Upstream fork: https://git.reauktion.de/marfrit/libva-v4l2-request-fourier
 set -euo pipefail
 
-# Same pin as the Arch PKGBUILD.  9898331 = LIBVA-2 close — completes
-# the per-codec dispatch from c332d34 (LIBVA-1) by adding video_fd_
-# daedalus to any_fd_supports_output_format's probe array.  Without
-# it, H.264/VP9/AV1 profiles never got advertised on Pi 5 mixed
-# deployments (rpi-hevc-dec primary, daedalus_v4l2 alt) — ffmpeg
-# bailed with "No support for codec h264 profile 578" before the
-# per-codec dispatch could even fire.
-UPSTREAM_COMMIT=989833114a7708ad999dc68309cbc181d9913bdb
-PKGVER=1.0.0+r380+g9898331
+# Same pin as the Arch PKGBUILD.  c1bb444 = PR #9 merge "h264:
+# max_num_ref_frames fallback + libva-boundary instrumentation (#8)" —
+# addresses the libva-side portion of marfrit/libva-v4l2-request-fourier#8.
+# The daedalus_v4l2-via-libavcodec strict consumer rejected frames whose
+# sps.max_num_ref_frames was 0 (older ffmpeg-vaapi paths leave the field
+# unset and HW decoders tolerated it).  PR adds a per-profile spec
+# minimum fallback (counts valid DPB entries first; 1 for baseline / 4
+# for main+high if even that is 0) and a one-line request_log at
+# h264_set_controls entry dumping raw VAAPI bitfields for diagnosing
+# the still-open PPS-flag-zero portion of issue #8.
+#
+# Prior pin (9898331) was the LIBVA-2 close — config-side
+# video_fd_daedalus added to the profile enumeration probe array.
+UPSTREAM_COMMIT=c1bb444d0731ca7ca831c7e01ec4b52ed736ca8e
+PKGVER=1.0.0+r382+gc1bb444
 PKGREL=1
 
 HERE=$(dirname "$(readlink -f "$0")")