Package Details: palemoon 1:33.0.2-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: GPL, MPL, LGPL
Submitter: artiom
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 141
Popularity: 0.037545
First Submitted: 2014-06-05 10:54 (UTC)
Last Updated: 2024-04-01 23:03 (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

1 2 3 4 5 6 .. 37 Next › Last »

WorMzy commented on 2024-04-06 11:42 (UTC)

@saburouta: I emailed Moonchild directly (using the email associated with the regular signing key), my account on the forums has long since been purged for inactivity. If you check the new key, you'll see it was signed by the regular signing key on April 1st, shortly before I pushed the update to this package.

saburouta commented on 2024-04-06 03:34 (UTC)

@WorMzy Yes, that is what I was responding to. Where did this communication take place? Was this by email? Is this on the palemoon forums? I just found older threads related to similar but distinct situations.

WorMzy commented on 2024-04-04 07:23 (UTC)

@saburouta: see that last comment before your own.

saburouta commented on 2024-04-04 00:56 (UTC)

That does not seem to be Moonchild's key. Where is it confirmed?

After checking the PM forums, it seems his key is still '3DAD 8CD1 0719 7488 D2A2 A0BD 4048 1E7B 8FCF 9CEC'. Which is not the one you provided.

WorMzy commented on 2024-04-01 23:07 (UTC)

Sorry for the delay. Moonchild has confirmed the key is valid, and has signed the new key with the release key, which is good enough for me. Apparently this key wasn't meant to be used for signing the release commit, so the usual key will probably be used next time.

WorMzy commented on 2024-03-30 17:49 (UTC)

Note that a new key has been used to sign the commit for v33.0.2: B615CD133D438D85, this hasn't been documented anywhere (AFAICS) on the official palemoon website or forums, and the commits look suspicious in the commit listings on the repo: https://repo.palemoon.org/MoonchildProductions/Pale-Moon/commits/branch/release

I'm uncomfortable updating this package until I've had some sort of clarification that this new key is legit, so I've reached out to the main developer of Palemoon for clarification. Note that the official binaries are still signed by 40481E7B8FCF9CEC, so I'm relatively confident that the new key is fine and just hasn't been announced.

micwoj92 commented on 2024-03-15 02:29 (UTC)

@nokangaroo Your information is out of date.

python2 will not fail to build.

python2-setuptools; python2-dbus are not needed build dependencies, everything works without this notify.

You no longer need to patch this as was fixed upstream. https://repo.palemoon.org/MoonchildProductions/UXP/commit/45b9cfbe932563d083637bd7a94fdfba8dd44955

nokangaroo commented on 2024-03-14 18:18 (UTC) (edited on 2024-03-14 18:19 (UTC) by nokangaroo)

The following worked for me:

Build dependencies (all in the AUR): python2 (disable check, or it will fail to build); python2-setuptools; python2-dbus (just for notification that the build finished; can probably be patched away)

According to forum.palemoon.org, the python2 dependency cannot be gotten rid of. And you need to patch Pale-Moon/platform/media/ffvpx/libavcodec/x86/mathops.h (using binutils-2.41.patch, supplied with ffmpeg4.4).

cd Pale-Moon/platform/media/ffvpx/libavcodec; patch -Np2 < /path/to/binutils-2.41.patch

1 2 3 4 5 6 .. 37 Next › Last »