Bug 1465935 - Output resulted from sha256sum claims "No such file or directory", while the file in question is present.
Summary: Output resulted from sha256sum claims "No such file or directory", while the ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: coreutils
Version: 26
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Kamil Dudka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-28 13:22 UTC by ricky.tigg
Modified: 2017-06-28 14:08 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-28 14:08:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
The verification by sha256sum of any ISO image file fails invariably. (415.56 KB, image/png)
2017-06-28 13:22 UTC, ricky.tigg
no flags Details

Description ricky.tigg 2017-06-28 13:22:43 UTC
Created attachment 1292652 [details]
The verification by sha256sum of any ISO image file fails invariably.

Description of problem:
The verification by sha256sum of any ISO image file fails invariably.

Version-Release number of selected component (if applicable):
8.27-5.fc26.x86_64

How reproducible:
Steps to Reproduce:
1. Move both one to another related downloaded official files to the same folder.
2. Compute required command mentioned on site’s url (https://fedoramagazine.org/verify-fedora-iso-file/) till the sha256sum command.

Actual results:
Output resulted from the function sha256sum claims "No such file or directory", while not only the very file is present at the correct location but also its related rights are sufficient enough (see attachment).

Expected results:
Function sha256sum should return a viable message regarding the ISO image file in directory.

Additional info:
Component’s identification resulted from:
$ rpm -qf /usr/bin/sha256sum

Comment 1 Kamil Dudka 2017-06-28 14:08:52 UTC
Please prefer pasted text over binary images next times.

Relative paths in the checksum file are resolved against your current directory, which in your case differs from the directory where the checksum file itself is stored.  So you can get around the problem by using 'cd' to change the current directory before running the sha256sum utility.

You can also consider using the --ignore-missing option of sha256sum in case you did not download all the files listed in the checksum file.


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