From Feb 09 to Feb 15

The primary focus across many groups this week was the upcoming Fedora 44 Beta freeze. Teams were busy finalizing changes, preparing for the code completion deadline, and scheduling blocker review meetings to address release-critical issues. Alongside this release work, a major ongoing effort is the migration of infrastructure and issue trackers from Pagure to the new Forge/Forgejo platform, a topic of significant discussion for the Council, Infrastructure, and EPEL teams. Package lifecycle management was another common theme, with proposals to deprecate unmaintained packages like python-dateutil, efforts to retire packages that consistently fail to build, and work to finalize the removal of python-mock. Finally, the week marked a key milestone with the completed transition to Packit as the default CI for Fedora dist-git.

📣 Announcements

This week's announcements covered significant project milestones and package maintenance activities. The transition to Packit as the default CI for Fedora dist-git has been completed, with updated documentation now available. Looking ahead, developers were reminded that the Fedora 44 Beta freeze and code complete deadline is set for February 17. The weekly Community Update highlighted the successful completion of the Fedora 44 mass branching and progress across various teams, including Infrastructure, QE, and Forgejo.

On the packaging front, a new change proposal for Fedora 45 suggests deprecating the python-dateutil package, as its upstream is unmaintained and may have security issues. Additionally, housekeeping efforts are underway, with an announcement identifying 167 inactive packagers who risk removal from the packager group. Finally, there is a plan to retire packages that have failed to build from source for an extended period in March.

Council

The Council's primary discussion during its weekly meeting revolved around the contentious migration of their issue tracker from Pagure to Forgejo. The debate focused on the best method for preserving historical data, particularly for sensitive Code of Conduct cases, leading to the task being reassigned to find a path forward. The group also discussed the recent Fedora Strategy Summit, with daily summaries available for community review and a public video meeting scheduled for February 25 to present the outcomes. Updates were also shared on the Flock to Fedora 2026 Call for Proposals, which has now closed with 113 submissions under review.

Decisions Taken

• Syria was officially approved for removal from the Fedora Export Control Policy, unblocking access for users in the region. A formal announcement is being prepared.

FESCO

During the weekly FESCo meeting, several changes for Fedora 44 were approved, including the shift of the TeXLive 2025 update, support for WhisperCpp in ibus-speech-to-text, and the move to build Fedora CoreOS on Konflux. A new internal process was also adopted for handling ticket approvals more responsively. The majority of the meeting was dedicated to reviewing the status of incomplete F44 changes, where it was decided that the Podman 6 update would be moved to Fedora 45, while others like the removal of Python Mock usage are being pushed for completion. A proposal to limit FESCo member terms was deferred for further feedback.

In the forums, new Change Proposals were submitted to FESCo for a vote, including one to restrict ptrace by default for F45 and another to update to Pandas 3. A new proposal was introduced to deprecate the unmaintained python-dateutil package, sparking discussion about its large number of dependents and the difficulty of migration. There was also significant follow-up discussion on the NodeJS alternatives change to address issues found in the build system, leading to a concrete proposal and a proof-of-concept pull request to ensure unversioned binaries are always available.

Decisions Taken

• Shift TeXLive 2025 change (#3562): The change to move the TeXLive 2025 update to Fedora 44 was formally approved.
• ibus-speech-to-text WhisperCpp support (#3556): The change was approved, with a recommendation to package at least one small model.
• Build FCOS on Fedora Konflux (#3546): The change to move the Fedora CoreOS build process to Konflux was approved.
• Ticket Handling Process (#3561): A new process was agreed upon where the member casting the deciding vote on a ticket is responsible for marking it as approved.

Magazine

This week, the Magazine team's discussions focused on a critical login issue affecting the Fedora Magazine WordPress instance. Several members reported being unable to log in using their FAS accounts, receiving an "invalid-iss" error. The problem, also raised in an older related topic, was identified as a bug in the OIDC authentication plugin. An infrastructure ticket was filed, and the issue was promptly investigated and resolved, restoring login access.

Decisions Taken

• The login issue on the Fedora Magazine WordPress site was fixed by updating the authentication plugin.

Workstation

This week, the Workstation Working Group held its regular meeting on February 10. Key discussions centered on the future of the ABRT crash reporting tool, following the recent removal of its GUI and the non-functional status of its retrace server. The group also evaluated a request for a freeze exception for a new QR code login feature in GNOME, expressing concerns about its large scope and lack of a testable specification. A plan was formulated for the ongoing maintenance of Rust packages, which is critical for the upcoming GNOME 50 release. Other topics included addressing repeated breakage of the background logo extension and improving wallpaper quality. Additionally, an announcement was made for the upcoming Fedora 44 Blocker Review Meeting, and the agenda for the next working group meeting was set.

Decisions Taken

• A plan was established for updating critical Rust packages: the packager on duty will coordinate with Fabio directly in the public Matrix channel to ensure transparency and document the process.
• The gnome-shell-extension-background-logo will be kept for now. Matthias Clasen will contact the maintainer to ensure it remains functional, and Neal Gompa will update its packaging to properly declare its dependency on GNOME Shell versions to prevent silent breakage.
• The group decided against getting officially involved in the wallpaper design process, though individual members are encouraged to participate. The topic will be discussed again next week to seek a clear response from the Design Team on a long-standing request for branding consistency.

KDE

This week, the KDE group's activity consisted of announcements for two meetings scheduled for the following week on February 16, 2026. An announcement was made for the Fedora 44 Blocker Review Meeting to discuss proposed blockers and freeze exceptions for the upcoming Fedora release. Additionally, a reminder was sent out for the regular KDE SIG meeting to discuss open topics related to the Special Interest Group. No decisions were made or significant discussions took place during this period.

Server

This week's activity for the Server group was centered on technical issues and coordination. The planned Fedora Server meeting on February 11 was cancelled shortly after starting due to low attendance and connectivity problems. The main technical discussion, which took place on the mailing list, revolved around a bug in Rawhide qcow2 images that prevented logins after initial setup. Adam Williamson confirmed this was a known Anaconda/SELinux issue and that a fix has been merged, also providing a temporary workaround. The group also received an announcement for the upcoming Fedora 44 Blocker Review Meeting.

Decisions Taken

• The Fedora Server meeting on 2026-02-11 was cancelled.
• The scheduled meeting time was to be used by attendees for individual testing of reported issues.

Infra & Releng

During their sprint planning meeting, the Infra & Releng team reviewed past work and set goals for the next sprint. The primary theme for both teams is the migration of repositories to Forge. The team celebrated successes from the previous sprint, including the smooth migration of registry.fp.o to quay.io and a successful mass branching for the new Fedora release. However, a significant blocker was identified: the Pagure staging instance (stg.pagure.io) has been broken since late January, which has impacted some RelEng work and requires a fix. Alongside the Forge migration, the RelEng team is also preparing for the Fedora 44 Beta freeze, which begins on February 17th.

Decisions Taken

• The main focus for the next sprint will be migrating Infrastructure and RelEng repositories to Forge.
• The Release Engineering team will begin preparations for the Fedora 44 Beta freeze.
• The meeting proceeded in Matrix, but the team will clarify the format (text vs. video call) for future sprint planning sessions.

Infrastructure

This week, the Infrastructure team focused on several key areas. Progress was made on the complex Pagure to Forge migration, with new forge messages becoming available that will help with syncing the Ansible repository; a production migration is tentatively planned for the following week. The team also spent significant time investigating issues with Anubis and Cloudfront, with a learning session on Anubis being planned to increase team familiarity. Operational tasks included the successful move of storinator01 to a new datacenter and catching up on reboots for servers that missed a recent mass update.

Community and documentation work was also prominent. A forum discussion was held on a proposal to provide daily incremental exports of the Datanommer database to assist the Data WG, a change that was met with positive feedback. On the mailing list, a user reported a persistently out-of-date mirror, which was subsequently disabled. Internally, a pull request to reorganize the team's Standard Operating Procedures was approved to improve documentation discoverability. Finally, the team welcomed back contributor Vit Smoliicek.

Decisions Taken

• The pull request to reorganize the Standard Operating Procedures (SOPs) documentation was approved for merging.
• Ticket #12643 related to a pagure/src issue was closed due to inactivity.
• The outdated Init7 mirror in Switzerland was disabled following a user report.

Releng

This week, the Releng team held its weekly meeting to discuss improving the "Post-branch Freeze" process, as the current method of delaying build signing causes problems with update gating. A potential solution was proposed to add a feature to Bodhi that would allow administrators to temporarily restrict the creation of updates for a newly branched release. The team also checked on the status of retiring FTI packages and confirmed readiness for the upcoming Beta Freeze. Additionally, an announcement was posted for the Fedora 44 Blocker Review Meeting scheduled for the following week.

Decisions Taken

• An investigation will be conducted into the complexity of implementing a Bodhi feature to temporarily restrict update creation on a new branch to admins only.
• A follow-up will be performed to ensure the task to retire FTI packages in a NEW state is completed.

Quality

This week, the Quality group's main activity was a Test Day for GRUB Out-of-Memory fix verification, part 2, which ran for the entire week to help test a fix for an installation issue on specific hardware. The group also prepared for the upcoming week by announcing a Fedora Quality Meeting and a Fedora 44 Blocker Review Meeting. The blocker review meeting agenda includes reviewing 6 proposed blockers and 5 freeze exceptions for the Beta release, and 4 proposed blockers for the Final release.

Design

During the single Fedora Design meeting this week, the team discussed logistics and creative direction. They explored using Google Meet and Gemini for future meetings to improve note-taking and decided that Alan Turing will be the inspiration for the Fedora 45 wallpaper. A significant discussion was held about reviving the supplemental wallpapers program. The team acknowledged that the old process and tools are outdated and a new, simpler submission method, such as a forum thread, would be required.

Decisions Taken

• The inspiration for the Fedora 45 wallpaper will be Alan Turing.
• Merge Request #4 for the Fedora Project Logos was approved for merging once more context is available.
• The outdated wiki page for supplemental wallpapers will be taken down.

Docs

During their weekly meeting, the Docs team discussed strategic updates and content planning. A key update came from CentOS Connect, where a plan was formed to create a Proof of Concept using Fedora Docs as an "upstream" for a CentOS mail service tutorial. The team also reviewed their contributor documentation strategy, deciding to simplify their approach by removing outdated guides and focusing on refining existing content to link to external resources. For the Quick Docs site, the group agreed to prioritize auditing and cleaning up existing content to remove or relocate outdated pages before considering a larger restructuring of the site's information architecture.

Decisions Taken

• Contributor Documentation: The team will simplify its contributor guides by dropping outdated GitLab and Pagure guides. The local authoring guide will be refined to link to external resources rather than duplicating comprehensive tutorials.
• Quick Docs Strategy: The immediate priority for Quick Docs is content, not structure. An audit will be conducted to "jettison" (remove, retire, or move) outdated or misplaced content before any redesign is attempted.
• CentOS Collaboration: A Proof of Concept will be developed using Fedora Docs as an "upstream" for a CentOS tutorial, starting with a guide on setting up a mail service.

Legal

The Legal team discussed the licensing of test data and assets shipped with the Goose software package. The issue arose during a package review regarding a PNG image and several data files that upstream developers believed might be AI-generated. Following advice from Richard Fontana, it was determined that most of the data files were either too trivial to be a copyright concern or otherwise acceptable for inclusion. The packager decided to remove the PNG image to avoid any potential complications.

Decisions Taken

• Several sets of data files included in the Goose package's test suite were approved for inclusion in Fedora.
• A specific PNG image file will be removed from the Goose package to avoid potential copyright issues, as its origin could not be definitively confirmed.

Packaging

This week, the Packaging group saw the final phase of a major infrastructure change and a new proposal for organizing packaging-related projects. The migration from Zuul to Packit for dist-git CI reached a key milestone with the disabling of Zuul runners for RPM projects. On the mailing list, a Request for Comments was posted proposing the creation of a "packaging" organization on forge.fedoraproject.org to house the Fedora Packaging Guidelines and tools like rpmdevtools and fedora-review.

Additionally, a user-reported packaging issue was discussed, where removing the openshot package via GNOME Software also removed git and numerous other dependencies, pointing to a potential bug in dependency handling. There was also renewed interest in the long-standing topic of packaging ProtonVPN for the official repositories.

EPEL

This week, the EPEL group's weekly meeting was shortened due to technical issues with the Matrix chat service. The primary discussion point was the migration from Pagure to Forgejo, for which testing is now complete and ready to proceed. On the mailing list, a maintainer announced their intent to retire the rust-pore package in EPEL 8 and 9 because of stalled upstream development. There was also a follow-up in a discussion about the uv package update for EPEL10, clarifying that a related component update will be treated as compatible and non-breaking.

Decisions Taken

• A consensus was reached to name the new issue repository for the Forgejo migration epel/steering.

CentOS Hyperscale

The CentOS Hyperscale SIG held a meeting to discuss follow-ups from CentOS Connect, the recent repository migration to GitLab, and a significant change regarding btrfs support in CentOS Stream 10. Red Hat plans to enable btrfs in the kernel, but will place the module in a non-default package (kernel-modules-internal), which will break the SIG's current implementation. Despite requiring adaptation, this was seen as a net positive, as it will allow the SIG to contribute to the btrfs code in the RHEL kernel, benefiting downstream users. The group also explored methods for tracking packager activity to identify inactive members, finding that their initial plan to use the GitLab API was flawed. Another brief meeting was disrupted by a bot malfunction, forcing the participants to move to a new channel where the main discussion took place.

Decisions Taken

• Due to inaccuracies found when using the GitLab API to track contributions, the group decided that querying build data from the CentOS Build Service (CBS)/Koji is a more reliable metric for packager activity and will be investigated further.

Atomic

During the week, the group held one meeting, the Fedora Atomic Initiative, which focused on the organizational strategy for Fedora's immutable variants. The main discussion revolved around how to structure projects like Atomic Desktops, CoreOS, and IoT, with proposals to create a new /atomic namespace on the forge and to decide whether to join the existing Atomic Desktops SIG or form a new, broader one. The idea of unifying documentation was also explored, acknowledging the challenges of different user bases but also the potential benefits from converging technology like bootc. A technical update noted that CoreOS builds on Konflux are paused until the end of Q1 2026, and a permissions issue for the bootc-tenant namespace was identified.

Decisions Taken

• A large group video call will be scheduled with representatives from CoreOS, IoT, and Atomic Desktops to discuss collaboration on tooling, documentation, and SIG structure.
• A topic will be created on the Fedora Discussion forum to formally propose joining the Atomic Desktop SIG.
• Read-only access will be enabled for all FAS-authenticated users to the bootc-tenant namespace in Konflux.

CoreOS

This week, the CoreOS team held their weekly meeting where they discussed delays in the Fedora 44 branching schedule and the temporary reversion from Konflux to in-pipeline builds for the Rawhide stream due to infrastructure issues. A request to add the mstflint package was declined for Fedora CoreOS, as it would add a Python dependency for a platform FCOS does not build for; the request will be handled downstream in RHCOS instead. The team also agreed to schedule a follow-up meeting with the Flatcar team to continue discussions on Ignition.

On the forums, a discussion continued around Pyromaniac, a tool for modular CoreOS configurations. The tool's author explained how to combine multiple self-contained configuration modules without them overwriting each other by using the std.merge component, which is designed to compile and merge several Butane structures into a single Ignition config. Additionally, a mailing list announcement was sent for a community video meeting on February 25th to revisit the topic of expanding Ignition for Azure-specific configurations.

Decisions Taken

• The mstflint package request will not be included in Fedora CoreOS due to its Python dependency and platform specificity. The request will be handled downstream in RHCOS.
• A follow-up video meeting will be organized with the Flatcar team to continue the conversation about Ignition.

ARM

This week, the ARM group's activity consisted of a single announcement on the mailing list. Adam Williamson posted an invitation to the Fedora 44 Blocker Review Meeting, scheduled for February 16, 2026. The purpose of the meeting is to review proposed blockers and freeze exceptions for the upcoming Fedora 44 release. The announcement provided details on the agenda, links to the bug lists, and encouraged community members to vote on the issues beforehand to streamline the meeting. No decisions were made this week.

Alternative Images

The Alternative Images group met this week, focusing on their participation at CentOS Connect in Brussels. Several members attended and presented the yearly "Alternative Images" talk, a recording of which is available on YouTube (starting at 1:21:37). A successful demo of installing the CS10 KDE live image on a SteamDeck was also presented. The main discussion centered on future plans and the roadmap for upcoming image releases.

Decisions

• CS10 KDE Live Images: Will be updated next quarter to replace sddm with Plasma Login Manager and to use Plasma Setup on firstboot.
• Aarch64 Raw Images: Are planned for release before the middle of the year, to be created by porting existing Kiwi configurations from Fedora.
• CentOS Stream 10 on Risc-V: Images are planned for the end of the year, dependent on a release build from the CentOS ISA Sig.

Cloud

During their weekly meeting, the Cloud group established its priorities for the year. The main goals include adding smoke tests for images, improving communication via changelogs and blog posts, and porting the LISA testing framework to EC2 and GCP. The team also acknowledged that significant work is needed to fix the GCP userspace stack and to complete the long-standing goal of integrating with Oracle Cloud. A "Cloud Workstation" was discussed as a potential future target, but it is currently blocked by the lack of a suitable open-source VDI technology.

Decisions Taken

• The group decided that creating a Fedora "hyperscale spin" was not a useful goal, as most of the enabling work from CentOS Hyperscale is already developed in or exists in Fedora.

kernel

This week, the kernel team's activity consisted of a single announcement from Justin Forbes regarding the kernel-ark os-build branch. The announcement stated that the branch has been rebased, a regular maintenance task performed with each new upstream kernel release. The goal of this recurring rebase is to keep Fedora's patch set clean, manageable, and closely aligned with the upstream tree, ensuring patches are no more than one release out of date.

Decisions

• The kernel-ark os-build branch has been rebased.
• Contributors with pending Merge Requests (MRs) must rebase their work on top of the new branch and repush their changes.

AI & ML

During the single AI & ML SIG meeting this week, the main topics of discussion were packaging strategies and meeting logistics. The group reviewed the progress of the ROCm 8.x change proposal and a new compatibility proposal designed to allow multiple ROCm versions to be installed side-by-side to prevent future breakages. A new package review for libggml was also discussed, with the goal of unbundling it from applications like llama.cpp to create a centralized system library. Finally, there was a discussion about moving the meeting to an earlier time to better accommodate European participants, with an action item to consult with the interested Red Hat CPT team.

Go

The Go group held one SIG meeting this week, which was conducted via text chat and had very low attendance. The primary point of discussion was an update on the status of Go versions in Fedora. It was shared that Go 1.26rc3 is in Fedora Rawhide and Fedora 44, while updates for Go 1.25.7 and 1.24.13 are in testing for Fedora 43 and Fedora 42. A brief, off-topic question about the QGIS project was also raised. No decisions were made or action items assigned during the meeting.

Python

This week's discussions focused on managing deprecated and unmaintained packages. The long-running effort to remove the python-mock package is in its final stretch, with pull requests opened for the last few packages that depend on it. In a separate discussion, concerns were raised about the python-dateutil package, which is unmaintained upstream, has an unaddressed security vulnerability, and is expected to fail building with Python 3.15.

Decisions

• The python-mock package will be retired from Rawhide soon to prevent it from being reintroduced, while it will be kept in the F44 release for now.
• Following a discussion about the unmaintained status of python-dateutil, a Change Proposal to deprecate the package has been drafted.

Perl

This week's activity for the Perl group centered on managing updates for two RPM packages. A pull request to rebuild perl-PkgConfig-LibPkgConf for pkgconf-2.5.1 was discussed. Following code review and suggested modifications by Petr Pisar, the changes were implemented and merged by Yaakov Selkowitz to meet the Beta freeze deadline. Another discussion involved an update to perl-Net-Server. This pull request was briefly closed by Michal Josef Špaček because a newer version of the package had been released, but it was subsequently reopened.

Decisions Taken

• The pull request to rebuild perl-PkgConfig-LibPkgConf for pkgconf-2.5.1 was merged after code modifications were made.

Rust

This week, the Rust group discussed package maintenance and the challenges of introducing new software. Michel Lind announced an intent to retire the rust-pore package in EPEL 8 and 9 due to its upstream development becoming inactive, which complicates updates for other Rust crates. In another thread, W. Michael Petullo sought advice on packaging wayscriber, which has several unpackaged or incompatibly versioned dependencies. The guidance provided was to either undertake the significant task of packaging the missing dependencies like the iced GUI toolkit, or to patch wayscriber to support the newer versions of crates like schemars and png that are already available in Fedora.

Decisions

• An intent was filed to retire the rust-pore package in EPEL 8 and 9.

Other Discussions

• The Packit team announced that its ogr library now supports Forgejo. This is part of a larger effort to enable the use of Forgejo as a dist-git backend in Packit, and more details are available in their blog post.

• In a discussion about the migration of the Fedora CI issue tracker to the new forge, Adam Williamson shared a link to helper scripts and a migration checklist to assist with the process, noting that these resources should be better documented.

• An announcement was made that all new Copr projects will use Pulp as their default storage backend starting the following day, as part of a larger migration effort. The team is confident but asks users to report any unusual behavior.

• A proposal was made to create a "packaging" organization on forge.fedoraproject.org. This would serve as a new home for the Fedora Packaging Committee's guidelines repository and other packaging-related tools, a suggestion which received positive initial feedback.

• The discussion on managing old software continued, exploring a policy to orphan packages with long-unresolved "the-new-hotness" update tickets. Participants debated the complexities of such a policy, such as packages that cannot be updated, and broadened the topic to Fedora's overall curation strategy, questioning whether stricter rules should apply to both new and existing packages. An idea to track package usage via repository logs was considered but found to be impractical.

• A review was requested for the new GKlib package. Two community members, Cristian Le and Steve Cossette, volunteered to conduct the review, with one noting some initial issues in the package specification that need to be addressed.

• Several threads were initiated due to a technical issue where a user was unintentionally sending empty or encrypted emails from a Protonmail account to the mailing list. Other members helped diagnose the problem, clarifying that encrypted mail is not suitable for public mailing lists, and the user eventually resolved the sending issue.

• An LWN article discussing future Git plans was shared, highlighting the "large-object promisors" feature as a potential alternative to Fedora's lookaside cache for handling large files in src.fedoraproject.org. A brief discussion followed about accessing the paywalled article.

• A renewed request was made for package reviewers for several audio and music production packages intended to modernize Fedora Jam, such as fedora-jam-audio-config and patchance. The contributor also expressed his renewed commitment to Fedora after a five-year hiatus.

• A user inquired about the Python SIG's activity due to a lack of response on the mailing list. It was clarified that the SIG is very active on Matrix and that the mailing list has low traffic. For new package requests, it was suggested that directly contacting maintainers of related packages might be more effective than a general post to the list.

• Fedora Release Engineering initiated a discussion to retire a list of package repositories that appeared to be empty, as they were causing problems during branching. The community provided feedback clarifying that some listed repositories did have content on older or EPEL branches, or were in the process of being imported. The plan to clean up truly empty repositories will proceed, but with more careful vetting to avoid unintended retirements.

• A user questioned the lack of traffic on the test mailing list. It was clarified that no technical issue was present; there simply had been no new messages sent, and more active QA discussions now take place on other platforms like Matrix.

• A post shared the presentation materials from the FOSDEM 2026 talk, "State of the Arch: Fedora on RISC-V," and directed interested community members to the main communication channels for the Fedora RISC-V SIG.

• A final announcement was made regarding the migration from Zuul to Packit for dist-git CI. Zuul runners for RPM projects on src.fedoraproject.org were disabled, and a reminder was issued that the Jenkins-based CI for pull requests would be turned off on February 16.

• The FESCo meeting agenda and minutes were posted. Decisions included approving the Build_FCOS_on_Fedora_Konflux change, the ibus-speech-to-text change (with a recommendation to package a model), and moving the TeXLive 2025 update to F44. The committee also reviewed the status of numerous other F44 changes, moving the Podman 6.0 update to F45 and pushing to complete the python-mock removal.

• A reminder was sent out that the Beta freeze and the 100% code completion deadline for all Fedora 44 Changes was scheduled for February 17, 2026.

• In a long-running thread concerning the guile30 package, the maintainer responded by adding Benson Muite as a co-maintainer to help get the package updated and unstuck.

• Fedora QA reported that a high number of openQA test failures were blocking updates. The issues were being actively investigated and included a broken KDE launcher icon, a tuned service failure on startup, and test instability related to the GNOME 50 update in Fedora 44.

• A discussion revealed that the /usr/lib/node_modules directory was unintentionally left unowned in Fedora 44 due to the Node.js alternatives change. The Node.js team confirmed this was a bug and that a fix would be submitted to restore shared ownership of the directory by all nodejs stream packages.

New contributor introductions

• New contributor Andreas Haupt introduced himself. With a background in managing compute clusters and building RPMs, he aims to contribute packages to EPEL and is currently seeking a sponsor for his first package, lesspipe.

Discussions about orphaning packages

• A proposal was made to reduce the maintenance burden of wlroots compatibility packages by orphaning wlroots0.15 and wlroots0.17, and retiring wlroots0.16. The maintainers of the dependent packages (hikari and python-pywlroots) were asked to take over maintenance if they wish to keep them.

• A Change Proposal for Fedora 45 was submitted to formally deprecate the python-dateutil package. This is due to its upstream being unmaintained, which has led to potential security issues and build failures. The goal is to raise awareness and encourage the many dependent packages to migrate to an alternative.

• In response to the list of packages scheduled for retirement due to long-term build failures, several were saved. Maintainers and contributors fixed and rebuilt libtpcimgio, bonnie++, and zork, while a new maintainer volunteered to take over ubloxcfg.

• In response to a previous announcement of packages to be retired for failing to build, it was reported that the embree3 package has now been fixed and successfully rebuilt.

Discussions about package updates

• The update of libdisplay-info to version 0.3.0, which includes a soname bump, was revisited. Dependencies were successfully rebuilt in a side-tag, and the updates for Fedora 45 and Fedora 44 were submitted to Bodhi for testing.

• An informational announcement was made about the upcoming update of wlroots to version 0.20.0 in rawhide and F44. The update includes API and library name changes, and a wlroots0.19 compatibility package will be provided to ensure no breakages.

• The effort to remove the deprecated python-mock package is nearing completion, with only a few dependent packages left to be fixed. Pull requests have been opened for the remaining build-time and stale run-time dependencies. The plan is to retire python-mock in Rawhide soon to prevent it from being re-introduced, while it may remain in Fedora 44 for the time being.

• An update to libupnp in rawhide, which included a soname bump, was pushed without the required one-week notice, leading to a build failure for vlc. The maintainer acknowledged the mistake. Separately, an ABI-breaking update to libupnp in F44 was also noted, with a corrective update being prepared.

• A user inquired why the maxima package was an old version. The investigation revealed that a newer version had been built months ago but was never submitted as an update. A maintainer then promptly submitted the update to Bodhi.

• An update for mupdf to version 1.27.1, which includes a soname bump, was announced for Rawhide (F45), F44, and F43. The maintainer has created side-tags to handle the necessary rebuilds of dependent packages.

• Following up on the planned update of the uv package, the maintainer announced that python-uv-build will also be updated to version 0.10.x in F42 and F43. This decision was made after upstream confirmed there were no breaking changes to the build backend in this release.