Dear Tumbleweed users and hackers,

Once again I dared not to be at my desk last Friday, which resulted in me having to cover two weeks of Tumbleweed updates again. Quite a few larger things are happening, and you certainly want to know what has been coming – and will be coming – your way. The review covers the 12 snapshots released since my last ‘weekly review’ (0119, 0121…0126, 0128…0201)

The most relevant changes to your Tumbleweed system have been:

  • rpm-config-SUSE: enable full ksym() dependencies in Tumbleweed
  • libvirt 10.0.0
  • PHP 8.2.15
  • NetworkManager-applet 1.36.0
  • Linux kernel 6.7.1 & 6.7.2. During the 6.7.1 lifetime, there were some package layout changes, which unfortunately resulted in build counters being reused; this had shown as ‘file conflicts’ in some cases. The later update to 6.7.2 solved this again for good.
  • PAM 1.6.0
  • Mesa 23.3.3 & 23.3.4
  • Ruby 3.3 (rebuild, to get all ruby3.3-rubygem packages built). Ruby 3.3 is the new system default. Ruby 3.2 is still in the repos, which in turn means zypper dup will not clean it up from your system. If you have Ruby mostly for yast, you can likely uninstall ruby3.2 without loss of functionality (make sure to carefully check the packages to be removed – if in doubt, week it installed)
  • Mozilla Firefox 122.0
  • Postfix 3.8.5
  • Ghostscript 10.02.1
  • cURL 8.6.0
  • RPM 4.19.1: some stricter spec file parsing. As a packager, make sure to read

These things are currently being staged and being prepared for future inclusion into Tumbleweed:

  • glibc 2.39
  • Python 3.12 (python modules built for it, but /usr/bin/python3 will still point to Python 3.11 for now)
  • GStreamer 1.22.9
  • QEmu 8.2.0: causes build failures of ovmf
  • dbus-broker: a big step forward; upgrades seem to be an issue that needs to be addressed
  • libxml 2.12.x: slow progress
  • openSSL 3.2.0
  • c-ares 1.21.0: nA new cycle has formed: appstream-glib, c-ares, curl, googletest, nghttp2, python311. This should be eliminated, as cycles cause massive trouble when branching new code streams
  • GCC 14: our usual 2-phase approach to introduce it. Currently working on phase 1, meaning GCC14 will be providing the base libraries (libgcc_s1, libstdc++…). The compiler itself will stay at version 13 for now.

Once we integrate glibc 2.39 plus the python 3.12 changes, we will let OBS sort the dep chain for the new Python 3.12 modules, as this task is not handled by our external bot that usually takes care of the rebuild strategy. This will result in a huge snapshot, likely to be published early next week.