Dear Tumbleweed users and hackers,

This week was truly crazy for the staging masters — apologies to Ana for flooding you with requests. Many contributors have been busy preparing our packages for RPM 4.20 (which is still at least half a year out – but we preferred to fix things now rather than being under pressure then). When the effort started on Feb 20, we had 2066 spec files that would have failed to build with RPM 4.20. Today, just 10 days later, we have less than 700 – and many requests in the queue to address those.

Of course, that’s not everything that happened this week. We have again delivered six snapshots (0223, 0225, 0226, 0227, 0228, and 0229) with the following changes:

  • libjxl 0.10.0 & 0.10.1 (this time the update went without fallout)
  • Samba 4.19.5
  • Linux kernel 6.7.6
  • mdadm 4.3: stricter on naming devices posix compliant
  • Mozilla Firefox 123.0
  • chrony 4.5
  • openSSH 9.6p1
  • fwupd 1.9.14
  • exiv2 0.28.2
  • Ruby 3.2 has been removed: this includes all the ruby gems AND the ruby 3.2 interpreter

The staging lists and backlog are largely filled with the same old topics:

  • ImageMagick 7.1.1.29
  • Python 3.x fixes for CVE-2023-6597 (TmpDir cleaning)
  • openblas 0.3.26: breaks python-networkx, and python-scikit-learn
  • openjpeg 2.5.1: breaks ghostscript
  • KDE Frameworks and Plasma 6: Staging turns out to be messy
  • KDE Gear 24.02.0 – Requires KDE Frameworks 6
  • Systemd 255.3
  • python 3.9 deprecation: we decided to postpone this a little but, due to the still large fallout from Python 3.12 addition. Removing a Python flavor will require us to rebuild all the Python packages for the new builds to drop the python39 flavor. Too many packages fail to build at this moment.
  • dbus-broker: a big step forward; upgrades seem to be an issue that needs to be addressed
  • libxml 2.12.x: slow/no progress
  • GCC 14: phase 2: use gcc14 as the default compiler