Hi FESCo,
Below are a list of changes that appear to be incomplete, or are still on either ASSIGNED or MODIFIED states in bugzilla after the Testable deadline with no updates posted as comments. I have added a comment to each change tracking bug requesting a status update, so this ticket is for awareness only.
System-Wide Changes
Stable SSID MAC addresses Tracker #2258088 Owner: @sfaye @till
Remove Python Mock Usage Tracker #2258085](https://bugzilla.redhat.com/show_bug.cgi?id=2258085) Owner: @gotmax23 @salimma
Enable IPv4 Address Conflict Detection by Default Tracker #2258083 Owner: @bengal @ihuguet
LLVM 18 Tracker Bug #2258084 Owner: @tstellar
Build Fedora Cloud Edition Images Using Kiwi in Koji Tracker Bug #2260081 Owner: @davdunc
java-21-openjdk as the system JDK in F40 tracker Bug #2262141 Owner: @pmikova
Boost 1.83 Upgrade Bug Tracker #2258089 Owner: @ppalka
Enable systemd service hardening features for default system services Tracker Bug #2260082 Owner: @metherid
Changes/Linker Error On Security Issues tracker Bug #2254787 Owner: @nickc
Modernize Thread Building Blocks for Fedora 40 Tracker Bug #2552075 Owner: @jwakely
SPDX Licence Phase 3 Bug Tracker #2258888 Owner: @msuchy
removing OpenSSL 1.1 package Tracker bug #2258090 Owner: @dbelyavs
GNU ToolchainF40 tracker Bug #2260083 Owner: @codonell
SQL Alchemy2 Tracker Bug #2249679 Owner: @nphilipp
Porting Fedora to Modern C Tracker Bug #2142177 Owner @fweimer
Ostree Native container Phase 2 Tracker Bug #2151321 Owner @walters @jmarrero @baude
KTLSSupportForGnuTLS Tracker Bug #2130000 Owner: @fkrenzel @ueno
DNF/RPM Copy on Write enablement for all variants Tracker Bug #1915976 Owner: @malmond @dcavalca @chantra
Self-Contained Changes
ROCm 6 release [Tracker Bug #2262138]( Owner: @trix
PytTorch release Tracker Bug #2262139 Owner: @trix
Haskell GHC 9.6 and Stackage LTS 22 Tracker Bug #2258070 Owner: @petersen
Podman 5 Tracker Bug #2258071 Owner: @lsm5 @mboddu
F40 MariaDB & MySQL repackaging Tracker Bug#2252771 Owner: @mschorm
PostgreSQL 16 Tracker Bug #2251109 Owner: @fjanus
Switch bogofilter to use SQlite Tracker Bug #2252772 Owner: @mikep
Enable auto-updates by default in Fedora Kinoite Tracker Bug #2233192 Owner: @siosm
mkosi-initrd Tracker bug#2203221 Owner: @zbyszek @ngompa
Unified Kernel Support Phase 2 Tracker Bug #2258073 Owner: @kraxel @vittyvk
Huh? I'm not involved in this Change.
I'm deferring this change to Fedora 41. Thanks.
We are mostly on track for the first part (producing container images) of this change for F40 on the Atomics desktop side but it's likely not going to be completed in whole for Fedora 40 (no installer and not the default).
So it's probably safe to say it will be for Fedora 41.
As Aoife is on vacation, I went through the changes today, updated statuses where appropriate, did deferrals that were requested, and regenerated the changeset page. I believe the list of changes still not deferred or set to at least MODIFIED is now:
This list has some that weren't in Aoife's initial list, I think she was working from a somewhat older version of the Changeset page.
Metadata Update from @zbyszek: - Issue tagged with: meeting
My change https://fedoraproject.org/wiki/Changes/Unify_bin_and_sbin is missing from this list. It also didn't get a tracker bug. Unfortunately, I need to postpone it for F41, because it needs to be done before the mass rebuild, and I very much missed the deadline for F40.
@ngompa apologies that was likely a typo on my part, looking at too many changes might have booggled my mind a bit!
@adamwill thank you kindly for updating the list while I was on vacation - it is very much appreciated :) One or two of the changes that weren't on my original list were being actively discussed in the blocker review & FESCo meetings, so I omitted them on purpose. In future should I include all changes in this report?
@zbyszek apologies, I remember processing the change, so I suspect there was a typo somewhere caused the bz script to miss assigning a tracker bug to it. Thank you for re-assigning it to F41, I will keep a close eye on it to make sure it receives a tracker bug for that release.
Remove Python Mock Usage
This change was re-targeted to F41, so it can be removed from the list.
We discussed this during today's FESCo meeting:
Updates: All deferred changes to F41 have now been re-targeted. Please let me know if there is any errors and I will correct.
The owner of https://fedoraproject.org/wiki/Changes/SystemdSecurityHardening has indicated that progress is slow, with only one PR merged to date and two still remaining. They suspect they will need to defer given the pace of the work. You can view the comment in the tracker bug https://bugzilla.redhat.com/show_bug.cgi?id=2260082
A self-contained change was missed when assigning a tracking bug: https://fedoraproject.org/wiki/Changes/Fedora_IoT_Bootable_Container This has now been corrected and assigned a tracker for F40 https://bugzilla.redhat.com/show_bug.cgi?id=2266470 As per the discussion with the proposal owner, the change is on track 'Everything is on track, the container is now included in our compose and we're on to the testing phase. We've hit an initial bug that should be fixed in our next compose.'
The change https://fedoraproject.org/wiki/Changes/ArmMinimalImageOSBuild has also now been assigned a tracker bug following Mondays approval of the change.
AGREED: Changes/FedoraSilverblueBootupd is deferred to F41 (+6, 0, 0) (@zbyszek:fedora.im, 20:29:23)
Arg, sorry, I forgot to update this bug. This ready in Fedora 40 so we don't need to defer it to Fedora 41.
Hi,
the update is now built and ready in f40 side tag (https://koji.fedoraproject.org/koji/taginfo?tagID=84857). We rebuilt the java stack and the build failure count is minimal - we are now fixing the last few remaining build failures. The freeze exception bug was filed (thank you Adam Williamson) as https://bugzilla.redhat.com/show_bug.cgi?id=2267486
The Bodhi update link: https://bodhi.fedoraproject.org/updates/FEDORA-2024-129d8ca6fc
We would really appreciate if the update could make it through; we aim to always have the newest stable JDK as a system JDK in Fedora to encourage users to keep their applications up to date, to match the fast development and release cadence of OpenJDK. The feature is finished and we are confident that it doesn't bring any major breaking changes, which would seriously disrupt the update.
In any way this turns out, we will respect your decision.
Thank you and see you tonight at the FESCO meeting.
Please create an actual Bodhi update, if you think it's ready. The mere existence of a Bodhi update is not significantly disruptive, the dist-git commits would be much trickier to unpick if we decided not to go ahead with this. An undesired update can just be unpushed.
This was discussed during the FESCo meeting on 2024-03-04: AGREED: Late merging of Changes/Java21 is accepted, provided that it happens no later than Wednesday March 6th. Otherwise the change will be postponed to F41. (+5, 1, -1)
FEDORA-2024-ba2b883c48 (System JDK bump from JDK 17 to JDK 21 - prometheus-jmx-exporter) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-ba2b883c48
For LLVM: we (FESCo) previously approved the late landing of LLVM. So we're still waiting for that to land.
For Changes/KiwiBuiltCloudImages and Changes/ArmMinimalImageOSBuild: AGREED: kiwi change and minimal ARM image change may still land (+5, 0, 0)
https://bodhi.fedoraproject.org/updates/FEDORA-2024-129d8ca6fc with java-21-openjdk-21.0.2.0.13-2.fc40 and 361 other packages landed in F40 stable on 2024/03/07, so we're good here.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-bde3811225 is in testing. There were some issues, but they have been resolved. We're waiting for more feedback.
This was merged, reverted, and resubmitted, and merging is blocked waiting on some other changes.
I'll unset meeting, since there doesn't seem to be anything that requires discussing today.
meeting
Metadata Update from @zbyszek: - Issue untagged with: meeting
I think we should look into the state of things during today's meeting:
https://bugzilla.redhat.com/show_bug.cgi?id=2258084 (LLVM 18) is still in progress. https://bugzilla.redhat.com/show_bug.cgi?id=2258090 (Removing Opessl 1.1) is waiting for python2.7 PR, but that seems almost ready. https://bugzilla.redhat.com/show_bug.cgi?id=2260081 (Cloud image kiwification) is in progress, but the state is complicated.
https://bugzilla.redhat.com/show_bug.cgi?id=2260082 (systemd service hardening) made a bit of progress, but not much.
I think the other items are on track.
LLVM 18 is basically done - it was pulled into Beta candidate builds - but I intentionally didn't want to push it stable (thus into the buildroot) while we were still doing Beta candidates in case it broke build of something important. Now Beta is done, the 18.0 update was pushed stable. There is now an 18.1 update pending. Neither of those has a mesa build, I don't know if it is planned to rebuild mesa with LLVM 18 before Final or not - @frantisekz ?
Cloud image kiwification is done as of Beta.
Neither of those has a mesa build, I don't know if it is planned to rebuild mesa with LLVM 18 before Final or not - @frantisekz ?
That would be up to mesa maintainers I'd guess, I've added spirv-llvm-translator17 to the first update, so mesa can be built against an older version of llvm. The question is if it should - already asked at https://src.fedoraproject.org/rpms/mesa/pull-request/48 .
@jexposit ^^
This was discussed during today's FESCO meeting:
TOPIC: #3173 F40 Change Proposal Status: Incomplete Changes
INFO: https://bugzilla.redhat.com/show_bug.cgi?id=2269411
LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2258084
INFO: LLVM 18 is effectively complete. (@zbyszek:fedora.im, 19:44:47)
LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2258090
LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2260081
INFO: Cloud image kiwification is done as of Beta. (@zbyszek:fedora.im, 19:49:25)
Removing Opessl 1.1 is waiting on a pull request for python2.7...
For clarification, that is python3.6, not python2.7.
The change owner for https://fedoraproject.org/wiki/Changes/DefaultBpfman confirmed with me that they are re-targeting the change for F41. The change page has been updated to reflect this and tracker bug added for F41 release.
@amoloney can you also regenerate the F41 ChangeSet page so it will include that one? it's generally a good idea to regenerate the ChangeSet pages frequently when changes are accepted or delayed or...you know...anything :)
Roger that, change set page is now regenerated!
We went over this again in today's FESCo meeting:
Metadata Update from @jistone: - Issue untagged with: meeting
Since I think we are all ok here now, I am going to close this. If there's anything missing, please reopen.
Metadata Update from @kevin: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)