Unable to calculate checksum about cubic HOT 11 CLOSED

cubic --verbose > log.txt :
log.txt

on line 1111 it says [Errno 2] No such file or directory:
'/home/ascend910/cubic/Winux7Basic/c
ustom-disk/EFI/boot/bootx64.efi'

But the file does exist
ls /home/ascend910/cubic/Winux7Basic/custom-disk/EFI/boot
bootia32.efi bootx64.efi grubx64.efi
weirdly bootx64.efi is red maybe a problom with Cubic unpacking the iso???

from cubic.

Red usually means this is a link to a file, and the file it links to does not exist.

You can see which file this links points to by typing

ls -la

...or...

readlink -f bootx64.efi

Nevertheless, thank you for attaching your log file; I'll look into this.

from cubic.

For reference, the relevant portion of the log file is...

• Exclude files from the checksum........ ['/home/ascend910/cubic/Winux7Basic/
                                          custom-disk/md5sum.txt', '/home/asce
                                          nd910/cubic/Winux7Basic/custom-     
                                          disk/isolinux/isolinux.bin', '/home/
                                          ascend910/cubic/Winux7Basic/custom- 
                                          disk/isolinux/boot.cat']            
• Get relative file paths in the      
  directory.............................. /home/ascend910/cubic/Winux7Basic/cu
                                          stom-disk                           
• Write to file.......................... /home/ascend910/cubic/Winux7Basic/cu
                                          stom-disk/md5sum.txt                
• Unable to calculate the md5 hash for
  file................................... EFI/boot/bootx64.efi                
• The exception is....................... [Errno 2] No such file or directory:
                                          '/home/ascend910/cubic/Winux7Basic/c
                                          ustom-disk/EFI/boot/bootx64.efi'    
• The trace back is...................... Traceback (most recent call last):  
                                          File "/usr/share/cubic/cubic/utiliti
                                          es/file_utilities.py", line 916, in 
                                          calculate_md5_hash     with         
                                          open(full_file_path, 'rb') as file: 
                                          ^^^^^^^^^^^^^^^^^^^^^^^^^^          
                                          FileNotFoundError: [Errno 2] No such
                                          file or directory: '/home/ascend910/
                                          cubic/Winux7Basic/custom-           
                                          disk/EFI/boot/bootx64.efi'          
• Error.................................. Unable to update checksums          
• The exception is....................... [Errno 2] No such file or directory:
                                          '/home/ascend910/cubic/Winux7Basic/c
                                          ustom-disk/EFI/boot/bootx64.efi'    
• Do not propagate exception............. [Errno 2] No such file or directory:
                                          '/home/ascend910/cubic/Winux7Basic/c
                                          ustom-disk/EFI/boot/bootx64.efi'    

from cubic.

ls -la:
lrwxrwxrwx 1 ascend910 ascend910 36 Feb 9 13:42 bootx64.efi -> /etc/alternatives/shimx64.efi.signed

readlink -f bootx64.efi:
/etc/alternatives/shimx64.efi.signed

from cubic.

bootx64.efi is a link to /etc/alternatives/shimx64.efi.signed, but /etc/alternatives/shimx64.efi.signed doesn't exist.

I've downloaded the linuxmint-21.3-cinnamon-64bit.iso ISO you shared...

• I see that <ISO>/EFI/boot/bootx64.efi is a link.
• This link does point to <ISO>/etc/alternatives/shimx64.efi.signed.
• However, there is no /etc directory on the ISO.

I compared this to linuxmint-21.1-cinnamon-64bit.iso.

• This 2.21 ISO does not have this superfluous link in the <ISO>/EFI/boot/ directory.

Therefore, this is a bug in the Linux Mint 21.3 ISO.

However, I will modify Cubic to ignore missing files (i.e. broken links) when calculating the checksum.

It will take me a few day to issue a new Cubic release.
In the meant time, you might want to open a bug with Linux Mint to correct this issue at the source.

from cubic.

ok thx :)

from cubic.

This is interesting.

I just tested Cubic using the linuxmint-21.3-cinnamon-64bit.iso file you linked to above.

I did not get the same error as you reported.

Even though, <ISO>/EFI/boot/bootx64.efi is a broken link, it should still have a md5 checksum.
It is also a file that appears on the ISO, and all files on the ISO need a checksum.
So my original idea, to not calculate the checksum for broken symlinks, is not the correct approach.

Which OS and version are you running Cubic in?

 lsb_release --all

Which version of Python do you have?

python3 --version

from cubic.

On your system (where you run Cubic), what are the outputs of these commands:

cd /home/ascend910/cubic/Winux7Basic/custom-disk/EFI/boot/

readlink -f bootx64.efi

file bootx64.efi

file `readlink -f bootx64.efi`

md5sum bootx64.efi

md5sum `readlink -f bootx64.efi`

from cubic.

Update:

I did not get the same error as you reported.

My host system is Ubuntu, and the <ISO>/EFI/boot/bootx64.efi actually resolves to /etc/alternatives/shimx64.efi.signed which exists on my system.

I suspect you are running Cubic with Linux Mint as your host OS, and /etc/alternatives/shimx64.efi.signed does not exist on a Linux Mint install. (Or perhaps, you do not have an EFI system).

I checked the man page for md5sum, but there was no explanation of how it behaves with symlinks.

However, I did find this accepted answer on stackoverflow which indicates that md5sum always follows symlinks and does not treat symlinks as individual files.

Note: Although Cubic does not directly invoke the md5sum command, the behavior of Cubic's implementation must be the same as the md5sum command.

from cubic.

The solution will be to not calculate the checksum for files that are symlinks.
Additionally, symlinks will not be listed in the md5sum.txt file (although the target files will still be listed along with their corresponding checksums).

from cubic.

Fix released in version 2024.02-86.

Please test, and report any issues.

from cubic.