Skip to content

Align release tooling and re-release as -3 - #12

Merged
DaniusKalv merged 4 commits into
debian/latestfrom
debian/release-workflow-fixes
Jun 18, 2026
Merged

Align release tooling and re-release as -3#12
DaniusKalv merged 4 commits into
debian/latestfrom
debian/release-workflow-fixes

Conversation

@DaniusKalv

@DaniusKalv DaniusKalv commented Jun 18, 2026

Copy link
Copy Markdown
Member

Summary

  • Build suffixed suites (bookworm's ~bpo12+1) from a dch source-version backport entry instead of sbuild --append-to-version, which implies --no-arch-all and only bumps the binary version (Debian #911399).
  • Drop the backport suffix from release asset filenames. The suite token already distinguishes the build, so the GitHub-safe + stand-in for ~ is redundant. The .deb keeps ~bpo12+1 internally.
  • Refresh a release's assets in place by clearing them before re-upload, so a packaging rebuild can't leave stale tarballs beside the new SHA256SUMS.
  • Bump to 0.7.1+rpt20260429+krks1-3: a packaging-only rebuild (no code changes) that publishes the above with the clean asset naming.

Test plan

  • -3 assets use the clean names (…-3_<suite>_arm64.tar.gz, no +bpo12+1).
  • Bookworm .deb carries internal ~bpo12+1.

sbuild --append-to-version implies --no-arch-all and only bumps the
binary version, dropping arch:all packages and breaking
${source:Version} deps (Debian #911399). Synthesize a source-version
backport changelog entry with dch instead and build normally.

Signed-off-by: Danius Kalvaitis <danius@kurokesu.com>
A packaging rebuild (-1 -> -2) renames the tarballs. gh release upload
--clobber only overwrites same-named files, so the old revision's
assets would linger beside the new SHA256SUMS. Clear the assets first,
then re-upload.

Signed-off-by: Danius Kalvaitis <danius@kurokesu.com>
@DaniusKalv DaniusKalv self-assigned this Jun 18, 2026
@DaniusKalv DaniusKalv added the bug Something isn't working label Jun 18, 2026
GitHub flattens ~ to . on upload, so the bookworm tarball used a +
stand-in (~bpo12+1 -> +bpo12+1) that reads like the inverted-sort bug
and overloads +. The suite token already disambiguates per-suite
builds, so the suffix is redundant in the name. The .deb keeps the
real ~bpo12+1, which is what apt sorts on.

Signed-off-by: Danius Kalvaitis <danius@kurokesu.com>
Signed-off-by: Danius Kalvaitis <danius@kurokesu.com>
@DaniusKalv DaniusKalv changed the title Fix backport builds and release asset re-runs Align release tooling and re-release as -3 Jun 18, 2026
@DaniusKalv DaniusKalv added enhancement New feature or request and removed bug Something isn't working labels Jun 18, 2026
@DaniusKalv
DaniusKalv merged commit 6cf3663 into debian/latest Jun 18, 2026
2 checks passed
@DaniusKalv
DaniusKalv deleted the debian/release-workflow-fixes branch June 26, 2026 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant