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 .. 12 13 14 15 16 17 18 19 20 21 22 .. 38 Next › Last »

tony.aln commented on 2019-07-04 20:09 (UTC)

huh, I built them without any patches or weird flags, and I read that thread a while back too. What I did was remove ggc8 from the PKGBUILD and the mozconfig and voilà. That gentleman on the thread is the one which is building pale moon with gcc9 right now for fedora which I mentioned before. I'm gonna try on some boxes without -flto to see if I can succeed building it.

WorMzy commented on 2019-07-04 11:25 (UTC)

I got a build failure with gcc9 (the same build failure that upstream was aware of in March) which is why I've switched to gcc8 in the mozconfig.

I'd rather not include patches to make the package build with gcc9, as upstream get really arsey about that sort of thing, and it's not worth dealing with their antics. The best thing you can do is make noise on their bug tracker about it (but don't expect anything to change).

tony.aln commented on 2019-07-04 09:38 (UTC)

For the record, gcc9 is building Pale Moon nicely since version 28.5, although apparently is not endorsed (or supported) by the devs yet. PM is built with gcc9 for fedora (copr repo) with an official third-party build endorsed by Moonchild Productions. The patch to build it with gcc8 seems unnecessary, I wonder what happened... I have to warn that building PM with gcc9 uses a tad bit of RAM more... Well, I built with -flto enabled so that takes more RAM, disk space and additional time to build. At linking stages, it will place files in /tmp, which in arch is tmpfs. So if you don't have much ram to spare, I think it's best not to compile with flto because of the added ram usage. Maybe you could mount tmpfs in disk and slash part of ram usage. Make sure to have at least 12G of RAM on the build PC so it's not needed to change /tmp to disk.

WorMzy commented on 2019-06-05 17:09 (UTC)

Looks like you found the culprit, but if you still get build failures after fixing your space issue, post the new logs.

keepitsimpleengr commented on 2019-06-05 16:18 (UTC) (edited on 2019-06-05 16:30 (UTC) by keepitsimpleengr)

@WorMzy

https://pastebin.com/V9A1xR18

https://pastebin.com/ex9gCdhn

Thanks

DEBUG: | /var/tmp/conftest.wrS_a1.c:8:1: fatal error: error closing /tmp/ccPfgeq6.s: No space left on device <- oops

WorMzy commented on 2019-06-05 15:41 (UTC)

Cannot reproduce. Please post the full build output and also upload /home/ljohnson/AUR/palemoon/src/pmbuild/config.log to a pastebin and link here.

keepitsimpleengr commented on 2019-06-05 14:57 (UTC)

Compile fail... 0:03.86 File "/home/ljohnson/AUR/palemoon/src/UXP/python/mozbuild/mozbuild/virtualenv.py", line 203, in create 0:03.86 'Failed to create virtualenv: %s' % self.virtualenv_root) 0:03.86 Exception: Failed to create virtualenv: /home/ljohnson/AUR/palemoon/src/pmbuild/_virtualenv

WorMzy commented on 2019-03-28 08:48 (UTC) (edited on 2019-03-28 10:50 (UTC) by WorMzy)

Jerome's issue (in the linked, linked thread) was that he needed to rebuild freshplayerplugin-git as it was linked against an old version of ICU. See https://aur.archlinux.org/packages/palemoon/?O=30&PP=10#comment-623566

Rebuild your freshplayer and see if you still get crashes.

jghodd commented on 2019-03-27 22:22 (UTC) (edited on 2019-03-27 23:08 (UTC) by jghodd)

@WorMzy yup. been there. done that.

https://forum.palemoon.org/viewtopic.php?f=37&t=21671&p=164063#p164063

Edit: palemoon is incompatible with freshplayerplugin. remove any incarnation of this package and palemoon runs.

https://forum.palemoon.org/viewtopic.php?t=17638

WorMzy commented on 2019-03-27 19:33 (UTC)

If you suspect a bug in the palemoon code, then your best bet is to seek support from the palemoon devs. Since you can reproduce the crash with the palemoon-bin package, get them a stacktrace from that (they are unlikely to respond well to a crash report from an independent build, even if it is their code that's getting built).

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 .. 38 Next › Last »