orc-0.4.32
https://gstreamer.freedesktop.org/sr...-0.4.32.tar.xz

glib-networking-2.66.0

sources --> https://ftp.gnome.org/pub/GNOME/sour...-2.66.0.tar.xz

in the news file only says updated translations , minor update.

https://ftp.gnome.org/pub/GNOME/sour...ng-2.66.0.news

dconf-editor-3.38.0
https://download.gnome.org/sources/d...-3.38.0.tar.xz

No thank you. Wiped out my calendar and address book!
I'll stay with 78.2.1.

gobject-introspection-1.66.0
https://download.gnome.org/sources/g...-1.66.0.tar.xz

pygobject-3.38.0
https://download.gnome.org/sources/p...-3.38.0.tar.xz

at-spi2-atk-2.38.0
https://download.gnome.org/sources/a...-2.38.0.tar.xz

at-spi2-core-2.38.0
https://download.gnome.org/sources/a...-2.38.0.tar.xz

dconf-0.38.0
https://download.gnome.org/sources/d...-0.38.0.tar.xz

78.2.2 is released.

adwaita-icon-theme-3.38.0
https://download.gnome.org/sources/a...-3.38.0.tar.xz

libsoup-2.72.0
https://download.gnome.org/sources/l...-2.72.0.tar.xz

gsettings-desktop-schemas-3.38.0
https://download.gnome.org/sources/g...-3.38.0.tar.xz

Ghostscript 9.53.1
https://github.com/ArtifexSoftware/g...-9.53.1.tar.xz

If you downgraded Thunderbird from 78.2.1 to 68.12.0, as this is not supported upstream, I am not that surprised. On the other hand I upgraded Thunderbird to 68.12.0 from 68.11.0 in Slint (both genuine Slackware packages intended for Slackware 14.2) with no issue.

Would be possible to have also mozjs-78 ?

A stable XFCE 4.16 is imminent - maybe at this point 4.14 should be skipped; since --Current is still at 4.12.

For a while I have wondered if part of the 15.0 holding pattern might be related to waiting for 4.16. Just speculating of course. :D

vte-0.62.0
https://download.gnome.org/sources/v...-0.62.0.tar.xz

libgudev-234
https://download.gnome.org/sources/l...dev-234.tar.xz

network-scripts: rc.ip_forward improvement
 

My /etc/sysctl.conf had "net.ipv4.ip_forward = 0" in it and "rc.ip_forward start" couldn't enable ip forwarding (technically it enabled it, but just for a few ms).
Here is a patch to make rc.ip_forward more predictable by ignoring all the ip forwarding keys in /etc/sysctl.conf.
Regards

mozjs78-78.2.0esr-x86_64-1.txz from Tue Sep 15 18:51:00 UTC 2020 is incompatible with polkit-0.117-x86_64-1alien.

A perfect storm is set for ktown users (like me):

1. Eric has dropped ktown development;
2. ktown depends on a number of packages from the official -current tree (like the above polkit > mozjs68);
3. As plasma and friends (aka kde5) are not integrated into -current, there is no quality assurance and things break.

Quoting Eric: "go with the flow and upgrade wisely."

When things go wrong, downgrade here:

http://slackware.uk/cumulative/slack...t/slackware64/

Can you just download polkit and rerun the SlackBuild?

https://slackware.nl/alien-kde/sourc...g/deps/polkit/

Does polkit-0.117 work with mozjs78? If not, does a simple version bump work?

Don't think so...

Also this:

Don't think this is the case either.

For someone who uses the latest Plasma5 shipped by Mr. Hameleers, updating the polkit properly is just a matter of updating the tarball in the deps folder, then to do a local build. Anyway, I believe that's a very good idea to blacklist the Slackware polkit (and ConsoleKit2) when upgrading the -current.

Right now, I run local builds of Plasma 5.19.5 and Frameworks 5.74, and I have a nice Plasma5/Wayland experience on a IGP Radeon HD4250 and the Intel HD2000 from a i3-2120 .

There's no need for us to wait to be spoon-feed by Papa Eric...

Still, I would love to see some comments of him about building Plasma 5.20 when time will come. Just comments, not builds.

I am very excited about this particular version, because from what I read, it comes with many Wayland improvements - big enough for Fedora considering to switch to Plasma5/Wayland as default...

Good for you!

You see, comments like this are the reason I'm becoming more and more away from anything community. I'm more than capable to keep my box up and running, but there might be others out there who can't. They jump in -current bandwagon, install ktown on top of it and have little to no clue on what are the implications of this choice just because, well, they are users. We can't blame them.

Then I come here just to let the people more acquainted to the subject aware of the issue, ask for nothing in return and as response I have to read such an idiotic comment.

If you can't help by avoiding such a childish behavior, I can by refraining to report anything.

My apologies if I bother anyone.

Welcome to my ignore list. Whatever kind of insults are coming next, I will not read them.

Excuse me? About what insults you talk?

All I wanted to say is that customizing your excellent Plasma5 build system we can solve some upgrades ourselves, without we to insists on asking to do them yourself.

And I am pretty sure that the phrase "don't wait to be spoon-feed by Papa <insert name here>" has the sense to take initiative and solve yourself the problem, without waiting for your boss to solve it.

I heard it many times in the last years, as some of my superiors at the mining/resources prospecting company where I work are British - BTW, I learned the English language not for love of Linux, but because I needed it at work.

And those gentlemen, who are rather very polite every day, used it many times over years, with exact the sense described by me.

SO, either you utterly overact, OR some guys used to insult many times some poor Russian guys, speculating their language ignorance - which is very hard to believe, as at least someone should have been figured it out already...

With all respect, but I believe that we can blame those who jump on -current without knowing (or, rather understanding) the consequences.

Because there was repeated many times, that Slackware-current is the development tree of Slackware, and NOT its rolling release variant. Then, it is assumed that as -current user, you accept to be a beta-tester of Slackware, with certain debugging skills, and able to solve your local issues in a certain extend, even as "simple user".

Add in this mix also Plasma5, which is a huge piece of software, and if the user is "just an user" like your said, then this is the perfect recipe for disaster.

I believe that those who are "just an user" should stay in the 14.2 version - after all it is maintained and there are no signs of going EOL.

As a native speaker, we'd be more likely to use "Uncle Eric" rather than "Papa Eric"¹, but using it in this context would be both intended and taken as a term of endearment, not insult. This seems like a misunderstanding to me.


LC's "Hey I maintain it myself so you can too" narrative does come across a little dick-wavey, but he has a point, and the advice about blacklisting ktown dependencies in current in order to prevent breakages of this sort seems like sound advice to me: although it's inevitable that something will break eventually.


Just my unsolicited take. YMMV.

---
¹ I don't think I've ever heard a Brit use "Papa", but maybe there are regional differences.

Suggestion: ship the extra utilities in ntfs-3g
 

Including the configure option:
--enable extras \
allows to build and ship in the package following additional programs in /bin:
ntfsrecover
ntfssecaudit
ntfstruncate
ntfsusermap
ntfswipe

Maybe few people will use them but that won't hurt and the respective man pages are already shipped.

Good advice, thanks! I have all alien packages blacklisted so I avoided getting bitten, but now I read from Eric that he will stop packaging Plasma 5 so in the meanwhile I will reconsider my options.

I think it's high time for Plasma 5 to be included in -current...

mesa is now 20.1.8

some incompatibility to upgrade python2 ?

https://www.python.org/downloads/release/python-2718/


And because is the last release for python2 , i think is not bad idea , upgrade 14.2 with this last release.

Request: Ship man pages with n/libnetfilter_queue
 

libnetfilter_queue 1.0.5 builds a full set of man pages with ./configure option
--with-doxygen.

This would have been the default except we couldn't get make distcheck to pass
without an ugly hack.

The SlackBuild needs to do the usual man page stuff - patch attached.

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.

Today i have compilation report "KF5 not found" in PLASMA 5.19.90 in today Slackware64,
but in UbuntuStudio.org daily 20.10, i have work distro with PLASMA 5.19.95, VLC 3.0.11, LibreOffice-7.0.1.2 and mach more. And test him.

What to do ?

Switch to Ubuntu then. Done with the complaints. Why are you here?

My dear Alien
 

My dear Alien,
I believe that you are thinking of me, that I am not experienced enough.
However, I have been working with computers since 1993.
And so I have just terrible experience of using various interfaces, including working with compilation.
I am a programmer and a very very old programmer.

I just want, like everyone else here, that Slackware was relevant.

It's a shame that Google won't be able to translate all those good words that I could say in my language. In a good way.

May be, at least I'm new to this forum.

I think you just have a good reason to work with the Slackware 64-bit distribution.

Try deepl.com. It could do a better job than Google translating from Russian to English.

Хорошего дня во Владивосток.

You deserve a better reply then. As a new user on this Slackware forum, all you ask is for things that are not going to happen. At some point you should start understanding that, and stop repeating yourself in multiple topic threads.
Plasma5 will get added when it gets added. In the meantime, you can install my Plasma5 packages. If you want to compile newer versions of KDE Frameworks, Plasma5 or the Applications, then be my guest. However when you run into issues, you surely understand that no one is going to provide any meaningful assistance if your feedback about the errors is just a statement "KF5 not found" and nothing else.
I mean, come on. If you are in the computer business for 27 years and a programmer, too... then you know you must share complete build logs.