Hello, there is a new pango out.

pango-1.46.2
https://download.gnome.org/sources/p...-1.46.2.tar.xz

I am kindly reminding if possible to get dconf, pygobject, at-spi2-core, at-spi2-atk , gobject-introspection, libsoup and other friends posted earlier in here updated.

Rgds
Saxa

tidy html5 man page in wrong location
 

Howdy,
I didn't see this reported earlier, but the package
tidy-html5-5.60-x86-64-1 places the man page in the wrong location.

It is placed at instead of at
Changing the SlackBuild script to use:
instead of
fixes the issue.

Regards,
-karl

Python's pygmentize needs MarkupSafe. https://www.linuxquestions.org/quest...nt-4175682366/

Slackware 14.3 == KDE 4
Slackware 15.0 == KDE PLASMA 5

Would have been a good idea a year or two ago. Too late for that now. IMO.

current > 14.3 and freeze at kde4. it nice.
 

hmmmm... current > 14.3 and freeze at kde4. it nice.

15.0 is clear and open for 5.20.

tagging is simple. but may be a 15.1 for kde 5.20 ? How did you mean ?

I like 5.4.66 for release ;-)

In the ntp package there is a file ntp.logrotate.
This code returns 1 if /etc/rc.d/rc.ntpd is not executable, causing logrotate to return an error.
I suggest inverting the logic to
so that the code always returns 0.
This covers the case where a user is not automatically starting ntpd (e.g. laptop user without permanent internet connectivity).

KDE4 is seriously EOL and releasing a stable release of Slackware now with it would be a bad look (I personally think that this far into the game, no release looks better than a new stable with KDE4). Plasma5 integration has got to be right around the corner at this point and I'm hoping it will be a quick road to a stable release after that (after the obvious betas and release candidates to ensure it is actually "stable").

I want to agree, but that right around the corner has been almost like a loop now; and the radio silence from Pat on this is not helpful. I also think the best course of action and most likely going to happen, is that Pat will absorb Alien's packages for Plasma5 - again I don't see why not.

Does anyone know what are the current impediments which are blocking the release of the next stable version of Slackware?

We are discussing it right now - Plasma5 is probably the elephant in the room.

There isn't anything publicly provided. Anything here will just be guesses unless it comes from Pat himself. But my guesses are integrating Plasma5 and xfce 4.14 (but since 4.16 is close to being released, maybe Pat will wait for that). And now that we're getting close to the end of the year, the next LTS kernel is pretty close, so that might be a waiting point as well. Since 4.x, almost all LTS releases have been every 5th release, meaning that 5.9 could just be the next LTS (if not that, then 5.10 is a likely candidate, but again, until there's an announcement, it's just guessing).

There's tons of things that *could* be a blocker on Pat's list. Short of an actual answer from him, we'll just be left to speculation.

If there are impediments, Patrick Volkerding knows what they are. If he wants to say it he will, else he won't, no need to ask once more.

Could we next time have OTR support for mcabber ? Just a matter of a configure option...

The core inclusion of QT5, and KDE Frameworks 5 via KDE/Plasma 5, is no longer and option: a number of Slackbuilds.org scripts are dead without that update. Anything that needed KDE Frameworks 4 has long since moved to KF 5 and thus can no longer be updated for bug/security fixes etc.