Currently if the zsync file is corrupt (i.e., its SHA1 checksum does not match the SHA1 checksum of the payload file), then we don't get an insightful error message.
me@host:~$ ./zsync_curl "http://ftp2.nluug.nl/os/Linux/distr/opensuse/repositories/home:/adrianSuSE:/AppImage/AppImage/QtQuickApp-1495317991.fce72f3.glibc2.2.5-x86_64.AppImage.zsync"Target QtQuickApp-1495317991.fce72f3.glibc2.2.5-x86_64.AppImage
Read QtQuickApp-1495317991.fce72f3.glibc2.2.5-x86_64.AppImage. Target 100.0% complete.
downloading from http://ftp2.nluug.nl/os/Linux/distr/opensuse/repositories/home:/adrianSuSE:/AppImage/AppImage/QtQuickApp-1495317991.fce72f3.glibc2.2.5-x86_64.AppImage:
###################- 100.0% 0.0 kBps aborted
failed to retrieve from QtQuickApp-1495317991.fce72f3.glibc2.2.5-x86_64.AppImage 1
Aborting, download available in QtQuickApp-1495317991.fce72f3.glibc2.2.5-x86_64.AppImage.part
If this happens, then it should give a more useful error message about what happened.
Currently if the zsync file is corrupt (i.e., its SHA1 checksum does not match the SHA1 checksum of the payload file), then we don't get an insightful error message.
If this happens, then it should give a more useful error message about what happened.