Arch Linux User Repository

diff --git a/PKGBUILD b/PKGBUILD
index 39a928a..05d50a2 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -17,7 +17,7 @@ url="https://www.palemoon.org/"
 license=('MPL-2.0')
 depends=('gtk2' 'dbus-glib' 'desktop-file-utils' 'libxt' 'mime-types' 'alsa-lib'
          'startup-notification')
-makedepends=('python2' 'autoconf2.13' 'unzip' 'zip' 'yasm'
+makedepends=('python2' 'unzip' 'zip' 'yasm'
              'libpulse' 'git')
 optdepends=('libpulse: PulseAudio audio driver'
             'ffmpeg: various video and audio support')
@@ -38,6 +38,10 @@ prepare() {
   git submodule init
   git config submodule.platform.url "${srcdir}/UXP"
   git -c protocol.file.allow=always submodule update
+  cd platform
+  git cherry-pick -n 6cbb2c372b208902e765aa577539c018d76ba1b8
+  git cherry-pick -n e484c9d31136fc7e197bb0d686463a6555897784
+  git cherry-pick -n acb34c35dbc3452101318cbb3cccf50b1a1c90b2
 }

 build() {
@@ -49,9 +53,6 @@ build() {
   export MOZCONFIG="${srcdir}/mozconfig"
   export CPPFLAGS="${CPPFLAGS} -O2 -Wno-format-overflow"

-  # Fix build failures with GCC>=14
-  export CFLAGS="${CFLAGS} -Wno-implicit-int -Wno-incompatible-pointer-types -Wno-int-conversion"
-
   ./mach build
 }

To drop autoconf2.13, alternatively just wait next month until 33.2.0, I cherry picked these patches for gtk3 version.

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

@haawda: I don't think plugin-container should be called by itself. It's called by the browser as required which presumably handles shared library access.

See https://support.mozilla.org/en-US/kb/what-is-plugin-container for Firefox's description of plugin-container (I couldn't find an equivalent page on the palemoon site, but I doubt the functionality is that different)

@micwoj92: Feel free to do so locally, but I suspect duplicate packages that just uses a different source to the original would be removed from the AUR by TUs. Feel free to ask on the mailing list (aur-general) and/or IRC (#archlinux-aur on freenode) if you want to confirm.

Alternatively, maybe use palemoon-bin?

That makes sense. I hope I am not the only one frequently deleting build directory of my aur helper. Do you think it is worth to make package that would be same just download the tarballs?

It is not an issue with palemoon itself, but running the plugin-container results in

# /usr/lib/palemoon/plugin-container
/usr/lib/palemoon/plugin-container: error while loading shared libraries: libxul.so: cannot open shared object file: No such file or directory

But I am not sure if there are circumstances where running this binary from command line is needed.

@haawda: what is the actual problem? libxul.so is loaded for me:

$ strace palemoon |& grep libxul 
access("/usr/lib/palemoon/libxul.so", R_OK) = 0
openat(AT_FDCWD, "/usr/lib/palemoon/libxul.so", O_RDONLY) = 4
openat(AT_FDCWD, "/usr/lib/palemoon/libxul.so", O_RDONLY|O_CLOEXEC) = 4

@micwoj92: Upstream release new versions semi-regularly (sometimes multiple releases per month). Although the initial clone may be substantial, every update after that will only include the upstream changes since the last time you pulled the repos, drastically reducing the amount of bandwidth consumed in the long run.

Is there a reason why this does not download tarballs? This would greatly reduce download from 730+ to only about 200 MB.

There seem to be some issues with libraries not found. But they are there.

ldd /usr/lib/palemoon/plugin-container

        libxul.so => not found

ldd /usr/lib/palemoon/libxul.so

        libmozsqlite3.so => not found
        liblgpllibs.so => not found

ldd /usr/lib/palemoon/libsoftokn3.so

        libmozsqlite3.so => not found

ldd /usr/lib/palemoon/libmozavcodec.so

        libmozavutil.so => not found

ldd /usr/lib/palemoon/browser/components/libbrowsercomps.so

        libxul.so => not found

This output comes from the checkrebuild script included in the rebuild-detector package run wit -v option, but plain ldd tells the same.

As always, you need to import GPG keys manually (and ideally verify them out-of-band). Make sure gpg is set up with a keyserver, then run this:

$ gpg --recv-key 40481E7B8FCF9CEC

So just now updating four palemoons on four systems and after 2 I get:

Pale-Moon git repo ... FAILED (unknown public key 40481E7B8FCF9CEC)Pale-Moon git repo ... FAILED (unknown public key 40481E7B8FCF9CEC)

:(

Further note: Upstream have renamed the repositories again. If you previously modified your git clone configs to point to https://repo.palemoon.org/MCP/... you will need to edit them again to point to https://repo.palemoon.org/MoonchildProductions/...

Note the repositories have moved to https://repo.palemoon.org/MoonchildProductions/Pale-Moon and https://repo.palemoon.org/MoonchildProductions/UXP, if you previously cloned the repos, you can update the URL in the config files (i.e. $SRCDEST/Pale-Moon/config and $SRCDEST/UXP/config) so you don't need to clone the full repo again.