When a backup to create an ISO is run with CU170 it fails to complete. This is due to a change in the name of the ISO file stored on the download site. The file name for the iso was modified by commit https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=fbd0608c2cb5372fff7857065ec7e605b1bf9cf7 to make it aligned with the image file name. This ISO filename is also used by the IPFire bacxkup process when creating an iso backup file. The iso file name in the backup program needs to be adjusted yo be in line with the modified template specified by the above commit.
Suggested fix (seems to works here, please test): diff --git a/src/scripts/backupiso b/src/scripts/backupiso index ef017e3be..2a016e067 100644 --- a/src/scripts/backupiso +++ b/src/scripts/backupiso @@ -35,7 +35,7 @@ case "${arch}" in esac URL="https://downloads.ipfire.org/releases/ipfire-2.x/$IPFVER-core$COREVER/" -ISO="ipfire-$IPFVER.$arch-full-core$COREVER.iso" +ISO="ipfire-$IPFVER-core$COREVER-$arch.iso" makeiso() { local dir="${1}"
Yes, that is the fix I have edited in my backupiso file but I will be testing it tomorrow morning as it is getting late here now.
Fix confirmed to work on my vm testbed system. Also confirmed on the forum:- https://community.ipfire.org/t/backup-pl-fails-to-create-full-iso-backup-after-core-update-170/8592/4
Patch submitted to dev mailing list and patchwork. https://patchwork.ipfire.org/project/ipfire/patch/20220918114517.7508-1-adolf.belka@ipfire.org/
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=c799e441a447863ff94cd27eb418616bc1200855
https://blog.ipfire.org/post/ipfire-2-27-core-update-171-is-available-for-testing
Tested this on CU171 Testing on my vm testbed. It didn't work but after some thought and checking I relaised that is because it downloads the original iso file from the standard IPFire downloads url and Core Update 171 is not yet available there as it is in Testing phase. So this bug will only be able to be formally verified when Core Update 171 Stable is released.
https://blog.ipfire.org/post/ipfire-2-27-core-update-171-released-security-advisory