janware/jw-pkg
Watch
1
Code Pull requests Activity Actions

pkg.sh: Use md5 for the dput hash option #158

Merged
Jan Lindemann merged 1 commit from jan/fix/20261027-pkg-sh-use-md-for-the-dput-hash-option into master 2026-10-27 08:27:58 +01:00 AGit
Conversation 0 Commits 1 Files changed 1 +3 -1
Jan Lindemann commented 2026-10-27 08:17:44 +01:00
Owner

pkg.sh: Use md5 for the dput hash option

Tonight's CI upgraded dput from 1.2.4 to 1.2.6 on Kali Linux and subsequently failed:

xzcat /tmp/20261027-010000-rollout-failed.log.xz | grep -ai -C 1 checksum
Trying to upload package to janware-debian
Checksum doesn't match for dist/src/jw-pkg_1.0.0-281.dsc
make[1]: *** [make/pkg-dist.mk:288: pkg-release-reinstall] Error 1

The dput config generated for debian uploads sets hash = sha, while the Files: section of a .changes file only carries MD5 checksums. dput verifies each listed file by comparing the configured hash of the file against that MD5 column, so a sha verification can never match and the upload is rejected at the first file, the .dsc.

Set the option to md5, the only hash the .changes Files: section carries and dput's built-in default.

Not sure, yet, if this is a fix or a workaround of a dput bug.

#### pkg.sh: Use md5 for the dput hash option Tonight's CI upgraded dput from 1.2.4 to 1.2.6 on Kali Linux and subsequently failed: ``` xzcat /tmp/20261027-010000-rollout-failed.log.xz | grep -ai -C 1 checksum Trying to upload package to janware-debian Checksum doesn't match for dist/src/jw-pkg_1.0.0-281.dsc make[1]: *** [make/pkg-dist.mk:288: pkg-release-reinstall] Error 1 ``` The dput config generated for debian uploads sets hash = sha, while the Files: section of a `.changes` file only carries MD5 checksums. dput verifies each listed file by comparing the configured hash of the file against that MD5 column, so a sha verification can never match and the upload is rejected at the first file, the `.dsc`. Set the option to md5, the only hash the `.changes` Files: section carries and dput's built-in default. Not sure, yet, if this is a fix or a workaround of a dput bug.
pkg.sh: Use md5 for the dput hash option
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 5m0s
Details
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 5m8s
Details
CI / Packaging test (pull_request) Successful in 0s
Details
CI / Packaging - Kali Linux (push) Successful in 4m59s
Details
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 4m58s
Details
CI / Packaging test (push) Successful in 0s
Details
0f6dd4dac8
 
Tonight's CI upgraded dput from 1.2.4 to 1.2.6 on Kali Linux and
subsequently failed:

  xzcat /tmp/20261027-010000-rollout-failed.log.xz | grep -ai -C 1 checksum
  Trying to upload package to janware-debian
  Checksum doesn't match for dist/src/jw-pkg_1.0.0-281.dsc
  make[1]: *** [make/pkg-dist.mk:288: pkg-release-reinstall] Error 1

The dput config generated for debian uploads sets hash = sha, while the
Files: section of a .changes file only carries MD5 checksums. dput verifies
each listed file by comparing the configured hash of the file against
that MD5 column, so a sha verification can never match and the upload is
rejected at the first file, the .dsc.

Set the option to md5, the only hash the .changes Files: section carries
and dput's built-in default.

Not sure, yet, if this is a fix or a workaround of a dput bug.

Assisted-by: unsloth/Qwen3.8-27B-GGUF:Q4_K_M with pi.dev v1.4.0
Signed-off-by: Jan Lindemann <jan@janware.com>
Jan Lindemann scheduled this pull request to auto merge when all checks succeed 2026-10-27 08:17:45 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
janware/jw-pkg!158
No description provided.