Fetched file: dxvk-1.7.1.tar.gz VERIFY FAILED! #9

New Issue

idarktemplar · 2020-08-14T20:04:16+02:00

idarktemplar commented

2020-08-14 20:04:16 +02:00

When trying to upgrade to dxvk-1.7.1 I'm getting following error:

!!! Fetched file: dxvk-1.7.1.tar.gz VERIFY FAILED!
!!! Reason: Filesize does not match recorded size
!!! Got:      1076712
!!! Expected: 1076757

Downloaded file has size and checksums different from ones recorded in Manifest. SHA512 of downloaded file is following:

e8e056fa7ef87e3fcab7584915524bf0d6e5462fd615fdbaa4a99462a5f66319c48bf7c8cbed85ac5ebbb3cdaa0e8478b0da45c1aa7439962e50b8ae51542fc1

I can think of a few reasons for mismatching size and checksums:

upstream tagged different commit (i.e. updated some commits and release tag)
github started generating requested archive differently (which is unlikely, but still possible)
at least one of us gets invalid archive when downloading it from github

Could you please verify whether you still get archive dxvk-1.7.1.tar.gz from upstream with size and checksums matching ones recorded in Manifest, or if you get size/checksums similar to those I'm getting, or if you get something else?

When trying to upgrade to dxvk-1.7.1 I'm getting following error: ``` !!! Fetched file: dxvk-1.7.1.tar.gz VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 1076712 !!! Expected: 1076757 ``` Downloaded file has size and checksums different from ones recorded in Manifest. SHA512 of downloaded file is following: e8e056fa7ef87e3fcab7584915524bf0d6e5462fd615fdbaa4a99462a5f66319c48bf7c8cbed85ac5ebbb3cdaa0e8478b0da45c1aa7439962e50b8ae51542fc1 I can think of a few reasons for mismatching size and checksums: 1) upstream tagged different commit (i.e. updated some commits and release tag) 2) github started generating requested archive differently (which is unlikely, but still possible) 3) at least one of us gets invalid archive when downloading it from github Could you please verify whether you still get archive dxvk-1.7.1.tar.gz from upstream with size and checksums matching ones recorded in Manifest, or if you get size/checksums similar to those I'm getting, or if you get something else?

tastytea commented

2020-08-14 21:31:32 +02:00

I get the same SHA512 checksums as you. Since the archive with the precompiled binaries still has the same checksum, I'm ruling out an attack. They did move a release tag before, so I guess that is what happened. I'll update the Manifest shortly.