Pale Moon x86-64 SSE2/AVX2

[Moonchild]

I apologise for the delay getting the automatic updates to production.

Just to confirm: The updates haven't been rolled out yet, right?
I'm getting a blank software update window.

It should be rolled out at this time.

[rainyd]

It should be rolled out at this time.

I can confirm that I was able to update AVX2 version to most recent one.

[back2themoon]

I am already updated (SSE2) but this still appears on a manual update check:

Clipboard Image.png

[flamelord]

Just updated
Everything's working fine

I am already updated (SSE2) but this still appears on a manual update check:

Clipboard Image.png

Here's mine(also SSE2)

Capture.PNG

[ron_1]

I'm just reporting this so it's known; I know there have been issues about it in the past. Starting today I am again getting an expired message when running the gpg verification.

Anyway I consider this a minor thing, I want to stress that I appreciate Nuck-TH's builds.

[Moonchild]

I am already updated (SSE2) but this still appears on a manual update check:

Clipboard Image.png

That's pretty strange. you should examine the toolkit error console and see if there are any specific errors there when you check for updates manually. Something blank like that tends to mean there's a localization issue, but it could potentially be something else.

[flamelord]

When can we expect the new SSE2 build?

[Moonchild]

When can we expect the new SSE2 build?

"When it's done", I'm sure.
Although right now I recommend Nuck skips 34.2.1 and goes straight to 34.2.2 what's being prepped right now.

[UCyborg]

Instead of waiting, I went and ran the build myself, buuut, the version still reads 34.2.0 like from the last time, though it recompiled a bunch of files and took half the time it normally does. Build system bug? Better to delete objdir and get it to recompile everything?

Or what do self-builders do?

FWIW, NSS library version reads like written in the changelog.

[Moonchild]

Make sure you've also checked out the correct version of the front-end repo, not just the platform.
If it doesn't look right though, even after that, then yes do a clobber build.

[UCyborg]

I ran Pull... and then Submodule Update... through TortoiseGit, had release branch checked out (or switched) from before. I clearly remember seeing a target.txt file in the repo reading 34.2.2. Both PM and platform repo appeared to be on correct respective commits.

Curious if I now have 34.2.2 that just pretends to be 34.2.0 or if there are other bits missing. Probably no one really knows?

[Moonchild]

if in doubt do a clobber build.

[athenian200]

Instead of waiting, I went and ran the build myself, buuut, the version still reads 34.2.0 like from the last time, though it recompiled a bunch of files and took half the time it normally does. Build system bug? Better to delete objdir and get it to recompile everything?

Or what do self-builders do?

FWIW, NSS library version reads like written in the changelog.

My recommended strategy is something like this, assuming you're like me and don't pick a custom name for your objdir:

1.

Code: Select all

cd Pale-Moon

(go to the directory you cloned Pale Moon into).
2.

Code: Select all

rm -rf obj* 

(I don't trust ./mach clobber, it's burned me before)
3.

Code: Select all

rm platform/old-configure && rm platform/js/src/old-configure 

(Make 100% sure old-configure is regenerated from the .in file, shouldn't be needed but again, I've been burned before)
4.

Code: Select all

git pull

(Make sure you have the latest changes)
5.

Code: Select all

git checkout 34.2.2_Release

(Ensures the version pointer is setup correctly, otherwise you'll either get an outdated one or one indicating an alpha)
6.

Code: Select all

git submodule update

(Ensures the platform is at the right commit for that release of Pale Moon, without you having to dig around in platform manually)
7.

Code: Select all

./mach build

8.

Code: Select all

./mach run

[Nuck-TH]

34.2.2 is finally up, with again extended old signing key

Public key:

-----BEGIN PGP PUBLIC KEY BLOCK-----

mQGNBGI0so0BDADpA18guP7Dj0rAwwQ/UY6pDC8gEIr38fg1MsRz1ltmvxULxwNw
XnPlEBe+rGtLrBWHlKnoxWwnLpNYKFx8C25PsPUqPBR3pHe3rvun795+WGJAhb1e
m93HOgSqgYt8mnQz+vA1KD8etZ07xO7/uQRsHLmEV3g6udaQpKH21PRJ2Ds7HtHV
kQW9bMAAmTsQlJswnug+aFxZzZarXp+Zh4Pm5U3doKL+A3H50f/8NBp5rIa+ionS
kGmO0JKKzuKNZjqrFXopgy1+bkL3XaglxmsbGBR56DdwX5nsAB1plz29WHGFTi2Y
ySCeEeBsJdPplXwYfFspFHgwxS69hXBWvtJPOB2wbMm/EryKXvaQEc6Cyn81TBCp
oFddlRhIkqOHw9cP2XHDTXLE8LAOIEDbah7syWWnozMUBIZwxdkxbHkQoUluI8eB
FDQthT8n9ts5cnMZuxwFdtPAQ9dF6nv4plNBdZNbOyINuSFHqXI4mVt0JAnmZeR9
S9o6Cbto7v2MajcAEQEAAbQfTnVjay1USCA8bnVjazY3ZDU2NGFAZ21haWwuY29t
PokB1AQTAQgAPgIbAwULCQgHAgYVCgkICwIEFgIDAQIeAQIXgBYhBFBhzFHJQwYF
DPof7kj60pB9hO3rBQJp+J0gBQkJpR4TAAoJEEj60pB9hO3rLLwL/2f6NW+P4yIa
3LYEr6KImLqGKx05dN+y9pIksrqeGldm40pteOTlIBQ0Gf2t+SMm6fYvBQ3PSXPB
TI2MOLvE2itTEB35mmoELOgjbF2R+Oi7khFlSx+fBt1tw9I7NJv8psDN/Pk8Q3Sv
CAgIklmoHIHMKNqlYjLVRSYVlphnKE+chhaflXEqOR5bajc9l87EKFmGHuYdm4An
PTy65jdrC2eyRFPVhZyBIed20mIBMHLfRL0FNP4EbQwmP39HtWzSgWsJayvghnYp
iV1QS8LxnlsKWy5OuKt+XgWT6AXqTAUHT7Q1iL/Mi1NCzrlwCw2TzjoAtjiLpK59
cvlYGtQsLEWuQ+OrbWgRBnx0G/bAN0vcrB0AQta51X5DGN4NWOD/SCQpDVAPSWKo
rsusBPFc+LxPgrfLpF7kxMj0QaT0oDVTOIZdXWOL511Ve6x9gWjKW3qtuXTpp7OB
doXBZU+h6aUd4kMZSjZV2Oewv9ztHVChheIl9O66OPYB+hO8Evee77kBjQRiNLKN
AQwAqCkvECGYQ4Iv//VO1yKNkNFBYQHsqXwy25prV9VPdm+H83BfQSe6QmugXY7X
L/3Uzok0aRE7tXoo0nOj5ev6OzgjQUt4B2XLSyBNmP8eusGQiZkzL71OuZbGN3Pu
vbtZgPtKKtXqN/+q84uiH8xxbVaeDV3WY7jSovbqmpBwXIAeRqeq4IRjPq0bUM6V
7g/PKabuAdEwe+YY4nCqUnOKe/fo8gtoOCVytMW46JCuGeZiSgDZywjqdiO8t9wD
COlAKu4bd2ykVvQU+pJsh47jHK5xp2PsD8r0sZke57VtTt4hXTZrkJqKyGajV8lk
TZ5vhGSwyIyRySFBiGId+9QuPf/umfU4peJlSFTl9dVjOuly0C/6gPD1nr2PMG1+
YNXwVRfTnRdV0t0MCJHAhN8M9T29NmGKTdzHMsRMhPFcOoiQt2lHYVe3z+xcvISx
jsCZtfvewXFjHs7Fm9xxCWwkiyUAuKbHoJzn4FgFH6AuhLuNCIKIc9sT5EsYDrrh
N0ADABEBAAGJAbwEGAEIACYCGwwWIQRQYcxRyUMGBQz6H+5I+tKQfYTt6wUCafid
TwUJCaUeQgAKCRBI+tKQfYTt64koC/9N02hSo9rfUmaEL90dQxzxNlZKxCuXi8FV
wHlYwE5qUT3N5emw6IrWNbk5CW0SQtnEyJN5cWGxbe0+Efo5OY5arDsjgTFssEzA
wQWPSQS4YSMWW/IwNjetjdtX6sh7H6hPba6ewk43QNITZXj580o/8UY8c01ZtErj
Zh8Rqvsj09Kvjm9p/EJeOuIHFpKrzpKbG9TfTx7JxE/Cw0HAiuEjtDAasHVSaCgz
aXKHZPVl6zbMjNZtHe5/JKN5tqG0mkTjpREJcMZ/q8AuIZGU0243Y9oaHD/HS6rv
FHIbtViipaE10qO1Rj/satJLLCNguTEW9b63yxztjaRElZWvtIkLeOGDPxUFHly9
XWH9WvVaZhT4e6nbHM2a0y/QCZCxl4MJq1kVlz8LBsVKRvZ9lK0IkakwyR8ana8G
PiXRkfnvUhznNF0D6rXCFl35ZmcxQRHNXMB3BHp+fQeVFdaBp+KWSiOCCRZceKp9
cM+BS0jWNNz8Hf2GP5bPMCh+rTD8CQU=
=VI8b
-----END PGP PUBLIC KEY BLOCK-----

If someone can come up with instructions how to properly generate and use new key and chain sign it with old one(or whatever it is called)[though i'm not sure that it is good idea, as previous key wasn't stored in encrypted storage], or knows where to read that - i will make new one. For now you'll have to put up with old...

[Moonchild]

The automatic updates server is now updated with these builds.

As for PGP and "chain-signing", I can just give you instructions for Kleopatra:

1. In Kleopatra, go to File -> New OpenPGP Key Pair
2. Fill in Name and e-mail address, and check "protect with a passphrase".
3. Click "Advanced settings" and choose your algo (recommended to use ECDSA and using ed25519/cv25519, but you can also use RSA with 3072bits or larger)
4. Make sure you check "signing" under certificate usage, and set an expiry date you want (or no expiry if you're going to be super diligent about safe storage).
5. Click OK, the OK again, and enter your passphrase (twice). After this, you will have a new key pair that is certified.
6. To "chain sign" (sign the new key with your old one), right-click on the new key pair entry in Kleopatra, select "Certify..."
7. In the dialog that opens, at "Certify with:" select the old key you want to sign with. Under "Advanced" you can double-check if it is set to "certify for everyone to see (exportable)" and "publish on key server". Do not check "certify as trusted invoker" or setting an expiration date.
8. If it asks you an extra confirmation because "you haven't certified all valid user IDs", just confirm with "export" - confirm again at the warning that once published it's almost impossible to revoke your signature (it's what you want!).
9. The signing process and publishing on keyserver will now happen. Kleopatra does not give feedback while this happens so just be patient. it can take some time. When done, it will tell you with a small dialog.

That's all there is to it.

[UCyborg]

2.

Code: Select all

rm -rf obj* 

(I don't trust ./mach clobber, it's burned me before)

Are you any closer to the build system you trust with Python 3? Probably unrelated, but still.

clobber command seemed fine when nothing like .mozconfig has changed, at least judging by the content of objdir folder afterwards.

Though the easiest method I find to start over is just purge everything with TortoiseGit's Cleanup command.