So this looks like a similar error we fixed to prevent volume difftar.gz files from causing CRC check failures, but it's now with sigtar.gz files.
For a workaround, you can delete the sigtar.gz file (which will invalidate that incremental backup completely) and next backup should succeed in creating a new incremental backup.
But for a long term fix, we need to either re-upload sigtar files on resume or find a way to verify the checksum.
Ah! Thanks for the research, Georg!
So this looks like a similar error we fixed to prevent volume difftar.gz files from causing CRC check failures, but it's now with sigtar.gz files.
For a workaround, you can delete the sigtar.gz file (which will invalidate that incremental backup completely) and next backup should succeed in creating a new incremental backup.
But for a long term fix, we need to either re-upload sigtar files on resume or find a way to verify the checksum.