wrong sha1 for pristine-tar-1.26-1-src.tar.bz2 in x86 setup.ini

[Wolfgang Goetz <Wolfgang dot ztoeG at web dot de>]

Hello,

since a few days there is a wrong sha1 sum for
pristine-tar-1.26-1-src.tar.bz2 in x86 setup.ini

file size is correct, sha1 is from the OLD(!) nonworking file, see below.




-----------------------------------------------------------------
x86/setup.ini:
source: x86/release/pristine-tar/pristine-tar-1.26-1-src.tar.bz2 215014 b2573a82f9657e4aa6cee1e8e0d8f298


-----------------------------------------------------------------
new file:
8d4dbb3fdd1673d30af205256584aa3c  pristine-tar-1.26-1-src.tar.bz2
215014 16. Okt 13:29 pristine-tar-1.26-1-src.tar.bz2




-----------------------------
old file, last seen 20131010:
md5 (20131010-21-daily/cygwin17_repo/repo/x86/release/pristine-tar/pristine-tar-1.26-1-src.tar.bz2) = b2573a82f9657e4aa6cee1e8e0d8f298
copy from zfs snapshot to old-...:

b2573a82f9657e4aa6cee1e8e0d8f298  old-pristine-tar-1.26-1-src.tar.bz2  
24010 16. Okt 13:33 old-pristine-tar-1.26-1-src.tar.bz2                 TOO SMALL!


tar tfj old-pristine-tar-1.26-1-src.tar.bz2 

bzip2: Compressed file ends unexpectedly;
	perhaps it is corrupted?  *Possible* reason follows.
bzip2: Inappropriate ioctl for device
	Input file = (stdin), output file = (stdout)

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

tar: Child returned status 2
tar: Error is not recoverable: exiting now




kind regards 
Wolfgang

helper for checking the downloaded files against gpg-checked ini:
md5sum -c <(awk '/install:|source:/{print $4"  "$2}' x86/setup.ini)|grep -v OK

Attachment: signature.asc
Description: PGP signature