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?
Search Criteria
Package Details: brave-bin 1:1.78.102-1
Package Actions
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: | brave |
Last Packager: | brave |
Votes: | 875 |
Popularity: | 17.39 |
First Submitted: | 2016-04-06 13:16 (UTC) |
Last Updated: | 2025-05-15 16:26 (UTC) |
Dependencies (8)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR, gtk3-classic-xfceAUR)
- libxss
- nss (nss-hgAUR)
- ttf-font (neuropol-ttfAUR, ttf-win7-fontsAUR, ttf-ms-win8AUR, ttf-ms-win8-arabicAUR, ttf-ms-win8-hebrewAUR, ttf-ms-win8-seaAUR, ttf-ms-win8-indicAUR, ttf-ms-win8-japaneseAUR, ttf-ms-win8-koreanAUR, ttf-ms-win8-zh_cnAUR, ttf-ms-win8-zh_twAUR, ttf-ms-win8-thaiAUR, ttf-ms-win8-otherAUR, ttf-kidsAUR, ttf-liberation-sans-narrowAUR, ttf-cavafy-scriptAUR, ttf-ms-fontsAUR, ttf-dejavu-ibAUR, ttf-zeldaAUR, ttf-oxygenAUR, ttf-oxygen-gfAUR, ttf-share-gfAUR, ttf-gostAUR, otf-inconsolata-dzAUR, ttf-d2codingAUR, ttf-agaveAUR, ttf-caracteresAUR, ttf-cuprumAUR, ttf-autour-oneAUR, ttf-impallari-milongaAUR, ttf-impallari-miltonianAUR, ttf-clarity-cityAUR, ttf-ms-win10AUR, ttf-ms-win10-japaneseAUR, ttf-ms-win10-koreanAUR, ttf-ms-win10-seaAUR, ttf-ms-win10-thaiAUR, ttf-ms-win10-zh_cnAUR, ttf-ms-win10-zh_twAUR, ttf-ms-win10-otherAUR, ttf-win10AUR, ttf-bmonoAUR, ttf-pt-astra-factAUR, ttf-weblysleekuiAUR, ttf-pt-astra-sansAUR, ttf-pt-astra-serifAUR, ttf-pt-sansAUR, ttf-pt-serifAUR, ttf-pt-monoAUR, ttf-pt-root_uiAUR, ttf-xo-fontsAUR, ttf-paratypeAUR, ttf-dejavu-emojilessAUR, ttf-lucida-fontsAUR, ttf-juiseeAUR, ttf-ms-win10-autoAUR, ttf-karlaAUR, ttf-ms-win11-autoAUR, ttf-ms-win10-cdnAUR, noto-fonts-liteAUR, ttf-ibm-plex-sans-scAUR, noto-fonts-variable-liteAUR, ttf-shangguAUR, noto-fonts-latin-greek-cyrillicAUR, apple-fontsAUR, ttf-ms-win11AUR, ttf-ms-win11-japaneseAUR, ttf-ms-win11-koreanAUR, ttf-ms-win11-seaAUR, ttf-ms-win11-thaiAUR, ttf-ms-win11-zh_cnAUR, ttf-ms-win11-zh_twAUR, ttf-ms-win11-otherAUR, ttf-plemoljp-binAUR, ttf-plemoljpAUR, ttf-noto-sans-vfAUR, ttf-noto-serif-vfAUR, ttf-noto-sans-mono-vfAUR, gnu-free-fonts, noto-fonts, ttf-bitstream-vera, ttf-croscore, ttf-dejavu, ttf-droid, ttf-ibm-plex, ttf-input, ttf-input-nerd, ttf-liberation, ttf-roboto)
- cups (cups-gitAUR, cups-gssapiAUR) (optional) – Printer support
- libgnome-keyring (optional) – Enable GNOME keyring support
- libnotify (libnotify-gitAUR) (optional) – Native notification support
Required by (9)
- brave-extension-bitwarden-git (requires brave) (optional)
- chromium-dearrow-bin (requires brave) (optional)
- chromium-material-icons-for-github-bin (requires brave) (optional)
- chromium-vencord (requires brave) (optional)
- chromium-vencord-bin (requires brave) (optional)
- chromium-vencord-git (requires brave) (optional)
- ice-ssb-git (requires brave) (optional)
- nfauthenticationkey (requires brave) (optional)
- profile-sync-daemon-brave (requires brave) (optional)
Sources (4)
Latest Comments
« First ‹ Previous 1 .. 44 45 46 47 48 49 50 51 52 53 54 .. 61 Next › Last »
afontenot commented on 2019-04-08 00:23 (UTC)
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.
-
Can you add yourself as the maintainer to the PKGBUILD? Currently now-im is listed as the maintainer.
-
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.)
-
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.
neontiger26 commented on 2019-03-09 23:51 (UTC)
@miomio I downloaded it from Brave's GitHub account.
Pinned Comments
brave commented on 2025-04-25 13:00 (UTC)