Guys this looks like handwaving ...
Is there a way to figure out which mirror is the culprit here? Or a way to influence the choice of the mirror? Without these the usefulness of slackware.com is limited ...


The workaround is to ftp down the text file. But ftp is (being) phased out -- at least Firefox now no longer "understands" the URL ... But luckily Caja does!
Actually there is something fishy with the ftp links on http://www.slackware.com/changelog/. Firefox used to and Caja does report 'Could not display "/tmp/mozilla_root0/ChangeLog.txt"', whereas Firefox shows e.g. the http://slackware.uk/slackware/slackw.../ChangeLog.txt file without a hitch.


I googled for "firefox ftp support" and found https://www.trishtech.com/2021/04/ho...rt-in-firefox/.
At least for now the ftp links in http://www.slackware.com/changelog/ work again.


Just a hunch: Might it be that the Changelog.txt file has become too big (it is 1.5 MB now!) to be handled properly by the "x86_64 Architecture" link?

1 members found this post helpful.

SeaMonkey 2.53.8 released
https://www.seamonkey-project.org/
https://archive.mozilla.org/pub/seam...x86_64.tar.bz2

Just in case we will switch to:

NetworkManager-1.32.2
https://download.gnome.org/sources/N...-1.32.2.tar.xz

PS: BTW I still see only up to June 24 the updates on slackware.com

Thanks for fix python2 collection modules , i love when pip2 or pip3 says all is fine.

I found this 64 bit changelog are stuck , but 32 bit works ..


http://www.slackware.com/changelog/current.php?cpu=i386

I stopped using the website a few years ago after the page loading became too much for my old work computer. It would stall out because of how long the ChangeLog is.

Now, I just open up the direct link for the ChangeLog (using my preferred mirror) and have that bookmarked. For those who like the old OSUOSL FTP link, you can actually just switch from ftp to https and view the ChangeLog on the same servers, just https protected now.

We haven't seen the code on how the ChangeLog page is generated. It might just be a script that is broken or it might be pointing to an out-of-date mirror. Other than the usefulness of the link itself, I don't think there's any other benefits by accessing the webpage instead of the ChangeLog directly.

1 members found this post helpful.

I confirm, i386 is showing 30/06/2021 as latest update here.

the latest seamonkey-2.53.8 is released and contain security fixes

Seconded, and also guidance on how we can add the additional stuff (docs | extra | fonts).

Request to recompile mc with --enable-aspell option to enable spellchecking with its internal editor. It looks like it just requires aspell to be installed, so there shouldn't be any additional dependencies. It was noted on this thread.

2 members found this post helpful.

libseat
see my prior post
https://www.linuxquestions.org/quest...re-4175696916/

For God's sake! Now that we replaced ConsoleKit2 with elogind, let's stuck with it!

I have no emotional attachment for elogind, BUT looks like it does a fine job for user sessions, seats and power management, even for Wayland/Plasma5.

So, we are more or less compatible with the other major distributions, even we do not use systemd. I think this is the most important thing.

3 members found this post helpful.

Since sway is not part of Slackware, I see no reason to add libseat.
You can compile libseat with support for elogind and then you can have both libseat and elogind on your computer.
I would expect that someone would add a SlackBuild for libseat to slackbuilds.org once Slackware 15.0 has been released. Will you be its maintainer?

3 members found this post helpful.

The GNU coreutils package in Slackware is built with a configure-time option of DEFAULT_POSIX2_VERSION=199209. This was added back in 2006 to prevent packages using obsolete command line params from breaking. I'm wondering when the last time was that this was revisited, as I've encountered a problem that I traced back to this forced default, specifically that tail -c +[NUM] does not work (e.g. echo "abc" | tail -c +1 fails with tail: cannot open '+1' for reading: No such file or directory). This can be worked around by setting the environment variable _POSIX2_VERSION=200809. I'm going to override this system-wide and see if anything breaks.

3 members found this post helpful.