Package Details: palemoon 1:33.4.1-1

Git Clone URL: https://aur.archlinux.org/palemoon.git (read-only, click to copy)
Package Base: palemoon
Description: Open source web browser based on Firefox focusing on efficiency.
Upstream URL: https://www.palemoon.org/
Keywords: browser goanna web
Licenses: MPL-2.0
Submitter: artiom
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 141
Popularity: 0.131247
First Submitted: 2014-06-05 10:54 (UTC)
Last Updated: 2024-11-05 20:54 (UTC)

Pinned Comments

WorMzy commented on 2021-03-02 16:19 (UTC) (edited on 2022-08-03 21:12 (UTC) by WorMzy)

The following key is used to sign release commits:

40481E7B8FCF9CEC

Import it into your keyring however you want.

https://wiki.archlinux.org/index.php/GnuPG#Import_a_public_key

Latest Comments

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 38 Next › Last »

<deleted-account> commented on 2017-04-18 16:40 (UTC)

https://www.dropbox.com/s/47vmswq9fgwudvd/output.txt?dl=0

WorMzy commented on 2017-04-06 17:36 (UTC) (edited on 2017-04-06 17:36 (UTC) by WorMzy)

Builds fine here in a clean chroot. Please post the full build log. (To a pastebin service, link here)

Larivact commented on 2017-04-05 18:29 (UTC)

Build fails because "Clobber required for gamepad disable (WebIDL change)".

sekret commented on 2017-03-30 09:17 (UTC)

FYI, I built palemoon 27.2.1-1 with gcc 6.3.1-2 to see how the browser behaves. I get very frequent crashes without any real reason. I block any content other than 1st party css and images by default, so no bad javascript or flash issues cause those crashes. This is not a bug report or anything, so no traces are attached. It's just a heads up for you guys: Don't build with gcc6, stick to gcc5 or if you want gcc4.

WorMzy commented on 2017-03-14 19:25 (UTC)

Do you get any errors? The uninitialized currentIsSelected messages are not the problem, but the NSModules order message looks suspicious. The package builds fine in a clean chroot for me. I would recommend using clean chroots over yaourt (or even direct makepkg) in any case. https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot

<deleted-account> commented on 2017-03-14 18:27 (UTC)

fails to build, can anybody try or advise? thnx 0:21.41 /tmp/yaourt-tmp-gofree/aur-palemoon/src/Pale-Moon/toolkit/xre/nsAppRunner.cpp: In member function ‘int XREMain::XRE_mainStartup(bool*)’: 0:21.41 Warning: -Wmaybe-uninitialized in /tmp/yaourt-tmp-gofree/aur-palemoon/src/Pale-Moon/toolkit/xre/nsAppRunner.cpp: ‘currentIsSelected’ may be used uninitialized in this function 0:21.41 /tmp/yaourt-tmp-gofree/aur-palemoon/src/Pale-Moon/toolkit/xre/nsAppRunner.cpp:2020:7: warning: ‘currentIsSelected’ may be used uninitialized in this function [-Wmaybe-uninitialized] 0:21.41 if (!currentIsSelected) { 0:21.41 ^ 0:21.41 /tmp/yaourt-tmp-gofree/aur-palemoon/src/Pale-Moon/toolkit/xre/nsAppRunner.cpp:2016:12: note: ‘currentIsSelected’ was declared here 0:21.41 bool currentIsSelected; 0:21.41 ^ 0:21.95 libtoolkit_xre.a.desc 0:21.98 libxul_s.a.desc 0:21.98 libxul.so 0:51.04 NSModules are not ordered appropriately 0:51.04 make[5]: *** [/tmp/yaourt-tmp-gofree/aur-palemoon/src/Pale-Moon/config/rules.mk:821: libxul.so] Error 1 0:51.04 make[5]: *** Deleting file 'libxul.so' 0:51.14 make[4]: *** [/tmp/yaourt-tmp-gofree/aur-palemoon/src/Pale-Moon/config/recurse.mk:74: toolkit/library/target] Error 2 0:51.14 make[3]: *** [/tmp/yaourt-tmp-gofree/aur-palemoon/src/Pale-Moon/config/recurse.mk:37: compile] Error 2 0:51.14 make[2]: *** [/tmp/yaourt-tmp-gofree/aur-palemoon/src/Pale-Moon/config/rules.mk:541: default] Error 2 0:51.15 make[1]: *** [/tmp/yaourt-tmp-gofree/aur-palemoon/src/Pale-Moon/client.mk:398: realbuild] Error 2 0:51.15 make: *** [client.mk:171: build] Error 2 0:51.18 243 compiler warnings present.

WorMzy commented on 2017-03-08 19:43 (UTC)

We have been building with gcc5 since ~April 2015, and I have never experienced instability with the core browser. I also haven't seen any such stability issues reported on the Arch Linux forums. A quick search of the Palemoon forums doesn't yeild any stability reports by Arch users either. I did follow a github topic about gcc5 stability, but that appeared to be caused by binaries built with bad mozconfigs on unstable/testing versions of debian, then run on stable versions of debian/ubuntu. As gcc49 is EOL (as of August last year [1]), insisting that people use it over gcc5 is not a long term solution. As it stands, we currently use gcc5 because when Arch updated to gcc6, Palemoon didn't support it. Arch currently ships a gcc5 package, so we get that for free; if we were to switch to gcc49, users would need to compile that too, adding a lot of burden to them (palemoon already takes long enough to compile without having to compile the compiler too). Cheers. [1] https://gcc.gnu.org/ml/gcc-announce/2016/msg00002.html

mattatobin commented on 2017-03-08 17:23 (UTC)

Because it produces unstable builds?!

WorMzy commented on 2017-03-03 16:21 (UTC)

No. I have discussed the matter with Travis already. Users can build gcc49 and then make the necessary changes to the PKGBUILD and mozconfig if they wish to, but I see no discernable benefit for forcing all users to do this.

mattatobin commented on 2017-03-03 15:40 (UTC)

You do realize that you MUST use GCC 4.9 and nothing else for building.. Please make this change at once.

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 38 Next › Last »