Closed
Description
Description
Everyday the repo URL is altered which broke brave update and whole rpm system update
RPM release ship /etc/cron.daily/brave-browser which update brave-browser.repo to link to hhtp://dl.google.com
The variable REPOCONFIG in /etc/cron.daily/brave-browser need to be updated to official brave repo.
Steps to Reproduce
- Install brave-browser via rpm-release repository
- Wait 1 day
- Update system/brave-browser
Actual result:
sudo (zypper|yum|urpmi) up brave-browser
Retrieving repository 'brave-browser' metadata [error]
Repository 'brave-browser' is invalid.
[brave-browser|http://dl.google.com/linux/brave-browser/rpm/stable/x86_64] Valid metadata not found at specified URL
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'brave-browser' because of the above error.
Some of the repositories have not been refreshed because of an error.
Reproduces how often:
Everyday (see /etc/cron.daily/brave-browser)
Brave version (brave://version info)
Brave 0.55.20 Chromium: 70.0.3538.67 (Build officiel) (64 bits)
Révision 9ab0cfab84ded083718d3a4ff830726efd38869f-refs/branch-heads/3538@{#1002}
Système d'exploitation Linux
Reproducible on current release:
- Reproducible on brave-browser release
- didn't try dev/beta
Additional Information
Open question: does a privacy oriented browser should alter the distro repo without user consent?
The update_bad_repo func in /etc/cron.daily/brave-browser should be controled via /etc/default/brave-browser