marfrit/marfrit-packages
0
0
Fork 1
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

libva-v4l2-request-fourier (deb): catch build-deb.sh up to c1bb444 (follow-up to #52) #53

Merged
marfrit merged 1 commits from claude-noether/marfrit-packages:noether/libva-deb-bump-c1bb444 into main 2026-05-20 18:30:24 +00:00
Conversation 0 Commits 1 Files Changed 1
+15 -9
claude-noether commented 2026-05-20 18:29:31 +00:00
Contributor
Copy Link
Copy Source

Follow-up to #52 — catches the parallel Debian-side pin in debian/libva-v4l2-request-fourier/build-deb.sh that I missed in the original bump.

Background

arch/libva-v4l2-request-fourier/PKGBUILD and debian/libva-v4l2-request-fourier/build-deb.sh each have their own copy of UPSTREAM_COMMIT / PKGVER / PKGREL. PR #52 bumped only the Arch one. Result post-merge: the Debian CI job ran check-already-published.sh debian/libva-v4l2-request-fourier, the script computed the .deb filename from build-deb.sh's still-9898331 pin, HEAD-checked the pool, found the existing r380 .deb, returned skip=1, and the job short-circuited. trixie repo Packages still serves 1.0.0+r380+g9898331-1.

This bump catches build-deb.sh up to c1bb444 so the next merge fires the build + publish-deb for bookworm + trixie suites.

Test plan

  • CI fires the libva-v4l2-request-fourier-debian path (not skipped this time).
  • https://packages.reauktion.de/debian/dists/trixie/main/binary-arm64/Packages advertises 1.0.0+r382+gc1bb444-1 post-merge.
  • apt update && apt-cache policy libva-v4l2-request-fourier on higgs picks up the new candidate.

Drift-prevention thought (out-of-scope for this PR)

The dual-pin convention drifts whenever a contributor edits only one side. Possible long-term cleanups (one-liner each):

  1. Ship a shared arch/libva-v4l2-request-fourier/pin.env and have both PKGBUILD + build-deb.sh source it.
  2. Add a make-fail in check-already-published.sh if the Arch + Debian recipe-computed pkgvers differ for the same package name.
  3. CI step that diffs the two before the build step.

Happy to do (2) as a separate PR if you'd like.

Follow-up to #52 — catches the parallel Debian-side pin in `debian/libva-v4l2-request-fourier/build-deb.sh` that I missed in the original bump. ## Background `arch/libva-v4l2-request-fourier/PKGBUILD` and `debian/libva-v4l2-request-fourier/build-deb.sh` each have their own copy of `UPSTREAM_COMMIT` / `PKGVER` / `PKGREL`. PR #52 bumped only the Arch one. Result post-merge: the Debian CI job ran `check-already-published.sh debian/libva-v4l2-request-fourier`, the script computed the .deb filename from build-deb.sh's still-9898331 pin, HEAD-checked the pool, found the existing r380 .deb, returned `skip=1`, and the job short-circuited. trixie repo `Packages` still serves `1.0.0+r380+g9898331-1`. This bump catches build-deb.sh up to `c1bb444` so the next merge fires the build + `publish-deb` for `bookworm` + `trixie` suites. ## Test plan - [ ] CI fires the libva-v4l2-request-fourier-debian path (not skipped this time). - [ ] `https://packages.reauktion.de/debian/dists/trixie/main/binary-arm64/Packages` advertises `1.0.0+r382+gc1bb444-1` post-merge. - [ ] `apt update && apt-cache policy libva-v4l2-request-fourier` on higgs picks up the new candidate. ## Drift-prevention thought (out-of-scope for this PR) The dual-pin convention drifts whenever a contributor edits only one side. Possible long-term cleanups (one-liner each): 1. Ship a shared `arch/libva-v4l2-request-fourier/pin.env` and have both PKGBUILD + build-deb.sh source it. 2. Add a make-fail in `check-already-published.sh` if the Arch + Debian recipe-computed pkgvers differ for the same package name. 3. CI step that diffs the two before the build step. Happy to do (2) as a separate PR if you'd like.
claude-noether added 1 commit 2026-05-20 18:29:32 +00:00
libva-v4l2-request-fourier (deb): 9898331 -> c1bb444 (parallel to PR #52) 42bf6b1633 
PR #52 bumped only arch/libva-v4l2-request-fourier/PKGBUILD; the
sibling debian/libva-v4l2-request-fourier/build-deb.sh has its own
parallel UPSTREAM_COMMIT + PKGVER + PKGREL pin that I missed.

Result: the libva-v4l2-request-fourier-debian CI job ran post-merge,
check-already-published.sh saw the .deb-side filename derived from
build-deb.sh (libva-v4l2-request-fourier_1.0.0+r380+g9898331-1_arm64.deb)
was already in the pool, returned skip=1, and the job short-circuited.
trixie repo Packages still advertises r380 instead of r382.

This bump catches build-deb.sh up to the same pin (c1bb444) so the
next merge triggers the build + reprepro publish path.

No code change beyond the three pinned variables + the comment block.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
marfrit merged commit 793187ff9e into main 2026-05-20 18:30:24 +00:00
marfrit deleted branch noether/libva-deb-bump-c1bb444 2026-05-20 18:30:24 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
marfrit (Markus Fritsche)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: marfrit/marfrit-packages#53
Delete Branch "claude-noether/marfrit-packages:noether/libva-deb-bump-c1bb444"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?