A corrupted deb should never make it on the harddisk, when it gets download we check md5/sha256 sum and if that does not match we delete it. Now either this check is sometimes broken (I doubt that, but its possible) or its actually filesystem corruption that manifests itself in this error message
Thanks for your bugreport.
A corrupted deb should never make it on the harddisk, when it gets download we check md5/sha256 sum and if that does not match we delete it. Now either this check is sometimes broken (I doubt that, but its possible) or its actually filesystem corruption that manifests itself in this error message