Package Details: palemoon 1:33.5.0-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.063030
First Submitted: 2014-06-05 10:54 (UTC)
Last Updated: 2024-12-05 10:09 (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 .. 20 21 22 23 24 25 26 27 28 29 30 .. 38 Next › Last »

AndyRTR commented on 2017-08-23 18:25 (UTC)

When building against new toolchain in testing the following fix is required: # fix build with glibc 2.26 sed -i "s:xlocale:locale:" Pale-Moon/intl/icu/source/i18n/digitlst.cpp And please drop the make job limitation in mozconfig. The build can finish much faster without that limit on a recent cpu. And be prepared: https://www.archlinux.org/todo/gcc5-removal/ !

WorMzy commented on 2017-07-14 10:00 (UTC)

Looks like the new default CFLAGS (as of pacman 5.0.2-2) don't work with gcc5. I'm not sure if this should be reported as a bug (to Arch, not Palemoon), or if PKGBUILDs that still use gcc5 should work around the problem. Unfortunately I'm stuck in a datacenter all day today so I can't research/test/get a new PKGBUILD out for a few hours but you should be able to fix the problem in the time being by exporting the old CFLAGS (and probably CXXFLAGS and LDFLAGS for good measure) at the top of the build function in the PKGBUILD. e.g. build() { export CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong" export CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong" export LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro" ...

anton-tsyganenko commented on 2017-07-14 08:47 (UTC)

I'm getting an error when building it: 0:01.54 configure:3304: gcc-5 -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -D_FORTIFY_SOURCE=2 -O2 -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now conftest.c 1>&5 0:01.54 gcc-5: error: unrecognized command line option '-fno-plt' 0:01.54 configure: failed program was: 0:01.54 0:01.54 #line 3299 "configure" 0:01.55 #include "confdefs.h" 0:01.55 0:01.55 main(){return(0);} 0:01.55 configure: error: installation or configuration problem: C compiler cannot create executables. 0:01.55 *** Fix above errors and then restart with\ 0:01.55 "/usr/bin/make -f client.mk build" 0:01.55 make[2]: *** [/tmp/yaourt-tmp-anton/aur-palemoon/src/Pale-Moon/client.mk:363: configure] Error 1 0:01.55 make[1]: *** [/tmp/yaourt-tmp-anton/aur-palemoon/src/Pale-Moon/client.mk:375: /tmp/yaourt-tmp-anton/aur-palemoon/src/pmbuild/Makefile] Error 2 0:01.55 make: *** [client.mk:171: build] Error 2 0:01.55 0 compiler warnings present. ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build palemoon.

WorMzy commented on 2017-06-24 13:31 (UTC)

No, I think you're right and I misinterpreted the announcement. The caveat at the bottom of the original announcement seems to still apply: "this currently has no impact on the Pale Moon browser. It will only become relevant if/when we move our Pale Moon application from our current Mozilla+Goanna 3 platform across to UXP in the future." Still, if you are still willing to be a co-maintainer, I'm happy to add you as one.

wolf commented on 2017-06-24 12:46 (UTC)

I'm not sure where you got the "in the near future" from it (but maybe me reading comprehension sucks), but if nobody else volunteers, I might as well do it since I have no plans to stop using palemoon at the moment. So I would need some AUR package anyway.

WorMzy commented on 2017-06-21 18:33 (UTC)

PSA: Looks like palemoon will be switching to gtk3 in the near future[1]. I have no intention of continuing to maintain this package once that happens. As such, if there is anyone who wants to step up as a co-maintainer, with the intention of taking over as full maintainer when gtk3 becomes default, please let me know in the comments or drop me an email. [1] https://forum.palemoon.org/viewtopic.php?t=15806&p=116121#p116121

bruno commented on 2017-06-20 14:40 (UTC)

sorry, effectively, i'm running out of space on /tmp. it works fine ! sorry and thanks for your quick reply

WorMzy commented on 2017-06-20 11:26 (UTC)

Are you running out of space? Where are you attempting to build?

bruno commented on 2017-06-20 08:50 (UTC)

Hello, I have multples errors : error: unable to write file xulrunner/tools/redit/redit.cpp error: unable to write file ... etc ... ==> ERREUR : Échec lors de la création d’une copie de travail du dépot Pale-Moon git Abandon... ==> ERREUR : Makepkg n'a pas pu construire palemoon. thanks

WorMzy commented on 2017-04-19 10:20 (UTC)

Fair enough. I still wasn't able to reproduce the build failure with the extra packages. It's possible that you have a different version of java than the one I tried building with (openjdk 7), but java doesn't appear to be used during the build process anyway. The only thing that sticks out in a comparison of my logs and yours, is that I get a lot more warnings about there being no preprocessor directives. Have you modified your CPPFLAGS at all?

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