The Pale Moon Web Browser-original GTK+ 2 builds
This repository now used for GTK 2 builds, which all my older builds were. Now that GTK 3 is an option, those builds are in a separate repository.
https://build.opensuse.org/package/show/home:stevenpusser:palemoon-GTK3/palemoon
In any case, to add this repository and its apt key, click on the "download package" link on the upper right of this page, then:
Click on what version of Linux you are using is compatible with (as Linux Mint is compatible with various Ubuntu releases, and Mint's Debian Edition with Debian releases)
To add the repo and its key, click on "Add repository and install manually" link
Then cut and paste the directions for your particular distro's release into a terminal. Take care to use the directions for your release, since it's easy to mistakenly copy and paste the set above or below the correct ones--you can read what you've just pasted into the terminal to make sure it matches what you are running.
Note that if you add both repos, the GTK 3 version will be seen as an upgrade over the GTK 2.
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:stevenpusser/palemoon && cd $_ - Create Badge
Source Files
| Filename | Size | Changed |
|---|---|---|
| _constraints | 0000000194 194 Bytes | |
| palemoon_33.0.2-1.gtk2.debian.tar.xz | 0000075540 73.8 KB | |
| palemoon_33.0.2-1.gtk2.dsc | 0000001190 1.16 KB | |
| palemoon_33.0.2.orig.tar.xz | 0207963024 198 MB |
Latest Revision
Steven Pusser (stevenpusser)
committed
(revision 1152)
Comments 23
ubuntu 18.04 x64 build was failed, is it possible to fix?
If it fails with the new 32.0.0 release, I'll try and build that version with a different gcc.
Debian testing and unstable have removed python2, so I don't know how I'll get native builds there.
seems like yes, its also failed :( so please if its possible, take a look into it. 18.04 is still continue to be reasonable choice for person who liked old ubuntu look-and-feel with classical gnome-panel, in 20.04 indicator applet was broken already
still nothing?
any updates? Sorry for annoying but I hope many new fixes should be available on new Palemoon I want to see
I tried, but the OBS errors out with some kind of gcc-8 version mismatch:
https://build.opensuse.org/package/show/home:stevenpusser/palemoon-bionic-amd64-gcc-8
Let me see if I can at least build a Bionic version on my own laptop and put that deb up for download.
I see manual deb build was successful at least :) Thanks a lot!
The OBS doesn't allow me to upload finished debs, so I did figure out how to get the Bionic amd64 version to build with gcc-8.
so we will have routine working again then, right?
Yes, I'm sending up the sources for the 32.0.1 Bionic amd64 version soon. I've managed to get all the other different configurations for enabling and disabling build-flags and jxl into one source file for all the other distro releases, but haven't figured out how to tell it to install gcc-8 for the build instead of the standard gcc when it sees bionic amd64...
I figured out how to have it all in one source file after I uploaded the new sources, but I'll wait until the next PM update. It's a bit clunky, as it may install gcc-8 if present and that may never get used on other distreleases, but shouldn't affect the finished debs. It's a kludge that a real Debian packager would work around with control.in files that generate a final control file depending on the distrelease.
18.04 builds are still broken it seems :(
Thanks a lot for your long time work for this project. In our dark times these little good things really making people a bit happier indeed :) And as result, Palemoon is now back in track and much more real important sites are functional again.
:) you know my message, right?
Yes, thank you for the kind words.
I am also helping with MX Linux, being one of the original guys that started it up, and am the lead packager for it.
but 18.04 build was failed again :(
any chance to fix my favorite 18.04 builds? ;)
still broken :(
if its a real problem I'll switch to manual building then, just need to know
I'll take a look at that amd64 Bionic problem tomorrow, since the automatic switching for gcc-8 still doesn't work, and 32.2.0 is out now.
It probably needs it's own source packages forcing gcc-8 without jxl being enabled.
still breaking on every new build
:)