Veit Kannegieser's repo

[ron_1]

Is Veit Kannegieser's repo an official 3rd-party build? There's no mention of it on the contributed builds page.

[Moonchild]

I'll be happy to add it if the community at large thinks it should be marked as such.

[Pentium4User]

Is Veit Kannegieser's repo an official 3rd-party build? There's no mention of it on the contributed builds page.

Can you please send a link?
I haven't heard of that yet.

[andyprough]

Can you please send a link?
I haven't heard of that yet.

Here's the thread where Veit announces the repo: viewtopic.php?p=254376#p254376

And here's the repo and instructions for use: https://kannegieser.net/palemoon/

Very nice and clean and simple, no complexities like with Steve Pusser's MX repo.

[moonbat]

Just switched to this from the tarball version, works and integrates great
I'm going to still keep the tarball version as a backup going forward.

[andyprough]

Veit already has today's new Pale Moon version 33.3.1 up in the repo. Steve Pusser's repositories were running days or sometimes weeks behind in getting the new Pale Moon packages uploaded. This is good stuff.

[moonbat]

I noticed that this build doesn't remove the auto updater - so I got a prompt saying Pale Moon couldn't update itself due to missing permissions. After updating to 33.4.0, I can still see the 'check for updates' in the help menu and the relevant settings in advanced preferences. Please remove it while building since it isn't needed for repo installs.

[BenFenner]

I noticed that this build doesn't remove the auto updater

Yep, I noticed the same thing this morning when I switched repos.

[Veit Kannegieser]

so I got a prompt saying Pale Moon couldn't update itself due to missing permissions.

The package is installed below /usr/lib/, the update script detects that it would not be able to write there.

After updating to 33.4.0, I can still see the 'check for updates' in the help menu and the relevant settings in advanced preferences.

For me the dialog is a reminder that i have to update.
You can disable the update checks in the settings/update tab.

Please remove it while building since it isn't needed for repo installs.

This just repackaged, not build from source, i can not change that function.
Please try settings option.

[moonbat]

Ok, thanks.

[andyprough]

This just repackaged, not build from source

That's good, less things that can go wrong between the official tarball and this repackaging of it into a deb. That's another advantage over any other Pale Moon deb package.

[moonbat]

That's another advantage over any other Pale Moon deb package.

There were no problems with stevepusser's build AFAIK, that removed the superfluous auto-updater.

[andyprough]

There were no problems with stevepusser's build AFAIK, that removed the superfluous auto-updater.

At least you have the new version. I'm on Steve's MX repo and might not have 33.4.0 for a few more days.

[Proteus]

Trying to install latest version 33.5.0 of Pale Moon from the kannegieser repo. Doesn't work.

Error message:
Dependency is not satisfiable: libgdk-pixbuf-2.0-0 (>= 2.22.0)

There is a small typo! This library is named libgdk-pixbuf2.0-0, not libgdk-pixbuf-2.0-0. Do you see the difference? There is a dash between pixbuf and 2.0. But there shouldn't be any!

@Veit: Would it be possible for you to fix this?

[Veit Kannegieser]

Error message:
Dependency is not satisfiable: libgdk-pixbuf-2.0-0 (>= 2.22.0)

Thanks for reporting. This worked here on Debian 12, also lintian was complaining about before

Code: Select all

E: palemoon: depends-on-obsolete-package Depends: libgdk-pixbuf2.0-0 (>= 2.22.0) => libgdk-pixbuf-2.0-0 and optionally libgdk-pixbuf-xlib-2.0-0

And in newer MX23 debs that change was done too:

Code: Select all

..
libfreetype6 (>= 2.2.1),
libgcc-s1 (>= 4.0),
libgdk-pixbuf-2.0-0 (>= 2.22.0),
libglib2.0-0 (>= 2.26.0)
..

I will revert the change for compatibility.
and suppress the warning, should take an hour.

[Veit Kannegieser]

Control file has libgdk-pixbuf2.0-0 (>= 2.22.0) again.
Other notable changes in the repacking for 33.5.0 are:
Optional "Recommends" keyring in the control file,
and a file /usr/lib/palemoon/updates is installed, that prevents updates early, even when run as root user which i had not considered before.

[Proteus]

Thanks for quickly fixing the update files. Now it works fine.

[Moonchild]

Sorry about not updating the website's contributed build page sooner. The repo is up there now.

[struppi]

I just updated Palemoon on three systems. Two VM with Linux Mint 22 and one Debian 11 (bullseye) Palemoon work well.

I had some problems to understand what SSE and AVX is and was not sure if I have gtk2 or gtk3. I am not a "poweruser" just a semi professional user (mostly I do some internet programming stuff with this machines). So my understanding of CPU is very low. But I found out, that the output of

Code: Select all

lscpu | grep avx

(or 'sse' or 'avx2' instead of 'avx') can help me to find out what version I need. For the gtk, I guess the gtk3 version is the right one today on most desktop environments.

I want to add thank you for this work. I like Palemoon and use it when ever it's possible.

[RealityRipple]

I just updated Palemoon on three systems. Two VM with Linux Mint 22 and one Debian 11 (bullseye) Palemoon work well.

I had some problems to understand what SSE and AVX is and was not sure if I have gtk2 or gtk3. I am not a "poweruser" just a semi professional user (mostly I do some internet programming stuff with this machines). So my understanding of CPU is very low. But I found out, that the output of

Code: Select all

lscpu | grep avx

(or 'sse' or 'avx2' instead of 'avx') can help me to find out what version I need. For the gtk, I guess the gtk3 version is the right one today on most desktop environments.

I want to add thank you for this work. I like Palemoon and use it when ever it's possible.

Usually gtk2 is only required if you're going to use any NPAPI plugins, as far as I know.