Dear Tumbleweed users and hackers,
What a bad decision of mine to include snapshot 0510 in the review before it hit the mirrors. Now I have barely anything to report this week. Only a single snapshot found its way to you: 20170516. On May 16th is when the openSUSE infrastructure was ‘released’ again to the openSUSE Release managers, as the audit of the events of the previous weekend had been completed.
We build/tested two more snapshots this week ((0517 and 0518) which both will not find their way to you. I’ll explain further down why.
So, let’s first focus on the positive side of things: snapshot 0516 released with some updates:
- Another batch of KDE Applications 17.04.0
- Boost fixed a regression which caused a build failure in quite some packages
Of course, there could not be that much in this snapshot, as the community did also not have access to the build server over the weekend and could not provide any updates.
That leads to a big backlog though, and the things that are coming to you shortly are numerous:
- KDE Applications 17.04.1
- KDE Framework 5.34.0
- KDE Plasma 5.10 is already being tested (beta state, will hit Tumbleweed once it reaches final release
- openSSL 1.0 and 1.1 will be parallel installable
- GCC 7 as default compiler for Tumbleweed. We are almost there!
- GStreamer 1.12 – with MP3 and A52 support enabled right away
Now, what happened to the two snapshots which are built bot won’t be released? Generally, a collection of things. For one, a regression in openQA caused some failures that needed to be understood. And due to the nature of the breakage, some test suites could simply not be run. And I don’t want to release a only partially tested snapshot out into the wild. I’m sure you will be hit by the corner cases we did not catch (this is the worst case of course. I would not expect there to be a problem. But I don’t gamble on the stability of your workstation).
The 2nd issue that arose now with snapshot 0518 is that the changes in openSSL packaging, making 1.0 and 1.1 able to co-exist nicely, caused a failure in bind, the major DNS server software used. Bind simply refuses to start in the current setup.
A solution to both issues is expected early next week, which means we can then resume releasing Tumbleweed.