proftpd-1.3.6b is released.
ftp://ftp.proftpd.org/distrib/source...-1.3.6b.tar.gz

1 members found this post helpful.

Hello.
Do you plan to switch to Kernel 5.4.X after it will be released?
If yes - how fast?

If we look through the history of -current for the kernel updates, here's when the LTS kernels were brought in.

4.9 -> 4.9.26
4.14 -> 4.14.0 (then it was found to be broken, so it went to testing/ and was readded as the default with 4.14.11)
4.19 -> 4.19.0

So, looking at the last two LTS kernel releases, there's a good chance -current will be updated to the 5.4 release when it is officially released by kernel.org.

2 members found this post helpful.

I had a look at www.kernel.org. See two issues: the EOL for 4.19 is in coming new year December, but careful look shows that EOL for 4.14 is in 2024 - so maybe don't be so quick to through out you 14.2 installation - it should obtain updates till 2024. If kernel minor version does not change along release then: a) if 15.0 will be shipped wit 4.19 then 15.1 appear before the end of dec 2020 - so 15.0 will live on about a year b) 15.0 will be shipped with 5.4 and will stay up to dec 2021 c) we will wait for LTS kernel version with longer life time. To allow longer period between releases 15.0 and 15.1. I hope what I written is clear. If-then it is just my bad custom - derivative of being pro math.

Edit: Ups, again my wrong - I have no idea why I was sure 14.2 is shipped with 4.14 - hm, just it is early hour as for me - or the sign from havens to upgrade by myself to 4.14 my 14.2 installation.

I will be happy with whatever major kernel version Mr Patrick J. Volkerding ships in Slackware 15.0. If anything happens during this version's life time that makes me prefer another one, I will just consider switching. Maybe he will too, who knows?

1 members found this post helpful.

glib-2.62.2
https://download.gnome.org/sources/g...-2.62.2.tar.xz

This upcoming release is the first release of Slackware since they started introducing 6 year LTS support timeframes. We don't know what Pat's plan is to manage these releases or what his plans are when a kernel used in a stable release is no longer updated by kernel devs.

As far as 4.19's EOL date, these EOL dates have been extended for all LTS kernels from 4.4 on, with 4.14 being recently updated to 6 year support. So, it is very possible that when 4.19 is getting close to EOL, that the kernel devs might add a longer period of support for it.

3 members found this post helpful.

The way I see it (just my 2c) is:

The longer the kernel's LTS support, Slackware ships with, is, the further "up hill" the next release will be.

Holding my fingers crossed for 5.4

3 members found this post helpful.

It is likely that Slackware is sticking with Python 2.x , so can we have version 3 in /extra at this point ?

Slackware-current has python3-3.7.4 already.

1 members found this post helpful.

I withdraw my request

But to be honest, its really difficult to understand what is better, do we stay with /usr/bin/python symlinked to python2 or wouldn't it be better to link it to the python3 ?

I think this was discussed already, but thinking of it I think it would be better to make python3 as default and try to port eventually
as much as possible to python3 since it is going into the future.

Just a guess.

Rgds
Saxa

2 members found this post helpful.

I also think even if python2 stays in the tree it makes sense to make python 3 the default; but I can well imagine there being a lot of gotcha's and perhaps the switch might be better done after the release of 15... but as always I trust the Slackware team; and am sure they'll pick the best way forward.

1 members found this post helpful.

In fact my thinking was just something what I thought in that moment and just some kind of brainstorming.
I also trust to the team decisions. In any case it surely would simplify things to be faster corrected or
ported to python3 if the default is python3. Users can make claims and bug reports to the relative maintainers
of packages which would still be asking for python2.

1 members found this post helpful.

All think the correct way is go python linked to version 3 , but i think this need some time to do , rewrite some slackbuilds, and test if all are correct under python 3 , version 2 is spected abandoned in january 2020.

1 members found this post helpful.