openSUSE Release Engineering meeting 14.12.2022
All meeting minutes can be found here: https://etherpad.opensuse.org/p/ReleaseEngineering-meeting Meeting is hosted here https://meet.opensuse.org/ReleaseEngineeringMeeting ## Attendees Sarah, rbrown, DimStar, lkocman, DocB, GuillaumeG, ddemaio, Gerald,maxlin, meissner ## Leap Christmas break starts for me on Monday 19th Dec. Leap 15.5 ftp-tree builds blocked on downloading of packages (Max tried retry, and it didn't help so far) 15.3 EOL this Dec (check news-o-o) Considering promoting yast-migration-sle from the tech preview state (approved by YaST team) Next step change docs (SLES docu-team is already aware) Chasing legal reviews might get even more difficult in near future, we might want to consider factory-like approach for community maintained packages. Factory accepts legal reviews within hour if not handled by legaldb, Leap could wait 3-4 days? Release Manager has an option to override this. Lubos to talk to Legal team * We plan to switch to 4096bit RSA key begin of 2023. Keys are added to the openSUSE-build-key for Leap 15.x. This will also include the SLES 15 key. Needs setup discussions for Leap. Code submission deadline for any SLES 15 SP5 related features (does not apply for 15SP4:Update etc), as well as Leap 15.5 Beta code-drop deadline is on January 25th 2023. 15.5 Feature tracking at https://code.opensuse.org/leap/features/issues Ongoing: SUSE Open Source policy review, SUSE Empoyees can participate https://opensource.suse.com/suse-open-source-policy (public facing url) I'd be happy for any feedback from community in form of e.g. email, since the github project SUSE/open-source-policy is private and limited to SUSE Employees as issues might contain discussion regarding confidential topics. Leap Micro 5.4 initial setup in place rename of JeOS to Minimal-VM seems to be finally finished This was a long struggle ## openSUSE Tumbleweed openSUSE:Factory build fail stats: 105 failed 2 unresolvable (last week: 80 / 5) https://tinyurl.com/ysy4nnnz * RPM 4.18 shipped as part of snapshot 1212 * Staging:J: Kernel 6.1 breaks quite a few builds, as early as the VM setup even happens. This seems not to be 100% reproducible (but happens often) which makes debugging slightly harder * Staging:H: initial tests with Ruby 3.2 as default (Pretty much all YaST breaks, plus webkit) * Staging:N: experiments with openssl-3 as default: main blocked are nodejs1[89] and openssh and ibmtss * Staging:O: gcc13 will be introduced and take over the 'library build' (the usual two-phase introduction we do with gcc); gcc12 will stay the default compiler for now 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 => the releases have been rolling on for the last three days, QA looks reasonable and things progress nicely. As planned, users should be able to migrate in January. We'll add some code to openSUSE-release in Tumbleweed to migrate repositories away when detected (with information logged of course) The maintenance of this port is uncertain though. Jiri Slaby volunteered, but that was back when the idea of having x86_64 there (and TW as v2) was current. As that decision was revised, I don't think Jiri is interested in maintaining i586; Felix Miata mentioned something, but no clear commitment to actually do it. I will keep an eye on it during the migration phase (just as I do with PPC and also s390x) - but no commitment, so things might fall over for weeks if not longer * We plan to switch to 4096bit RSA key begin of 2023. Keys are added to the openSUSE-build-key for Leap 15.x. ## Richard (MicroOS) Desktop-GNOME: The Road to Release: transactional-update-notifier is once again WIP after great feedback about why the current approach wasn't the best idea from a security standpoint Bugs still WIP osinfo-db still doesn't recognise MicroOS as a seperate distribution - debates with upstream ongoing General MicroOS Stuff: new podman, conmon, buildah all merged new os-update package Working on YaST-less installation media with FDE by default Lubos: Does D-installer fits "Yast-less"? Richard: It would, but its current model is installing different products - we only have 2 (Tumbleweed and MicroOS) but have far more reliance on system-roles (KDE Desktop, GNOME Desktop, Server, MicroOS Server, MicroOS Desktop, etc etc) Dirk: Curious on why this is not an issue on ALP? Richard: Unlike ALP, we utilize system-roles and we might have bit difficulty with getting request priotity over ALP Dirk: That is worth discussing with the ALP folks - to be taken offline. ## Max 15.5 * KDE update is not ready yet, it's still pending in staging * Update Cinnamon: did not get response from Cinnamon maintainer, and security believe the policy file can be removed from cinnamon-settings-daemon since it should be uselesss * Hits an bad host issue for ftp-tree build, we did retry many times but always end up to a pacakge download fail, https://build.opensuse.org/packages/000product:Leap-ftp-ftp-x86_64_aarch64_p... Build stats(x86_64): 47 build fails, 4 unresolvables(last week: 49 build fails, 4 unresolvables) ## Guillaume - Arm Tumbleweed: * Rolling * 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 Leap: * no update WSL: * Works with x86 emulator since appx installer is x86 lkocman: Can we document "steps" in wiki? https://en.opensuse.org/WSL GuillaumeG: Yes ALP: * aarch64 back in openQA ALP and sync with :ToTest sub-project: https://openqa.opensuse.org/group_overview/100 ## Sarah - s390 Bug (multi-arch) in openQA with unreadable fonts is fixed (https://bugzilla.opensuse.org/show_bug.cgi?id=1205585). Tumbleweed * Is rolling again Leap: * log file issue is fixed -> tests are green New s390x upstream enablements for qore and aircrack-ng (patches or new versions will be integrated before Christmas) ## Doug * FOSDEM * Bus has 19 sign ups * Contact ddemaio if you're in Nuremberg and want to take the bus to FOSDEM. Space may be limited. * Plan on publishing second ALP prototype article next week * Budget discussions provided some help * Forwarded freewear proceeds to board for decision * Published Leap 15.3 EOL * Working on "good commit messages" article * Will ship some marketing material to Austria * GSoC 2023 * Will have GSoC Workshop to generate momentum and grow mentors * Jan. 10 or 17 during normal community meeting time * https://etherpad.opensuse.org/p/GSoC2023WS * Planning to be guest on FLOSS Weekly podcast for Feb. 8 * Anyone interested in joining contact ddemaio * oSC23 * May 26 - 28 * EarlyEnablement team meeting before OSC, should we do extended event for other openSUSE Release team members? ## Dirk * 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)) 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 mls is fallback during Adrian's Christmas break Axel: there were some cleaning activities in OBS, to determine inactive users and related unmaintained projects. Is there anything going on? Adrian: the script checks a project or a package that has no changes for more than one year. It will create a delete request, that can be deleted. If there is no reaction there will be auto-acceptance in few days. Package can be always manually submitted back if the DR was missed. Users will not be deactivated. Adrian: User cleanup would have to be discussed with IDP team (SUSE IT). OBS is just a consumer. Lubos will create a request to suggest this action in Service desk. Adrian: if the user never logged in into OBS, that's probably a cleanup that could stay in touch. ## Open Floor Many submitrequests seem to be pending for a long time; even projects with 10 maintainers (e.g. hardware) seems to allow SRs to fall through the cracks lkocman: Could there be official wiki page proposing to chase "Factory maintainers" in such case? Gerald: Freebsd has 2 weeks maintainer timeout, then every other commiter (could be maintainer/contributor) can handle it. Richard: Root cause issue is that each devel project is its system. Dimstar: Some project are team centric (e.g. devel:langauages:python) some are more topic centric (hardware). Richard: Setting initial expectations like maintainer timeout should empower project maintainers. Adrian: If we have a defined timeout then we can have a list of packages for missing maintainer. Next steps: Early Enablement (Dominique's) team writes procedure, define it (maintain wiki, or perhaps create an attritubte). Factory maintainers would be still the last resort.
Hi, On 14. 12. 22, 12:52, Lubos Kocman wrote:
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 => the releases have been rolling on for the last three days, QA looks reasonable and things progress nicely. As planned, users should be able to migrate in January. We'll add some code to openSUSE-release in Tumbleweed to migrate repositories away when detected (with information logged of course)
The maintenance of this port is uncertain though. Jiri Slaby volunteered, but that was back when the idea of having x86_64 there (and TW as v2) was current. As that decision was revised, I don't think Jiri is interested in maintaining i586;
You are right ;). As I explicitly wrote in the e-mail I never intended to maintain ix86. I also asked there for maintainers and noone raised their hands. Does this mean noone is interested and we can drop the port at last? (Hint: it's the right time to wave your hands NOW.) That would render all the work Dominique and others invested into :LegacyX86 futile :/.
but no commitment, so things might fall over for weeks if not longer
Maybe it will prove noone cares when the project fails to build completely. Good riddance then. regards, -- js suse labs
On Thu, 15 Dec 2022, Jiri Slaby wrote:
Hi,
On 14. 12. 22, 12:52, Lubos Kocman wrote:
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 => the releases have been rolling on for the last three days, QA looks reasonable and things progress nicely. As planned, users should be able to migrate in January. We'll add some code to openSUSE-release in Tumbleweed to migrate repositories away when detected (with information logged of course)
The maintenance of this port is uncertain though. Jiri Slaby volunteered, but that was back when the idea of having x86_64 there (and TW as v2) was current. As that decision was revised, I don't think Jiri is interested in maintaining i586;
You are right ;). As I explicitly wrote in the e-mail I never intended to maintain ix86. I also asked there for maintainers and noone raised their hands. Does this mean noone is interested and we can drop the port at last? (Hint: it's the right time to wave your hands NOW.) That would render all the work Dominique and others invested into :LegacyX86 futile :/.
but no commitment, so things might fall over for weeks if not longer
Maybe it will prove noone cares when the project fails to build completely. Good riddance then.
At least since we are going to need a ix86 tree to build some 32bit support libraries for x86-64 we are likely at least keeping a ix86 Ring-0 building. So resurrecting ix86 should be possible later. The most "interesting" part will be old BIOS and 32bit kernel support of course. Richard. -- Richard Biener <rguenther@suse.de> SUSE Software Solutions Germany GmbH, Frankenstrasse 146, 90461 Nuernberg, Germany; GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman; HRB 36809 (AG Nuernberg)
Am Donnerstag, 15. Dezember 2022, 08:15:54 CET schrieb Jiri Slaby: ....
The maintenance of this port is uncertain though. Jiri Slaby volunteered, but that was back when the idea of having x86_64 there (and TW as v2) was current. As that decision was revised, I don't think Jiri is interested in maintaining i586;
You are right ;). As I explicitly wrote in the e-mail I never intended to maintain ix86. I also asked there for maintainers and noone raised their hands. Does this mean noone is interested and we can drop the port at last? (Hint: it's the right time to wave your hands NOW.) That would render all the work Dominique and others invested into :LegacyX86 futile :/.
As I'm still running 32bit HW I'm tempted to raise hand, but I'm not sure if this is not too deep in the engine room for my skills.... However, if I can help I'm happy to do so Cheers Axel
On 15.12.22 12:34, Axel Braun wrote:
Am Donnerstag, 15. Dezember 2022, 08:15:54 CET schrieb Jiri Slaby:
....
The maintenance of this port is uncertain though. Jiri Slaby volunteered, but that was back when the idea of having x86_64 there (and TW as v2) was current. As that decision was revised, I don't think Jiri is interested in maintaining i586;
You are right ;). As I explicitly wrote in the e-mail I never intended to maintain ix86. I also asked there for maintainers and noone raised their hands. Does this mean noone is interested and we can drop the port at last? (Hint: it's the right time to wave your hands NOW.) That would render all the work Dominique and others invested into :LegacyX86 futile :/.
As I'm still running 32bit HW I'm tempted to raise hand, but I'm not sure if this is not too deep in the engine room for my skills....
I would try to help you out if there are problems identified. I will, however, not have time to e.g. look at all the openQA tests or such. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
participants (5)
-
Axel Braun
-
Jiri Slaby
-
Lubos Kocman
-
Richard Biener
-
Stefan Seyfried