Ubuntu 14.04, 16.04, 16.10, 17.04, Debian 7, 8, 9 Pale Moon repositories

[balloon]

My PC got a package update, but it has not been improved yet.
Some desktop icons are still lost.

Please "[Desktop Entry]" needs to be moved to the first line:

Code: Select all

[Desktop Entry]
Actions=NewWindow;NewPrivateWindow;
Categories=Network;WebBrowser;
Comment[en_US]=Browse the World Wide Web
Comment=Browse the World Wide Web
Exec=palemoon %u
:


[stevepusser]

OK, does the -5 update the problem?

[stevepusser]

OK, does the -5 update the problem?

Hmmm...I see Sparky Linux, which is based on Debian testing, just added what appears to be another homebuilt-from-source version of 27.0.1. I can't find the source files they used when snooping around their repository, and it doesn't install the debian/changelog file like a proper .deb package, either, so I can't really be sure.

[stevepusser]

OK, does the -5 update the problem?

I mean "fix the problem"--can't edit the post for some reason.

Hmmm...I see Sparky Linux, which is based on Debian testing, just added what appears to be another homebuilt-from-source version of 27.0.1. I can't find the source files they used when snooping around their repository, and it doesn't install the debian/changelog file like a proper .deb package, either, so I can't really be sure.

[balloon]

OK, does the -5 update the problem?

Hmmm...I see Sparky Linux, which is based on Debian testing, just added what appears to be another homebuilt-from-source version of 27.0.1. I can't find the source files they used when snooping around their repository, and it doesn't install the debian/changelog file like a proper .deb package, either, so I can't really be sure.

I also use and support Sparky. I will confirm to the developer about it.

[balloon]

Regarding the Sparky package, I gave this question to the developer pavroo and got such a response:

I just debianized binary packages of palemoon so there are debs only in repos now. I am really busy in this moment (new iso) so after finishing them I try to build the palemoon in proper way, means with full source code packs as well.

SparkyLinux will release 4.5 in a few days, he is working on it now.

[stevepusser]

Regarding the Sparky package, I gave this question to the developer pavroo and got such a response:

I just debianized binary packages of palemoon so there are debs only in repos now. I am really busy in this moment (new iso) so after finishing them I try to build the palemoon in proper way, means with full source code packs as well.

SparkyLinux will release 4.5 in a few days, he is working on it now.

Thanks for the information--we could recommend his packages for Debian Stretch users. I'm still trying to get it to build from source on the similar Ubuntu 16.10 platform; Trava tells me it's due to the newer binutils 2.26 there and suggested some workarounds. Debian testing currently has 2.27.51.

[stevepusser]

27.0.2 is now in the repository. I tested the gcc-5 build from the separate Ubuntu 16.10 OBS repository, and it seems their gcc-5.4 has fixed some issues that occur with a gcc-5.2 build on Centos 7, at least in limited testing. Youtube and Vimeo also worked in the test with the gstreamer 1.0 good and bad plugin packages plus gstreamer1.0-libav.

Debian testing is currently using gcc-6 as the default gcc, so Sparky Linux may need to add some tweaks for PM to build correctly, as in this: https://github.com/AOSC-Dev/aosc-os-abb ... ld/prepare

[trava90]

Debian testing is currently using gcc-6 as the default gcc, so Sparky Linux may need to add some tweaks for PM to build correctly, as in this: https://github.com/AOSC-Dev/aosc-os-abb ... ld/prepare

The build system already detects if GCC 6 is being used and applies required tweaks need for the build process to complete. Note that it is not recommended to use GCC 6 and your mileage may vary on stability of the resulting binary.

[stevepusser]

Debian testing is currently using gcc-6 as the default gcc, so Sparky Linux may need to add some tweaks for PM to build correctly, as in this: https://github.com/AOSC-Dev/aosc-os-abb ... ld/prepare

The build system already detects if GCC 6 is being used and applies required tweaks need for the build process to complete. Note that it is not recommended to use GCC 6 and your mileage may vary on stability of the resulting binary.

Thanks for the info. It's possible on Stretch to tell it to use gcc-5 instead, since that seems to be working on Ubuntu 16.10.

Since the same source packages are building correctly on 16.10, I added the repository to the others instead of having a separate one, which I'll soon delete.

I also searched around the OBS for other palemoon packages; this one for 26.5.0 on openSUSE was successful.

https://build.opensuse.org/package/show ... p/palemoon

since I know nothing about rpm packaging nor run that type of distro, I don't know whether these source files can be used for other rpm type distros offered by the OBS, such as Centos 5, 6, 7 or Redhat.

[stevepusser]

Loading 27.0.3 source files into the OBS now. This will take down the repository for an hour or so, depending on how busy the OBS is.

[balloon]

I had encountered a problem of Pale Moon crashing since PM 27.0.0:
viewtopic.php?t=14073

However, as a result of long use, I noticed that the crash was limited to Ubuntu and not encountered in Debian.
I tried to switch Linux Mint 18.1's Pale Moon to the official pminstaller. As a result, no crash occurred.

Therefore crash reported in PM 27 may have occurred when using package in Ubuntu.

[stevepusser]

Packages updated today to restore the dev tools.

[gracious1]

For the life of me, I am not able to update Pale Moon using apt on Ubuntu 14.04. There seems to be something wrong with the repository. Or possibly I am an idiot.

Whenever I run..

Code: Select all

sudo apt-get update

I get this error:

Code: Select all

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://download.opensuse.org  Release: The following signatures c[code][/code]ouldn't be verified because the public key is not available: NO_PUBKEY 0FAD31CA8719FCE4

W: Failed to fetch http://download.opensuse.org/repositories/home:/stevenpusser/xUbuntu_14.04/Release 

W: Some index files failed to download. They have been ignored, or old ones used instead.


And so when I run...

Code: Select all

sudo apt-get install palemoon

All I get is this:

Code: Select all

Reading package lists... Done
Building dependency tree       
Reading state information... Done
palemoon is already the newest version.


I have followed directions on the repo page (https://software.opensuse.org/download. ... e=palemoon) for adding the repository and the key, but to no avail. I use apt all the time and have never had this kind of problem with adding repositories, upgrading, etc. Please help!

G.

P.S. Using Ubuntu 14.04 LTS 64-bit on an Acer Aspire laptop.

[stevepusser]

Is the repository still having problems? I think the server may have been having some trouble that day.

[pale_moon_user]

Is the repository still having problems? I think the server may have been having some trouble that day.

I suspect so, yes. I have been using the 14.04 repository and gotten at least 3 updates through it in that time. I have not yet seen any updates since version 26.4.1, however.

[stevepusser]

I think that was about the time I had to restore the repo and ended up with a new signing key, so you may have to install that one. A workaround is just to directly download the appropriate deb package from the bottom of that instruction page and install it

[pale_moon_user]

I think that was about the time I had to restore the repo and ended up with a new signing key, so you may have to install that one. A workaround is just to directly download the appropriate deb package from the bottom of that instruction page and install it

I removed the Opensuse repository and the Authentication key, then copied and pasted the commands from https://software.opensuse.org/download.html?project=home%3Astevenpusser&package=palemoon for Ubuntu 14.04 to add both the repository and the key back. Unfortunately, I got this error.

Code: Select all

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://download.opensuse.org  Release: The following signatures c[code][/code]ouldn't be verified because the public key is not available: NO_PUBKEY 0FAD31CA8719FCE4

W: Failed to fetch http://download.opensuse.org/repositories/home:/stevenpusser/xUbuntu_14.04/Release 

W: Some index files failed to download. They have been ignored, or old ones used instead.

Is there an additional step I should take?

I see the binary packages at the bottom of the page, which you've suggested downloading and installing as a workaround. If I do that, will the installation begin to receive regular updates going forward? Or would it be temporary?

[balloon]

When PM 26.4 was released, software.opensuse.org server was having problems and updated.
At that time the repository key has been updated.

If Release.key file remains, The registration of the repository key does not work well. (file name will be changed)
Remove Release.key and try again:

Code: Select all

rm Release.key
wget http://download.opensuse.org/repositories/home:stevenpusser/xUbuntu_14.04/Release.key
sudo apt-key add - < Release.key
sudo apt-get update
sudo apt-get upgrade

[Moonchild]

Of note, there have been several people (see posts on the forum and some issues on GitHub) who have complained that these builds are crash-prone, while the official binaries release on linux.palemoon.org are not.

This should be solved, Steve. Please work with Travis to improve stability of your builds. Enforce a specific version of your toolchain if you have to.