Looks better now:

$ rpm -ql busybox | grep sbin | xargs ls -lgo
-rwxr-xr-x. 1 1409840 Jan 10 23:03 /usr/sbin/busybox
lrwxrwxrwx. 1       9 Jan 10 23:03 /usr/sbin/busybox.musl.static -> ./busybox

$ rpm -ql busybox | grep sbin | xargs ldd
/usr/sbin/busybox:
        not a dynamic executable
/usr/sbin/busybox.musl.static:
        not a dynamic executable

Chromium 105.0.5195.125 works nicely, yes. Are there any plans to update the chromium package to the latest stable release for Fedora 37? The security updates from November looked quite scary.

Seen this too, on an upgrade run, and reproducible via dnf reinstall --debuglevel=10 kernel-core-5.9.16-200.fc33.x86_64. Not many more details here though:

[...]
Reinstall: kernel-core-5.9.16-200.fc33.x86_64
  Reinstalling     : kernel-core-5.9.16-200.fc33.x86_64                     1/2 
  Running scriptlet: kernel-core-5.9.16-200.fc33.x86_64                     1/2 
Reinstalled: kernel-core-5.9.16-200.fc33.x86_64
  Running scriptlet: kernel-core-5.9.16-200.fc33.x86_64                     2/2 
  Cleanup          : kernel-core-5.9.16-200.fc33.x86_64                     2/2 
  Running scriptlet: kernel-core-5.9.16-200.fc33.x86_64                     2/2 
sort: fflush failed: 'standard output': Broken pipe
sort: write error

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe
sort: write failed: 'standard output': Broken pipe
sort: write error

RPM transaction over.

Hm, instead of removing the expired cert from the CA store, this update...ignores the expired certificate now?

$ gnutls-cli host:443
[...]
- Certificate[2] info:
 - subject `CN=COMODO RSA Certification Authority,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB', issuer `CN=AddTrust External CA Root,OU=AddTrust External TTP Network,O=AddTrust AB,C=SE', 
serial 0x2766ee56eb49f38eabd770a2fc84de22, RSA key 4096 bits, signed using RSA-SHA384, activated `2000-05-30 10:48:38 UTC', expires `2020-05-30 10:48:38 UTC', pin-sha256="grX4Ta9HpZx6tSHkmCrvpApTQGo67
CYDnvprLg5yRME="
- Status: The certificate is trusted. 

Thanks for fixing this so quickly! Installing this version pulls in libgnome-keyring and now Nextcloud credentials are remembered.

$ sudo dnf install https://kojipkgs.fedoraproject.org//packages/nextcloud-client/2.6.4/4.fc31/x86_64/nextcloud-client-{,libs-,nautilus-}2.6.4-4.fc31.x86_64.rpm
[...]
Installing dependencies:
 libcloudproviders
 libgnome-keyring
[...]

Fixes #1566706 for me - thanks!

No more SELinux alerts when accessing NFS shares on the same machine, yay!

No more warnings when enabling/disabling Bluetooth, yay!

OK, so for some reason the last updates to nagios-plugins* (or upgrading from F25 to F26) broke nagios-plugins-load- and nagios-plugins-procs:

$ /usr/lib64/nagios/plugins/check_load -w 20,15,10 -c 30,25,20
CRITICAL - You need more args!!!
Error opening

$ /usr/lib64/nagios/plugins/check_procs -w 400 -c 450
Unable to read output

Maybe some kind of overflow? ISTR to have seen this somewhere before...

In other news, nagios-plugins-ide_smart is now working, as the nrpe user is added to the nagios group during installation (and check_ide_smart is still owned by root:nagios, so that works):

Jul 13 18:56:39 disko usermod[2551]: add 'nrpe' to group 'nagios'
Jul 13 18:56:39 disko usermod[2551]: add 'nrpe' to shadow group 'nagios'