[SOLVED] rebuilding a few outdated 15.0 parts from source

elcore · 03-16-2023, 10:35 AM

What I got compiled/tested (mostly, but not completely from -current /source/):

Code:

alsa-lib-1.2.8
alsa-utils-1.2.8
alsa-plugins-1.2.7.1
curl-7.88.1
dnsmasq-2.89
ffmpeg-6.0
htop-3.2.2
iptables-1.8.9
libvpx-1.13.0
libwebp-1.2.3
mc-4.8.29
mpg123-1.31.2
mplayer-20230228
openssl-3.1.0
openssl-solibs-3.1.0
qt5-5.15.8_20230304_d8b881f0
wget-1.21.3
xf86-video-nouveau-20220125_29cc528

Got a few more, but it's mostly SBo, or 5-10 years old GTK+2 and similar stuff, which still compiles fine in 2023.
I've also bumped mesa/libdrm to latest at some point, but it wasn't very stable so I did disregard that and revert to default.

Kinda bored today, I wonder what others have compiled to keep 15.0 more up to date?
What to rebuild next? I'm lacking inspiration.

metaed · 03-16-2023, 11:55 AM

Quote:

Originally Posted by elcore

I wonder what others have compiled to keep 15.0 more up to date?

Just sysklogd.
A few nasty bugs were fixed in 2.4.2 -- buffer overruns and corruption of log entries.
15.0 sysklogd is still at 2.3.0 so I created a sysklogd-2.4.2 slackbuild and rebuilt it.
15.1 sysklogd has those bug fixes, so this is just a stopgap measure until 15.1 general release.

business_kid · 03-16-2023, 11:59 AM

I updated Mesa to 22.x. It didn't seem unstable. Chromium ≥108.x is worth having unless you hate it and I always use the ungoogled version. I presume you have the patches directory also?

pghvlaans · 03-16-2023, 12:14 PM

ksh. I also rebuild xorg-server* for rootless and ffmpeg for reasons that I don't quite recall, but probably have something to do with codecs for OBS.

elcore · 03-16-2023, 01:37 PM

Quote:

Originally Posted by metaed

A few nasty bugs were fixed in 2.4.2 -- buffer overruns and corruption of log entries.

Haven't see that, but stranger things have happened. It might be upgraded/patched if you insist on it in security thread.

Quote:

Originally Posted by business_kid

I updated Mesa to 22.x. It didn't seem unstable.

This requires new libdrm, which basically requires a new kernel, which has changed a lot between 5.15 and 6.1.

Quote:

Originally Posted by business_kid

I presume you have the patches directory also?

Just these few packages here:

Code:

aaa_base-15.0-x86_64-4_slack15.0
libtiff-4.4.0-x86_64-1_slack15.0
at-3.2.3-x86_64-1_slack15.0
libxml2-2.9.14-x86_64-1_slack15.0
boost-1.78.0-x86_64-2_slack15.0
libxslt-1.1.35-x86_64-1_slack15.0
ca-certificates-20221205-noarch-2_slack15.0
mozilla-nss-3.87-x86_64-1_slack15.0
cyrus-sasl-2.1.28-x86_64-1_slack15.0
polkit-0.120-x86_64-3_slack15.0
expat-2.5.0-x86_64-1_slack15.0
poppler-21.12.0-x86_64-2_slack15.0
flac-1.3.4-x86_64-1_slack15.0
ruby-3.0.5-x86_64-1_slack15.0
glibc-zoneinfo-2022g-noarch-1_slack15.0
sdl-1.2.15-x86_64-13_slack15.0
gnutls-3.7.9-x86_64-1_slack15.0
gzip-1.12-x86_64-1_slack15.0
wavpack-5.5.0-x86_64-1_slack15.0
hunspell-1.7.1-x86_64-1_slack15.0
xorg-server-1.20.14-x86_64-7_slack15.0
hwdata-0.367-noarch-1_slack15.0
xz-5.2.5-x86_64-4_slack15.0
libXpm-3.5.15-x86_64-1_slack15.0
zlib-1.2.13-x86_64-1_slack15.0
libarchive-3.6.2-x86_64-2_slack15.0

There's more of them, like git and python3 but I don't use/install these on my laptop. Had openssl-11 there and removed it.
Since some 15.0 stuff depends on 1.1, I've just copied libcrypto.so.1.1 and libssl.so.1.1 from solibs package to /usr/local/lib64

metaed · 03-16-2023, 02:25 PM

Quote:

Originally Posted by elcore

Haven't see that, but stranger things have happened

The ChangeLogs that I upgraded for:

Prevent over-read when scanning a new-style kernel message
prevent log file corruption when kernel messages contain control codes
logging to remote machine stops after receiving a few SIGHUPs
do not lose file mode on rotated files
fix issue with wall message (wall message corruption)

Quote:

Originally Posted by elcore

It might be upgraded/patched if you insist on it in security thread

I posted there in November and nothing came of it. I didn't feel like being a pest.

LuckyCyborg · 03-16-2023, 02:38 PM

Quote:

Originally Posted by elcore

This requires new libdrm, which basically requires a new kernel, which has changed a lot between 5.15 and 6.1.

Who told you that a newer libdrm needs a newer[1] kernel?

I have custom builds of latest Mesa (and libdrm) for Slackware 15.0 and they work fine with the stock generic kernel.

BUT, I made those builds on a clean & updated system.

[1] In the limits of decency, of course.

elcore · 03-16-2023, 03:05 PM

No, it does not need specific kernel version. It just requires a kernel feature which can change at any time.
And because subtle change in kernel creates a cascade where it may or may not break libdrm which then may or may not break mesa..
I compiled/tested, but got rid of both mesa and kernel 6.1 simply because it's too much work to keep track of, no other reason.

baumei · 03-17-2023, 05:45 AM

Hi "elcore", building replacements for the various outdated parts of Slackware 15.0 is a great idea!

Quote:

Originally Posted by elcore

Kinda bored today, I wonder what others have compiled to keep 15.0 more up to date?
What to rebuild next? I'm lacking inspiration.

I suggest the "qt5-webkit" library.

In Slackware 15.0 the version is:
"qt5-webkit-5.212.0_alpha4-*-7.txz" dated 2021-04-17.

In Slackware-current the version is:
"qt5-webkit-5.212.0_alpha4-*-10.txz" dated 2022-10-26.

elcore · 03-17-2023, 07:18 AM

Quote:

Originally Posted by baumei

I suggest the "qt5-webkit" library.

At some point I used kde4, where the webkit package may have been required.
Not using kde anymore, I barely even use the web these days, so compiling this would be a complete waste of my time.
Same goes for; in no particular order: qtwebengine, kde, gnome, xfce, chrome/chromium, libpulse, and many other packages.
Not personal or anything, but I simply lack the time to maintain stuff I don't use, would rather spend time on something I enjoy.

MDKDIO · 03-17-2023, 10:24 AM

Quote:

Originally Posted by baumei

Hi "elcore", building replacements for the various outdated parts of Slackware 15.0 is a great idea!

I suggest the "qt5-webkit" library.

In Slackware 15.0 the version is:
"qt5-webkit-5.212.0_alpha4-*-7.txz" dated 2021-04-17.

In Slackware-current the version is:
"qt5-webkit-5.212.0_alpha4-*-10.txz" dated 2022-10-26.

That is the same version, just a rebuild (if you check the current changelog you'll see what I mean)

baumei · 03-17-2023, 10:57 AM

Thank you MDKDIO, for pointing this out to me:

Quote:

Originally Posted by MDKDIO

That is the same version, just a rebuild (if you check the current changelog you'll see what I mean)

I had noticed the "5.212" part of the "qt5-webkit-5.212.0_alpha4-*-10.txz" filename was not changing, and had guessed the "-10" part indicated patches were being applied. Having now looked in the changelog, as you suggested, I now see my guess about patches was wrong.

Looking further down the changelog I found:

Code:

Mon Mar 16 21:20:17 UTC 2020
[snip]
l/qt5-webkit-5.212.0_alpha4-x86_64-1.txz: Upgraded.
[snip]

Three years, and no patches for this piece of software. Really?

MDKDIO · 03-18-2023, 03:07 AM

Quote:

Originally Posted by baumei

Thank you MDKDIO, for pointing this out to me:

Three years, and no patches for this piece of software. Really?

https://github.com/qtwebkit/qtwebkit/tags

Might give you an idea

elcore · 03-19-2023, 04:22 AM

3 more in next batch, compiles:+++ installs/runs:+++

Code:

eudev-3.2.11
gnutls-3.8.0
sysklogd-2.4.4

Not responsible for any breakage, and also: not redistributing (just testing stuff).

baumei · 03-19-2023, 04:18 PM

Thank you MDKDIO, for the suggestion and the URL.

Quote:

Originally Posted by MDKDIO

https://github.com/qtwebkit/qtwebkit/tags
Might give you an idea

I see the maintainer/developer of the qtwebkit has published no newer version in about three years, and says:

Quote:

WARNING: This release is based on old WebKit revision with known unpatched vulnerabilities. Please use it carefully and avoid visiting untrusted websites and using it for transmission of sensitive data. Please wait for new release from qtwebkit-dev branch to use it with untrusted content.

Since web related software is notorious for having many security holes, it seems odd the qtwebkit has not been moved to Slackware's 'pasture' sub-directory.