Comment 2 for bug 260748

The absence of the sfv check is because the code hasn't changed to work with the segmented download method (even if the changelog sates so for version 0.702). The attached patch can solve the problem...

Regarding the CRC check itself I can't see any reason to retrying the download once more if the sfv check is fails. I assume it works like that because in pre-TTH era it was a chance to get CRC errors because of a file transfer failure. But nowadays with TTH and zlib transfers its impossible so if there's no other reason to keep this behaviour I'd suggest to remove the CRC warn flag from sources and mark the source bad immediately if the sfv check fails.