When running integrity checks on the latest MX15-x64_KDE_added_June_2016.iso monthly snapshot, the md5sum check is failing because the format of the text file containing the md5sum has an error.
Unmodified from their downloaded state;
the file name for the downloaded file is: MX15-x64_KDE_added_June_2016.iso
the file name containing the checksum is MX15-x64_KDE_added_June_2016.iso.md5
This is all fine and dandy until one tries to check the md5sum from the terminal using the following command:
Code: Select all
md5sum -c MX15-x64_KDE_added_June_2016.iso.md5
Code: Select all
md5sum: MX15-x64_KDE_added-20160616_1626.iso: No such file or directory
MX15-x64_KDE_added-20160616_1626.iso: FAILED open or read
md5sum: WARNING: 1 listed file could not be read
After reading the md5sum in the file, the md5sum utility is attempting to load the file name following the md5sum, but the file name does not match any file name in the current directory, therefore, the process fails. It's a simple fix, the filename following the checksum in the .md5 file needs to match the name of the file to be checked.
The contents of the .md5 contents read
3ac9393891a0669b67361855bedd47fa MX15-x64_KDE_added-20160616_1626.iso
where they need to be
3ac9393891a0669b67361855bedd47fa MX15-x64_KDE_added_June_2016.iso
Having corrected the contents of the .md5 file, as in the example above, saving it and re-running the command, the process works as intended and the result looks much better
Code: Select all
$ md5sum -c MX15-x64_KDE_added_June_2016.iso.md5
MX15-x64_KDE_added_June_2016.iso: OK
By the way, thank you for this fine piece of work, my wifes PC will be upgraded this week, starting with the June Snapshot.