[Bug 1282228] New: Problems Verifying Checksums on both Mac OS X and Ubuntu Linux

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1282228

            Bug ID: 1282228
           Summary: Problems Verifying Checksums on both Mac OS X and
                    Ubuntu Linux
           Product: Fedora Documentation
           Version: devel
         Component: install-guide
          Severity: medium
          Assignee: pbokoc at redhat.com
          Reporter: ajstewart426 at gmail.com
        QA Contact: docs-qa at lists.fedoraproject.org
                CC: pbokoc at redhat.com, zach at oglesby.co



Description of problem:

shasum and sha256 sum do not like the format of your checksum files for some
reason.

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

Fedora-Live-Workstation-x86_64-23-10.iso
Fedora-Workstation-23-x86_64-CHECKSUM

How reproducible:

Follow the instructions in section 3.3.2

Steps to Reproduce:
1. Download the Fedora image and appropriate checksum file. I was using the
versions listed above. I tried both saving the checksum webpage itself and
copying and pasting the text into a txt file.
2. In a terminal, navigate to the directory containing the files
3. For Linux:
$ sha256sum -c *CHECKSUM
For OS X:
$ shasum -a 256 -c *CHECKSUM

Actual results:

When running the above commands on both OS X and Ubuntu, I get something along
the lines of the following:
shasum: Fedora-Workstation-23-x86_64-CHECKSUM: no properly formatted SHA1
checksum lines found
For some reason it does not like the formatting of your files.

Expected results:

Something saying the checksum is valid I assume.

Additional info:

When I remove the -c option, it spits out the checksum itself. I was able to
manually verify the download that way. This solution should be sufficient for
most users. At least, it's better than having them run into the above error
message. A better solution would involve figuring out why it doesn't like the
formatting. I tried switching the line-ending characters from \n to \r\n since
that's such a common problem but it didn't help. If you want any more detailed
information on how to recreate this bug just let me know.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.