I was asked to remove the branded palemoon package until the crashing was solved for Ubuntu 16.04 and 16.10 packages, despite no problems with the other distro versions. I think I have it solved. PM seems to be unstable when compiled with the default gcc 5 or 6 on those, but those Ubuntus still have gcc-4.9, so I forced them to use that. In the meantime, I've replaced it with the unbranded "newmoon" package, which is Pale Moon under a different name and icon. Hopefully I can get the palemoon package back in there.
I also have builds of newmoon-27.2.0~alpha1 in a separate repository, if anyone wants to test/hunt bugs for the upcoming version: https://software.opensuse.org/download. ... ge=newmoon
If anyone can help, I first tried to make a "one debian/rules file to rule them all" with some code I lifted from other packages, but it didn't seem to work. It's supposed to use lsb_release to detect Ubuntu xenial and yakkety build platforms, and then export the gcc-4.9 enviroment if they are detected. The export commands work fine on their own, so it's something in the conditional part.
- Code: Select all
# Build with gcc-4.9 on Stretch, Xenial, Yakkety, and Zesty.
distrelease := $(shell lsb_release -cs)
ifeq (,$(filter $(distrelease),stretch xenial yakkety zesty))
The MX Linux repositories
: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: AzPainter 2.0.4, Pale Moon 27.2.1, Liquorix kernel 4.10-2, mpv 0.24, Kodi 17.1, Ksnip 1.3.1, Mesa 13.0.6