Package Details: palemoon 1:33.5.0-1

Git Clone URL: https://aur.archlinux.org/palemoon.git (read-only, click to copy)
Package Base: palemoon
Description: Open source web browser based on Firefox focusing on efficiency.
Upstream URL: https://www.palemoon.org/
Keywords: browser goanna web
Licenses: MPL-2.0
Submitter: artiom
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 141
Popularity: 0.063030
First Submitted: 2014-06-05 10:54 (UTC)
Last Updated: 2024-12-05 10:09 (UTC)

Pinned Comments

WorMzy commented on 2021-03-02 16:19 (UTC) (edited on 2022-08-03 21:12 (UTC) by WorMzy)

The following key is used to sign release commits:

40481E7B8FCF9CEC

Import it into your keyring however you want.

https://wiki.archlinux.org/index.php/GnuPG#Import_a_public_key

Latest Comments

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 38 Next › Last »

WorMzy commented on 2017-03-08 19:43 (UTC)

We have been building with gcc5 since ~April 2015, and I have never experienced instability with the core browser. I also haven't seen any such stability issues reported on the Arch Linux forums. A quick search of the Palemoon forums doesn't yeild any stability reports by Arch users either. I did follow a github topic about gcc5 stability, but that appeared to be caused by binaries built with bad mozconfigs on unstable/testing versions of debian, then run on stable versions of debian/ubuntu. As gcc49 is EOL (as of August last year [1]), insisting that people use it over gcc5 is not a long term solution. As it stands, we currently use gcc5 because when Arch updated to gcc6, Palemoon didn't support it. Arch currently ships a gcc5 package, so we get that for free; if we were to switch to gcc49, users would need to compile that too, adding a lot of burden to them (palemoon already takes long enough to compile without having to compile the compiler too). Cheers. [1] https://gcc.gnu.org/ml/gcc-announce/2016/msg00002.html

mattatobin commented on 2017-03-08 17:23 (UTC)

Because it produces unstable builds?!

WorMzy commented on 2017-03-03 16:21 (UTC)

No. I have discussed the matter with Travis already. Users can build gcc49 and then make the necessary changes to the PKGBUILD and mozconfig if they wish to, but I see no discernable benefit for forcing all users to do this.

mattatobin commented on 2017-03-03 15:40 (UTC)

You do realize that you MUST use GCC 4.9 and nothing else for building.. Please make this change at once.

WorMzy commented on 2017-02-13 18:31 (UTC)

True, but Travis (Palemoon Linux dev) asked me to leave --enable-gstreamer in the mozconfig for the 27.1 release, and remove it for the 27.2 release. I'm not sure if there is a toggle in about:config which you can use to select your preference in the mean time.

alium commented on 2017-02-13 17:09 (UTC) (edited on 2017-02-13 17:19 (UTC) by alium)

palemoon 27.1.0 use now FFMPEG as backend for audio/video - please read release notes https://www.palemoon.org/releasenotes.shtml Gstreamer wil be remove: https://github.com/MoonchildProductions/Pale-Moon/commit/090b8adf6a62c007f4d5d91da73bf1f2b2873c1f

WorMzy commented on 2017-01-24 19:27 (UTC)

Where are you running the scripts from? The sources /should/ be stored there. So if you download the AUR snapshot for this package and extract it to ~/builds/palemoon, cd to that directory, and run 'sudo extra-x86_64-build', you will end up with a clean-chroot-built package and the palemoon git repository stored in ~/builds/palemoon/Pale-Moon. Note that this repository is "bare", not a "working copy", so may be causing some confusion. When you next run 'sudo extra-x86_64-build' from ~/builds/palemoon, this bare copy will be updated and a "working copy" will be cloned from it. This behaviour is the same as using makepkg directly, so if you have SRCDEST set anywhere, that might be affecting the behaviour. See also: http://www.saintsjd.com/2011/01/what-is-a-bare-git-repository/

wolf commented on 2017-01-24 19:02 (UTC)

So the devtool's chroot scripts should preserve sources? They don't, but I'll look into it, thanks for the tip. And thank you so much for the fix :)

WorMzy commented on 2017-01-24 18:35 (UTC)

I've pushed an update that includes the fix. I've not bumped the pkgrel because there is no need to rebuild for this change if you already have 27.0.3 installed.

WorMzy commented on 2017-01-24 15:22 (UTC) (edited on 2017-01-24 15:44 (UTC) by WorMzy)

The clean chroot scripts in devtools retain sources, likewise things that use devtools (like Graysky's clean-chroot-manager) will also retain them. If you're using some other chroot solution, then you'll need to check the documentation for that, but I'd find it strange if it removes sources post-build. As for 2) I actually reported this and it's fixed in the master branch, but I forgot to backport the fix to this package, will fix this when I get home. If you're feeling adventurous, the fix is quite simple, just apply the commit mentioned in this issue (via patch, or using sed) in prepare(): https://github.com/MoonchildProductions/Pale-Moon/issues/836 Edit: see the palemoon-beta package for an example of the fix.

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 38 Next › Last »