Pale Moon forum

Thanks for the info...I often worry that it's "just me" having the trouble.

OK, after a hour or two, I restarted the process and it was back up to full speed this time. I guess if you start at a crawl, it leaves you there. Now compressing the source into the orig.tar.xz file for uploads to the OBS.

stevepusser wrote: ↑

2022-06-07, 21:45

I've dropped the GTK2 builds for the most recent distro releases, but could add them back if requested.

It would be nice if you could still provide GTK2 builds for current Ubuntu and Debian. It just looks better than GTK3.

Additionally, if GTK3 is the new default, the PM Linux page should be updated: http://linux.palemoon.org/
I already created an updated version in git months ago, maybe have a look at it.

Pentium4User wrote: ↑

2022-06-08, 05:09

Additionally, if GTK3 is the new default, the PM Linux page should be updated

It isn't, but what Steve here does for the Ubuntu/Debian crowd is entirely up to him. Linux.palemoon.org is for and about our mainline binaries, not contributed builds.

Moonchild wrote: ↑

2022-06-08, 06:32

Pentium4User wrote: ↑

2022-06-08, 05:09

Additionally, if GTK3 is the new default, the PM Linux page should be updated

It isn't, but what Steve here does for the Ubuntu/Debian crowd is entirely up to him. Linux.palemoon.org is for and about our mainline binaries, not contributed builds.

The link on the linux page links to his GTK2 builds, the GTK 3 builds are in a different repo, therefore I suggested a change.

Pentium4User wrote: ↑

2022-06-08, 06:39

The link on the linux page links to his GTK2 builds, the GTK 3 builds are in a different repo, therefore I suggested a change.

Ahh ok. I thought you meant we should change the information about out binary distributions. You weren't exactly clear it was about a link

Steve, what do you think? Should it be changed and if so, what to?

I can provide gtk2 builds for all the Debian and Ubuntu versions the OBS supports--it's just a few button clicks. Yes, put both repositories in the guide, please. I have a link to the GTK 3 one in the description of the original OBS repo. https://build.opensuse.org/project/show ... emoon-GTK3

Debian packages use "debhelper" to automate a lot of package builds, and I thought I'd update it from the ancient debhelper 9 I was using with this refresh, since I'm getting a lot of messages about how old it is during the build. But updating it to 10 must have changed the flags passed to autoreconf in Debian Testing, Sid, and Ubuntu 22.04, and the builds error out there. I did an update for the GTK 3 packages from 31.1.0-1.gtk to 31.1.0-1.1gtk3 to account for the update, so those users that already got the successful builds for earlier releases, will be getting that update even though it doesn't fix anything on their release, just so I can keep everything in one repo for GTK 3 now.

Anyway, I'll have to do the same thing now for GTK 2 if I add those three newer distreleases--the older ones built fine with debhelper 10, so I was just going to revert it with the next Pale Moon release. Hopefully everyone can spare the bandwidth!

OK I'm a little confused here.
the only link I see on the site is listing to software.opensuse.org, but the gtk3 link given is linking to build.opensuse.org, they look vastly different and I don't think linking those side by side would be very clear as to what people need.

OK, the OBS has a landing page for each project's repo, but then a separate page for each package in that repo. Let's just send them to the "palemoon" package's page:

The original GTK 2 page: https://build.opensuse.org/package/show ... r/palemoon

The newer and separate repo for the GTK 3 builds: https://build.opensuse.org/package/show ... 3/palemoon

I just updated the description for the GTK 2 palemoon page, and will add a simila rdescription to the GTK 3 page now:

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. In any case, to add the 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.

OK, I updated the front page with those. Let me know if there's anything else that needs doing?

Hmmm..since this thread title is now far out of date and I can't edit it, can it get changed to "Repositories for supported Debian, Raspbian, and Ubuntu releases", which should be future-proof?

Done!

stevepusser wrote: ↑

2022-05-12, 21:00

when gcc-12 makes it into upstream Debian.

Do you mean when testing/sid's gcc package points to 12.1 (which currently isn't), or when gcc-12 with a proper version number (i.e. no git date number) is now in testing and sid? Your build currently uses GCC 11.3.

Pale Moon builds totally fine for me in GCC 12 and it runs well so far without any crashes fwiw.

Every Debian and Ubuntu version has a "gcc" metapackage that depends on the default gcc version, so it's still pulling in gcc-11 in Sid:

https://packages.debian.org/search?keyw ... ection=all

But many times, they may have older gcc versions still in the repo, such as the gcc-10 you see lower down in the results for testing and Sid. If gcc-11 builds turn out to be crash prone, it's possible to tell Pale Moon builds to use gcc-10 instead of the default 11, for example, with this type of stuff in the debian/rules file: But remember, this is a hobby pastime for me, so most of the stuff I know is just copied from other Debian packages I've backported. I am by no means a coder. Once in a while, I manage to figure out something tricky, like getting the new nala-0.9.1 source in Sid to build and work correctly in Debian 11 like I did today (needed about sixteen other python3 backports first, though )

Moonchild wrote: ↑

2022-06-10, 09:35

OK, I updated the front page with those. Let me know if there's anything else that needs doing?

The contributed builds page still links only to the GTK2 build.

Dear all,

Since a week or so, when manually running apt-get update on my Raspberry Pi it gives the error:
"Repository ... stevenpusser/ ... raspbian_9.0 release ... does no longer have a release file ...
... updating is therefore disabled"

The Pi currently runs palemoon 29.4.6-1.gtk2 (and it runs good and fast enough on my old Pi v. 3
Could someone please assist in how to solve this and get updating of palemoon running again?

Cheers!

Ps, excuse me if this is the wrong place for my question...

Which OS do you have on your Raspi?

Raspbian 9 (stretch)

Stretch only has gcc-6 available, and as of version 31.0.0, Pale Moon requires a minimum of gcc-7 to build.

Debian is dropping any further security support for Stretch June 30, anyway, so maybe it's time to upgrade to Raspian 11 or 10?

I didn't think of that... okay, all clear now, willdo.
Thanks for your help and time!