Arch Linux User Repository

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.

Thanks @alissonlauffer @arun321. I'll make that change.

depends electron not needed.

Unless we use the system electron, the electron dependency is unused, since the .deb already comes with a bundled electron.

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.

@ast no error for me, did you try to remove via package manager and re-install ?

Hello, just to let you know that I'm getting the "ERROR: One or more files did not pass the validity check!" once more. I deleted previous download and tried again but no avail.

@metaanon : thanks for your fix. So I'm confused on what happened this morning, seems for me that the binance cheksum files wasn't updated but maybe it was my fault on the bad use of sha256sums... Thank you for your patience, and now I'm confident in using binance package from AUR.

@metaanon Thanks for the recommendation. I cleared my catch and correct key showed up. Odd, that it took that to show the correct key.

@huck I suggest you try clearing your cache or trying in a private browser session, that is not the current sha hosted on binance at that address.

I've tried on multiple browsers, multiple machines including my phone, and a few friends some who don't user linux or binance.

The sha you've posted happens to be exactly the same as version 1.15.0 from 19th April.

https://aur.archlinux.org/cgit/aur.git/commit/?h=binance&id=38281c069780d8f34fe5171a81f0dc0c134e4058

author  metaanon    2021-04-19 21:12:34 +0100
committer   metaanon    2021-04-19 21:12:34 +0100
commit  38281c069780d8f34fe5171a81f0dc0c134e4058 (patch)
tree    8db8da767e62f5e39466f5d2d1fe911d558c4e54
parent  4fc5a6eb72b6ee559250d67d1f1ceda256f9f9ed (diff)
download    aur-38281c069780d8f34fe5171a81f0dc0c134e4058.tar.gz
Version 1.15.0
Diffstat
-rw-r--r--  .SRCINFO    6   

-rw-r--r--  PKGBUILD    4   

2 files changed, 5 insertions, 5 deletions
diff --git a/.SRCINFO b/.SRCINFO
index c5173fc7882..c417b3a61ac 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,13 +1,13 @@
 pkgbase = binance
    pkgdesc = The Binance desktop application
-   pkgver = 1.14.1
+   pkgver = 1.15.0
    pkgrel = 1
    url = https://www.binance.com/en/download
    arch = x86_64
    license = unknown
    depends = electron
-   source = binance-1.14.1.deb::https://ftp.binance.com/electron-desktop/linux/production/binance-amd64-linux.deb
-   sha256sums = 4fb7d70b820b7fab105e8055887bce328796b1cfeebe4fd80210ce8306683a4b
+   source = binance-1.15.0.deb::https://ftp.binance.com/electron-desktop/linux/production/binance-amd64-linux.deb
+   sha256sums = 7154ed2490a9c6ff5a8af372388d1bea7ec84257302a1ef7cc83e7d38df971fb

@metaanon

Here is is the sha256 listed on binance: 7154ed2490a9c6ff5a8af372388d1bea7ec84257302a1ef7cc83e7d38df971fb Gotten here : https://ftp.binance.com/electron-desktop/linux/production/binance-amd64-linux-deb-sha256.txt

Here is the SHA256 within the .deb file: [huck@arch Downloads]$ sha256sum binance-amd64-linux.deb 96add572427cc441e63637311f5c4151250140df813f75d904a8d69c93b7d1ba binance-amd64-linux.deb

Clearly they do not match.