Right unless I'm seriously thick, or totally missing the point I can't see where you guys are having an issue with the checksums.
There's nothing wrong with the current Binance hosted checksum. It's the same checksum that I pushed 42 hours ago.
metaanon > wget https://ftp.binance.com/electron-desktop/linux/production/binance-amd64-linux.deb
binance-amd64-linux.deb 100%[====================================================================================================>] 78.86M 10.6MB/s in 7.6s
2021-04-28 17:30:03 (10.3 MB/s) - ‘binance-amd64-linux.deb’ saved [82691782/82691782]
metaanon > sha256sum binance-amd64-linux.deb
96add572427cc441e63637311f5c4151250140df813f75d904a8d69c93b7d1ba binance-amd64-linux.deb
metaanon > curl https://ftp.binance.com/electron-desktop/linux/production/binance-amd64-linux-deb-sha256.txt
96add572427cc441e63637311f5c4151250140df813f75d904a8d69c93b7d1ba
@tyjak your file vs sha check was always going to fail because the output of sha256sum appends the file name checked so the string wouldn't match the $binanchecksum. I've fixed this up and removed the exit 0 as this was causing the build to fail.
I've also added some echos just for clarity:
metaanon > makepkg -Cic
==> Making package: binance 1.15.4-2 (Wed 28 Apr 2021 17:24:06 BST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading binance-1.15.4.deb...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 78.8M 100 78.8M 0 0 9957k 0 0:00:08 0:00:08 --:--:-- 10.5M
==> Validating source files with sha256sums...
binance-1.15.4.deb ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Extracting binance-1.15.4.deb with bsdtar
==> Starting check()...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 64 100 64 0 0 54 0 0:00:01 0:00:01 --:--:-- 54
Checksum verification...
1 Binance : 96add572427cc441e63637311f5c4151250140df813f75d904a8d69c93b7d1ba
2 PKGBUILD: 96add572427cc441e63637311f5c4151250140df813f75d904a8d69c93b7d1ba
3 Deb File: 96add572427cc441e63637311f5c4151250140df813f75d904a8d69c93b7d1ba binance-1.15.4.deb
4 Compare : 96add572427cc441e63637311f5c4151250140df813f75d904a8d69c93b7d1ba 96add572427cc441e63637311f5c4151250140df813f75d904a8d69c93b7d1ba
binance checksum file and PKGBUILD declared checksum: OK
deb checksum and binance file checksum: OK
But as you can see the initial pkgbuild sha check was successfully passing so again I don't know why you guys are seeing an error.
I've brought the version back to 1.15.4-2. So you might need to uninstall binance and remove your cached version (yay -Sc) if you've tried to download 1.15.5
Pinned Comments
metaanon commented on 2021-05-13 07:29 (UTC) (edited on 2021-05-13 08:08 (UTC) by metaanon)
Binance don't version their binaries. They simply replace the binance-amd64-linux.deb with a newer version. This means you will correctly receive a validity check error as the deb file no longer matches with the SHA sum.
Please confirm the latest Binance version and then mark this package as out of date.
Unless Binance change their release strategy or someone can come up with a clever solution, it is what it is.