All meeting minutes can be found here: https://etherpad.opensuse.org/p/ReleaseEngineering-meeting Meeting is hosted here https://meet.opensuse.org/ReleaseEngineeringMeeting ## Attendees DimStar,GuillaumeG, Sarah, Rbrown, lkocman, ddemaio, DocB, maxlin ## Leap Waiting for a new Leap build Leap Builds were stuck on https://bugzilla.suse.com/show_bug.cgi?id=1206718 kernel was accepted yesterday Cisco openh264 setup is finialized on our side - http://codecs.opensuse.org/ big thanks to openSUSE Heroes and Adrian for finalizing publishing Changes to https://en.opensuse.org/OpenH264 No response from cisco on my request Code submission deadline for any SLES 15 SP5 related features in a week fro now. I'm bit concerned that we'll have to shift schedule a bit given the fact that we were stack on SLES 15.5 Feature tracking at https://code.opensuse.org/leap/features/issues Legaldb issues https://github.com/openSUSE/cavil/issues/62 that seems to cause serious delays ## openSUSE Tumbleweed openSUSE:Factory build fail stats: 21 failed 24 unresolvable (last week: 22 / 4) https://tinyurl.com/ysy4nnnz * Most work for the x86-64-vN multiarch libs should be in place, RPM as one of the last missing bits should be merged this week (allowing us to co-install -vN builds based on hwcaps for specifically identified libs) * Ruby 3.2 made some progress, only 3 more yast build fails in Staging:H * Staging:L has a few failures collected: * boost: breaks libreoffice (incl. libetonyek) * gpg2: breaks gpgme * libpcap: breaks meson's test suite * Staging:N openssl-3-as-default testing * Various announcer emails are not going out: seems -Current iso files are no longer symlinks (or not followe symlinks?) DimStar noticed it on MicroOS x86_64 i586 carve-out from Factory * openSUSE:Factory:LegacyX86 is setup and builds are in a similar state as openSUSE:Factory * Bots are already up and running: ttm, pkglistgen, trigger-rebuild for rebuild=local * openQA is setup https://openqa.opensuse.org/group_overview/75 => Migration (manual so far) is possible for users. The first 'zypper dup' after changing the repo could include a bunch of 'package downgrades' as the rebuild counters are not synced across projects. Automatic migration of users (by means of openSUSE-release) will happen by end of January (giving the braves ones time to test and report issues before we mass-switch) * We plan to switch to 4096bit RSA key begin of 2023. Keys are added to the openSUSE-build-key for Leap 15.x. Marcus: the 15.3, 15.4 key was updated. 15.4 continues to rebuild. I'd like to do it for 15.5 during the development phase. Then I'd switch it for only for 15.5 and TW , but not 15.4. We need to handle transition effort for 15.4 as it will switch from 2k to 4k key. ## Richard (MicroOS) Desktop-GNOME: The Road to Release: transactional-update-notifier is in Factory! Finally! Working on a "mod-check" tool to report the following to users List of installed (1st party) packages, with comparisions to both an upstream pristine list and previous snapshots Automatically reset official packages to that upstream pristine list, or previous snapshots Any 3rd party packages and their origin Any known unsupported configurations/alterations and offer remedies if possible mod-check doesn't really 'check' as much as planned at the moment, instead going way further and effectively reinstalling MicroOS Desktop (GNOME) in place, making that new snapshot the new boot target. This will be awesome for any user who wants to 'freshen' up an otherwise heavily altered MicroOS Desktop, or when major Tumbleweed/MicroOS changes occur that otherwise cant be easily modeled in patterns. It also potentially could be a method of migrating non-transactional systems to a transactional one. Heavy testing/development underway..and possibly a rename if mod-check doesn't start actually -checking stuff soon. Bugs still WIP osinfo-db still doesn't recognise MicroOS as a seperate distribution - debates with upstream ongoing Working on YaST-less installation media with FDE by default ## Max Leap Micro 5.4 * The project has been bootstrapped * The missing bits ** Tweak Leap specific patches ** Enable pkglistgen lkocman: is on it Leap 15.5 * The fixed kernel for bsc#1206718 has got merged to SLE15-SP5(just yesterday) * Build stats in Backports(x86_64): 8 unresolvables, 59 fails(last week: 8 unresolvables, 54 fails) ## Guillaume - Arm Tumbleweed: * Rolling, but e-mail with changes for 20230116 has not been sent (See Tumbleweed section above). * WiFi is broken on RPi3/4 (and other systems) with kernel 6.1. A fix has been submitted upstream - https://bugzilla.suse.com/show_bug.cgi?id=1206697 * Pointer Authentication issue, seen in zypper. Fixed upstream, gcc13 should be updated soon in Factory - https://bugzilla.suse.com/show_bug.cgi?id=1206684 * 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: covered by Leap section above * 15.5 armv7 now in openQA: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=106 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. 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 Tumbleweed * kdump is fixed (with calibrate.conf by SLE because of blocked builds for s390x) -> Tumbleweed is rolling again Leap: * tests are failing because of timeout (my next ToDo) * qore updated Question: What should we do with packages buildable only on s390x and not on x86? Example: https://build.opensuse.org/package/show/home:AdaLovelace:branches:server:dat... lkocman: I'd start with a bug against the package, then let's agree on next steps with maintainer. Please use bug against openSUSE.org choose 3rd party package. Can be used for anything that is from OBS. ## Doug * Updating openSUSE wiki * Summarizing release manager info for those who can help maintain other architectures * GSoC * Closing out issues * Workshop to finalize projects & application scheduled for on Feb. 7 (deadline at 18:00 UTC) * oSC23 * PO made * Waiting on contract signature * 10 registered, 8 submissions * FOSDEM * Booth in Building/Hall H (we have traditionally be in Building/Hall K) * Bus has 29 sign ups * Article about booth location & activities published * Contact ddemaio if you're in Nuremberg and want to take the bus to FOSDEM. Space may be limited. * FLOSS Weekly podcast schedule for Feb. 8 ## Dirk Not available * Continued work on SUSE:ALP:RISCV bootstrap issues - looking into the java stack which can not be built within ALP * force published 15.4 and 15.5 for armv7 builds, openqa builds have been triggered it appears it is set to do post-release testing? * qemu/libseccomp 15.5 failure still in investigation * made a x86_64-baseline with x86_64-v3 hwcaps prototype for Tumbleweed. Seems successful, has open issue on debuginfo and auto- installation of the v3 optimized version. Performance benefit seems hard to measure. Biggest speedup can be observed by switching zlib to zlib-ng, so looked into fixing the build failures caused by switching to zlib-ng-compat ## Wolfgang (Package Hub), Scott Bahling Not available 15 SP5 Package HUB channel is set up. Stefan did initial testing and looks good. Some packages are still missing, this is on agenda for today and next week. The workshop regarding Package HUB equivalent for ALP Lubos will schedule a call with wolfgang and Scott to ensure that they're in loop for the High Level requirements document. https://en.opensuse.org/openSUSE:ALP/Workgroups/Community/Workshops/Consumig... Package Hub for SLE-15-SP5 product definition added and SCC is currently picking it up so it will be ready for testing with the beta of SLE-15-SP5 ## Maintenance team (Marcus or Maurizio (m4u)) Fixed a long standing issue with gnome-music that was blocking openqa for a long time. 15.4 is working 5.3 is working 15.5 setup TBD (Mid-to-End February would be preferred). Nothing worrysome, preannoucement for 15.3 EOL was sent to mainling list End of December 2022. There were three chromium updates in single week. 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. ## Adrian - OBS DimStart pointed me to the fact that ftp-trees with factory ppc and s390x are not building. It seems to be caused by a smallest worked who is not large enough to handle the cache (caching of all rpms takes about a 1 TB) and it times out. New year cleanup requesting removal of repositories building against EOL distros. ## Project maintainer work flow Status * Base policy to be developed Background on topic found at https://etherpad.opensuse.org/p/ReleaseEngineering-20221221 For me it comes down to a matter of communication. A note like 'thx for your SR, I think we should adapt the following ' or ' we are reviewing your SR, and quite stuck with work...' could already change a lot. Silence for more then 4 week is clearly a perfect way to annoy contributors. And the question should be asked if those unresponsive maintainers are still willing to maintain their projects. Or they may even not be active anymore, another discussion we are having