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

daedalus-v4l2{,-dkms}: fix hallucinated upstream commit SHA #37

Merged
marfrit merged 1 commits from noether/daedalus-sha-fix into main 2026-05-19 10:06:13 +00:00
Conversation 0 Commits 1 Files Changed 4
+8 -8
marfrit commented 2026-05-19 10:04:09 +00:00
Owner
Copy Link
Copy Source

Recipes pinned f55b2cdab8a8c0bc04e8c1bb1d0b6ca85e7d96d2 — that SHA does not exist in git.reauktion.de/reauktion/daedalus-v4l2. Actual main tip is f55b2cd002afdfd08f3c093627317f92e4929074 — same 7-char prefix (f55b2cd), different full hash. Looks like a manually-typed SHA from a never-pushed working copy.

CI symptom: curl: (22) ... error: 500 during build daedalus-v4l2 .deb. Root cause traced via gitea container log: git archive --format=tar.gz f55b2cdab8... → fatal: not a tree object.

Fixed in all four recipes (arch + debian, daedalus-v4l2 + dkms). pkgrel bumped to signal new build. PKGVER short-prefix gf55b2cd stays the same (both SHAs share that prefix), so no semver change.

Test plan

  • CI green for daedalus-v4l2-debian + daedalus-v4l2-dkms-debian on rerun
  • .deb artifacts appear at packages.reauktion.de/debian/pool/main/d/{daedalus-v4l2,daedalus-v4l2-dkms}/
  • arch siblings rebuild + appear in /arch/aarch64/
Recipes pinned `f55b2cdab8a8c0bc04e8c1bb1d0b6ca85e7d96d2` — that SHA does not exist in `git.reauktion.de/reauktion/daedalus-v4l2`. Actual `main` tip is `f55b2cd002afdfd08f3c093627317f92e4929074` — same 7-char prefix (`f55b2cd`), different full hash. Looks like a manually-typed SHA from a never-pushed working copy. CI symptom: `curl: (22) ... error: 500` during `build daedalus-v4l2 .deb`. Root cause traced via gitea container log: `git archive --format=tar.gz f55b2cdab8...` → `fatal: not a tree object`. Fixed in all four recipes (arch + debian, daedalus-v4l2 + dkms). pkgrel bumped to signal new build. PKGVER short-prefix `gf55b2cd` stays the same (both SHAs share that prefix), so no semver change. ## Test plan - [ ] CI green for daedalus-v4l2-debian + daedalus-v4l2-dkms-debian on rerun - [ ] `.deb` artifacts appear at packages.reauktion.de/debian/pool/main/d/{daedalus-v4l2,daedalus-v4l2-dkms}/ - [ ] arch siblings rebuild + appear in /arch/aarch64/
marfrit added 1 commit 2026-05-19 10:04:10 +00:00
daedalus-v4l2{,-dkms}: fix hallucinated upstream commit SHA 3548a761a5 
The recipes pinned `f55b2cdab8a8c0bc04e8c1bb1d0b6ca85e7d96d2` as the
"Phase 8.13: byte-exact end-to-end via libva" commit, but that SHA
does not exist in git.reauktion.de/reauktion/daedalus-v4l2.

The actual `main` tip (per gitea's for-each-ref) is
`f55b2cd002afdfd08f3c093627317f92e4929074` — same 7-char prefix
(`f55b2cd`), different full hash.  Likely a manually-constructed SHA
based on a short prefix from a working copy that was never pushed.

git archive --format=tar.gz on the bad SHA fails with
  fatal: not a tree object: f55b2cdab8a8...
which surfaces as 500 from Gitea's archive endpoint, which curl in
the CI build-deb.sh sees as `curl: (22) ... error: 500`.

Diagnosed by tailing gitea.log during a fresh archive request from
the CI runner; the underlying `git archive` command in the gitea
container is logged with the full failing SHA + error.

Fixed in all four recipes (arch + debian, daedalus-v4l2 + dkms).
pkgrel bumped to signal new build (PKGVER short-prefix `gf55b2cd`
stays the same — both bad and good SHA share that prefix).
marfrit merged commit b4d1a47d6b into main 2026-05-19 10:06:13 +00:00
marfrit deleted branch noether/daedalus-sha-fix 2026-05-19 10:06:13 +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#37
Delete Branch "noether/daedalus-sha-fix"

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?