pagure

#3121 CHECKSUMS is polluted by duplicit records while trying to upload already uploaded tarball
Closed: Fixed Opened by jkucera.

Closed: Fixed
Reopen Issue

Consider a tarball foo-0.01.tar.gz that is still uploaded in release folder and the CHECKSUMS file with the content:

# Generated and updated by pagure
SHA256 (foo-0.01.tar.gz) = <SHA256 value for foo-0.01.tar.gz>
SHA512 (foo-0.01.tar.gz) = <SHA512 value for foo-0.01.tar.gz>

The attempt to upload foo-0.01.tar.gz again correctly inform the user that foo-0.01.tar.gz is already uploaded (issue #1666), but the content of CHECKSUMS is changed to:

# Generated and updated by pagure
SHA256 (foo-0.01.tar.gz) = <SHA256 value for foo-0.01.tar.gz>
SHA512 (foo-0.01.tar.gz) = <SHA512 value for foo-0.01.tar.gz>
SHA256 (foo-0.01.tar.gz) = <SHA256 value for foo-0.01.tar.gz (same as previous)>
SHA512 (foo-0.01.tar.gz) = <SHA512 value for foo-0.01.tar.gz (same as previous)>

If I am right, the content of CHECKSUMS should remain untouched in this case.

I believe you're right, thanks for the report

Metadata Update from @pingou:
- Issue tagged with: bug

Metadata Update from @pingou:
- Issue assigned to pingou

Commit 1a1f1e99 fixes this issue
Metadata

bug

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.