Unrelated to python.

Curl now has non-experimental support for QUIC/http3 when built with nghttp3 and ngtcp2 and gnutls.
https://github.com/curl/curl/pull/12235

nghttp3 and ngtcp2 have both reached version 1.0+ (1.1 and 1.2).

I think they are considered good enough now.

I have builds for those three on SBo (https://gitlab.com/SlackBuilds.org/s...ts/608/commits), and I would once again ask for the inclusion of those two into mainline Slackware.
(curl-quic is just normal curl with enabled http3, installed into /opt)

1 members found this post helpful.

I would also like to ask to add ipv6 to "slackware.com".
"slackware.com" normally redirects to "www.slackware.com", which works in a straightforward way for ipv4, but for ipv6, "www.slackware.com" works as intended, whereas "slackware.com" does not:

I'm good with python 3.11 or 3.12, which has on been out since October of last year. So 3.11 meets the at least one year out thought. So far I've only encountered =>3.10 and was able to work around it by modifying the script to use pre-3.10 code.

1 members found this post helpful.

Security fix for CVE-2023-6246, CVE-2023-6779 and CVE-2023-6780

May I ask that htop be _removed_ from mainline Slackware?

While it is a nice and useful tool, mainline Slackware already has classic top, for the cases when installing external software is not possible, whereas having htop outside of mainline would allow SBo to update its versions in an asynchronous manner. (I am ready to volunteer for its maintenance.)

(Or maybe I just would like to ask to update htop in 15.0 to 3.3, as it has much better support for filters (line editing).)

I understand that packages in stable versions are usually not updated for new features but rather for security fixes. However, if you still want a newer version of some software than the version in your stable Slackware you are still free to download and build the sources from Slackware current: http://ftp.slackware.com/pub/slackwa...ource/ap/htop/

Doing so would not be much more work than installing third party packages from slackbuilds.org.

Having an application as an official package from Slackware has its benefits. You know that you will see a notification in the ChangeLog and get a new package from the patches directory whenever there is a security update.

regards Henrik

4 members found this post helpful.

May I ask that that Lockywolf be stripped of rights to demand silly and outrageous things?

While I am aware there might be programs and features that evolve over the cycle of Slackware (or any other Linux distribution) releases, it would quickly devolve into the dev-team chasing its own tail if we come to expect the stable release hunts for latest and newest program features and/or updates.

Or, better yet, someone advise him to try some rolling release distro if he depends on quickest and latest features

By plain silly or outrageous understand asking to remove a program just so he could try (or fail) to keep up with the pace we have (or he craves for) already on the ever busy SBo thread

@LockyWolf:
did it ever occur there might be a flatpak or Appimage of said app where you could update it ad nauseam and your own leisure?

1 members found this post helpful.

Hmmmm, that rings of the philosophy of...

"I do not agree with what you say therefore I will try to prevent you from saying it."

6 members found this post helpful.

http://ftp.slackware.com/pub/slackwa.../ChangeLog.txt

Fri Feb 2 22:12:45 UTC 2024
A test mass rebuild here didn't find any new failure-to-build-from-source, so
we'll go ahead and upgrade to the new glibc. Enjoy! :-)
a/aaa_glibc-solibs-2.39-x86_64-1.txz: Upgraded.
________

Fantastic !

With that we seem to me to be just one step closer to v15.1

Step 2 would be a release to the public in -current of that mass rebuild.

1 members found this post helpful.

3 members found this post helpful.

Anyone know why procps-ng are freezed in 3.x ?

Have new branch 4.x since moths , i build and test 4.0.4 and appears okey ..

slackbuild only need ./autogen.sh before configure.

???

Probably because nobody never requested it in a gentle way :-)

Because it breaks API and ABI and brings nothing worthwhile to the table.

EDIT: perhaps none of that matters Still, it looks like most distros are sticking with 3.x for now.

Interesting to mention that, it never crossed my mind while i was writing my reply.

My remark was made in the same jest as LockyWolf's i was replying to- OFC we won't really strip him of rights nor would i really stand behind a move like that!

libxml2-2.12.5
https://download.gnome.org/sources/l...-2.12.5.tar.xz