Arch Linux User Repository

Because upstream take a while to release their 'official' Linux binaries, while the source code is available immediately. If the PKGBUILD is updated before the binaries are available, then people will get 404 errors until upstream pull their finger out. ;)

@micwoj92 the binary has been released literally TODAY! "So long", are you serious? If you cannot wait for a few hours for someone to update the PKGBUILD for you, just simply edit pkgver and checksum locally for Christ's sake!

Why does this package always takes so long to update on aur compared to 'palemoon' ?

@WorMzy yes that's weird. I just checked and both versions work. 'palemoon -h' however shows double-hyphens...

Either should work just as well, however it should be noted that upstream uses single dashes in the official .desktop file (and they get pissy if you deviate even slightly from what they dictate): https://repo.palemoon.org/MoonchildProductions/Pale-Moon/src/branch/master/palemoon/branding/official/palemoon.desktop

Thank you @andym . Fixed.

There are errors in the palemoon.desktop file. In each or the three [Desktop Action ...] sections the Exec= line is missing a "-". For example: Exec=palemoon -private-window should be Exec=palemoon --private-window

Thanks, but it's not that much effort to increment pkgver and run updpkgsums.

Sorry for the delay, I wasn't aware oberon hadn't pushed the update yet.

I edited the PKGBUILD so that it never needs manual a update. i saved you a lifetime of work. https://pastebin.com/raw/ZJ67Bkcq

diff --git a/PKGBUILD b/PKGBUILD
index eb3854c..64d5167 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,7 +4,7 @@
 # Contributor: sumt <sumt at sci dot fi>

 pkgname=palemoon-bin
-pkgver=28.14.2
+pkgver="$(curl -sf 'http://linux.palemoon.org/download/mainline/' | grep 'Latest release:' | grep -o '[0-9]*\.[0-9]*' | sed 'N;s/\n//g')"
 pkgrel=1
 pkgdesc="Open source web browser based on Firefox focusing on efficiency."
 arch=('i686' 'x86_64')
@@ -26,9 +26,9 @@ source_x86_64=("https://linux.palemoon.org/datastore/release/palemoon-$pkgver.li
 source_i686=("https://linux.palemoon.org/datastore/release/palemoon-$pkgver.linux-i686.tar.xz"{,.sig})
 # link to latest tarball: http://linux.palemoon.org/download/mainline/
 sha256sums=('c6cae1c0de6b59da1d846cb2092ca2725ba2baa4d554223f747a4a71ee63002e')
-sha256sums_i686=('6f63a92f439b68f8d7751d1b2f49e00432c58e35f965fa0ba2e8b479d0b08bf6'
+sha256sums_i686=($(curl -sf 'http://linux.palemoon.org/download/mainline/' | grep -o "checksum: .\{64\}" | sed -n "s/checksum: // ; 2p")
                  'SKIP')
-sha256sums_x86_64=('6fdc4a02da13d58368fc363058dce6111c029b2f153055a0fb1188d9ed5fef4c'
+sha256sums_x86_64=($(curl -sf 'http://linux.palemoon.org/download/mainline/' | grep -o "checksum: .\{64\}" | sed -n "s/checksum: // ; 1p")
                    'SKIP')

 validpgpkeys=('439F46F42C6AE3D23CF52E70865E6C87C65285EC' # T. Wine

Hi pieraper44, is there any chance that you are using an unsupported AUR helper? Since the required keys were already imported on my machine, I could build the package without the need to import the keys.

$ makepkg -s 
==> Making package: palemoon-bin 28.14.2-1 (Sat 03 Oct 2020 05:14:50 CEST)
[snip]
==> Finished making: palemoon-bin 28.14.2-1 (Sat 03 Oct 2020 05:15:06 CEST)

However, I tested, if the keys are available by hkp://keys.gnupg.net.

$ gpg2 --keyserver hkp://keys.gnupg.net --recv-keys 439F46F42C6AE3D23CF52E70865E6C87C65285EC 
gpg: key 865E6C87C65285EC: "trava90 <travawine@protonmail.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
$ gpg2 --keyserver hkp://keys.gnupg.net --recv-keys 3DAD8CD107197488D2A2A0BD40481E7B8FCF9CEC 
gpg: key 40481E7B8FCF9CEC: "Moonchild (RSA signing key) <moonchild@palemoon.org>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

As you can see, they are available. Then I tested with the shortened fingerprint, if one of the two keys, the one mentioned by the pinned comment, is provided by keyserver.ubuntu.com.

$ gpg --keyserver=keyserver.ubuntu.com --recv-keys 8FCF9CEC 
gpg: key 40481E7B8FCF9CEC: "Moonchild (RSA signing key) <moonchild@palemoon.org>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

It is. So what you call "bs" is an issue on your side.