Package Details: palemoon 1:33.7.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.006846
First Submitted: 2014-06-05 10:54 (UTC)
Last Updated: 2025-04-08 10:24 (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 2 3 4 5 6 7 8 .. 39 Next › Last »

micwoj92 commented on 2024-05-12 01:41 (UTC)

This will not be needed in next release since UXP team followed Mozilla's suit(e) and now the autoconf2.13 is vendored in the source tree of the engine.

https://repo.palemoon.org/MoonchildProductions/UXP/issues/2512

WorMzy commented on 2024-05-11 23:49 (UTC)

Thanks for the heads up, switchnode. Added you as a contributor and pushed an PKGBUILD update. Sorry for the slow response, it's been a rough week, just catching up.

switchnode commented on 2024-05-09 16:33 (UTC)

Presently fails to configure/build due to certain warnings becoming errors as of GCC 14, since autoconf 2.13 (pinned) and cairo 1.10.28 (included) do not account for these changes.

I was able to build successfully by adding export CFLAGS="${CFLAGS} -Wno-implicit-int -Wno-incompatible-pointer-types -Wno-int-conversion" to the PKGBUILD's build().

saburouta commented on 2024-04-26 17:47 (UTC)

Happily, all the key-signing business seems to be resolved now, with "33.1.0"!

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.

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 39 Next › Last »