Welcome!
Forum users

Current releases
--MX-23 release info here
--Migration information to MX-23 here
--antiX-23.1 (Arditi del Popolo) release info here

Important information
--If in starting your system it boots to an unwanted Desktop, right click desktop, then select leave and logout. At the
login screen there is a session chooser at the top of the screen.

News
-- MX Linux on social media: here
-- New Forum Features, Marking Solved and Referencing a User: here

md5sum checking on monthly releases

Help on all MX Re-spins
Post Reply
Message
Author
User avatar
m_pav
Developer
Posts: 1383
Joined: Sun Aug 06, 2006 3:02 pm

md5sum checking on monthly releases

#1 Post by m_pav »

This has happened a few times recently and I haven't bothered checking it out until now.

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
The result of the above is.....

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
Here's why it is failing.
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
So in short, if an ISO name is modified after the checksum file has been created, the checksum file needs to be amended or re-created prior to distribution to avoid this type of failure.

By the way, thank you for this fine piece of work, my wifes PC will be upgraded this week, starting with the June Snapshot.
Mike P

Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD FX 6100 CPU, nVidia, 8Gb, 3.25TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs

User avatar
Adrian
Developer
Posts: 8230
Joined: Wed Jul 12, 2006 1:42 am

Re: md5sum checking on monthly releases

#2 Post by Adrian »

So in short, if an ISO name is modified after the checksum file has been created, the checksum file needs to be amended or re-created prior to distribution to avoid this type of failure.
Hopefully we won't see a lot of this since I made it easier to name the snapshots at the time they are taken.

User avatar
Stevo
Developer
Posts: 12745
Joined: Fri Dec 15, 2006 8:07 pm

Re: md5sum checking on monthly releases

#3 Post by Stevo »

That's my fault--I didn't change the file name in the md5 file from the automatically generated one. I didn't know one could use the file with the md5sum command. I'll make sure they match for the July one.

Post Reply

Return to “MX Respins”