Hello all! Been about a year since I was last here.
(Spent about five years participating | contributing 
)
Sadly, I have an issue/challenge, that I can’t solve.
I have Brave Stable and Brave Beta installed on my openSUSE Leap system (Linux). I run a system update almost every day (which includes Brave).
Brave Stable is updated every week or two.
Brave Beta would get updated every few days.
The last update (here) for Beta was on Aug 21 (two weeks ago):
brave-browser-beta : 1.94.109-1 → 1.95.87-1
I went to Brave’s Github site and I see that the current Beta version is:
brave-browser-beta-1.96.46-1.x86_64.rpm
So, yea, obviously, updated versions are happening.
However, when I run “zypper update” (updates all software), a Beta update is never included.
.
And guess what? I just installed a new openSUSE Leap version in a VBox virtual machine. I then added the Brave-Beta repository and ran a “zypper install Beta”.
It installed 1.95.87-1 !! (should be 1.96.46) … the same version of the last update on my other (completely different) machine. 
Also, on a third different machine, Beta is NOT getting updated.
Brave Stable gets updated on all the machines.
It seems the Beta repository isn’t getting updates??
.
Anyone have any thoughts what’s rwong ??
.
Here’s my repository configuration, showing the URL to the Brave source repos.
(I snipped out unnecessary repos for other software).
cc@mach:~> zypper lr -d
| Alias |Name |Enabled|Refresh|URI |
+--------------------+------------+-------+-------+-----------------------------------------------------+
| brave-browser |Brave Stable|Yes |Yes |https://brave-browser-rpm-release.s3.brave.com/x86_64|
| brave-browser-beta |Brave Beta |Yes |Yes |https://brave-browser-rpm-beta.s3.brave.com/x86_64 |
+--------------------+------------+-------+-------+--------------------+
cc@mach:~>
Very quiet out here … I guess folks are on a 3 day vacation 
.
So, just a few minutes ago, I ran another [daily] system update.
There is now an issue with the Beta URL to the its Repository (but the Stable Repo URL is accessible, no error) - here’s the error snippet for Beta:
.
Checking whether to refresh metadata for Brave Browser - Beta
Retrieving repository 'Brave Browser - Beta' metadata ...[error]
Repository 'Brave Browser - Beta' is invalid.
[brave-browser-beta|https://brave-browser-rpm-beta.s3.brave.com/x86_64] Failed to retrieve new repository metadata.
History:
- [|] Error trying to read from 'https://brave-browser-rpm-beta.s3.brave.com/x86_64'
- Timeout exceeded when accessing 'https://brave-browser-rpm-beta.s3.brave.com/x86_64/repodata/repomd.xml'.
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'Brave Browser - Beta' because of the above error.
Well, I thought I’d try a workaround, since Brave is STILL not being updated via the Brave repo. 
So I downloaded a newer Beta version (95.98) from Brave Github. I then installed it using "zypper install ...".
So, after a few days waiting for a newer version (there is), I did my usual "zypper update" to install any updated software.
Did Brave get updated (knowing there is a newer version) … NOPE. But hey, Chrome got an update 
So, the dedicated, created by Brave repo, still did not provide the newest update.
Checking whether to refresh metadata for Brave Browser - Beta
Retrieving: repomd.xml ...[done]
Looking for gpg keys in repository Brave Browser - Beta.
gpgkey=https://brave-browser-rpm-beta.s3.brave.com/brave-core-beta.asc
Retrieving: brave-core-beta.asc ...[done]
Retrieving: repomd.xml.asc ...[done (833 B/s)]
Repository: Brave Browser - Beta
Key Fingerprint: 56F4 9901 AB19 BAF0 99A9 5A76 C3DE 1DD4 F661 CDCB
Key Name: Brave Linux Pre Release (Brave Linux Pre Release) <brave-linux-pre-release@brave.com>
Key Algorithm: RSA 4096
Key Created: Thu Dec 19 11:48:43 2024
Key Expires: Fri Dec 24 09:05:17 2032
Rpm Name: gpg-pubkey-f661cdcb-67645c7b
Retrieving: 52741e070db97c6420998825ac77aa2d4b03c51660d1007d5b617338e6366f69-prestodelta.xml.gz ....[done (78 B/s)]
Retrieving: d6fdc2997b835cc373afd4415e56199d46493550b41680bbcd6714ac2430ef4b-primary.xml.gz ..[done]
Retrieving repository 'Brave Browser - Beta' metadata ....[done]
Building repository 'Brave Browser - Beta' cache ...[done]
Checking whether to refresh metadata for google-chrome
[ ... ]
[ ... ]
Reading installed packages...
Force resolution: No
The following package is going to be upgraded:
google-chrome-stable 152.0.7977.82-1 -> 153.0.8010.36-1
1 package to upgrade.
Package download size: 138.4 MiB
Package install size change:
| 433.7 MiB required by packages that will be installed
-2.1 MiB | - 435.8 MiB released by packages that will be removed
Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y):
committing
Retrieving: google-chrome-stable-153.0.8010.36-1.x86_64 (Google-Chrome) (1/1), 138.4 MiB
Retrieving: google-chrome-stable-153.0.8010.36-1.x86_64.rpm ... [done (45.3 MiB/s)]
Checking for file conflicts: ...[done]
(1/1) Installing: google-chrome-stable-153.0.8010.36-1.x86_64 ...[done]
.
Seventeen days later … still have issue (plus new), on multiple machines.
And still, no response out here.
Warning: Digest verification failed for file 'brave-browser-beta-1.97.47-1.x86_64.rpm'
expected c9617d5330c150c13b4f04f9be1a3b6a4e75bd38b52204417f261e09e01550db
but got 05b4c8124526b263670bf5f9b099bf57f426dadcabe72fd73cd11dfba69bbd7e
Accepting packages with wrong checksums can
lead to a corrupted system and in extreme cases
even to a system compromise.