Package Details: beaker-browser-bin 0.8.8-1

Git Clone URL: (read-only)
Package Base: beaker-browser-bin
Description: Peer-to-peer browser with tools to create and host websites
Upstream URL:
Licenses: Modified MIT License (MIT)
Provides: beaker-browser, beakerbrowser
Submitter: jeancf
Maintainer: jeancf
Last Packager: jeancf
Votes: 11
Popularity: 0.018635
First Submitted: 2018-01-03 15:20
Last Updated: 2019-04-04 09:13

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

jeancf commented on 2018-08-26 08:37

@aurelieng It should be fixed now. Sorry for that.

aurelieng commented on 2018-08-26 08:13

I just tried to install it with the yay AUR helper. The build failed with the following error, which can be reproduced with makepkg manually:

==> Sources are ready.
==> Making package: beaker-browser-bin 0.8.0_prerelease.7-3 (Sun 26 Aug 2018 09:50:19 AM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Entering fakeroot environment...
==> Starting package()...
install: cannot stat '/home/aurelien/.cache/yay/beaker-browser-bin/src/beaker-browser': No such file or directory
==> ERROR: A failure occurred in package().
Error making: beaker-browser-bin

jeancf commented on 2018-08-21 15:25

I only notice now your edits to your last message (edits don't trigger notifications).

I will push the update on AUR.

pegasus commented on 2018-08-18 19:30

Thanks for the lesson on how open source software works. If it weren't for lovely folk like you I would have absolutely no idea how I should treat people who use any software, but most especially the software I write. I'll be sure to neglect them more. Especially when they put forth effort to figure out how to fix problems that I apparently don't have any time or desire to investigate on my own. And then when they give me a ready-made solution, hoo buddy, I'm gonna ignore them for a whole day, and then give 'em hell. Lesson learned.

Here I thought taking on the job of maintainer entailed responsibility just like a paying job, but now I know better! I should go adopt literally every orphan package on the AUR and then fail to do anything at all with them. Best package maintainer ever! Look at how many packages I "maintain"!

...holy shit this host is slow. I wrote this entire comment while waiting for it to download. When it finally finishes downloading, I'll edit this post and let you know if it works.

EDIT: Yeah, that seems to be the exact solution I gave you, and therefore it seems to work fine. I deleted /opt/beaker-browser/app/resources/app.asar.unpacked as a test, and it still seems to work fine. So can it officially be declared out-of-date now, or are you going to complain when I flag it again?

EDIT2: Also, I'm not taking your advice on how to treat people that rely on me, even if I don't get paid by them. As such, I apologize for the delay in testing your candidate package.

jeancf commented on 2018-08-18 14:16

@pegasus can you please try installing this package and let me know if it works for you?

Just run sudo pacman -U ./beaker-browser-bin-0.8.0_prerelease.7-3-x86_64.pkg.tar.xz

If it works I will release it on AUR.


jeancf commented on 2018-08-18 07:32

Dear @pegasus, I would appreciate if you could tone it down one notch or two! I am not at your service and I don't remember you paying me for a Service Level Agreement.

Open source software is PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. If you are not happy, you are free to take your arrogance somewhere else and sort your issue on your own.

I will work on this when I find the time.

Best Regards.

pegasus commented on 2018-08-17 13:13

Perfectly functional for Manjaro users. This isn't the Manjaro user repository. Still waiting for you to implement the non-git fix that took me less than an hour to figure out. Been ...SIXTEEN?!?! hours now...

jeancf commented on 2018-08-17 12:51

The package is perfectly functional for other users.

There is a bug that affects you and possibly some others and as I said, I am prepared to try and fix it.

pegasus commented on 2018-08-17 12:44

I'm not reporting a bug. I'm reporting the package nonfunctional. Slight difference. When they add a "flag package defective" I'll use that instead.

jeancf commented on 2018-08-17 12:41

Yes it is. Read what the "flag out-of-date" form says:

"Please do not use this form to report bugs. Use the package comments instead. Enter details on why the package is out-of-date below, preferably including links to the release announcement or the new release tarball."

I will try to implement your suggestion.