| Summary: | Duplicate sha512sum files in ftp/dwz/releases dir | ||
|---|---|---|---|
| Product: | dwz | Reporter: | Tom de Vries <vries> |
| Component: | default | Assignee: | Nobody <nobody> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | dwz |
| Priority: | P2 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Host: | Target: | ||
| Build: | Last reconfirmed: | ||
(In reply to Tom de Vries from comment #0) > It seems the easiest should be to remove sha512sum Done. > and hope that sha512.sum > gets updated automagically to remove the sha512sum entry. Let's wait and see. (In reply to Tom de Vries from comment #1) > > and hope that sha512.sum > > gets updated automagically to remove the sha512sum entry. > > Let's wait and see. That has happened now: ... $ wget https://sourceware.org/ftp/dwz/releases/sha512.sum $ awk '{print $2}' sha512.sum dwz-0.13.tar.gz dwz-0.13.tar.xz md5sum ... Fixed contrib/upload-release.sh: https://sourceware.org/git/?p=dwz.git;a=commit;h=f10d7fbbbffb9974b07f0a91c10993448cf5c47f |
Using the new contrib/upload-release.sh I've created two checksum files: md5sum and sha512sum, but it seems there's some site mechanism that has added another checksum file: sha512.sum: ... $ ls -la totaal 272 drwxr-sr-x. 2 vries dwz 4096 okt 2 14:44 . drwsrwsr-x. 3 vries dwz 4096 okt 2 13:55 .. -rw-r--r--. 1 vries dwz 143279 okt 2 14:26 dwz-0.13.tar.gz -rw-r--r--. 1 vries dwz 114016 okt 2 14:26 dwz-0.13.tar.xz -rw-r--r--. 1 vries dwz 100 okt 2 14:26 md5sum -rw-r--r--. 1 vries dwz 292 okt 2 14:26 sha512sum -rw-r--r--. 1 root dwz 569 okt 2 14:44 sha512.sum ... The sha512.sum file also contains entries for md5sum and sha512sum: ... $ awk '{print $2}' sha512.sum dwz-0.13.tar.gz dwz-0.13.tar.xz md5sum sha512sum ... It seems the easiest should be to remove sha512sum and hope that sha512.sum gets updated automagically to remove the sha512sum entry.