Problems installling brave-browser*.rpm current stable on Mageia (Linux)

[andr222]

My system : Mageia 7 (Linux 64b), with Mate 1.22.0 (desktop), and
Vivaldi 2.4.1488.40 (Stable channel) (64 bits)

I tried to install the current stable .rpm for Mageia from the download page, but the rpm command on Mageia doesn't recognize the --import option.
(If it does and somehow it doesn't work, the --import option is not documented.)

Also, Mageia uses urpmi as a front end to rpm, and not dnf used by fedora.

On the https://github.com/brave/brave-browser/releases/download/v0.66.101/
page, I downloaded and attempted to install
brave-browser-0.66.101-1.x86_64.rpm
This fails because brave-keyring is not found.

Why isn't the installed keyring service used ?
(My configuration uses gnome-keyring, one of the major such services on Mageia.)

Another Mageia user successfully installed brave-v0.66.100-linux-x64.zip
I will look for the details, and try it.

[kjozwiak]

CCing @fmarier.

[fmarier]

Thanks @andr222 for providing these details.

I have just installed Mageia 7.1 and was able to install Brave successfully by following the official installation instructions for CentOS/RHEL.

I strongly recommend that you use that method to install Brave on your machine because that will ensure that your copy of Brave is always up-to-date with security fixes.

Please let me know how that works on your machine and I will add Mageia to the installation page if you can confirm that it works for you too.

[andr222]

It is a bit of a cludge. Installing a foreign package management front end and a set of parallel repos, most of which will never be used.
It would be much simpler to simply facilitate direct access to the brave package, with a function in brave that warns if a new version is available. (A very common practice of open source software not tied to a particular distro.)
The current approach almost guarantees that the most recent stable version will NOT be installed.
Sorry to say ...
Note that non-Mageia rpm front ends often do not work properly for Mageia packages.

If one wishes to create a repo for brave, it would be much better to do it in the native repo structure of Mageia (which is the same as Mandriva). That would help ensure that the latest stable version were always installed, along with regular updates of Mageia repos.
Mageia repos are defined in /var/lib/urpmi/ .

It does show that the --import option of rpm works in Mageia, but is undocumented.

[andr222]

Note that what makes the proposed solution problematic is to use it one needs 2 rpm front ends installed, one of which is only used for a single package, thus readily overlooked. The native rpm front end (urpmi) gives automatic update warnings, whenever an update is available for any of its' defined repos.

[andr222]

Downloading the most recent brave-v{version}-linux-x64.zip file and unzipping it to an arbitrary location, and making a link in the menu to the brave executable works nicely.
It doesn't use mageia's system of automatic warning of available updates.
For that a repo would have to be added in mageia's repo structure. Each repo can have a defined key, to ensure that the package is appropriately signed.

Making distro-specific packages has the disadvantage of limiting usage by other distros.
A generic rpm could be installed on all rpm-based distros without problem. (fedora, centos, mageia, suse, mandriva).