All meeting minutes can be found here: https://etherpad.opensuse.org/p/ReleaseEngineering-meeting The meeting is hosted here https://meet.opensuse.org/ReleaseEngineeringMeeting ## Attendees DimStar, GuillaumeG, ddemaio, lkocman, wolfgang, dirk, maxlin We tried https://meet-test.opensuse.org/ReleaseEngineeringMeeting so far it was a pleasant experience ## Leap Leap 15.5 a new build finally looks good. Leap Micro 5.4 is Beta since yesterday https://news.opensuse.org/2023/03/28/leapmicro-54-beta-hands-on/ Prepping for the Devconf mini conference @Brno on Friday. 15.4 image respin based on QU2 - TBD Leap 16.0 Putting high level requirements for Alpha. I think I could have something usable by end of this week. https://en.opensuse.org/Portal:16.0 So far everything shows that base system will have traditional 12 months + overlap support. ## openSUSE Tumbleweed openSUSE:Factory build fail stats: 200 failed 53 unresolvable (one week ago: 479 / 94) https://tinyurl.com/ysy4nnnz * GNOME 44 was published shortly after made avaialble by upstream. (0324) * Staging:C: openssl 3.1 incoming; a few packages failing to build * Staging:O: preparation work to identify the minimal list of 'i586' builds to enable in openSUSE:Factory to allow wine/steam to build/install (currently ~1800 packages) i586 carve-out from Factory => Automatic migration kicked off with snapshot 0201. The port is rolling Snapshot 0327 does no longer contain i586; users have been auto- migrated (when using default repos) since beginning of February. ## Richard (MicroOS) Distrobox Packaging container out and documented - https://en.opensuse.org/Distrobox#Distrobox_For_Packagers No negative feedback (yet?) lkocman: small change to wiki related to --root lkocman: we should add ca-certificates-suse (sr on the way) MicroOS Desktop users may be experiencing reboots managed by rebootmgr instead of the expected notifications - this is due to a mismatch in config between MicroOS Desktop branding packages and transactional- update. Working with the transactional-update maintainer on a proper solution, meanwhile creating an /etc/transactional-update.conf and setting REBOOT_METHOD=notify works around it ## Max Leap 15.5 * New snapshot 442.1 published with KDE updates * Focus on build fails in Backports * Build stats in Backports(x86_64): 3 unresolvables, 24 fails(last week: 7 unresolvables, 38 fails) ## Guillaume - Arm Tumbleweed: * Regression on aarch64 with gcc13 fixed (with an overlay in :ARM for now): https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109230 * Still building atm * NVIDIA: tester with aarch64 server and NVIDIA card wanted - Proprietary drivers are now available for aarch64 (only G06): https://download.nvidia.com/opensuse/tumbleweed/ - New opengpu driver also available in OBS: https://build.opensuse.org/project/monitor/X11:Drivers:Video lkocman to check on who is the aarch64 + nvidia effort blocked on. I recall that there was a chosen point of contact. Leap: * 15.5 aarch64: No aarch64 specific issues * 15.5 armv7: no blocker ALP: * No aarch64 specific issues WSL: * Works with x86 emulator since appx installer is x86-64, but this is not really an issue since arm64 Win11 includes x86 emulator by default. => Could we publish it on Microsoft store anyway? lkocman: Team is okay, but we need to make sure that such case is covered in openQA https://progress.opensuse.org/issues/126083. Steps documented on the wiki to install the appx from download.o.o: https://en.opensuse.org/openSUSE:WSL#With_Appx_from_openSUSE_download_server ## Sarah - s390x Not available Tumbleweed * release is rolling Leap: * bootloader issue after network configuration in textmode -> I will analyze kernel configuration suggestions by IBM: https://bugzilla.opensuse.org/show_bug.cgi?id=1188896 lkocman: Should I share it with Virt team + Ihno? How to handle qemu/kernel bug report (handled by SUSE in the past): https://bugzilla.opensuse.org/show_bug.cgi?id=1202727 other output than on x86 for backup software restic: https://bugzilla.suse.com/show_bug.cgi?id=1208665 -> forwarded as upstream issue (with hint, how to receive a s390x vm by IBM) ## Doug * Google Summer of Code * 10 Proposals Submitted; deadline April 4 (18:00 UTC) * Ranking session planned for April 25 (deadline April 27) * oSC23 * Meeting on 30.03 * Coordinated Keynote * Catering arranged * Sent technical info to Z-Bau * 76 registered, 48 submissions * Sent packages of marketing material * Updated logo/trademark links via commit & PR * GUADEC sponsorship lkocman: quiz for conference booths in openSUSE/artwork link TBD ## Dirk Experimented with a CDN for download.opensuse.org together with d.o.org admins (Andrii and Bernhard) * potentially > factor 5 latency improvement * Budget / funding tbd * also todo announce tumbleweed maintainer policy draft currently working on testing those in a private staging test project * Started ALP:RISCV builds in the new build setup Biggest speedup can be observed by switching zlib to zlib-ng, so looked into fixing the build failures caused by switching to zlibo-ng- compat ## Wolfgang (Package Hub), Scott Bahling * Moved duplicated packages to subpackages for SLE-15-SP5 (thanks to Max for the list of packages) * Packages in subpackages for SP5 is up to the level of SP4 (still considering putting more packages there because of migration from Leap to SLE) * patterns-mate added to openSUSE:Backports:SLE-15-SP5 (thanks Max) ## Maintenance team (Marcus or Maurizio (m4u)) Not available 15.5 setup is done - Do we want to swap key for the 4096 rsa key now? Done lkocman: We're still not in RC phase, so better now than later. openSUSE:Leap15.5 would be affected for now, backports are bit more challenging because of SLES. Wolfgang: we're injecting the key. Marcus we probably want to do only Backports 15 SP5 for now. Marcus is working also on the SLES side, the update of package with the new key was released last week, it's just not activated yet, but it will be already trusted by Leap 15.5 systems. 15.4 is working 5.3 is working 5.4 testing is now passing as well Leap 16.0 - we should revisit the update/sle repo as the current setup not exactly mirror friendly. Solutions could be dropping not so popular architectures or split repositories per architecture. securebootkey for SLES was rotated, it should be autotrusted and not noticeable. This will be in QU3, QU2 is already done. 15.5 setup is done (status 21.2.2023). lkocman needs to do official 15.5 Maint setup request beta in ~2 weeks lkocman: 15.3 EOL could lead to stopping our physical Source DVD effort, as it seems we will not produce. As this was the last release which you could still get on a physical media. Lkocman: anything against decomissioning it? Configuration setup problem for Maintenance of Leap 15.4 maintenance updates / openQA Marcus regarding Leap 15.4 Image respin - package set will change, we do need to refresh the packagelist * Lubos to talk to Jan Stehlik, we can't put all on Marcuses shoulder. https://etherpad.opensuse.org/p/ReleaseEngineering-20221110-maintenance-disc... Confirmation that QA/QA-maint team will oversee the setup (issues) Lubos: I was asked to provide requirements for the QA team. Mostly for the GA/current release but also for the update. Lubos will make wiki with requirements (something like maintenance plan perhaps). Marcus will review it. * Leap Micro 5.3 maint setup done ffmpeg - (still unsolved) possible file conflict on the next update, no idea how to avoid vendor switching at the moment. Removing the patch on the openSUSE side (that might contain security fixes) or releasing update on the packman side could fix the issue. Lubos to give Marcus some working contact for the team. (Was done, Olaf Hering) ## Adrian - OBS No updates lkocman: Please reach out to legal@suse.de ## Open Floor metrics-o-o https://metrics.opensuse.org/ https://github.com/openSUSE/openSUSE-release-tools/tree/master/metrics/acces... openSUSE Leap 15.4 stats are suspiciously spiking up. Is it an anomaly are we accidentally countining in openQA? Doug mentioned that we have suddenly have increased sales of openSUSE stuff in Germany. So he is not surprised. We're still investigating if the data is valid. Doug is already on it with Witek, Witek is trying to apply filtering only the HTTP code that is 200 (40X is not currently filtered out).