523086 – Releng page does not reflect current *.DIGEST.asc checksums

Bug 523086 - Releng page does not reflect current *.DIGEST.asc checksums

Summary: Releng page does not reflect current *.DIGEST.asc checksums

Status:	RESOLVED OBSOLETE

Alias:	None

Product:	Gentoo Release Media
Classification:	Unclassified
Component:	Stages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal
Assignee:	Gentoo Release Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-09-18 04:08 UTC by Walter
Modified:	2020-04-08 04:20 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Walter 2014-09-18 04:08:22 UTC

Trying to validate the checksums in *.DIGEST.asc, I get errors because the documentation is out of date.

Reproducible: Always

Steps to Reproduce:
1. Download a stage3*.DIGEST.asc file
2. Observe contents are like...

# SHA512 HASH
9997b46ad5b4e86c44abd0522277df2fa8d5d39636c6e89a2c410b9c84e1b75ed44ad49ecd2c56ed6755b3e000933b0e92b55bb9c0d299847d3c3ea0db128ddc  stage3-amd64-hardened+nomultilib-20140904.tar.bz2
# WHIRLPOOL HASH
527d38d3a9919def5931880a1a19644addb900d111dc746f3e28cf185cc2a70751671005d187b78dd16a7b1c7e43bb9cb67edfaf4f698083f847772225d5cc2c  stage3-amd64-hardened+nomultilib-20140904.tar.bz2
# SHA512 HASH
8bb38a6668c48c8778b7d0a6762e4ee99477d7213754320605bac6154f677c0d7e37f16f76e6d6cbf82a52db66d7c3a1ab141fd48f881370e145a37f98f8ce17  stage3-amd64-hardened+nomultilib-20140904.tar.bz2.CONTENTS
# WHIRLPOOL HASH
16791150f85e58d286a3dc9a2e6ea17a542e04aa17f481cc4442670d26d172a9c388989351fd34a4a7605eb56cd526f44663b316e324f7a48511dfdfbdc765f7  stage3-amd64-hardened+nomultilib-20140904.tar.bz2.CONTENTS
...

3. Attempt to apply instructions from http://www.gentoo.org/proj/en/releng/ -- ie.

$ sha512sum -c <foo.DIGESTS.asc>
$ sha256sum -c <foo.DIGESTS.asc>
$ sha1sum -c <foo.DIGESTS.asc>

4. Get errors due to sha1/sha256 missing, sha512 sum with stated invocation getting confuzzled.
Actual Results:  
Errors.

Expected Results:  
Clean validation.

Comment 1 Walter 2014-09-18 07:10:59 UTC

I note further that the portage snapshots have a still different system, with all files in /snapshots including a .gpgsig, .md5sum and .umd5sum checksum alongside except for the portage-latest-* files which are missing .umd5sum.

Ideally their validation would be an identical process.