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

ondoho commented on 2017-09-20 17:42 (UTC)

nope, it didn't fix the issue at all. tried running palemoon from the terminal but there was no ouput at all. can anyone at least confirm this? btw, sorry forgot to mention, kernel is 4.9.50-1-lts x86_64, gpu is Intel HD Graphics 530

ondoho commented on 2017-09-18 06:15 (UTC)

after a system update, palemoon started glitching - when i opened another window on top of palemoon, sometimes even only when i switched desktops, palemoon's window would become blank, and palemoon unresponsive until i kill it. something to do with gpu accel no doubt. this went on for a couple of weeks and across at least one kernel upgrade - until i simply re-installed (recompiled) palemoon, now it's fine again. has this happened before? is there any way to deal with that through package management?

WorMzy commented on 2017-08-30 15:08 (UTC)

> enough memory/disk space seem to be available Your output suggests otherwise. You mention disk space, but it looks like you're building in /tmp which, on Arch, is a tmpfs by default. When building on tmpfs, you need to have enough free memory to handle the git repository, the checked out source code, the actual build process (including temporary files and compiler/linker processes), and the packaging. When the build fails, the compiler/linker processes get reaped and the memory they were using gets freed, so checking the free space of /tmp or the memory usage of the system after the build fails is not actually indicitive of the situation during the build. How big is your /tmp? Anything smaller than 5GB is unlikely to result in a successful build.

kzoli429 commented on 2017-08-30 14:27 (UTC)

Although enough memory/disk space seem to be available, building failed with: " ... {standard input}: Assembler messages: 2:14.21 {standard input}: Fatal error: can't close Unified_cpp_js_src4.o: No space left on device 2:14.23 In the directory /tmp/makepkg/palemoon/src/pmbuild/js/src 2:14.23 The following command failed to execute properly: 2:14.23 g++-5 -o Unified_cpp_js_src4.o -c -I../../dist/system_wrappers -include /tmp/makepkg/palemoon/src/Pale-Moon/config/gcc_hidden.h -DFFI_BUILDING -DEXPORT_JS_API -DJS_HAS_CTYPES -DDLL_PREFIX="lib" -DDLL_SUFFIX=".so" -DMOZ_GLUE_IN_PROGRAM -DAB_CD= -DNO_NSPR_10_SUPPORT -I/tmp/makepkg/palemoon/src/Pale-Moon/js/src -I. -Ictypes/libffi/include -I/tmp/makepkg/palemoon/src/Pale-Moon/intl/icu/source/common -I/tmp/makepkg/palemoon/src/Pale-Moon/intl/icu/source/i18n -I../../dist/include -I/tmp/makepkg/palemoon/src/pmbuild/dist/include/nspr -fPIC -D_FORTIFY_SOURCE=2 -O2 -DMOZILLA_CLIENT -include ../../js/src/js-confdefs.h -MD -MP -MF .deps/Unified_cpp_js_src4.o.pp -D_FORTIFY_SOURCE=2 -O2 -Wall -Wsign-compare -Wtype-limits -Wno-invalid-offsetof -Wcast-align -march=native -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -pipe -DNDEBUG -DTRIMMED -g -O2 -msse2 -mfpmath=sse -fomit-frame-pointer /tmp/makepkg/palemoon/src/pmbuild/js/src/Unified_cpp_js_src4.cpp 2:14.23 make[5]: *** [/tmp/makepkg/palemoon/src/Pale-Moon/config/rules.mk:937: Unified_cpp_js_src4.o] Error 1 2:14.24 make[4]: *** [/tmp/makepkg/palemoon/src/Pale-Moon/config/recurse.mk:74: js/src/target] Error 2 2:14.24 make[3]: *** [/tmp/makepkg/palemoon/src/Pale-Moon/config/recurse.mk:37: compile] Error 2 2:14.24 make[2]: *** [/tmp/makepkg/palemoon/src/Pale-Moon/config/rules.mk:541: default] Error 2 2:14.24 make[1]: *** [/tmp/makepkg/palemoon/src/Pale-Moon/client.mk:398: realbuild] Error 2 2:14.24 make: *** [client.mk:171: build] Error 2 2:14.27 262 compiler warnings present. 2:15.36 Failed to parse ccache stats output: cache hit rate 0.00 % ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build palemoon. ==> Restart building palemoon ? [y/N] "

WorMzy commented on 2017-08-23 20:09 (UTC)

Thanks for the heads up. :) The gcc5 drop shouldn't be too much of a problem. The current gcc5 package hasn't been touched in over a year, so there's probably not much risk in users installing it from the ALA once it disappears from the repos. Unfortunately I think it's unlikely that upstream will support/recommend a modern gcc any time soon. It doesn't look like that fix for 2.26 causes any problems for 2.25, so I'll push out a pkgrel bump adding it and the job limit change shortly.

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.

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