Repositories for supported Debian, Raspbian, and Ubuntu releases

[stevenpusser]

OK, then it sounds necessary. I also know that there's the PineBook that uses it...

[stevenpusser]

Well, somehow the forums stopped recognizing my password and didn't send me email to reset it, so I'm here with a new account.

32.0.0 is building on the OBS, and I hope the jxl issues on arm are solved now. <cross_fingers>

I do have some newer coyote pictures, maybe I can update my avatar.

[satrow]

Well, somehow the forums stopped recognizing my password and didn't send me email to reset it, so I'm here with a new account.

See here: viewtopic.php?f=17&t=29323 ?

[Mæstro]

I am happy to follow on my report installing the keys. I had run Mint Update today and, on refreshing, Pale Moon 32 had shown up in available upgrades. I have just installed it. Thank you again for your help!

[stevenpusser]

Highway in the palemoon source is included third-party code, so I guess I'll need to patch it myself to get it to build on arm64 with jxl.

[Pentium4User]

Currently no PM is available for Debian Unstable:

http://download.opensuse.org/repositori ... _Unstable/

[stevenpusser]

Debian testing and unstable have removed Python 2, since it's reached EOL and isn't being maintained, so I can't do native builds on those platforms any longer. It's not a runtime dependency, but the build system uses it.

If the Bullseye builds don't work on upstream Debian, then your other option has to be the static builds that Pale Moon provides.

The arm64-with-jxl builds work out of the box with Buster's gcc-8, but die on Bullseye's gcc-10. Go figure. I have one failed patch attempt, so I tried another patch and loaded it a few hours ago in my MX 21 version build--still cooking right now: https://build.opensuse.org/package/live ... 11/aarch64

Then I have to fiddle around with getting it to build on Ubuntu 18.04's amd64 platform.

[Pentium4User]

That is bad news, because Python 2 will fade away from most distributions. Is it possible to migrate the build system?

I can run the PM from Debian 11 on Debian sid.

EDIT: Can you just upload the deb for 11 in Unstable?

[stevenpusser]

That is bad news, because Python 2 will fade away from most distributions. Is it possible to migrate the build system?

I can run the PM from Debian 11 on Debian sid.

EDIT: Can you just upload the deb for 11 in Unstable?

No, the OBS requires that the source files get uploaded, and then the debs are built from that source. Have you tried just adding the Bullseye repository instead to unstable, and see how much smoke comes out?

It seems that jxl fails on the gcc-10 arm64 builds in Bullseye, and also with armhf with the gcc-12 in Ubuntu 22.10, so I'm testing some code to automatically disable jxl if those distros and architectures are detected as the build platform. If it works, the missing 32.0.0 packages will just appear for those users.

[Pentium4User]

Have you tried just adding the Bullseye repository instead to unstable, and see how much smoke comes out?

No dependency problem, no problem with the package either. It seems to work.

[stevenpusser]

Have you tried just adding the Bullseye repository instead to unstable, and see how much smoke comes out?

No dependency problem, no problem with the package either. It seems to work.

Thanks for the report. Debian Bookworm in getting closer to a release date, and I guess the only way I can provide builds for those is just tell folks to use the Bullseye repo instead.

The repo also finally has Ubuntu 18.10 Bionic amd64 packages, though I had to disable the jpeg-xl feature for those, too.

[Mæstro]

Off-topic:
I am happy to see you have reclaimed your old account after being shut out. You seem nonetheless to have lost your contributor banner with the blue bar on the way. Could somebody please return that to you?

[random]

Thanks for the report. Debian Bookworm in getting closer to a release date, and I guess the only way I can provide builds for those is just tell folks to use the Bullseye repo instead.

Isn't it possible to build a Python 2.7 package or a Python 2.7 binary for Bookworm and use it for building Pale Moon? Just because Python 2.7 is not included anymore doesn't mean it wouldn't work on Bookworm. Maybe it's even possible to use a static Python binary for all Pale Moon builds on whatever Linux distro?

https://wiki.python.org/moin/BuildStatically

(not that I've tested it, just thinking out loud)

[Pentium4User]

Would it be possible to upload the deb builds (including apt repo files) to the Pale Moon ftp server instead of using the OpenSUSE build service?

[Moonchild]

Would it be possible to upload the deb builds (including apt repo files) to the Pale Moon ftp server instead of using the OpenSUSE build service?

I think part of Steve's problem is that he has limited hardware to build on (let alone for many distros).

[stevenpusser]

The OBS is a workaround for limited hardware, as it is a free-to-use build and server farm that emulates various distro's build environments, builds various packages from the original source code from the instructions I give it in the debian.tar.xz folder, and then automatically creates a repository for the finished package.

Trying to shoehorn Python2 into a distro that doesn't have it seems like it would take a lot of time and effort when the Bullseye packages are reported to work on upstream Debian...for now. I might as well suggest that Pale Moon source ship with a static Python2 build...

[Moonchild]

I might as well suggest that Pale Moon source ship with a static Python2 build...

You may have to consider supplying a toolchain package if this remains a problem, similar to the "MozillaBuild" package we've been using on Windows since forever. But i guess that would step on various people's toes as well if that becomes a dependency to build.

[stevenpusser]

Is there any hope of the python 2 code in the source being converted to python 3 eventually?

Are there any tools that advertise being able to convert the code automatically?

[Moonchild]

Is there any hope of the python 2 code in the source being converted to python 3 eventually?

No. Our build system is huge and very complex, and relies heavily on Python 2 specifics. It's not feasible to rewrite it into python 3 for us.

convert the code automatically

Not possible.

[Pentium4User]

Is there any hope of the python 2 code in the source being converted to python 3 eventually?

No. Our build system is huge and very complex, and relies heavily on Python 2 specifics. It's not feasible to rewrite it into python 3 for us.

Doesn't that mean it will "die" in the future?
Python 2 is EoL.