What
bonedigger-report reads the image identity from the build-time /usr/share/ublue-os/image-info.json, the same staleness class fixed for bctl/ujust in #820 / PR #942.
After a user rebases, the baked file still describes the image the filesystem was built as, not what is booted. For report intake this means bug reports can be routed to the wrong variant repo, and the image identity shown in a report may not match the user's actual system.
Evidence
Found while fixing #820. bonedigger-report currently reads .status.booted.imageDigest from bootc for the digest, but takes name/tag from the baked JSON.
Fix
Consume the resolver introduced in PR #942:
/usr/libexec/ublue-image-resolve image-name
/usr/libexec/ublue-image-resolve image-tag
/usr/libexec/ublue-image-resolve image-path
It is bootc-first with a graceful fallback to the baked file, so non-bootc hosts and containers keep working.
Depends on
PR #942 landing first (it introduces the resolver).
Automatable
Yes — mechanical substitution plus bats coverage, once #942 is merged.
What
bonedigger-reportreads the image identity from the build-time/usr/share/ublue-os/image-info.json, the same staleness class fixed forbctl/ujustin #820 / PR #942.After a user rebases, the baked file still describes the image the filesystem was built as, not what is booted. For report intake this means bug reports can be routed to the wrong variant repo, and the image identity shown in a report may not match the user's actual system.
Evidence
Found while fixing #820.
bonedigger-reportcurrently reads.status.booted.imageDigestfrom bootc for the digest, but takes name/tag from the baked JSON.Fix
Consume the resolver introduced in PR #942:
It is bootc-first with a graceful fallback to the baked file, so non-bootc hosts and containers keep working.
Depends on
PR #942 landing first (it introduces the resolver).
Automatable
Yes — mechanical substitution plus bats coverage, once #942 is merged.