openSUSE Tumbleweed – Review of the weeks 2019/48 & 49

Dear Tumbleweed users and hackers,

Once again I’m spanning two weeks; besides the normal work on getting you openSUSE Tumbleweed updated and timely delivered, the release team has been working together with the build service team to implement/stabilize the OBS-internal staging workflow. There is (should) not be any real noticeable difference for the contributors – except the new used URLs. The Factory Staging dashboard can now be found at https://build.opensuse.org/staging_workflows/1

During the last two weeks, we have pushed out 10 Tumbleweed Snapshots (1121, 1122, 1123, 1124, 1126, 1127, 1128, 1202, 1203 and 1204) containing those changes:

  • openSSL 1.1.1d
  • YaST updates
  • Linux kernel 5.3.12
  • Mesa 19.2.6
  • firewalld 0.7.2
  • bind 9.14.8
  • alsa 1.2.1
  • fprintd 0.9.0
  • Perl 5.30.1
  • QEmu 4.2.0-rc3

Currently, all stagings are full and a lot of things are happening – and OBS does not like me for this it seems. Stagings seem to progress a bit slower at the moment than they used to. But this could be just a timing issue as all stagings were rebased at the same time after the workflow switch. Hopefully, things will settle soon there. The notable changes being staged at the moment are:

  • RPM 4.15.0
  • Python 3.8
  • Rust 1.39.0: break Firefox and Thunderbird so far
  • libxml 2.9.10
  • Linux kernel 5.4.1
  • libvirt 5.10.0
  • KDE Frameworks 5.17.4
  • KDE Applications 19.12.0 (currently rc2 in testing)
  • Qt 5.14.0 (currently release candidate in testing)

3 responses to “openSUSE Tumbleweed – Review of the weeks 2019/48 & 49”

  1. Anton Mahler Avatar
    Anton Mahler

    Hello,
    with introduction of Perl 5.30.1 the dependency of the packet “amanda” was (and still is) broken in Tumbleweed.
    Is this already known by the team? Who needs to be informed if not?

    best regards,
    Anton

  2. Dominique Leuenberger Avatar

    We rebuild (attemped) everything against perl 5.30 – if things fail to build, there is nothing we can do except wait for the maintainer to catch up and submit fixes. As far as I can see, this did happen for amanda by now