Package Details: brave-bin 1:1.73.89-1

Git Clone URL: https://aur.archlinux.org/brave-bin.git (read-only, click to copy)
Package Base: brave-bin
Description: Web browser that blocks ads and trackers by default (binary release)
Upstream URL: https://brave.com
Keywords: brave browser
Licenses: BSD, MPL2, custom:chromium
Conflicts: brave
Provides: brave, brave-browser
Submitter: toropisco
Maintainer: alerque (alosarjos)
Last Packager: alosarjos
Votes: 822
Popularity: 18.67
First Submitted: 2016-04-06 13:16 (UTC)
Last Updated: 2024-11-13 21:57 (UTC)

Dependencies (8)

Required by (10)

Sources (4)

Pinned Comments

alerque commented on 2021-11-27 03:11 (UTC)

@ant0n et all, lets keep the comments here about packaging issues, general Brave usage issues should go in another forum to not clutter up this comment space. I'm deleting comments that have no relation to packaging. Grey areas like crashes that could be blamed on Arch can stay until proven otherwise, but things like how to configure Brave to handle popups or site X or whatever just don't belong here. Thanks for understanding.

Latest Comments

« First ‹ Previous 1 .. 41 42 43 44 45 46 47 48 49 50 51 .. 59 Next › Last »

mixedCase commented on 2019-04-08 17:50 (UTC)

Hey guys, sorry I didn't respond earlier just saw the comments today and re-enabled notifications. So:

afontenot: Removed gconf from depends and moved libgnome-keyring to optional dependencies.

digitalone: Thanks for the reminder on pkgrel, I made the change on a machine without my usual pre-commit hook and didn't notice. Regarding the extension bug, I was looking into avoiding a second download of the browser just because of an upstream packaging issue; but since a lot of people use Brave solely for the crypto stuff I'll just merge those changes until I have more time to look into using the deb alone. Thank you for the patchset, just merged.

digitalone commented on 2019-04-08 16:27 (UTC) (edited on 2019-04-08 16:29 (UTC) by digitalone)

When you modify the PKGBUILD, you should also increase pkgrel number otherwise users that already installed the package won't get any change.

And, please, merge my modification reported here to include resources directory from deb release so Brave Shield issue can be fixed until developers will make a fully working linux zip package.

digitalone commented on 2019-04-08 15:24 (UTC) (edited on 2019-04-08 15:25 (UTC) by digitalone)

This PKGBUILD modified by me fixes Brave Shield issue. Please update.

afontenot commented on 2019-04-08 00:23 (UTC)

Following up: I've been running an edited version of this PKGBUILD with libgnome-keyring and gconf removed from depends for a while with no problems under KDE. As I said in a previous comment, they're not required by the Debian brave package. Can you move them to optdepends please?

neontiger26 commented on 2019-03-29 23:59 (UTC)

@vith If you're referring to the Brave Shield and Brave Rewards, use the fix Cpt_Pi brought up in a prior comment that states,

"The no text in Shield and missing translation in Rewards are due to how Brave have been packaging the .tar.gz.

To fix the "No text in Shield and no translation in Rewards" - you have to download the .deb and extract the Resources directory into /usr/lib/brave-bin"

vith commented on 2019-03-29 21:27 (UTC)

There seems to be some problem with some (localized?) strings in Brave's customizations. Their added icons in the right side of the address bar have missing and/or placeholder text in their popups.

afontenot commented on 2019-03-29 06:35 (UTC)

@mixedCase: Several issues / questions.

  1. Can you add yourself as the maintainer to the PKGBUILD? Currently now-im is listed as the maintainer.

  2. I haven't flagged it, since you say you have a script, but is this not a more recent release from 8 days ago? https://github.com/brave/brave-browser/releases/tag/v0.61.52 (I'll flag to get your attention if you don't respond within a day or two.)

  3. Can you please check to see whether moving libgnome-keyring and gconf to optdepends (or removing them entirely) is possible. The official debian package of the most recent release does not have these listed as dependencies. In particular removing the latter would eliminate the dependency on Python 2, which I do not have installed.

Thanks!

mixedCase commented on 2019-03-11 13:52 (UTC) (edited on 2020-09-01 20:39 (UTC) by mixedCase)

=== PLEASE READ PLEASE READ BEFORE REPORTING OUT OF DATE ===

Before making your report, please note that the newer GitHub release you're looking at belongs to the "Release Channel" and --isn't marked as prerelease--.

I have a cron running that's checking every 30 minutes if there's a new release and sends me an email if so. If you see the release was tagged in the last couple of hours please give it some time before flagging.

Also please take into account a stable version may be "released" on GitHub but not marked as ready (read, NOT PRELEASE) for a long time.

Another handy tool to check latest OFFICIALLY MARKED AS STABLE version of Brave is to run:

curl https://brave-browser-downloads.s3.brave.com/latest/release.version

Cpt_Pi commented on 2019-03-11 12:26 (UTC)

@miomio, this is fixed with PR-3446 which should be in a release soon.

neontiger26 commented on 2019-03-10 19:15 (UTC)

@miomio No, one should have too. Unfortunately, that's the reality of not having an official Arch build and having to rely on a user repository to use a preferred piece of software.

If the Brave team could include the resource directory in the official zip file, then it's my understanding that you wouldn't have to go through this extra step. The best thing to do would be to let Brave developers know of this problem so it can be included in future releases.

« First ‹ Previous 1 .. 41 42 43 44 45 46 47 48 49 50 51 .. 59 Next › Last »