Requests for current-next (15.0-->15.1)

HQuest · 05-07-2024, 08:13 AM

Quote:

Originally Posted by ponce

https://www.linuxquestions.org/quest...7/#post6493226

Helpful, but even if we remove any python related entry, there are still a few left:

Code:

at-spi2-core-2.52.0-x86_64-1:usr/lib/systemd
binutils-2.42-x86_64-1:usr/lib/ldscripts
glib-networking-2.80.0-x86_64-1:usr/lib/systemd
imagemagick-7.1.1_32-x86_64-1:usr/lib/perl5
iproute2-6.8.0-x86_64-1:usr/lib/iproute2

cwizardone · 05-07-2024, 09:48 AM

Quote:

Originally Posted by lostintime

Some time back Pat said 15.1 would have 5.27.x. I am hoping he sticks to his word.

At first glance (without looking under the hood) there doesn't appear to be much difference between kde5 and kd6. Some casual users might not even notice the difference.

lostintime · 05-07-2024, 10:26 AM

Quote:

At first glance (without looking under the hood) there doesn't appear to be much difference between kde5 and kd6. Some casual users might not even notice the difference.

Are Slackware users casual users?

I follow KDE discussions. Still not ready for prime time or what is considered Stable for an official Slackware release. Under the hood there are little things that have changed, such as ripping the System Settings evdev support for mice because of an underlying presumption that everybody is using libinput.

If history is some indication, often software is not "stable" until at least a x.3 or x.4 release. KDE 4 is an example and some might argue KDE 4 never was really stable.

Although I have no leverage with Pat's decisions, the next Slackware release is a dot-one release. I am comfortable that 5.27.x is appropriate for 15.1 and leave KDE 6.0 for Slackware 16.0.

Pat has been in this situation before with KDE. A few times he released Slackware only to see a version bump in KDE a month or two later. I'm glad he chooses stability over PR value.

Ok, I've said my piece. Back to regular scheduled programming.

cwizardone · 05-07-2024, 01:14 PM

Quote:

Originally Posted by lostintime

..........If history is some indication, often software is not "stable" until at least a x.3 or x.4 release. KDE 4 is an example and some might argue KDE 4 never was really stable...........

When KDE-4.0 was released I switched to Xfce and stay with it for years.
During that time KDE-4.x finally became stable and I switched back to it somewhere after the release of KDE-4.10.
Thanks to LuckyCyborg* I'm still using it to this day as I don't care for KDE-5 (or 6). I just don't like the looks of KDE-5 and, yes, I've tried all the "themes" to make it look more like KDE-4. Plus the KDE developers removed two or three "features." IIRC, one or two have bee added back in recent KDE-5 releases.
While using Xfce I found other applications to replace the KDE applications I liked, so those KDE apps are not missed.
In the end it is a matter of personal choice.

*https://www.linuxquestions.org/quest...es-4175722060/

LuckyCyborg · 05-07-2024, 01:34 PM

Quote:

Originally Posted by lostintime

Are Slackware users casual users?

BUT, what do you believe they are? MIT scientists? NASA engineers? Multimillionaire international companies?

But of course they are "casual" users - in fact they are some casual users, because everyone else was driven away by the LinuxPAM/Kerberos famine.

LuckyCyborg · 05-07-2024, 01:42 PM

Quote:

Originally Posted by lostintime

Although I have no leverage with Pat's decisions, the next Slackware release is a dot-one release. I am comfortable that 5.27.x is appropriate for 15.1 and leave KDE 6.0 for Slackware 16.0.

Honestly, I wonder IF is worth to ship a Slackware 15.1 release with Plasma5 some-when in 2025 (please note my high enthusiasm regarding the release date, now being on May 2024) when everybody else will ship a rock solid Plasma6 ...

Because even today Plasma6 is practically on pair with Plasma5 as stability. I talk about this practically, not ideologically. BUT be my guest to NOT believe me and to test the Plasma6 yourself.

So, sincerely I believe that's better to leave the Slackware 15.1 to have the same fate as Slackware 4.1 - a fine dot-one too. I guess you loved it!

reddog83 · 05-07-2024, 05:43 PM

glib2 2.80.1

Quote:

Overview of changes in GLib 2.80.1, 2024-05-07
==============================================

* Fix CVE-2024-34397: GDBus signal subscriptions for well-known names are
vulnerable to unicast spoofing (#3268, work by Simon McVittie, reported by
Alicia Boya García)

* Bugs fixed:
- GNOME/tracker-miners#315 3.7.0 - GLib-GIO-WARNING **: 09:27:12.186: Error
creating IO channel for /proc/self/mountinfo: Invalid argument (g-io-error-
quark, 13) (Ondrej Holy)
- #3268 CVE-2024-34397: GDBus signal subscriptions for well-known names are
vulnerable to unicast spoofing (Simon McVittie)
- #3287 Devhelp does not show indexes for GLib, GIO, or GObject (Philip
Withnall)
- #3289 readlink -f fails in CI on macOS (Simon McVittie)
- #3342 Crash in gdbus schedule_callbacks() due to missing NULL check before
g_str_equal() (Philip Withnall)
- !3954 [th/performance] add script for combining performance results
- !3959 [th/gobject-toggle-refs-check] Fix critical warning for toggle
notifications in g_object_ref()/g_object_unref()
- !3962 meson: Fix a needless recompilation of some gdbus tests
- !3966 girparser: Don't assume sizeof(size_t) == sizeof(void *)
- !3967 girparser: Allow time_t, off_t, etc. to appear in GIR XML
- !3969 Ported the first few documentation comments in `gio/gaction.c` to gi-
docgen
- !3970 girparser: Make sizes in integer_aliases more obviously correct
- !3972 girparser: Adjust signedness() macro
- !3973 glib/gvariant: fix compile error with GCC 14.0.1
- !3974 tests: Mark several additional tests as can_fail on GNU Hurd
- !3981 Backport !3979 "Use CPU_COUNT to get the number of set CPUs" to
glib-2-80
- !3992 Backport !3989 “completion: make gsettings work in nounset mode” to
glib-2-80
- !4004 Backport "Remove unused cmph files" for glib-2-80
- !4021 Backport !4019 “gunixmounts: Use fallback if libmount monitoring
fails” to glib-2-80
- !4025 Backport !4005 “Fix various bugs found by scan-build“ to glib-2-80
- !4029 Backport !4028 “gdbusconnection: Fix a crash on arg0 matching” to
glib-2-80
- !4032 Backport !4031 “gdocumentportal: Handle EROFS and similar errors more
gracefully” to glib-2-80
- !4039 Backport !4038 “gdbusconnection: Don't deliver signals if the sender
doesn't match” to glib-2-80

https://download.gnome.org/sources/g...-2.80.1.tar.xz
https://download.gnome.org/sources/g...80.1.sha256sum

glennmcc · 05-07-2024, 07:35 PM

Quote:

Originally Posted by reddog83

glib2 2.80.1

https://download.gnome.org/sources/g...-2.80.1.tar.xz
https://download.gnome.org/sources/g...80.1.sha256sum

Yet again, stuff coming from gnome.org
so, I say again... https://www.linuxquestions.org/quest...ml#post6460546

jloco · 05-07-2024, 08:28 PM

Quote:

Originally Posted by glennmcc

Yet again, stuff coming from gnome.org
so, I say again... https://www.linuxquestions.org/quest...ml#post6460546

If extra/ was expanded to be a "Disk 2", if one goes with the DVD size standard, would give about 4.7GB more for just about all the FOSS projects one could stuff in it.

This is the one true dream. Bring back the disk sets!

reddog83 · 05-07-2024, 10:34 PM

adwaita-icon-theme-legacy 46.0

Quote:

A fullcolor icon theme providing fallback for legacy apps.

https://gitlab.gnome.org/jimmac/adwa...n-theme-legacy

https://reddoglinux.ddns.net/linux/g...-theme-legacy/

Here are my slackbuild and slack-desc file's based on adwaita-icon-themes,there has been much talk from the Plasma developer Nate Graham as seen here https://gitlab.gnome.org/GNOME/adwai...e/-/issues/288 , the developer jimmac has brought the legacy icons back.

jloco · 05-07-2024, 11:02 PM

Quote:

Originally Posted by reddog83

adwaita-icon-theme-legacy 46.0

Here are my slackbuild and slack-desc file's based on adwaita-icon-themes,there has been much talk from the Plasma developer Nate Graham as seen here https://gitlab.gnome.org/GNOME/adwai...e/-/issues/288 , the developer jimmac has brought the legacy icons back.

Once upon a time in the not-too distant past, slackware's adawaita-icon-theme package also did retain these symlinks. At some point on -current (actually between version 41.0 & 42.0) the package was upgraded and this was left behind. Since, it's gotten much smaller, so one can assume it's just a straight packaging of what gnome is shipping, which, yes, is broken as all hell. I used to make myself a package by dumping the latest over the 3.38 package and doing a makepkg, it worked well enough for me, but maybe one could take the older source, and the newer source and smush it into one proper release again as well. It really wasn't as difficult as those guys are making it out to be.