Comment 4 for bug 1979844
Revision history for this message
| John Neffenger (jgneff) wrote Re: Add SHA-512 hash code to snap package build status page | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
Thank you, William.
> A simple solution might be to log hashes at the end of the build log.
Yes, a hash code in the build log would solve the problem, too! I was surprised to find no hash value at the end of the log file right after the package is created:
Snapping...
Snapped openjdk_
Revoking proxy token...
I could print the hash value myself, but Snapcraft doesn't provide an override hook for the 'snap' or 'pack' step of the lifecycle.
> Snaps are often referred to by (a weird encoding of) their SHA3-384 ...
Is that the revision string?
Build status
[FULLYBUILT] Successfully built on lcy02-amd64-010
Revision: a7335859baa3c35
I checked that string against every hash value that 'openssl' can create, and nothing matched. What is that string?