Bug 643906 – stage3-amd64-systemd-20180103.tar.bz2 bad checksum

• Status: RESOLVED FIXED
• Product: Gentoo Release Media

[Description Althorion 2018-01-08 15:29:36 UTC]

stage3-amd64-systemd-20180103.tar.bz2 doesn’t match checksums from the DIGESTS:
$ sha512sum stage3-amd64-systemd-20180103.tar.bz2
ffefd7720a3b6a364f583f74a2c76f2bcf888c92f778d65a1179b2b9c5e0f45c73202b107c0a34ec47f5ea1a3285f28bc1e55f14a11abdf7e8c2e8e50307dc6d  stage3-amd64-systemd-20180103.tar.bz2
$ fgrep SHA512 -A 1 stage3-amd64-systemd-20180103.tar.bz2.DIGESTS
# SHA512 HASH
d217589405f6a669f3459d0a32e3a917429b99da30de10af9706d4432bad5711888f7e47a4ef50c62d11c1466b002ce93d121e16f8f7021a524b3af9ab4ea11c  stage3-amd64-systemd-20180103.tar.bz2

Reproducible: Always

Steps to Reproduce:
1. Download stage3-amd64-systemd-20180103.tar.bz2 and stage3-amd64-systemd-20180103.tar.bz2.DIGESTS
2. Compare checksums
Actual Results:  
Checksums don’t match

Expected Results:  
Checksums match

[Comment 1 Michael Schnaitter 2018-01-08 17:36:57 UTC]

I can confirm this.  I have downloaded the archive from multiple mirrors over both rsync and http and the checksum is always the same and differs from the one listed in DIGESTS

[Comment 2 Thorsten Fröse 2018-01-10 02:14:34 UTC]

I can confirm this.
# MD5 HASH
expected 85705f62d48082ea740dba02f9a5b2ae  stage3-amd64-systemd-20180103.tar.bz2
got 698db9753163c05ce279cd40ddb85860  stage3-amd64-systemd-20180103.tar.bz2
# SHA1 HASH
ed32255ad47ba60eb7e361dbbac002e716bf89de  stage3-amd64-systemd-20180103.tar.bz2
got 59e40084a7c8564d315aeebdda66ecca29ee7b69  stage3-amd64-systemd-20180103.tar.bz2
# SHA512 HASH
expected d217589405f6a669f3459d0a32e3a917429b99da30de10af9706d4432bad5711888f7e47a4ef50c62d11c1466b002ce93d121e16f8f7021a524b3af9ab4ea11c  stage3-amd64-systemd-20180103.tar.bz2
got ffefd7720a3b6a364f583f74a2c76f2bcf888c92f778d65a1179b2b9c5e0f45c73202b107c0a34ec47f5ea1a3285f28bc1e55f14a11abdf7e8c2e8e50307dc6d  stage3-amd64-systemd-20180103.tar.bz2

bzip2 -tvv stage3-amd64-systemd-20180103.tar.bz2 
  stage3-amd64-systemd-20180103.tar.bz2: 
    [1: huff+mtf rt+rld]
    [2: huff+mtf rt+rld]
    [3: huff+mtf rt+rld]
    [4: huff+mtf rt+rld]
    [5: huff+mtf rt+rld]
    [...]
    [994: huff+mtf rt+rld]
    [995: huff+mtf rt+rld]
    [996: huff+mtf file ends unexpectedly

the file is incomplete, compared to the last working stage3 from 20171228 about 67M of the file are missing.
273972104 Jan 10 02:31 stage3-amd64-systemd-20171228.tar.bz2
203849728 Jan 10 02:21 stage3-amd64-systemd-20180103.tar.bz2

http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64-systemd/stage3-amd64-systemd-20180103.tar.bz2

[Comment 3 Anthony Basile 2018-01-10 05:54:27 UTC]

Thanks for the report.  The stage3's are correct on the build server and not correct on the mirrors, so something went wrong.  I'm sending them again.  It takes up to 24 hours for the new stages to propagate through.  Can you check then and let me know if the correct images have landed?

[Comment 4 Thorsten Fröse 2018-01-10 21:21:26 UTC]

Check on 3 mirrors
Checkt file works, checksum matches


# MD5 HASH
Expected 85705f62d48082ea740dba02f9a5b2ae  stage3-amd64-systemd-20180103.tar.bz2
Got 85705f62d48082ea740dba02f9a5b2ae  stage3-amd64-systemd-20180103.tar.bz2
# SHA1 HASH
expected d32255ad47ba60eb7e361dbbac002e716bf89de  stage3-amd64-systemd-20180103.tar.bz2
Got ed32255ad47ba60eb7e361dbbac002e716bf89de  stage3-amd64-systemd-20180103.tar.bz2
# SHA512 HASH
expexted d217589405f6a669f3459d0a32e3a917429b99da30de10af9706d4432bad5711888f7e47a4ef50c62d11c1466b002ce93d121e16f8f7021a524b3af9ab4ea11c  stage3-amd64-systemd-20180103.tar.bz2
Got d217589405f6a669f3459d0a32e3a917429b99da30de10af9706d4432bad5711888f7e47a4ef50c62d11c1466b002ce93d121e16f8f7021a524b3af9ab4ea11c  stage3-amd64-systemd-20180103.tar.bz2

Result Passed

[Comment 5 Althorion 2018-01-11 07:24:37 UTC]

Checksum is now correct and the archive unpacks without issues. Thank you.