Requests for -current (14.2-->15.0)

atelszewski · 01-26-2022, 12:54 PM

Hi,

a couple of smalish issues in /etc/rc.d/rc.bluetooth:

- shebang is not set to bash,

- there is no protection for starting the service more than once.
Maybe you could reimplement this using daemon?

- the script always exits with status 1. This because:

Code:

grep -v '^[[:space:]]*(#|$)' /etc/bluetooth/uart.conf | while read i; do

in start_uarts() returns 1 if there are no matching entries in /etc/bluetooth/uart.conf.

Hope this helps! :-)

--
Best regards,
Andrzej Telszewski

marav · 01-26-2022, 01:23 PM

Quote:

Originally Posted by atelszewski

Hi,

a couple of smalish issues in /etc/rc.d/rc.bluetooth:

- shebang is not set to bash,

- there is no protection for starting the service more than once.
Maybe you could reimplement this using daemon?

- the script always exits with status 1. This because:

Code:

grep -v '^[[:space:]]*(#|$)' /etc/bluetooth/uart.conf | while read i; do

in start_uarts() returns 1 if there are no matching entries in /etc/bluetooth/uart.conf.

Hope this helps! :-)

--
Best regards,
Andrzej Telszewski

Hi, Andrzej,
some elements of response

Code:

blackstar:~:# checkbashisms /etc/rc.d/rc.bluetooth  
blackstar:~:#

no bashism, so #/bin/sh seems appropriate

Code:

blackstar:~:# ps faux | grep "[b]luetoothd"
root      1340  0.0  0.0   6836  4232 ?        S    08:52   0:00 /usr/sbin/bluetoothd

blackstar:~:# /etc/rc.d/rc.bluetooth start
Starting Bluetooth services:  bluetoothd hciconfig D-Bus setup failed: Name already in use
sdptool hciattach

blackstar:~:# ps faux | grep "[b]luetoothd"        
root      1340  0.0  0.0   6836  4232 ?        S    08:52   0:00 /usr/sbin/bluetoothd

the service is started only once

Code:

blackstar:~:# /etc/rc.d/rc.bluetooth stop 
blackstar:~:# echo $?                    
0

baldzhang · 01-26-2022, 02:20 PM

mkinitrd: support modules compressed with xz.

Code:

--- mkinitrd.orig	2022-01-25 11:37:53.000000000 +0800
+++ mkinitrd	2022-01-26 15:16:16.949987620 +0800
@@ -763,7 +763,7 @@
         fi
 
         if ! grep -Eq " $(basename $SRCMOD .ko)(\.| |$)" $SOURCE_TREE/load_kernel_modules 2>/dev/null ; then
-          LINE="$(echo "modprobe -v $(basename ${SRCMOD%%.gz} .ko)" )"
+          LINE="$(echo "modprobe -v $(basename ${SRCMOD%%.ko*})" )"
 
           # Test to see if arguments should be passed
           # Over-ride the previously defined LINE variable if so

Nobby6 · 01-26-2022, 02:51 PM

Today ISC is pleased to announce the release of BIND 9.18.0

This is the first stable release that contains support for DoT and DoH.

This new release of BIND is available for download from the Internet
Systems Consortium web site (https://www.isc.org/downloads)

Significant work covered in the 9.18.0 branch includes:

- Support for securing DNS traffic using Transport Layer Security (TLS).
TLS is used by both DNS-over-TLS (DoT) and DNS-over-HTTPS (DoH).
- Support for zone transfers over TLS (XFR-over-TLS, XoT) for both
incoming and outgoing zone transfers.
- The dig tool is now able to send DoT queries (+tls option).
- Support for OpenSSL 3.0 APIs was added.

You can read more about this new edition of BIND in the release notes:

9.18.0: https://downloads.isc.org/isc/bind9/...nd-9.18.0.html

Didier Spaier · 01-26-2022, 03:10 PM

Nobby6: the Release Notes mention a known issue and a lot of removed features and feature changes and also mentions under End of Life:

Quote:

BIND 9.18 is a stable branch, suitable for production use. After it has been in production use for a while it will be designated as an Extended Support Version (ESV). Until then, the current ESV is BIND 9.16, which will be supported until at least December 2023

Whether it is preferable to make new bind users happy or possibly cause trouble to current bind (and Slackware) users is up to Patrick J. Volkerding...

PS that the next (maybe minor) version after 15 be provided at the beginning of 2024 would make everybody happy (sorry, I couldn't resist...).

atelszewski · 01-26-2022, 03:22 PM

Hi,

@marav @rc.bluetooth

- Slackware is moving /etc/rc.d towards Bash, so bash is more apropriate nowadays :-),

- what I mean by no protection against double start is that, if you do rc.bluetooth start twice in a row, a DBus related error will be spit out, instead of the more general approach of saying "hey, I am already running, go bug someone else" :-).

Cheers!

--
Best regards,
Andrzej Telszewski

marav · 01-26-2022, 04:48 PM

Quote:

Originally Posted by atelszewski

Hi,

@marav @rc.bluetooth

- Slackware is moving /etc/rc.d towards Bash, so bash is more apropriate nowadays :-),

- what I mean by no protection against double start is that, if you do rc.bluetooth start twice in a row, a DBus related error will be spit out, instead of the more general approach of saying "hey, I am already running, go bug someone else" :-).

Cheers!

--
Best regards,
Andrzej Telszewski

Yep. thx & sorry for the noise ;-)

volkerdi · 01-26-2022, 07:27 PM

Quote:

Originally Posted by atelszewski

- what I mean by no protection against double start is that, if you do rc.bluetooth start twice in a row, a DBus related error will be spit out, instead of the more general approach of saying "hey, I am already running, go bug someone else" :-).

Yeah, I didn't do anything about that issue (yet), but the rest of it seemed good. Thanks!

marav · 01-26-2022, 09:31 PM

Firefox 91.5.1esr

Release notes (when avalaible)
https://www.mozilla.org/en-US/firefo.../releasenotes/

marav · 01-27-2022, 03:36 AM

Pipewire 0.3.44

https://gitlab.freedesktop.org/pipew.../-/tags/0.3.44

This is a bugfix release that is API and ABI compatible with previous
0.3.x releases.

Code:

Highlights

- It is now possible to run a minimal PipeWire server without a session
manager, enough to run JACK clients.
- The maximum buffer size is now configurable and can be larger than
the previously hardcoded limit of 8192 samples. When using high sample
rates, the larger buffer size can avoid xruns.
- The default maximum latency was reduced from 170ms to 42ms. This should
improve overall latency for application that ask for a large latency,
such as notifications.
- Better JACK compatibility. Patchbays should now get less confused about
ports appearing and disappearing.
- Fix some bluetooth crashes.
- Fix some races in ALSA device detection.
- Many bug fixes and improvements all over the place.

ctrlaltca · 01-27-2022, 07:59 AM

Not a request but just a heads-up, Plasma 5.24 will be an LTS release: https://community.kde.org/Schedules/Plasma_5
but with 5.24.0 getting released on feb 8 and surely needing a couple of weeks to get to a mostly bugfree .1/.2 patch version, this is probably off the deadline.

Windu · 01-27-2022, 08:08 AM

Quote:

Originally Posted by ctrlaltca

Not a request but just a heads-up, Plasma 5.24 will be an LTS release: https://community.kde.org/Schedules/Plasma_5
but with 5.24.0 getting released on feb 8 and surely needing a couple of weeks to get to a mostly bugfree .1/.2 patch version, this is probably off the deadline.

I sincerely hope he does not wait for Plasma 5.24!
This has exactly been the issue for the past years - there is always an update right around the corner, you just need to wait a few days more. And then nothing gets finalized, shrink-wrapped and handed over to happy customers.

marav · 01-27-2022, 08:10 AM

Quote:

Originally Posted by ctrlaltca

Not a request but just a heads-up, Plasma 5.24 will be an LTS release: https://community.kde.org/Schedules/Plasma_5
but with 5.24.0 getting released on feb 8 and surely needing a couple of weeks to get to a mostly bugfree .1/.2 patch version, this is probably off the deadline.

Plasma 5.24 release : 8/02
Slackware 15.0 release : 2/02

Haha

LuckyCyborg · 01-27-2022, 09:11 AM

Quote:

Originally Posted by ctrlaltca

Not a request but just a heads-up, Plasma 5.24 will be an LTS release: https://community.kde.org/Schedules/Plasma_5
but with 5.24.0 getting released on feb 8 and surely needing a couple of weeks to get to a mostly bugfree .1/.2 patch version, this is probably off the deadline.

Well, according with even the KDE developers, would be an extremely bad idea to use a Plasma LTS series.

Quote:

Originally Posted by Nate Graham

No KDE developer I know uses the Plasma LTS release. Working on old crappy code isn’t any fun. Backporting fixes is a thankless task. I think we would probably have to pay someone to be the full-time LTS developer-and-backporter if we wanted to have an LTS product worth of its name. It will most likely need to be on the back burner for a while.

https://pointieststick.com/2021/11/

Let's hear them, as probably they know about what they talk, and let's stay away of this unworthy crap.

After all, it's useful like a massage at a wood leg, because LTS is ONLY the KDE Plasma, while the KDE Frameworks and KDE Applications are released always as usual pace.

bender647 · 01-27-2022, 09:19 AM

Boost 1.78.0 fixes build issues on -current with povray.

https://www.boost.org/users/history/version_1_78_0.html

Probably 3, maybe 4 deps link to libboost so not risk free.