Help : Pale Moon28.5.2 on LM18.3

[gene1]

Hi,
I am using LinuxMint 18.3, based on Ununtu 16.04.
I downloaded Pale Moon 28.5.2 from StevenPusser website.
Version is for xUbuntu 16.04

I have removed functioning Pale Moon25.x I''m now down to Firefox.
I try to install Pale Moon 28.5.2 via Package Installer.
I get the following error...

Error: Dependency is not satisfiable: libc6 (>=2.27)

'Install Package' button is greyed out.

I go to pkgs.org to get this file for Ubuntu 16.04.
Ubuntu 16.04 only has libc6 to version 2.23.

Can I install PaleMoon 28.5.2 onto LM18.3, based on Ubuntu 16.04?
If so, has someone done this, and how.
I don''t want, try this... try this.... responses.
Frightening detail please. No response is also information.

I don't have time to play with this. It should just work.
It used to be so straightforward with the pminstaller.

If this is a known issue, can we have a list of Minimum System Requirements for PM28.5.2.

thanks g

[Isengrim]

PM 28.x definitely worked on my Mint 18.3 system before I upgraded to 19.1. When you downloaded from Steven Pusser's site, did you install the binaries directly or did you install from the PPA? Installing from the PPA should have taken care of any dependencies you needed.

[gene1]

Thanks Isengrim,

Used the PPA method from StevenPusser Webpages as advised.
Had to restart laptop for Pale Moon to be listed in Applications menu.
I realised that I had to read, re-read, re-read and re-read the Pusser instructions page.
I glossed over those instructions because it appeared like a block of mostly continuous instructions, and there was a ton of redundancy.
Lists should be presented as such - bullet points or numbered, no unnecessary duplication, and/or indented list items.
That's why I paid no attention to THAT web page.

For example:

For xUbuntu 19.04 run the following:

You can add the repository key to apt. Keep in mind that the owner of the key may distribute updates, packages and repositories that your system will trust (more information). To add the key, run:

For xUbuntu 18.10 run the following:

You can add the repository key to apt. Keep in mind that the owner of the key may distribute updates, packages and repositories that your system will trust (more information). To add the key, run:

For xUbuntu 18.04 run the following:

You can add the repository key to apt. Keep in mind that the owner of the key may distribute updates, packages and repositories that your system will trust (more information). To add the key, run:

For xUbuntu 16.04 run the following:

You can add the repository key to apt. Keep in mind that the owner of the key may distribute updates, packages and repositories that your system will trust (more information). To add the key, run:

Just sayin'.

thanks, g

[Dustie_Rose]

Hello "gene1,"

I read the issues you were having on Linux Mint. "I am using LinuxMint 18.3, based on Ununtu 16.04."
I currently use LM 19.1 on several PCs, I figured out what worked for me at least. The PPA method only worked on some computers, with difficulty on LM 19.0. forward.
The easiest method I found is the Debian binaries from Steve Pusser's downloads page, also should work on most Ubuntu distros, that still have Debian based packages, (deritives). For LM, I use the Debian 8.0 repak, as it is the stable version, since Mint uses stable kernels and software in repositories, not always the most recent version.
Download, then open containing folder, right click on it, the Deb package installer does the rest. Then it is automatically updated with system updates, and listed in software sources. I believe they want users to use apps thru the repositories which are more secure than apps outside of it, especially for beginners. Hope this helps.
Dustie_Rose

[Dustie_Rose]

I forgot to mention, i usually have issues with Ubuntu's instructions, on most their stuff, too complicated. Not on Mint.

[Isengrim]

Off-topic:

I currently use LM 19.1 on several PCs, I figured out what worked for me at least. The PPA method only worked on some computers, with difficulty on LM 19.0. forward.

I'm curious, what's difficult about it in 19? I had no problem re-adding the PPA when I upgraded to 19 just a few weeks ago. The only difference is the version of Ubuntu that the PPA targets - you have to use the 18.04 version rather than the 16.04 version, but everything else is the same as in Mint 18.

[Flawless]

The instructions works like a charm if you replace
ln -s with ln -vs.

[stevenpusser]

The OpenSUSE Build Service automatically generates those instructions. They do need to be carefully looked at.

You seem to have accidentally downloaded a newer Ubuntu's deb file instead of the correct 16.0.4 version. Please carefully try again and let me know if you get the same error.

[Dustie_Rose]

post by Isengrim » 2019-06-20, 11:41

I'm curious, what's difficult about it in 19?
Isengrim, I am not really sure which Mint version it was, between 18-19, when we were not able to use the PM downloader anymore, and I think it was 18.3 when the Mint team were doing major changes like the upgrades downloadable directly instead of burn/reinstalling.
I have never had issues with PPAs but somewhere in there, probably due to the instructions not being straight forward. Ubuntu PPAs have always been easy by command in terminal. The Deb install version works everytime because it installs the dependencies along with it, adds to repository list, etc. Don't quote me on exact versions as I have used so many distros over the last couple years on several computers. Thanks for asking.
To all the hard working developers, designers, moderators, Cudos!
Dustie

[stevenpusser]

If someone wants to set up a separate, actual Launchpad PPA for Pale Moon Ubuntu packages, I certainly have no objections. Then I'd only have to do the Debian packages on the OBS.

[New Tobin Paradigm]

Excuse me, but I must interject. If someone else does this they need to be approved by Moonchild with input from Travis and maybe my self if Travis is busy. So don't just.. do it.

[stevenpusser]

Sorry I left that out, but of course they need approval. If they just reuse the debianized source from the OBS repo, I can't forsee any problems getting that, though.

[New Tobin Paradigm]

Well I do from past experence.