Package Details: brave 0.19.105-1

Git Clone URL: https://aur.archlinux.org/brave.git (read-only)
Package Base: brave
Description: Web browser that blocks ads and trackers by default.
Upstream URL: https://www.brave.com/
Keywords: browser muon web
Licenses: custom
Provides: brave-browser
Submitter: mischka
Maintainer: mischka (vorbote)
Last Packager: mischka
Votes: 40
Popularity: 1.673442
First Submitted: 2016-01-29 19:47
Last Updated: 2017-12-01 19:34

Dependencies (12)

Required by (0)

Sources (1)

Latest Comments

mdl054 commented on 2017-12-07 02:16

Errors here still, unable to build

at Object.long (/tmp/yaourt-tmp-matt/aur-brave/src/browser-laptop-0.19.105dev/node_modules/git-rev-sync/index.js:92:11) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! brave@0.19.105 build-package: node ./tools/buildPackage.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the brave@0.19.105 build-package script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/matt/.npm/_logs/2017-12-07T02_16_24_139Z-debug.log ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build brave. ==> Restart building brave ? [y/N]

rican-linux commented on 2017-12-04 02:32

The errors are resolved with the latest version!

rican-linux commented on 2017-11-28 01:46

I also have the same errors that @FreelancePolice. I reported it upstream here: https://github.com/brave/browser-laptop/issues/12114

mischka commented on 2017-11-04 19:09

Hm. Are you sure that the installation is being run with your globally installed node and not some lower version that's in your path (installed via nvm maybe)?

I believe node's strictness checking that returns those errors shouldn't be an issue after about v7.5.

jperic commented on 2017-11-04 17:39

Hello and thank you.

I'm trying to update with packer to v0.19.80-1

pacman -Q nodejs
nodejs 8.8.1-1

pacman -Q npm
npm 5.5.1-1

packer -S brave

Aur Targets (1): brave

Proceed with installation? [Y/n]

Edit brave PKGBUILD with $EDITOR? [Y/n]

==> Making package: brave 0.19.80-1 (Sat Nov 4 13:09:43 EDT 2017)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found browser-laptop-0.19.80dev.tar.gz
==> Validating source files with md5sums...
browser-laptop-0.19.80dev.tar.gz ... Passed
==> Extracting sources...
-> Extracting browser-laptop-0.19.80dev.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...

> brave@0.19.80 postinstall /tmp/packerbuild-1000/brave/brave/src/browser-laptop-0.19.80dev
> npm run download-sync-client && webpack


> brave@0.19.80 download-sync-client /tmp/packerbuild-1000/brave/brave/src/browser-laptop-0.19.80dev
> node ./tools/downloadSyncClient

writing sync bundle to /tmp/packerbuild-1000/brave/brave/src/browser-laptop-0.19.80dev/app/extensions/brave/content/scripts/sync.js
/tmp/packerbuild-1000/brave/brave/src/browser-laptop-0.19.80dev/webpack.config.js:13
let c = {
^^^

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:387:25)
at Object.Module._extensions..js (module.js:422:10)
at Module.load (module.js:357:32)
at Function.Module._load (module.js:314:12)
at Module.require (module.js:367:17)
at require (internal/module.js:20:19)
at module.exports (/tmp/packerbuild-1000/brave/brave/src/browser-laptop-0.19.80dev/node_modules/webpack/bin/convert-argv.js:80:13)
at Object.<anonymous> (/tmp/packerbuild-1000/brave/brave/src/browser-laptop-0.19.80dev/node_modules/webpack/bin/webpack.js:39:40)
at Module._compile (module.js:413:34)

npm WARN optional Skipping failed optional dependency /7zip-bin/7zip-bin-mac:
npm WARN notsup Not compatible with your operating system or architecture: 7zip-bin-mac@1.0.1
npm WARN optional Skipping failed optional dependency /7zip-bin/7zip-bin-win:
npm WARN notsup Not compatible with your operating system or architecture: 7zip-bin-win@2.1.1
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.1.2
npm WARN eslint-plugin-react@6.9.0 requires a peer of eslint@^2.0.0 || ^3.0.0 but none was installed.
npm WARN react-dom@15.6.2 requires a peer of react@^15.6.2 but none was installed.
npm WARN react-select@0.9.1 requires a peer of react@^0.14.1 but none was installed.
npm WARN react-select@0.9.1 requires a peer of react-dom@^0.14.1 but none was installed.
npm WARN react-test-renderer@15.6.2 requires a peer of react@^15.6.2 but none was installed.
npm ERR! Linux 4.13.8-1-ARCH
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v5.11.0
npm ERR! npm v3.8.6
npm ERR! code ELIFECYCLE
npm ERR! brave@0.19.80 postinstall: `npm run download-sync-client && webpack`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the brave@0.19.80 postinstall script 'npm run download-sync-client && webpack'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the brave package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! npm run download-sync-client && webpack
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs brave
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls brave
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /tmp/packerbuild-1000/brave/brave/src/browser-laptop-0.19.80dev/npm-debug.log
==> ERROR: A failure occurred in build().
Aborting...
The build failed.

I get the same messages with yaourt but then it goes on to building and installing.

mischka commented on 2017-10-10 02:51

@Chiruno looks like https://github.com/npm/npm/issues/18520, should be fixed upon upgrading npm to 5.5.0 or downgrading to 5.4.0 (I think, maybe lower). Not sure what I should do here to work around that for now. Any suggestions?

@FreelancePolice I'm willing to bet that will be fixed in a new release of brave (should be soon), that has tended to be the case for errors in `buildPackage.js` for me before. Sorry, also not sure what I should do here to fix it.

I'd recommend using brave-bin in the meantime, but I'm happy to hear suggestions.

Chiruno commented on 2017-10-10 02:28

make: Entering directory '/home/chiruno/.cache/pacaur/brave/src/browser-laptop-0.18.36dev/node_modules/tracking-protection/node_modules/cppunitlite/build'
CXX(target) Release/obj.target/CppUnitLite/src/Failure.o
CXX(target) Release/obj.target/CppUnitLite/src/SimpleString.o
CXX(target) Release/obj.target/CppUnitLite/src/Test.o
CXX(target) Release/obj.target/CppUnitLite/src/TestResult.o
CXX(target) Release/obj.target/CppUnitLite/src/TestRegistry.o
AR(target) Release/obj.target/CppUnitLite.a
COPY Release/CppUnitLite.a
CXX(target) Release/obj.target/test/test/StackMain.o
CXX(target) Release/obj.target/test/test/StackTest.o
LINK(target) Release/test
make: Leaving directory '/home/chiruno/.cache/pacaur/brave/src/browser-laptop-0.18.36dev/node_modules/tracking-protection/node_modules/cppunitlite/build'
+ cppunitlite@1.0.0
added 1 package in 1.38s
npm ERR! Cannot read property 'pause' of undefined

npm ERR! A complete log of this run can be found in:
npm ERR! /home/chiruno/.npm/_logs/2017-10-10T02_25_16_154Z-debug.log
==> ERROR: A failure occurred in build().
Aborting...
:: failed to build brave package(s)

FreelancePolice commented on 2017-09-30 20:12

This package fails to compile. The error message is:

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! brave@0.18.36 build-package: `node ./tools/buildPackage.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the brave@0.18.36 build-package script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/adam/.npm/_logs/2017-09-30T20_11_31_303Z-debug.log
==> ERROR: A failure occurred in build().
Aborting...

Chiruno commented on 2017-08-11 21:34

This package seems to be outdated.
https://github.com/brave/browser-laptop/releases/tag/v0.18.14dev

ZioCroccante commented on 2017-06-05 14:38

@palopezv
Thanks for the clear answer.

vorbote commented on 2017-06-05 14:30

@ZioCroccante

Can't be helped. It is a perfect storm of upstream changing library requirements to versions incompatible with npm 4.6.x. Thus, we need newer tools in Arch (will require a staging transition I think) and upstream to straighten out its act.

Patience. As you should be aware, brave is a browser in development and code quality is poor, not even alpha at some release milestones. That is, when it breaks you get to keep the pieces. Being brutally honest, if you are depending on it for something more than playing around at this stage, you are in trouble.

In the meantime, I'll fake the version to push the last working version.

vorbote commented on 2017-05-28 19:16

I just pushed 0.16.0 for your compiling and browsing pleasure. :-)

pseudoramble commented on 2017-05-28 16:41

Thanks @palopezv. I updated my comment to clarify what I was doing (which is not a good way to go). I've had a very simple script to do AUR package installations for a long time, and didn't realize some packages won't support the snapshot method anymore.

You should install cower, like I will :)

vorbote commented on 2017-05-28 13:32

I'll spell it out for you people:

YAOURT NOT SUPPORTED.

USE cower (OR SIMILAR) TO MAINTAIN AUR PACKAGES. IF YOU INSIST ON USING YAOURT, USE brave-bin INSTEAD.

@pseudoramble If you believe that is a true bug (that is, you did not use yaourt to compile the package), report it upstream. Thanks.

pseudoramble commented on 2017-05-28 13:11

EDIT: As @palopezv points out above, downloading the snapshot (or using Yaourt it seems) isn't supported for this. You _must_ use the git repo cloning method (or Cower) for this specific package. Some details can be found here: https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_packages. The first method (cloning the git repo) should work. The other ways will not without the hack I did below. You can also use brave-bin instead it seems. I've left my old comment just in case people are curious what I did.

I also had the same error is @mazzolino. I was able to resolve the issue with a tweak to the file ./tools/buildPackages.js on line 44 like this:

Before: BROWSER_LAPTOP_REV: require('git-rev-sync').long(),

After: BROWSER_LAPTOP_REV: 'unknown',

Then rebuild using makepkg -e from the package directory.

vorbote commented on 2017-05-25 21:27

Ahhh!!! Yaourt! DISCLAIMER: We are not responsible for any bodily harm you cause yourselves. From where I stand playing Blue Whale and using yaourt are the same thing. Use cower instead.

malfunc commented on 2017-05-25 21:20

I get the same error as mazzolino. Removing both directories didn't solve the issue for me.

vorbote commented on 2017-05-21 21:37

@mazzolino WFM. I suggest you purge both the npm cache and node-gyp rebuild directories ($HOME/.npm and $HOME/.node-gyp), after this build again while purging your build directory (makepkg -C).

mazzolino commented on 2017-05-21 13:05

I have a new error during build. Here is the relevant snippet:

> node ./tools/buildPackage.js

Writing buildConfig.js...
/tmp/yaourt-tmp-myuser/aur-brave/src/browser-laptop-0.15.306dev/node_modules/git-rev-sync/index.js:47
throw new Error('[git-rev-sync] no git repository found');

warai_otoko commented on 2017-05-14 17:04

Seems to be fixed by the new version.

warai_otoko commented on 2017-05-10 07:52

Actually, there are some worrying lines in the output of makepkg; there are five error messages that look more or less like this:
ERROR in aboutPages.entry.js from UglifyJs
SyntaxError: Unexpected token: name (ImmutableComponent) [./js/components/immutableComponent.js:7,6]

warai_otoko commented on 2017-05-10 07:48

Version 0.15.2 seems to install fine, but when I try to run brave, I just get "Trace/breakpoint trap (core dumped)".

mischka commented on 2017-04-30 22:47

This is what was causing the issue: https://github.com/maxogden/extract-zip/issues/38

For the time being, I've locked extract-zip to 1.6.0 in the installer for this package.

mischka commented on 2017-04-30 06:08

Actually I still can't seem to get it to build successfully, I'm not entirely sure what's happening. I keep getting a strange error in `npm install` that looks like it's an upstream issue. Sorry, please use brave-bin in the meantime.

mischka commented on 2017-04-30 03:00

Whoops, sorry about that. Thanks for letting me know!

MD20-20 commented on 2017-04-30 02:46

Package will not build,
Cloning the repo and running "updpkgsums" then "makepkg" fixes this.

vorbote commented on 2017-04-14 14:15

@Plexcon, upstream bugs are reported upstream. Here such reports are a nuisance at best...

Plexcon commented on 2017-04-14 12:55

npm WARNING deprecated css-list@0.1.3: Deprecated.
npm WARN deprecated babel@6.23.0: In 6.x, the babel package has been deprecated in favor of babel-cli. Check https://opencollective.com/babel to support the Babel maintainers
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated to-iso-string@0.0.2: to-iso-string has been deprecated, use @segment/to-iso-string instead.
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue


Luego se instala correctamente

Nobabs27 commented on 2017-02-16 02:56

Does not work.

npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the brave@0.13.2 build-package script 'node ./tools/buildPackage.js'.

vorbote commented on 2016-12-06 21:24

Yes, it is broken with the tooling available in Arch. Switch to brave-bin or brave-git for the time being.

Timothee commented on 2016-12-04 15:34

Hi, I have a problem for update brave :

npm ERR! Linux 4.8.11-1-ARCH
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v7.2.0
npm ERR! npm v4.0.3
npm ERR! code ELIFECYCLE

npm ERR! abp-filter-parser-cpp@1.2.10 preinstall: `npm install bloom-filter-cpp && npm install hashset-cpp`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the abp-filter-parser-cpp@1.2.10 preinstall script 'npm install bloom-filter-cpp && npm install hashset-cpp'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the abp-filter-parser-cpp package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! npm install bloom-filter-cpp && npm install hashset-cpp
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs abp-filter-parser-cpp
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls abp-filter-parser-cpp
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /tmp/yaourt-tmp-timothee/aur-brave/src/browser-laptop-0.12.11dev/npm-debug.log


Can you help me ? Thanks for your work :)

vorbote commented on 2016-09-21 16:50

The latest nodejs to hit the repos produces fully functional binaries. Enjoy!

vorbote commented on 2016-09-01 19:10

It seems there is a problem with the npm version in the repo. Please stick to the binary releases for now (you are welcome to hack your private PKGBUILD to use an older npm).

vorbote commented on 2016-09-01 17:43

I'm testing 0.11.6dev before pushing it as I write this. Did anyone get around to report this bug upstream?---I tend to use the upstream binary instead of compiling it myself these days.

chipmunkboogie commented on 2016-09-01 17:15

Package stops building:
npm WARN deprecated cross-spawn-async@2.2.4: cross-spawn no longer requires a build toolchain, use it instead!
[ .....] \ extract:xml2js: sill doParallel extract 1436

Kasperos commented on 2016-08-31 23:50

@ukbeast
Had it stuck in the same spot, running for ~1h. CPU usage on one core was constantly 100%.

ukbeast commented on 2016-08-31 18:37

Does it hang for anyone else at - extract:xml2js: sill doParallel extract 1436?

vorbote commented on 2016-08-25 15:33

We can take care of packaging bugs and perhaps some serious bugs in between releases that have patches released upstream.

Everything else must be reported to the upstream bug tracker, where it belongs.

I feel I must mention, saffronsnail, that brave is pre-alpha quality software in active development. To trust it for anything more than a toy for testing features and helping upstream iron out the bugs, can lead to losing data and serious hair loss.

saffronsnail commented on 2016-08-24 18:53

Hello,

I'm not 100% sure if this is an issue that should be reported to you or upstream, but I think I'm should report it to you because I don't experience this issue when I use Brave on my Windows installation.

Sometimes when I hit a special character into a text box, such as an @ or a space, that page freezes. It won't respond to any buttons, scroll, etc. All the other tabs continue working fine, and if I close that tab and re-open the page, everything works fine again. I have no clue why this would happen, any assistance you could give me would be appreciated.

Thanks,
saff

EDIT: 'appreciated' has two e's, not two i's

vorbote commented on 2016-08-09 22:02

Hey GI_Jack, that's the kind of issues that you must report upstream. They have a bug tracker and are the developers of the software, y'know...

GI_Jack commented on 2016-08-07 00:42

Tell the author that this fails on your system:
npm ERR! npm install bloom-filter-cpp && npm install hashset-cpp


Tell the author that this fails on your system:
npm ERR! npm install bloom-filter-cpp && npm install hashset-cpp

WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14
npm ERR! Linux 4.6.4-1-ARCH
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v6.3.1
npm ERR! npm v3.10.5
npm ERR! code ELIFECYCLE

dangerginger commented on 2016-07-23 16:34

@cnpovedaruiz I opened an issue and submitted a pull request (https://github.com/brave/browser-laptop/pull/2650) for the scrollbar. Until then, use the following workaround:

1. Press Ctrl+Alt+J
2. Use the DOM Inspector button in the top left (looks like a mouse pointer)
3. Click on the tab bar
4. Edit the css property `overflow-x` to be `hidden` for the class `.tabStripContainer`

.tabStripContainer {
overflow-x: hidden;
overflow-y: hidden;
}

vorbote commented on 2016-07-08 21:53

@cnpovedaruiz That's a known problem and something you should take upstream. Although I have not scourged the bug database for this particular bug, I'm sure it has already been reported many times. You may want to try the git package and see if there is already a fix upstream.

Do consider that brave is in active development and hasn't reached even alpha state yet. That it is usable is a tremendous accomplishment in itself! When you use pre-alpha, alpha and beta software, you are expected to report bugs to the authors, not the humble packagers. And always remember, when you use dev software and it breaks, you get to keep the pieces. :-)

cnpovedaruiz commented on 2016-07-08 18:39

There is a problem with Gnome and Brave, if you open enough tabs, a scroll bar appears over the tab bar hiding it.

Voice commented on 2016-04-26 09:59

Thank you mischka and fyi, I'm hardly new to Arch, an expert in fact. I know what a TTF font is.

What I don't is where ttf-font is defined or even described on any web page or git repo or wiki or anyplace. Such a lapse in Arch documentation is awful. Either ttf-font is defined in pacman source code (haven't looked) or it's just a convention among package maintainers meaning "any single TTF font." In the latter case it is only defined in the heads of the maintainers but should still be documented.

That said, my answer was given for another AUR package and you kindly echoed it:
https://aur.archlinux.org/packages/vivaldi/
BlackIkeEagle commented on 2016-04-24 11:51
ttf-font is required, but its free for you to choose which ttf-font you install. There is no need to install all packages that provide ttf-fonts.

mischka commented on 2016-04-25 15:28

@Voice "ttf" means TrueType Font (https://wiki.archlinux.org/index.php/fonts#TrueType), but there are a lot of packages in the repos and on the AUR that aren't in this short list on this page. Pretty much any font should work fine with Brave, though I doubt the settings menu in the application is good enough yet to let you select one.

As far as the PKGBUILD goes you can pretty much install any font, but if it's a question about getting brave to actually use the font you want you'll probably have to ask upstream, I don't know.

Another page where they mention truetype fonts: https://wiki.archlinux.org/index.php/general_recommendations#Fonts

vorbote commented on 2016-04-25 14:59

Voice, Study how pacman works and you will understand what is a virtual package and how it works. Use "pacman -Ql pacman | less" on a terminal; you will find a bunch of manual pages. Read them.



Voice commented on 2016-04-25 11:08

@vorbote Please stop. I wish to ask someone else. Can someone tell me simply where to find the definition of ttf-font. That was my question. Thank you.

vorbote commented on 2016-04-25 01:29

Voice, what you ask and how you ask will get you the answers you request, not the answers you need. http://deoxy.org/iching/4

Let's see:

1. No, font packages do not conflict. They do have a predefined score to be the default system serif, sans and monospace. Familiarize with fontconfig and you'll be able to tweak the system fonts as you like. All documentation is included in the package and the default configuration files are good reading.

2. Virtual packages are exactly what you found explained in the wiki. As packages were renamed to match opera and vivaldi I had to provide virtual packages for the old ones, as many people use things like certain tool that has a name that rhymes with curdled milk and rots your system just as easy. All font packages that can provide a set of serif, sans and monospace have a provides line. Read their PKGBUILDs.

3. As Brave *is* _opensource_, this package points to the source code to be built by yourself, Unfortunately, as Arch tooling is more recent than used by upstream, the binaries you compile are somewhat broken, such as not handling right-click events. Use brave-bin, the upstream provided binary. It works fine.

4. Bog. Ha! Sometimes I let through my dialectal influences. It means "plain old" in Southern England dialects (but no, I don't do Cockney).

5. Don't touch the pkgname. Use the brave-bin package.

Voice commented on 2016-04-24 03:52

Go decaf. I didn't ask you to change this PKGBUILD. I asked info to modify it correctly at home. No desire to fight design. Do whatever you want.

Most deps I already have onboard, save these fonts. Some conflict with extant fonts I don't want to replace.

I don't know Arch virtual packages. I know AUR has been revamped a lot lately. Is there any tutorial on virt/meta pkgs? Who or what is "Bog"? I did find
https://wiki.archlinux.org/index.php/creating_packages#Meta_packages_and_groups

But zip, nada on "ttf-font" - where is ttf-font defined? Thanks

Unrelated - is this fix needed?

brave.install
-pkgname=brave-browser-bin
+pkgname=brave

Thanks

vorbote commented on 2016-04-23 09:53

Binary package at https://aur.archlinux.org/pkgbase/brave-bin

vorbote commented on 2016-04-23 09:45

Bog standard virtual package as there are several others, such as bad and base-devel. It is there to guarantee that even people that refuse to install anything but an xserver and xterm with misc bitmap fonts have a decent set of outline font replacements for Arial, Courier and Times New Roman.

It is puzzling how you stomach installing all the dependencies pulled in by gtk+2, all the cruft pulled in by npm, the 1.6Gb debris left by compilation, yet protest for a little font package you can pick and choose if you want the smallest.

Voice commented on 2016-04-23 01:57

The font deps are too heavy for my taste. Does Arch give any web page for ttf-font? I can't find one. Should I look in source trees? Thanks

mischka commented on 2016-04-02 22:20

Oh, nice catch. I'll fix it this evening, I think there's a version update I need to put out as well.

And yes, it was Brave initially, I'm glad they fixed it though.

gok commented on 2016-04-02 11:08

The symlink on line 39 is incorrect: the filename of the brave binary in /usr/lib/brave-browser/ does not start (anymore?) with a capital 'B'.

The symlink command should be:
ln -s /usr/lib/brave-browser/brave "$pkgdir"/usr/bin/brave

vreyes commented on 2016-03-06 01:12

brave 0.8 is out. Please update

kozaki commented on 2016-02-25 21:39

Whatever happens was cool to use your PKGBUILD mischka (that is when it built ;). Smoother than to manually npm build-package, thank you for that.

vorbote commented on 2016-02-25 17:21

And the deed is done. Please kick the tires of the new package!

mischka commented on 2016-02-25 16:26

@vorbote Oh cool, alright. I didn't notice they released a binary with the newest one. I'll actually probably unsub from this package myself and start using -bin.

I just use an IfTTT recipe to notify me of new releases: https://ifttt.com/recipes/389669-notify-of-new-brave-releases

vorbote commented on 2016-02-25 16:21

I am packaging the upstream binaries that started showing up. I'll include you as co-maintainer mischka, as you are more aware of new releases than I. :-)

Keep an eye for brave-browser-bin

mischka commented on 2016-02-23 15:25

It seems that 32bit builds don't work. Apologies if anyone has tried installing with that architecture, I've fixed the pkgbuild.

mischka commented on 2016-02-23 14:35

@0xR are you on x64 or i686? Did you get any errors on install?

0xR commented on 2016-02-23 12:38

I have installed this package. When I run the brave command I get a window with this error:

Please make sure the webpack devserver is running via:
npm run watch

mischka commented on 2016-02-07 04:56

Should be up to date now, 0.7.13 builds. Full disclosure the internet where I am is bad so I built it somewhere else via ssh, so I haven't run it yet.

vorbote commented on 2016-02-04 00:34

Hi again, I have gone ahead and upload the brave-browser-git package (it compiles, you out-of-date marker...)

@mishka, I have done a thorough dependency analysis with the help of namcap and ldd and have added the following depends:

depends=('gtk2' 'nss' 'alsa-lib' 'libnotify' 'gconf' 'libxtst' 'desktop-file-utils')

feel free to scavenge anything you like in the PKGBUILD and .install file.

Cheers.

mischka commented on 2016-02-02 07:00

To whoever marked this out of date, 0.7.12 straight up doesn't build because it fails tests. It's been fixed in master but there have been no releases since.

I guess I can disable the tests, but I was hoping that they would make a new release soon.

mischka commented on 2016-01-31 23:10

Oh okay, thanks. I'll change it when I get home this evening.

vorbote commented on 2016-01-31 20:41

Hi, you got to this first! Congratulations.

One observation: nodejs is a makedepend not a depend. The browser works perfectly well without nodejs installed in the system because it includes the runtime lib (list the contents of the installed top directory). Just makedepend on npm as it depends on nodejs.

Cheers.