Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1350454

Summary: Error on Shasum Check for Mac OS
Product: [Retired] Fedora Documentation Reporter: wk4
Component: install-guideAssignee: Jaromir Hradilek <jhradile>
Status: CLOSED EOL QA Contact: Fedora Docs QA <docs-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: develCC: pbokoc, zach
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Mac OS   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-21 09:21:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description wk4 2016-06-27 13:33:35 UTC
Description of problem:


Version-Release number of selected component (if applicable):
24


How reproducible:
100%


Steps to Reproduce:
1. open terminal
2. $ cd ~/Downloads/
3. shasum -a 256 -c *CHECKSUM


Actual results:
shasum: Fedora-Workstation-24-x86_64-CHECKSUM: no properly formatted SHA1 checksum lines found


Expected results:
shasum: Fedora-Workstation-netinst-x86_64-24-1.2.iso: 
Fedora-Workstation-netinst-x86_64-24-1.2.iso: FAILED open or read
Fedora-Workstation-Live-x86_64-24-1.2.iso: OK
shasum: WARNING: 1 listed file could not be read


Additional info:
Tested on Mac OS X 10.11.5 (15F34)
Submitting a separate report as the bug (1282228) mentions both Mac OS and Ubuntu. I do not have a fix for Ubuntu, only Mac OS.

How to fix:
I recommend replacing the step 3 in the guide with "$ grep '^SHA256' *-CHECKSUM | awk -F '[()=]' '{ print $4 "  " $2 }' | shasum -a 256 -c".

Credit (Fredy): https://web.archive.org/web/20160627132229/https://ask.fedoraproject.org/en/question/74873/cant-verify-the-image-checksum-fedora-22/?answer=78954

Comment 2 Petr Bokoc 2024-05-21 09:21:52 UTC
The install guide has been retired, therefore I'm closing this bug. 

If you would like to report Fedora docs bugs in the future, please use the "bug" icon on the top right of the affected page, it will take you directly to the appropriate issue tracker.