Arch Linux User Repository

Based on architecture, You can do some conditional check maybe (setting up proper version)? Because for arm64, it's always failing unless manual changes.

Correct. This is an issue somewhere between Brave upstrean and Arch. Brave's ARM packages fail to build quite often, while the Intel versions work. Arch doesn't allow split package versions by architecture. The choice I face is to either wait to upgrade intel until Arm is fixed (a very poor choice - almost everybody uses intel), drop ARM support (or maybe create a brand new package for it - and since I have no way to test this package, not a great choice), or just ignore Arm fails and move forward, thus keeping Intel up to date.

For now, I chose the latter.

I'm sure that at some point, the Brave ARM builds will build consistently, at which point this will be a non-issue.

  -> Downloading brave-browser-beta_1.59.79_arm64.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     9    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading https://github.com/brave/brave-browser/releases/download/v1.59.79/brave-browser-beta_1.59.79_arm64.deb

The solution is to downgrade the version, as I did locally:

diff --git a/PKGBUILD b/PKGBUILD
index f02d67f..e9d43e0 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -2,7 +2,7 @@
 # Maintainer: Greg White <gwhite@kupulau.com>

 pkgname=brave-beta-bin
-pkgver=1.59.79
+pkgver=1.59.78
 pkgrel=1
 pkgdesc='Web browser that blocks ads and trackers by default (beta binary release).'
 arch=(x86_64 aarch64)

==> Validating source_aarch64 files with sha512sums...
    brave-browser-beta_1.58.91_arm64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
 -> error downloading sources: /home/<user>/.cache/yay/brave-beta-bin 
         context: exit status 1 


:: (1/1) Parsing SRCINFO: brave-beta-bin
==> Making package: brave-beta-bin 1.58.91-2 (Sat 19 Aug 2023 10:07:48 AM +04)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found brave-beta-bin.sh
  -> Found brave-browser-beta_1.58.91_arm64.deb
==> Validating source files with sha512sums...
    brave-beta-bin.sh ... Passed
==> Validating source_aarch64 files with sha512sums...
    brave-browser-beta_1.58.91_arm64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
 -> error making: brave-beta-bin-exit status 1
 -> Failed to install the following packages. Manual intervention is required:
brave-beta-bin - exit status 1

Thanks. I'm using the github API to pull the actual builds as they occur.

hey @gregbunk. please take a look at https://versions.brave.com/ - it's an overview of Brave versions, including links to individual endpoints returning a version for a given platform/architecture, that can be used in automation - e.g. https://versions.brave.com/latest/beta-linux-x64.version and https://versions.brave.com/latest/beta-linux-arm64.version.

Sorry for the long update interval; missed that the script had broken.

@gregbunk

Slight issue with brave-beta-bin 1.53.87-1 update:

It's creating a Brave-Browser-Nightly in ~/.config so it's can't see the Beta folder and thinks it's a freshly installed browser.

EDIT: Thanks for the fix in 1.53.87-2 @gregbunk. Appreciate you as a maintainer.

I have added experimental aarch64 support. I have no way to test this, so I'm flying blind. If someone can try and let me know that would be great.

Please note that aarch64 Brave builds are VERY spotty right now. They seem to not be available a lot of the time.

Thanks - fixed.