devel October 2026

devel@lists.fedoraproject.org

33 participants
23 discussions

Orphaning WebKitGTK
by Michael Catanzaro 07 Oct '26

07 Oct '26

Hi, I'm planning to orphan WebKitGTK in Fedora since I'm leaving my job at Red Hat at the end of this month. I think Red Hat no longer intends to maintain this package. If anybody wants to own it, let me know. This package is not terribly difficult to maintain downstream, but it does require keeping up pretty closely with upstream updates. The volume of CVEs is considerable, so please only take the package if you're comfortable with watching for upstream releases and preparing those releases for all supported versions of Fedora. The main risk is s390x-specific build failures, since that architecture is not tested or supported upstream.

5 9

HEADS UP: Updating OpenColorIO to 2.6
by Richard Shaw 07 Oct '26

07 Oct '26

I plan to update OpenColorIO to 2.6 later this week. There are no ABI changes but upstream did bump the SONAME anyway. All dependent packages rebuilt in COPR[1]: OpenImageIO: OpenImageIO2.5: blender: krita: luxcorerender: olive: usd: Thanks, Richard

1 1

RFC: splitting perf out of the kernel packaging
by Michel Lind 07 Oct '26

07 Oct '26

Hi all, For background: back in January, Neal and I presented a kernel refactoring proposal at CentOS Connect https://cfp.fedoraproject.org/centos-connect-2026/talk/X9JHNV/ This is informed by our work in CentOS' Hyperscale SIG, which builds faster-moving backports (many coming from Fedora) and rebuilds stock CentOS Stream packages with additional features. So - some of our work there could potentially feed back to Fedora; see my previous CentOS Showcase talk for examples - https://cfp.fedoraproject.org/centos-showcase-2024-11/talk/PTV8JM/ For the particular case of perf, we think it might make sense to split out the packaging from the kernel and build it standalone, for the reasons below: - while perf is mostly stable on x86_64, on aarch64 it is still getting a lot of fixes. e.g. the last update I made incorporated 20 cs-etm fixes: https://gitlab.com/CentOS/Hyperscale/rpms/perf/-/commit/8f8b93b559f9204d118… - perf build has some BuildRequires that are not needed for building the kernel itself. Isolating the builds help reduce the number of BRs needed on both sides (including, yes, *Java*) - separating the two makes it easier for interested contributors to help out - the kernel.spec is huge and kernel-ark packaging takes a while to get used to. - Also while kernel modules need to be specially signed for Secure Boot, perf does not need to be! - one pain point we have is that perf headers inconsistently show up in kernel-headers. If, say from F46 onwards perf is shipped standalone and perf-devel is the only place that ships perf headers, we can at least stop special-casing this. see e.g. https://gitlab.com/CentOS/Hyperscale/rpms/perf/-/blob/8f8b93b559f9204d1188b… - perf's maintainer (acme) has mentioned in the past that almost nobody consumed the standalone perf tarballs - indeed, 6.15 came out with a bug where some aarch64 headers were left out so the tarball cannot be used to build on that architecture. With a standalone packaging, like in Hyperscale, we can consume the upstream tarball, but fall back to using the full Linux tarball when necessary (or generating our own tarballs from specific Git tags; the makefile targets make this easy) Hoping to get some discussions going, and especially buy in from Justin Forbes (cc:ed) - if generally this seems like a good idea, we're going to submit a Change Proposal for Fedora 46. Anyone interested is welcome to join, we're hoping to have at least the two of us and Justin onboard. Best regards, -- _o) Michel Lind _( ) https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 README: https://fedoraproject.org/wiki/User:Salimma#README

5 5

rpminspect
by Alejandro Lopez 07 Oct '26

07 Oct '26

Hi, rpminspect is reporting errors in my MR <https://src.fedoraproject.org/rpms/sudo/pull-request/40>. The reported problem is that "/usr/bin/sudo in sudo on x86_64 carries insecure mode 4111" which is true, but it has been like this for years. Additionally, sudo is listed in the fileinfo file <https://codeberg.org/rpminspect/rpminspect-data-fedora/src/commit/3387fc6cb…> . Did something change in the testing environment? Am I doing something wrong? Thank you. -- Alejandro

5 8

Summary/Minutes from today's FESCo Meeting (2026-10-06)
by Fabio Valentini 06 Oct '26

06 Oct '26

===================================== # #meeting:fedoraproject.org: fesco ===================================== Meeting started by @decathorpe:fedora.im at 2026-10-06 17:02:10 Meeting summary --------------- * TOPIC: Init Process (@decathorpe:fedora.im, 17:02:24) * LINK: Meeting Agenda https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… (@decathorpe:fedora.im, 17:06:03) * TOPIC: #3664 Requirements and Investigation Ticket Tracker for Fedora's (@decathorpe:fedora.im, 17:07:05) * LINK: FRCL JIRA ticket for "Bugzilla Part 3" https://redhat.atlassian.net/browse/FRCL-106 (@decathorpe:fedora.im, 17:08:37) * TOPIC: #3682 F45 Incomplete Changes Report (@decathorpe:fedora.im, 17:10:34) * TOPIC: F45 Incomplete Changes Report: Encapsule devel containers (@decathorpe:fedora.im, 17:12:10) * INFO: The package reviews have been processed and ideally this would land in Fedora 45 before GA via a freeze exception. (@decathorpe:fedora.im, 17:18:59) * TOPIC: F45 Incomplete Changes Report: Relocate RPM repository configs (@decathorpe:fedora.im, 17:19:37) * AGREED: fedora-third-party adaptations are completed, FESCo elects to mark fedora-third-party updates a blocker for Fedora Linux 45. (+8, 0, -0) (@decathorpe:fedora.im, 17:25:17) * ACTION: ngompa to file a blocker bug for the pending update (@decathorpe:fedora.im, 17:25:42) * TOPIC: #3687 Reaffirm provenpackager policy bounds (@decathorpe:fedora.im, 17:30:09) * ACTION: everyone to look at proposed wording and vote in ticket. (@decathorpe:fedora.im, 17:34:08) * TOPIC: #3689 Offboard FESCo member: duffy (@decathorpe:fedora.im, 17:35:41) * TOPIC: Council happenings (@decathorpe:fedora.im, 17:44:06) * LINK: Agenda for next Council meeting (Oct. 7, 2026): https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… (@decathorpe:fedora.im, 17:47:24) * TOPIC: Open Floor (@decathorpe:fedora.im, 18:01:13) * TOPIC: Next Week's Chair (@decathorpe:fedora.im, 18:02:03) * ACTION: zbyszek to chair next week (@gotmax23:fedora.im, 18:03:57) * TOPIC: Open floor (again) (@gotmax23:fedora.im, 18:04:02) Meeting ended at 2026-10-06 18:10:45 Action items ------------ * ngompa to file a blocker bug for the pending update * everyone to look at proposed wording and vote in ticket. * zbyszek to chair next week People Present (lines said) --------------------------- * @decathorpe:fedora.im (101) * @gotmax23:fedora.im (73) * @nirik:matrix.scrye.com (57) * @conan_kudo:matrix.org (50) * @salimma:fedora.im (33) * @zodbot:fedora.im (32) * @siosm:fedora.im (17) * @supakeen:fedora.im (16) * @zbyszek:fedora.im (16) * @amoloney:fedora.im (5) * @meetbot:fedora.im (3)

1 0

Fedora 45 is in final freeze
by Samyak Jain 06 Oct '26

06 Oct '26

Hi all, Today, 2026-10-06, is an important day on the Fedora Linux 45 schedule [1], with significant cut-offs. Today we have the Final Freeze [2], which starts at 14:00 UTC. This means that only packages which fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted, and packages can move to the 'updates' repository. Pending updates will be pushed before final release as zero-day updates. Regards, Samyak Jain Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-45/f-45-key-tasks.html [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/f45/final/buglist

1 0

Schedule for Tuesday's FESCo Meeting (2026-10-06)
by Fabio Valentini 06 Oct '26

06 Oct '26

Following is the list of topics that will be discussed in the FESCo meeting Tuesday at 18:00 Europe/London in #meeting:fedoraproject.org on Matrix. To convert Europe/London (UTC/UTC+1) to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d 'TZ="Europe/London" 2026-10-06 18:00' Links to all issues to be discussed can be found at: https://forge.fedoraproject.org/fesco/tickets/issues?labels=6114 = Discussed and Voted in the Ticket = N/A = Followups = #3664 Requirements and Investigation Ticket Tracker for Fedora's Bugzilla Replacement https://forge.fedoraproject.org/fesco/tickets/issues/3664 #3682 F45 Incomplete Changes Report https://forge.fedoraproject.org/fesco/tickets/issues/3682 = New business = #3687 Reaffirm provenpackager policy bounds https://forge.fedoraproject.org/fesco/tickets/issues/3687 #3689 Offboard FESCo member: duffy https://forge.fedoraproject.org/fesco/tickets/issues/3689 = Council happenings = = Open Floor = For more complete details, please visit each individual issue. The report of the agenda items can be found at https://forge.fedoraproject.org/fesco/tickets/issues?labels=6114 If you would like to add something to this agenda, you can reply to this e-mail, file a new issue at https://forge.fedoraproject.org/fesco/tickets, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting.

1 0

Fedora Council Bi-Weekly Agenda: 2026-10-07
by Aoife Moloney 06 Oct '26

06 Oct '26

Please see below the discussion agenda for the upcoming council meeting. == Agenda == * Reminders and Announcements * Ticket Discussions: ** #513 - Conflict of Interest Guidelines https://forge.fedoraproject.org/council/tickets/issues/513 Summary: A solution has been proposed in the ticket and discourse thread. We will discuss this proposal, and hopefully have a clear path forward to close the issue. ** #578 - Flock to Fedora 2027 CfP Themes Brainstormin https://forge.fedoraproject.org/council/tickets/issues/578 Summary: Discuss cfp themes for Flock 2027 * Next Meeting Topics *Open Floor All welcome to join us at 1400 UTC in #meeting:fedoraproject.org. More information about the council meeting and rolling agenda can be found on the council meetings wiki page https://fedoraproject.org/wiki/Council_Meetings Minutes, summary and outcomes (if any) will be posted to discussions.fedoraprojet.org and here as an email reply. This agenda is also posted at https://discussion.fedoraproject.org/t/fedora-council-bi-weekly-meeting-age… -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney

1 0

PETsc release to 3.26
by sagitter＠fedoraproject.org 05 Oct '26

05 Oct '26

Hi all. PETSc will be updated in Rawhide/f45 branches in 7 days and all related dependencies rebuilt: $ fedrq whatrequires-src --branch rawhide --format source --exclude-subpackages petsc bout++ freefem++ getdp python-steps sundials Tested builds: https://copr.fedorainfracloud.org/coprs/sagitter/petsc3.26/builds/ --- Antonio Trande Fedora Project, User:Sagitter Website: antoniotrande.blog mailto: sagitter(a)fedoraproject.org GPG key: 0x6ea362cc4c1aeac10b3a5c5402b0e70b4933065a GPG keys server: https://pgp.mit.edu/

1 0

Backwards-incompatible change to python-openai coming to Rawhide/F45
by Stephen Gallagher 05 Oct '26

05 Oct '26

I'm not aware of any package other than `logdetective` using it (who requested this upgrade), but just to be aware: I am upgrading F45 and Rawhide to python-openai 3.24.0, up from 2.24.0. The two backwards-incompatible changes are: * Removal of the long-deprecated `/usr/bin/openai` CLI tool * HTTPX2 is now the default HTTP client, and httpx is no longer installed automatically. Applications using custom HTTPX clients, transports, or configuration objects must migrate to their HTTPX2 equivalents or use the temporary, runtime-only legacy HTTPX escape hatch. See the HTTPX2 migration guide[1]. For most projects, this should not have a meaningful impact, unless they were using custom HTTPX features. [1] https://github.com/openai/openai-python/blob/main/httpx2.md

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel October 2026