Dear Tumbleweed users and hackers,
Last weekend and the beginning of this week, Tumbleweed hit some small roadblocks. A minor change in the selinux-policy package—which looked (and was confirmed to be) obviously correct—resulted in various openQA failures where systems refused to boot due to SELinux enforcement rules.
Luckily, we had openQA to detect this early. After some head-scratching on Monday, we discovered that while the change itself was correct, other code was inadvertently “relying on the wrong behavior” of the previous policy. We always prefer identifying these issues in QA rather than locking users out of their systems. Once this was resolved, Tumbleweed resumed its natural glory and delivered three snapshots (0302, 0303, and 0304).
The main changes delivered in these snapshots were:
- Complete rebuild: all python312-* modules were removed, freeing build power to add python314-* modules. Such a change requires giving control to the OBS scheduler and relying on the internal logic, rather than using our own bots (that save some build time in regular days, but can’t cope with a full Python stack change without breakage)
- KDE Plasma 6.6.1 & 6.6.2
- Linux kernel 6.19.5
- postfix 3.10.8
- procps 4.0.6
- systemd 258.5
- PostgreSQL 18.3
Looking at the next snapshot in QA and the staging projects, we can predict these changes to reach you in due time:
- Shadow 4.19.4
- iptables 1.8.13
- gstreamer 1.28.1
- PackageKit 1.3.4
- kernel longterm 6.18.16
- KDE Gear 25.12.3
- Linux kernel 6.19.6
- systemd 259.3
- Switch default bootloader on uefi systems to systemd-boot (aligning tumbleweed to microos)
- GCC 16: our typical 2-phase introduction: first, we change libgcc to come from this compiler, later then use the compiler to build the distro)
- GNOME 50: RC is staged for QA; release planned for March 18
- glibc 2.43: metabug: https://bugzilla.opensuse.org/show_bug.cgi?id=1257250
Leave a Reply