19 Nov 2026

feedFedora People

Fedora Infrastructure Status: Updates and reboots on Fedora infrastructure

19 Nov 2026 10:00pm GMT

12 Nov 2026

feedFedora People

Peter Czanik: The syslog-ng Insider 2026-11: Tor; Java; Elasticsearch

12 Nov 2026 1:05pm GMT

Fedora Infrastructure Status: Fedora Copr outage - updating servers

12 Nov 2026 10:30am GMT

11 Nov 2026

feedFedora People

Fedora Community Blog: TWIF: November 02 to 08, 2026

Fedora Community Blog's avatar

This Week in Fedora (TWIF) is the Fedora community's weekly report on project news, decisions, and contribution opportunities. Across the Fedora ecosystem this week, the primary focus was the highly anticipated release of Fedora Linux 45, with teams including Release Engineering, Quality, Infrastructure, Server, and Docs finalizing release candidates, deploying updates, and immediately transitioning into Fedora 46 planning. Beyond the release cycle, a major shared initiative is the Bootable Image Unification ("Atomic Fusion") project, which dominated the agendas for the Council, Atomic, IoT, and Hummingbird groups as they prepared proof-of-concept demos. Infrastructure and tooling migrations also commanded significant cross-team collaboration; the Council, FESCo, and Quality teams are actively evaluating a potential transition from Bugzilla to a Forgejo-integrated issue tracker, while FESCo, Release Engineering, and ELN are coordinating the complete removal of the legacy DNF4 stack. Finally, adapting to upstream shifts and reinforcing system security were key technical themes, highlighted by FESCo and the KDE SIG managing the deprecation of X11 in KDE Plasma 6.8, alongside widespread security patching and cryptographic upgrades-such as the adoption of %openpgpverify-across the Perl, Rust, Cloud, and Infrastructure teams.

NOTE: This is an experiment of translating the This Week in Fedora report into a Fedora Community Blog series. Do you have feedback? Reply to the Fedora Discussion topic attached to this post and let us know your thoughts.

Announcements

Announcements

The highly anticipated release of Fedora Linux 45 is now officially available, as announced across the project forums, community posts, and the announce and devel-announce mailing lists. This milestone brings exciting updates across the ecosystem, including Fedora Workstation 45 featuring GNOME 51's reworked frame scheduling, and the KDE Plasma Desktop Edition highlighting KDE Plasma 6.8, the 30th-anniversary release of KDE. Hardware support continues to expand with the Fedora Asahi Remix 45 introducing out-of-the-box support for Apple M3 chips, alongside community-maintained RISC-V GA images available for testing, providing a great opportunity for contributors to report hardware enablement issues. For immutable OS users, detailed instructions are available for rebasing to Silverblue 45, while Fedora Atomic Desktops now utilize the new Anaconda Web UI and have migrated their repositories to the atomic-desktops organization, offering streamlined engagement for future contributors.

To avoid disruptive surprises, users and system administrators should note several key technical shifts in this release. The Anaconda installer now includes native support for Stratis storage configuration, simplifying advanced local storage management through an easy-to-use interface. Additionally, the unmaintained NetworkManager-vpnc and NetworkManager-fortisslvpn plugins are officially retired in Fedora 45, requiring users to migrate to actively supported VPN alternatives to maintain enterprise connectivity. Finally, on the infrastructure side, a brief planned server outage occurred on November 6th to reboot main VPN, email, and bastion servers into a new kernel for CVE mitigation, ensuring the ongoing security of the project's backend services.

AI

AI

The AI/ML SIG discussed new package reviews, notably OpenShell, an NVIDIA-driven tool for agent sandboxing. Packaging updates were announced, with the latest AI and ROCm packages now available in COPRs for released distributions, and new LLM servers like Gufo and Colibri landing in Rawhide. The group is also collaborating on a Fedora Magazine article highlighting the use of the pi-coding-agent to help Fedora contributors, which may evolve into a broader series exploring how AI is utilized within the Fedora ecosystem. Other chat discussions touched on integrating hardware volunteering for AI tasks and addressing Wayland compatibility issues for freelance time-tracking tools.

Decisions

  • The latest AI and ROCm packages are now available for general use in COPRs for released Fedora distributions.
  • New LLM servers, Gufo and Colibri, have been packaged and are available in Rawhide.
  • The SIG will pitch and publish a Fedora Magazine article focusing on the pi-coding-agent, potentially kicking off a series on how AI is used in Fedora.

Contribution opportunities

Learn more about the AI team.

Ambassadors

Ambassadors

The Ambassadors group saw two forum discussions this week. A new contributor asked for help setting up their Fedora Campus Ambassador profile, including access to the wiki, Fedora People, and Libravatar, and received troubleshooting steps from the community. Additionally, a member started an organizational thread to coordinate a meetup for Fedora, CentOS, AlmaLinux, and RockyLinux contributors attending SFSCON 2026 in Bolzano, Italy.

Contribution opportunities

  • Contributors attending SFSCON 2026 in Bolzano, Italy (Nov 13-14) are invited to connect and team up with other community members.

Learn more about the Ambassadors team.

Atomic

Atomic

This week, the Atomic group focused on bootable image unification ("Atomic Fusion") with an upcoming presentation to the Workstation WG and a seed proof-of-concept demo (Meeting Agenda). In addition, there are ongoing discussions about rebasing Fedora Atomic Desktops on Fedora Bootc base images, which will modernize the build flow (Issue #88).

Several technical issues were also addressed, including a bug where systemd-oomd fails to intervene during memory exhaustion on Kinoite 44 (Issue #130), a syncing issue with the Fedora Cosmic-Atomic image (Issue #137), and an anomaly where rpm-ostree stable commits occasionally bundle packages from the updates-testing repository (Discussion).

Decisions

  • Systemd services in Atomic images will use ConditionPathIsMountPoint=/sysroot instead of checking for /run/ostree-booted to ensure compatibility with the composefs backend (Issue #133).
  • The Fedora Cosmic-Atomic update failure was identified as a release tooling script issue and moved to a releng ticket (Issue #137).

Contribution opportunities

  • Help is needed to file a releng ticket to investigate why rpm-ostree stable commits occasionally pull packages from the updates-testing repository (Discussion).
  • Contributors are invited to help create and review test cases for the upcoming Fedora Atomic Desktops Test Week, covering installations and upgrades via rpm-ostree, gnome-software, and plasma-discover (Issue #87).
  • Assistance is requested to test and provide a controlled reproducer for a memory exhaustion bug where systemd-oomd fails to intervene on Kinoite 44 (Issue #130).

Learn more about the Atomic team.

Cloud

Cloud

This week, the Cloud group focused on image configuration and distribution infrastructure. A key update involves adding the SUSPEND_SAFE_FPR guest OS feature to Fedora Cloud GCP images to address a page reporting suspend UAF vulnerability (CVE-2026-74481), which is now being applied to new nightly builds (Issue 449). Additionally, following the announcement that the HCP Vagrant Registry is shutting down on December 31, the group is discussing setting up a self-hosted Vagrant registry to ensure continued availability of Vagrant boxes, drawing inspiration from AlmaLinux's recent implementation (Issue 450).

Contribution opportunities

  • Help is needed to set up a self-hosted Vagrant registry for Fedora to replace the retiring HCP Vagrant Registry before December 31 (Issue 450).

Learn more about the Cloud team.

COPR

COPR

This week, the COPR team successfully completed a scheduled server upgrade on November 3rd, bringing new features and bug fixes to the platform. Following the upgrade, an ongoing data migration to Pulp temporarily affected several projects (alphabetically from "sar" to "siddharthvipul1"), causing some 404 errors and pending builds which are expected to resolve as the migration progresses. Additionally, the team discussed the timeline for IPv6 support on the Pulp instance, estimating a fix for early next year, and provided support for building bleeding-edge Rust packages with vendored crates in Copr.

Decisions

  • Completed the scheduled COPR server upgrade on November 3rd to deploy new features and bug fixes. Details can be found in the mailing list thread, the Fedora Infra ticket, and the release notes.
  • Proceeded with the ongoing data migration to Pulp, which temporarily causes 404 errors and pending builds for affected project owners while their specific data is being migrated.

Contribution opportunities

  • Help is welcome to set up automation that recognizes new copr-cli tags being pushed, creates the sdist tarball, and automatically uploads it to PyPI.

Learn more about the COPR team.

CoreOS

CoreOS

This week, the CoreOS team celebrated the general availability release of Fedora Linux 45. The testing stream has been successfully rebased to version 45.20261030.2.1, bringing notable changes such as native Butane support in Ignition, the use of chunkah for better layer reuse in container images, the relocation of RPM repository configs out of /etc, and the update to Podman 6.0. The team is currently in the post-release cleanup phase and has already opened the tracker for the upcoming Fedora 46 rebase. In addition to the release activities, the team addressed several critical bugs and infrastructure tasks. A fix for the IPv4 TCP use-after-free vulnerability (CVE-2026-98432) was shipped in the stable stream, and workarounds are being tested for an ext4 /boot corruption issue affecting upgrades. The team also approved a proposal to switch Konflux-driven streams to a Jenkins poll-based import model to simplify downstream pipeline management.

Decisions

Contribution opportunities

Learn more about the CoreOS team.

Council

Council

This week, the Council focused on the long-term future of Fedora's issue tracking and ongoing image unification efforts. A major discussion was initiated regarding the potential transition from Bugzilla to a Forgejo-integrated system (related to FESCO#3664), weighing the necessity of adopting modern, open-source infrastructure against concerns over Forgejo's current maturity and feature parity. Additionally, the agenda for the November 5th Bootable Image Unification ("Atomic Fusion") meeting was published, featuring a review of the project board, a seed proof-of-concept demo, and a planned presentation to the Workstation Working Group.

Contribution opportunities

Learn more about the Council team.

Design

Design

The Design team focused on the initial sketches for the F46 wallpaper, discussing the use of alternative geometric shapes for bubbles while prioritizing iridescence. They also reviewed poster designs, noting layout inconsistencies and the need for better text hierarchy and spacing, and successfully closed the F45 Virtual Release Party graphics ticket. Additionally, the team discussed accessibility improvements for international audiences, agreeing to spell out acronyms like DEI. In the Matrix chat, automated alerts indicated that the "Fix time of day path" action failed in both the main and f45-backgrounds branches of the backgrounds repository.

Decisions

  • Iridescence will remain the primary visual focus for the F46 wallpaper bubbles, regardless of the final geometric shape chosen.
  • The Fedora logo and mascots will not be included in the wallpaper to comply with guidelines and avoid clutter; instead, mascot concepts will be repurposed for promotional art.
  • Acronyms such as DEI (Diversity, Equity, and Inclusion) will be spelled out in designs to improve accessibility and clarity for international audiences.

Learn more about the Design team.

Docs

Docs

The Fedora Docs team successfully navigated the Fedora 45 release, merging numerous release notes covering updates like GNOME 51, KDE Plasma 6.8, and various system changes. Following the release, the team is restructuring the release notes repository to stop versioning; future notes will be built directly from the main branch, displaying the three most recent supported releases on a single page while older notes remain available via the Internet Archive.

Additionally, the team is revamping its infrastructure by transitioning the site-builder repository to build from main rather than prod. They are also evaluating "Bruce," a new broken-link detection script, for CI integration to automatically generate static reports and eventually file issues for broken links. Furthermore, discussions are ongoing regarding Antora component consolidation to allow cross-repository module inclusion and integrating the Fedora Design Suite documentation.

Decisions

  • Stop versioning the release notes repository and build them exclusively from the main branch, preserving only the three most recent supported releases (Meeting, Issue #449).
  • Transition the site-builder repository (formerly docs-fp-o) to drop the prod branch and build the production site directly from main (Meeting, Issue #61).
  • Integrate the "Bruce" link-checking script into the CI pipeline in phases, starting with generating a static HTML report before moving to automated issue creation (Issue #69).
  • Retain docsbuilder.sh as a wrapper for local documentation previews while updating the underlying container to support Aarch64 and dropping npm dependencies (Issue #65).

Contribution opportunities

  • Review and merge open pull requests for the Fedora 45 Release Notes, as requested by community members (Forum Topic).
  • Help replace legacy {partialsdir} includes with the partial$ syntax across documentation repositories to align with current Antora standards (Issue #38).
  • Assist in documenting the Fedora Docs site build and monitoring process for the prod and stg branches (Issue #59).
  • Provide feedback on the proposed integration of the Fedora Design Suite documentation into the official Fedora Docs website (Issue #68).
  • Test and provide feedback on the proposed Antora module inclusion methods (component merge vs. Antora extension) to improve cross-SIG documentation discoverability (Issue #66).

Learn more about the Docs team.

ELN

ELN

The ELN SIG held a meeting on November 3, 2026 (meeting log). Key updates include the complete removal of dnf-4 from ELN, the completion of rebuilds for libxml2 2.15, and the replacement of perl-Params-Util with perl-Params-SomeUtil. Additionally, the Content Resolver now displays daily diffs. On the RISC-V front, approximately 140 packages have been built, though progress is currently paused pending fixes for toolchains like gcc, golang, and rust. The group also discussed ongoing issues with KDE Discover (Issue #633) and the unmaintained libappstream-glib (Issue #486), as well as upcoming libical4 rebuilds.

Decisions

  • dnf-4 has been completely removed from ELN and will not be included in RHEL 11.
  • perl-Params-Util has been replaced with perl-Params-SomeUtil.

Learn more about the ELN team.

EPEL

EPEL

This week in EPEL, discussions highlighted a known daily cache delay in the CentOS Stream repo for Fedora's Koji, which temporarily caused scratch build failures in epel9-next (URL). Security updates were a major focus, with uv (v0.13.5) and ruff (v0.17.2) being pushed to stable for the EPEL10 leading branch to address multiple RUSTSEC vulnerabilities and the eMudhra CA compromise (URL). Additionally, pipx is being retired from EPEL9 due to 23 security vulnerabilities that cannot be practically patched on the older Python 3.9 stack (URL). Other activities included the EPEL 10.2 retirement announcement, progress on bringing mailman to EPEL10, and participation in the release party CLE presentation.

Decisions

  • The pipx package is being retired from EPEL9 due to severe security vulnerabilities and incompatible Python version requirements (URL).
  • Versions 0.13.5 of uv and 0.17.2 of ruff were pushed to stable for the EPEL10 leading branch to address critical security flaws (URL).

Learn more about the EPEL team.

Fedora Join

Fedora Join

Andrew Heath introduced himself to the Fedora community, sharing his extensive background in enterprise Linux, infrastructure automation, and image building. He expressed interest in contributing to packaging, image building, QA, and infrastructure automation. In response, he was welcomed by the community and advised to engage with the packaging team in their Matrix room to find a sponsor and initial tasks.

Contribution opportunities

  • Andrew Heath is seeking a packaging sponsor and looking for good first tasks, particularly in co-maintaining existing packages or picking up orphaned ones in the automation and sysadmin tooling space.
  • Opportunities exist to mentor or collaborate with Andrew in areas like image building (osbuild), QA testing, and infrastructure automation.

Learn more about the Fedora Join team.

FESCo

FESCo

During this week, FESCo celebrated the release of Fedora 45 and announced upcoming elections. The committee held a meeting and processed numerous tickets, focusing heavily on the future of Fedora's issue tracking system, with extensive debate on whether to migrate to Forgejo or maintain a community-run Bugzilla instance. Other major topics included the coordinated removal of the legacy DNF4 stack and Modularity, as well as handling the deprecation of X11 support in KDE Plasma 6.8 for stable releases.

Decisions

  • Rejected the request to revert the removal of plasma-workspace-x11 from Fedora 44 and 45 in Ticket #3707.
  • Approved the pull request clarifying the responsibilities of the Engineering representative for the Council in Ticket #3613.
  • Rejected the Thin LTO Build Flag (F47) change proposal due to a lack of votes over five weeks in Ticket #3692.
  • Transferred maintainership of python-authlib to a new co-maintainer following the non-responsive maintainer policy in Ticket #3697.

Contribution opportunities

  • Community members are asked to help identify tools and scripts that depend on the legacy DNF4 stack or libmodulemd to assist with their planned removal in Ticket #3702.
  • Volunteers interested in maintaining a community-run Bugzilla instance are invited to put forward a proposal to the Fedora Infrastructure group, as discussed in Ticket #3664.

Learn more about the FESCo team.

Hummingbird

Hummingbird

The Hummingbird group prepared for their upcoming "Atomic Fusion" (bootable image unification) meeting on November 5, 2026. The agenda included a project board review, a potential demo of a seed proof-of-concept, and preparations for presenting to the Workstation Working Group.

Contribution opportunities

Learn more about the Hummingbird team.

Infrastructure

Infrastructure

The Infrastructure team successfully navigated the Fedora 45 release, officially lifting the infrastructure freeze on November 4th. The week involved significant maintenance and troubleshooting, including resolving a storage-related outage on Fedora Forge by resizing its Persistent Volume Claim and NetApp volume, and investigating persistent login issues with Fedora Accounts (FAS) linked to FreeIPA OTP interactions.

In addition to routine maintenance, the team began planning the deployment of Siguldry to the production environment for RPM and OSTree signing. They also scheduled a mass upgrade and reboot of infrastructure servers for November 19th, and discussed ongoing efforts to optimize AWS resource usage and clean up untagged cloud instances.

Decisions

  • The infrastructure freeze for the Fedora 45 release was officially lifted on November 4th. (URL)
  • A mass upgrade and reboot of most infrastructure servers is scheduled for November 19th at 22:00 UTC, which will cause short outages for many contributor services. (URL)
  • Mirrors that transparently redirect HTTP traffic to HTTPS will be updated in MirrorManager to explicitly use HTTPS URLs only, improving crawler compatibility. (URL)
  • The Limestone Networks mirror (mirror.lstn.net) was disabled in MirrorManager due to an expired TLS certificate. (URL)
  • New FAS groups were created for chromium-sig, sysadmin-oraculum, napkinstack-labs, tablepro, and nanlang.

Contribution opportunities

  • Help is needed to investigate and resolve the persistent Unauthorized: bad credentials login errors on accounts.fedoraproject.org, which appear to be related to FreeIPA OTP module interactions. (URL)
  • Contributors can help clean up NetApp and host storage, including moving older releases to archive volumes, increasing partition sizes on alerting hosts, and compressing logs. (URL)
  • Assistance is requested to set up a Zabbix HTTP check for Oraculum and retire its old watchdog email alerts. (URL)
  • There is an opportunity to help set up Zabbix monitoring for the staging autosign service by implementing checks for AMQP, RPMs, OSTree, and CoreOS metrics. (URL)
  • Help is needed to create an announcebot Discourse service user and API key for sending compose announcements. (URL)
  • A new contributor expressed interest in helping with virtualization and infrastructure tasks, presenting an opportunity for onboarding and mentorship. (URL)

Learn more about the Infrastructure team.

IoT

IoT

This week, the IoT group focused on bootable image unification and resolving a system upgrade issue. Laura Santamaria shared the agenda for the "Atomic Fusion" meeting, which included a seed proof-of-concept demo and a presentation to the Workstation Working Group (URL). Additionally, a user reported a bug where upgrading to Fedora 45 fails due to a missing GPG public key in rpm-ostree. The issue was resolved locally by updating the gpgkeypath in the fedora-iot.conf file to point to /usr/share/pki/rpm-gpg/ (URL).

Contribution opportunities

Learn more about the IoT team.

KDE

KDE

This week, the Fedora KDE group navigated discussions regarding Plasma 6.8 updates and overall desktop stability. Notably, the update to Plasma 6.8 officially drops X11 session support upstream, resulting in the obsoletion of kwin-x11 and plasma-workspace-x11 packages in Fedora 44. Users relying on X11 were advised that locking packages might prevent future UI updates, though community workarounds like Copr repositories have emerged. Additionally, the community discussed the marketing and perceived stability of Fedora KDE, with maintainers emphasizing that upstream KDE's rapid release cadence inherently involves trade-offs. Users seeking long-term support might look toward LTS distributions, while those experiencing bugs are encouraged to contribute directly to upstream bug resolution.

Decisions

  • The update to Plasma 6.8 proceeds with the obsoletion of X11 packages (kwin-x11 and plasma-workspace-x11) due to upstream dropping X11 session support, as discussed in Why the Obsoletes: kwin-x11 and plasma-workspace-x11 in 6.8?.
  • The replacement of kwallet with oo7-daemon is currently deferred for KDE Plasma and Plasma Mobile variants due to a lack of time for integration, as noted in Issue #700.
  • The screen package will not be added to the Kinoite base image; users are advised to use package layering or system extensions instead (Issue #723).

Contribution opportunities

  • Contribute to upstream KDE bug resolution to improve the stability of the Plasma desktop environment, as suggested in the discussion on Fedora KDE stability.
  • Assist with testing and providing feedback on whether KDE processes crashing on boot is still an ongoing issue.
  • Help integrate oo7-daemon and build automatic migration paths from kwallet for future releases (Issue #700).

Learn more about the KDE team.

Legal

Legal

In a discussion regarding the koneko license and copyright, Cristian Le followed up on concerns regarding copyrighted sprites included in the project, specifically characters from Cardcaptor Sakura and the BSD Daemon. Following previous advice to drop the artwork, Cristian confirmed that the issue has been flagged to the upstream developers and that the problematic sprites will be removed via a downstream patch if necessary.

Decisions

  • The copyrighted sprites (Cardcaptor Sakura and BSD Daemon) in koneko must be removed, either by upstream or via a downstream patch. (Source)

Learn more about the Legal team.

Magazine

Magazine

This week, the Magazine group's activity centered around a comprehensive guide on Complete FIDO2 Integration with Fedora Luks2, Unlock, GUI Login, and Sudo Auth. Administrative actions were taken to split three posts from this discussion into a new topic dedicated to revising the guide for Fedora Linux 44.

Contribution opportunities

  • Community feedback is welcome to improve the FIDO2 integration living document.
  • Contributors are encouraged to explore, test, and share improvements regarding FIDO2 integration for Polkit GUI prompts, as the original author left this partially incomplete.

Learn more about the Magazine team.

Mindshare

Mindshare

This week, Mindshare began early planning for the Virtual F46 Release Party, aiming for May 2027, to ensure a smooth event by crowd-sourcing ideas and recruiting role leads well in advance. Additionally, a community member reached out to organize an informal meetup for Fedora, CentOS, AlmaLinux, and RockyLinux contributors attending SFSCON 2026 in Bolzano, Italy.

Contribution opportunities

  • Help organize the Virtual F46 Release Party by volunteering for event team roles including Wrangler, Speakers, Design, Promotion & Content, and Production & Video. To get involved, join the #commops:fedoraproject.org Matrix room and reply to the ticket.
  • Connect with other community members at SFSCON 2026 in Bolzano, Italy, by joining the organizational thread.

Learn more about the Mindshare team.

Perl

Perl

This week, the Perl group focused heavily on package maintenance, dependency management, and security enhancements. Maintainers implemented source signature verification using openpgpverify for packages like perl-Net-DNS and mod_perl. Several packages received routine version bumps, including perl-Mozilla-CA, perl-CGI, and perl-Tk-Text-SuperText. Additionally, contributors collaborated on adjusting dependencies for downstream distributions, such as adding build conditionals for Lexical::Var in perl-Exporter-Tiny and disabling optional dependencies in RHEL builds for perl-File-ShareDir.

Decisions

Learn more about the Perl team.

Python

Python

The Python group discussed reversing the deprecation of python-dateutil following a new upstream 4.0.0 release. Contributors agreed to undeprecate the package and patch out its new tzdata dependency to rely on the system's time zone data instead. Additionally, a proposal was made to automatically set LD_LIBRARY_PATH in %py3_test_envvars to streamline testing, and feedback is currently being sought on potential breakages.

Decisions

  • Undeprecate the python-dateutil package following the new upstream 4.0.0 release.
  • Patch out the tzdata dependency in python-dateutil 4.0.0 to rely on system timezone data instead.

Contribution opportunities

Learn more about the Python team.

Quality

Quality

The Quality team successfully verified and tested the release candidates for Fedora 45, officially declaring it "GO" for release, alongside publishing and updating the Common Issues. The team also hosted a Test Week for Linux Kernel 7.3, encouraging users to test the kernel rebase on Fedora 44 and 45.

In other activities, the team concluded the F45 test days planning and GRUB EFI for Confidential Computing test days, while scheduling an upcoming KDE Plasma 6.8 test week for November 9-15. Infrastructure and CI improvements continued, including fixes for ELN Koji repositories and successful Fedora 45 installations on Beaker hardware. The team also finalized their requirements for the Bugzilla to Forgejo migration.

Decisions

Contribution opportunities

Learn more about the Quality team.

Release Engineering

Release Engineering

Fedora 45 has been officially released, with the team handling final release candidate composes, signing the IoT compose, and managing post-release cleanup and synchronization. During the rollout, a minor synchronization issue with the Labs images was manually resolved, and discussions were held to better align fedora_distro_aliases and releases.json updates in future cycles.

In addition to the release, the team resolved several infrastructure and build issues. This included fixing broken RHEL 9 repositories for EPEL 9 builds, addressing a bug where Rawhide .treeinfo files were missing kernel image information, and removing several underpowered x86_64 hosts from the heavybuilder channel to prevent Out-Of-Memory errors during large builds like Chromium.

Decisions

  • Fedora 45 has been officially released.
  • Several underpowered x86_64 build hosts were removed from the heavybuilder channel to prevent OOM errors during large package builds. (URL)
  • A fix was implemented and backported in Pungi to ensure .treeinfo files contain kernel image information, restoring virt-install functionality for Rawhide. (URL)
  • The EPEL 7 meson tagging order issue will not be fixed because EPEL 7 is End of Life. (URL)

Contribution opportunities

Learn more about the Release Engineering team.

RISC-V

RISC-V

The Fedora RISC-V team successfully finalized and announced the Fedora 45 RISC-V GA images, including Server, Container, and Cloud variants. A major focus this cycle was clarifying kernel recommendations: the 'Omni' kernel is highly recommended for most physical hardware to avoid issues like PCIe/NVMe data corruption on JH7110-based boards (e.g., VisionFive 2), while the 'Generic' kernel is primarily targeted at QEMU and a select few boards. Meanwhile, the bootstrap of Fedora ELN (Enterprise Linux Next) for RISC-V is making significant progress, with Koji fully configured for ELN and RVA23 channels, and over 140 packages already built. The team is also actively debugging hardware-specific issues, including GCC build hangs on the SpacemiT K3 and a QEMU KVM guest initialization bug.

Decisions

  • The 'Omni' kernel is officially recommended for most physical RISC-V hardware (including VisionFive 2) to prevent potential data corruption with certain PCIe/NVMe storage configurations, while the 'Generic' kernel is recommended primarily for QEMU.
  • Koji hub policies and channels have been updated to route RVA23-specific builds appropriately, enabling the ongoing Fedora ELN bootstrap.

Contribution opportunities

  • Help is needed to debug and resolve a hard lockup issue occurring during GCC ELN and Rust builds on SpacemiT K3 hardware (disabling Transparent Huge Pages is currently being tested as a workaround).
  • Contributors can assist with upstreaming vendor patches from the Omni kernel to the Mainline kernel to improve out-of-the-box hardware support.
  • Developers familiar with QEMU and KVM can help investigate a guest initialization failure when using -cpu max on RISC-V KVM hosts.

Learn more about the RISC-V team.

Rust

Rust

The Rust group focused heavily on security updates and package rebuilds this week, addressing multiple RUSTSEC advisories across crates like zstd, zip, ruzstd, rustls, and webpki-roots. Additionally, there was a mailing list discussion regarding a request to package crubit for Fedora and EPEL to support Chromium builds, though it faces significant hurdles due to its reliance on nightly Rust and unstable compiler internals.

Decisions

  • The request to package crubit for Fedora to support Chromium builds is currently blocked, as the required cc_bindings_from_rs tool depends on a nightly compiler and unstable compiler internals, which cannot be shipped in Fedora (Mailing List).
  • The effort to update packages to ruzstd v0.9 to address RUSTSEC-2026-0344 has been completed and the tracking ticket is closed (Issue 42).

Contribution opportunities

  • Assist with rebuilding or updating applications not co-maintained by the Rust SIG that vendor affected versions of zstd, zstd-safe, rustls, and webpki-roots (Issue 48, Issue 43, Issue 46).
  • Help port applications currently depending on older versions of zip (v0.6), rustls (v0.21/v0.22), and webpki-roots (v0.25) to their latest secure releases (Issue 47).

Learn more about the Rust team.

Server

Server

The Server Working Group celebrated the release of Fedora 45 Server and immediately began preparing for Fedora 46 by setting up a new testing project. A significant portion of the week was dedicated to the "Strengthening Server Updates" project, focusing on system resilience using LVM snapshots. Following the F45 release, the group closed numerous tracking tickets for system-wide changes and package updates.

In addition, the group discussed ongoing work on Ansible support, deciding to catch up on outstanding tasks over the next two weeks before reconvening on the topic. New contributors joined the meeting and immediately volunteered to help with testing and documentation efforts.

Decisions

  • The group agreed to continue using the ticket system for release testing (starting with Fedora 46), with optimizations to be discussed in the process. (Meeting Log, Mailing List)
  • For the "Strengthening Server Updates" project, the agreed next steps are testing the snapshot procedures, adding them as a step in post-installation, and preparing a Fedora Magazine article. (Meeting Log, Mailing List)
  • Members will use the coming weeks to catch up on outstanding tasks for the Ansible support project, deferring further discussion for 14 days. (Meeting Log)

Contribution opportunities

  • Testers are highly needed for the "System Resilience Using LVM Snapshots" procedures. Findings should be reported in Ticket #272.
  • Contributors are invited to help write a how-to style article for the post-installation section regarding server update resilience (Ticket #271).
  • There is an open opportunity to help draft a Fedora Magazine article about the "Strengthening Server Updates" project.
  • Assistance is welcome for the ongoing Ansible support project, specifically regarding the creation of an Ansible management CLI and configuring CI/CD runners (Ticket #268).

Learn more about the Server team.

Websites and Apps

Websites and Apps

This week, the Websites and Apps team resolved an issue where the x86_64 folder was missing from the Fedora 45 Labs download page by syncing the content and rebuilding the site. The team also successfully closed the F45 beta release tracker and opened tickets for UI improvements, including fixing dark-mode logos on the CoreOS page and improving contrast in the Fedora Media Writer section. In addition, a community member reported that the captive portal check URL is on an HSTS-preloaded domain, which breaks Wi-Fi login detection; the infrastructure team plans to move it to another domain in the future. Finally, a bug in Fedocal where events with past repeat-end dates fail to appear was identified and resolved for a user.

Decisions

Contribution opportunities

  • Review requested for the Fedora Maubot/Zodbot plugin for cookies: PR #257 and PR #161.
  • Help needed to fix missing dark-mode variant logos on the CoreOS page (Work item #439).
  • Help needed to improve the contrast of download items in the Fedora Media Writer section (Work item #438).

Learn more about the Websites and Apps team.

Workstation / GNOME

Workstation / GNOME

A brief 20-minute meeting was held on November 3rd, following up on the agenda from October 27th. The original agenda included topics such as Fedora 45 blockers and exceptions, appstream-data automation, and DNF updating without wheel.

Learn more about the Workstation / GNOME team.

Other Discussions

Other Discussions

  • From F45 onwards: Fedora-maintained (self-updating) hardening…: Chris announced a new self-updating kernel hardening feature available from Fedora 45 onwards. Designed for both beginners and advanced users on GNOME and KDE, it applies security-first configurations automatically, overriding certain defaults like yama-ptrace-enable. Users discussed its interaction with Atomic variants, Toolbox containers, and potential impacts on specific applications, with Chris noting that a new #hardening tag will be used to consolidate feedback.
  • Btrfs-patrol: snapshots before every dnf transaction…: JC shared updates on btrfs-patrol, a snapshot and rollback tool tailored for Fedora's default Btrfs layout. It automatically takes read-only snapshots before dnf5 transactions and allows for one-command rollbacks while ensuring the restored snapshot has the necessary kernel modules to boot.
  • GitLab access for inactive accounts: Shaun McCance announced that due to Fedora exceeding its seat limit on GitLab, accounts with no activity in the past 12 months will be downgraded to view-only access. This will free up seats for active teams without deleting any data, and edit access can be restored if needed.
  • Proposal: Optional CJK input method support for Fedora's kmscon console: Skyter Lin proposed adding optional CJK (Chinese, Japanese, Korean) input method support for Fedora's new kmscon virtual console, having successfully tested Traditional Chinese using uim-fep and m17n. Jocelyn Falempe confirmed the technical feasibility of using Super+Space for toggling and suggested starting by adding a kmscon-uim man page.
  • Some news about the Audinux activity for october: Yann Collette provided an October update for the Audinux repository, highlighting the addition of 29 new audio-related packages and 155 package updates. Notable additions include several AI-generated standalone applications like bytebeat, ibniz-rust, and mx44-rust, which underwent security and performance audits.
  • New packages in Fedora Linux (October 2026): Miroslav Suchý shared a comprehensive list of newly added packages to Fedora Linux during October 2026, generated using the rawhide-changes.py script.
  • F46 Change Proposal: Usermode2 (self-contained): On the devel-announce mailing list, Aoife Moloney shared a Fedora 46 Change Proposal to replace the C implementation of the usermode package with a memory-safe Rust rewrite of its userhelper and consolehelper tools. The rewrite serves as a drop-in replacement while dropping several obsolete standalone GUI tools, and developers discussed ensuring the Rust standard library safely handles the SUID execution environment.
  • Is packaging a fork permissible?: Łukasz Wojniłowicz asked if packaging a fork under the same name as the upstream project is permissible. Developers clarified that while it is allowed and sometimes necessary for dormant projects, the spec file should clearly explain the relationship between the original repository and the fork to avoid confusion.
  • F46 Change Proposal: Libical4 (system-wide): On the devel-announce mailing list, Aoife Moloney announced a Fedora 46 Change Proposal to update the libical library to its 4.x series, which introduces an API/ABI break from the 3.x series. Milan Crha and Michel Lind coordinated the necessary package rebuilds in a side tag, noting that only a subset of dependent packages required direct updates.
  • Heads-up: %gpgverify -> %openpgpverify PRs are coming: Jakub Jelen notified maintainers about upcoming pull requests to migrate packages from %gpgverify to the new %openpgpverify macro, which uses Sequoia's sqv for upstream source signature verification. He advised maintainers to check if their upstream keys need refreshing or updating to comply with current cryptographic standards.
  • Other discussions included Orion Poplawski checking on a non-responsive maintainer for cmake, Nick inquiring about src.fedoraproject.org UI issues, Dawid Wrobel raising concerns about Btrfs metadata exhaustion defaults, Gordon Messmer offering review swaps for podman-desktop, Nick seeking to co-maintain c-toxcore, Miro Hrončok noting a license change in python-cffi, Benson Muite unretiring python-hl7, the cancellation of a Fedora Council meeting, and Petr Pisar correcting the createrepo_c-devel license.

Orphaning packages

  • Orphaned packages looking for new maintainers (on devel-announce): Several orphaned packages were adopted, including tunneler and openfortivpn, while Dominik Mierzejewski advised against adopting rubygem-drake due to obsolescence.
  • Orphaned - singularity-ce: David Trudgian orphaned singularity-ce as the upstream project reached EOL, recommending apptainer as a suitable replacement.

Package updates

  • libcdio 2.4.0 update comes with new sonames: Adrian Reber announced an upcoming update to libcdio 2.4.0 in Rawhide, which bumps several SONAMEs and requires rebuilding dependent packages in a side tag.
  • Soname bump: libcamera: Milan Zamazal planned an update to libcamera 0.8.0 in Rawhide, noting ABI changes that require rebuilding pipewire-plugin-libcamera, libcamera-apps, and plasma-camera.
  • openapv SONAME bump: Dominik Mierzejewski announced an update to openapv that includes a SONAME bump and API changes, requiring a rebuild of FFmpeg to fix a high-severity CVE.
  • sonivox SONAME bump: Yaakov Selkowitz noted an upcoming update to sonivox 4.0.2, which will involve a side tag rebuild for its dependents.
  • CRI-O v1.37 and Go: Brad Smith reported that CRI-O v1.37.3 now requires Go 1.27.1 or newer, blocking updates on F43 and F44.
  • Heads-up: croaring 5.4.0 coming to Rawhide: Ben Beasley announced an ABI-breaking update for croaring to version 5.4.0, which will be coordinated with updates to python-pyroaring and groonga.

New contributor introductions

  • Aashish Jha: A software engineer at Microsoft working on Azure Confidential VMs, introduced himself and his work packaging azure-protected-vm-secrets as his first contribution to Fedora.
All contribution opportunities

All contribution opportunities

Quality Assurance and testing offer some of the most accessible entry points for community members outside of specific working groups. Contributors can participate in the Linux Kernel 7.3 Test Week and the upcoming KDE Plasma 6.8 Test Week, or help draft test cases for the Fedora Atomic Desktops Test Week. There are also numerous opportunities to test specific system features and provide feedback, such as evaluating "System Resilience Using LVM Snapshots" (Ticket #272), the btrfs-patrol snapshot tool, and the new self-updating kernel hardening feature. Furthermore, testers are needed to reproduce a memory exhaustion bug in Kinoite 44, verify if KDE processes are still crashing on boot, and validate a workaround for an ext4 /boot corruption issue in CoreOS.

For those with skills in technical writing, design, or event organization, there are several ways to make an immediate impact. The community is seeking volunteers to fill Wrangler, Speaker, Design, and Promotion roles for the Virtual F46 Release Party, as well as attendees to connect at SFSCON 2026. Writers can help draft Fedora Magazine articles covering Server Update Resilience and AI in Fedora, or write a how-to guide for post-installation server updates (Ticket #271). Documentation contributors are encouraged to review F45 Release Notes pull requests, replace legacy includes with Antora syntax (Issue #38), and provide feedback on integrating the Design Suite docs. Additionally, general feedback is requested on the proposed transition to Forgejo and agenda topics for the Bootable Image Unification meetings.

Contributors with system administration and infrastructure experience can assist with vital operational tasks, and mentorship is available for newcomers interested in virtualization and infrastructure. Immediate needs include setting up a self-hosted Vagrant registry for the Cloud SIG, configuring Zabbix monitoring for the staging autosign service and Oraculum, and cleaning up NetApp and host storage. Automation enthusiasts can help the COPR team set up PyPI upload automation for copr-cli tags, or assist the Server SIG with creating an Ansible management CLI and configuring CI/CD runners (Ticket #268). There is also an ongoing investigation into persistent login errors on accounts.fedoraproject.org related to FreeIPA OTP modules.

Developers and packagers can contribute by adopting orphaned packages like cmake and c-toxcore, or by helping identify tools that still depend on the legacy DNF4 stack for its planned removal. The Rust SIG needs help rebuilding applications that vendor affected versions of libraries like zstd and rustls, and porting others to secure releases. Web developers can submit fixes for missing dark-mode logos on the CoreOS page and review Maubot plugin pull requests. Finally, systems programmers can tackle complex hardware issues, such as debugging a hard lockup during GCC and Rust builds on RISC-V SpacemiT K3 hardware, or investigating a guest initialization failure on RISC-V KVM hosts.

The post TWIF: November 02 to 08, 2026 appeared first on Fedora Community Blog.

11 Nov 2026 5:02pm GMT

10 Nov 2026

feedFedora People

Peter Czanik: Thanks to Sam Altman... ;-)

10 Nov 2026 11:50am GMT

Justin Wheeler: Copr, explained: the sandbox where Fedora packaging starts

10 Nov 2026 8:00am GMT

09 Nov 2026

feedFedora People

Avi Alkalay: Falando de uma Revolução

Avi Alkalay's avatar

Joyce Moreno adaptou para português do Brasil a linda canção Talkin' Bout a Revolution, de Tracy Chapman. Foi lançado em seu álbum Music Inside de 1990. O álbum não está disponível nas plataformas musicais, mas tem no YouTube da Joyce. Eis a letra que ela adaptou e a rara gravação.


Todos 'tão falando de uma revolução
Assim, baixinho

Sopra o vento nos seringais
O que está marcado a fogo e aço nas usinas
Sobe os morros, os becos das capitais
E lá vai o buxixo nas esquinas

Todos 'tão falando de uma revolução
Assim, baixinho

Quem não tem nada vai querer
Pegar o que é seu
Quem não tem nada vai querer
Ganhar o que perdeu

E corre, anda logo logo logo logo
Corre corre corre corre corre, vai vai corre

Um dia vira a mesa, não dá prá evitar
Uma revolução vem vindo
Um dia vira a mesa e todos vão falar
E já não vai ser baixinho

09 Nov 2026 9:36pm GMT

Aurélien Bompard: From November 02 to November 08

Aurélien Bompard's avatar

Across the Fedora ecosystem this week, the primary focus was the highly anticipated release of Fedora Linux 45, with teams including Release Engineering, Quality, Infrastructure, Server, and Docs finalizing release candidates, deploying updates, and immediately transitioning into Fedora 46 planning. Beyond the release cycle, a major shared initiative is the Bootable Image Unification ("Atomic Fusion") project, which dominated the agendas for the Council, Atomic, IoT, and Hummingbird groups as they prepared proof-of-concept demos. Infrastructure and tooling migrations also commanded significant cross-team collaboration; the Council, FESCo, and Quality teams are actively evaluating a potential transition from Bugzilla to a Forgejo-integrated issue tracker, while FESCo, Release Engineering, and ELN are coordinating the complete removal of the legacy DNF4 stack. Finally, adapting to upstream shifts and reinforcing system security were key technical themes, highlighted by FESCo and the KDE SIG managing the deprecation of X11 in KDE Plasma 6.8, alongside widespread security patching and cryptographic upgrades-such as the adoption of %openpgpverify-across the Perl, Rust, Cloud, and Infrastructure teams.

Announcements

The highly anticipated release of Fedora Linux 45 is now officially available, as announced across the project forums, community posts, and the announce and devel-announce mailing lists. This milestone brings exciting updates across the ecosystem, including Fedora Workstation 45 featuring GNOME 51's reworked frame scheduling, and the KDE Plasma Desktop Edition highlighting KDE Plasma 6.8, the 30th-anniversary release of KDE. Hardware support continues to expand with the Fedora Asahi Remix 45 introducing out-of-the-box support for Apple M3 chips, alongside community-maintained RISC-V GA images available for testing, providing a great opportunity for contributors to report hardware enablement issues. For immutable OS users, detailed instructions are available for rebasing to Silverblue 45, while Fedora Atomic Desktops now utilize the new Anaconda Web UI and have migrated their repositories to the atomic-desktops organization, offering streamlined engagement for future contributors.

To avoid disruptive surprises, users and system administrators should note several key technical shifts in this release. The Anaconda installer now includes native support for Stratis storage configuration, simplifying advanced local storage management through an easy-to-use interface. Additionally, the unmaintained NetworkManager-vpnc and NetworkManager-fortisslvpn plugins are officially retired in Fedora 45, requiring users to migrate to actively supported VPN alternatives to maintain enterprise connectivity. Finally, on the infrastructure side, a brief planned server outage occurred on November 6th to reboot main VPN, email, and bastion servers into a new kernel for CVE mitigation, ensuring the ongoing security of the project's backend services.

Council

This week, the Council focused on the long-term future of Fedora's issue tracking and ongoing image unification efforts. A major discussion was initiated regarding the potential transition from Bugzilla to a Forgejo-integrated system (related to FESCO#3664), weighing the necessity of adopting modern, open-source infrastructure against concerns over Forgejo's current maturity and feature parity. Additionally, the agenda for the November 5th Bootable Image Unification ("Atomic Fusion") meeting was published, featuring a review of the project board, a seed proof-of-concept demo, and a planned presentation to the Workstation Working Group.

Contribution opportunities

Learn more about the Council team.

FESCo

During this week, FESCo celebrated the release of Fedora 45 and announced upcoming elections. The committee held a meeting and processed numerous tickets, focusing heavily on the future of Fedora's issue tracking system, with extensive debate on whether to migrate to Forgejo or maintain a community-run Bugzilla instance. Other major topics included the coordinated removal of the legacy DNF4 stack and Modularity, as well as handling the deprecation of X11 support in KDE Plasma 6.8 for stable releases.

Decisions

Contribution opportunities

Learn more about the FESCo team.

Mindshare

This week, Mindshare began early planning for the Virtual F46 Release Party, aiming for May 2027, to ensure a smooth event by crowd-sourcing ideas and recruiting role leads well in advance. Additionally, a community member reached out to organize an informal meetup for Fedora, CentOS, AlmaLinux, and RockyLinux contributors attending SFSCON 2026 in Bolzano, Italy.

Contribution opportunities

Learn more about the Mindshare team.

Magazine

This week, the Magazine group's activity centered around a comprehensive guide on Complete FIDO2 Integration with Fedora Luks2, Unlock, GUI Login, and Sudo Auth. Administrative actions were taken to split three posts from this discussion into a new topic dedicated to revising the guide for Fedora Linux 44.

Contribution opportunities

Learn more about the Magazine team.

Fedora Join

Andrew Heath introduced himself to the Fedora community, sharing his extensive background in enterprise Linux, infrastructure automation, and image building. He expressed interest in contributing to packaging, image building, QA, and infrastructure automation. In response, he was welcomed by the community and advised to engage with the packaging team in their Matrix room to find a sponsor and initial tasks.

Contribution opportunities

Learn more about the Fedora Join team.

Ambassadors

The Ambassadors group saw two forum discussions this week. A new contributor asked for help setting up their Fedora Campus Ambassador profile, including access to the wiki, Fedora People, and Libravatar, and received troubleshooting steps from the community. Additionally, a member started an organizational thread to coordinate a meetup for Fedora, CentOS, AlmaLinux, and RockyLinux contributors attending SFSCON 2026 in Bolzano, Italy.

Contribution opportunities

Learn more about the Ambassadors team.

Workstation / GNOME

A brief 20-minute meeting was held on November 3rd, following up on the agenda from October 27th. The original agenda included topics such as Fedora 45 blockers and exceptions, appstream-data automation, and DNF updating without wheel.

Learn more about the Workstation / GNOME team.

KDE

This week, the Fedora KDE group navigated discussions regarding Plasma 6.8 updates and overall desktop stability. Notably, the update to Plasma 6.8 officially drops X11 session support upstream, resulting in the obsoletion of kwin-x11 and plasma-workspace-x11 packages in Fedora 44. Users relying on X11 were advised that locking packages might prevent future UI updates, though community workarounds like Copr repositories have emerged. Additionally, the community discussed the marketing and perceived stability of Fedora KDE, with maintainers emphasizing that upstream KDE's rapid release cadence inherently involves trade-offs. Users seeking long-term support might look toward LTS distributions, while those experiencing bugs are encouraged to contribute directly to upstream bug resolution.

Decisions

Contribution opportunities

Learn more about the KDE team.

Server

The Server Working Group celebrated the release of Fedora 45 Server and immediately began preparing for Fedora 46 by setting up a new testing project. A significant portion of the week was dedicated to the "Strengthening Server Updates" project, focusing on system resilience using LVM snapshots. Following the F45 release, the group closed numerous tracking tickets for system-wide changes and package updates.

In addition, the group discussed ongoing work on Ansible support, deciding to catch up on outstanding tasks over the next two weeks before reconvening on the topic. New contributors joined the meeting and immediately volunteered to help with testing and documentation efforts.

Decisions

Contribution opportunities

Learn more about the Server team.

Infrastructure

The Infrastructure team successfully navigated the Fedora 45 release, officially lifting the infrastructure freeze on November 4th. The week involved significant maintenance and troubleshooting, including resolving a storage-related outage on Fedora Forge by resizing its Persistent Volume Claim and NetApp volume, and investigating persistent login issues with Fedora Accounts (FAS) linked to FreeIPA OTP interactions.

In addition to routine maintenance, the team began planning the deployment of Siguldry to the production environment for RPM and OSTree signing. They also scheduled a mass upgrade and reboot of infrastructure servers for November 19th, and discussed ongoing efforts to optimize AWS resource usage and clean up untagged cloud instances.

Decisions

Contribution opportunities

Learn more about the Infrastructure team.

Release Engineering

Fedora 45 has been officially released, with the team handling final release candidate composes, signing the IoT compose, and managing post-release cleanup and synchronization. During the rollout, a minor synchronization issue with the Labs images was manually resolved, and discussions were held to better align fedora_distro_aliases and releases.json updates in future cycles.

In addition to the release, the team resolved several infrastructure and build issues. This included fixing broken RHEL 9 repositories for EPEL 9 builds, addressing a bug where Rawhide .treeinfo files were missing kernel image information, and removing several underpowered x86_64 hosts from the heavybuilder channel to prevent Out-Of-Memory errors during large builds like Chromium.

Decisions

Contribution opportunities

Learn more about the Release Engineering team.

Quality

The Quality team successfully verified and tested the release candidates for Fedora 45, officially declaring it "GO" for release, alongside publishing and updating the Common Issues. The team also hosted a Test Week for Linux Kernel 7.3, encouraging users to test the kernel rebase on Fedora 44 and 45.

In other activities, the team concluded the F45 test days planning and GRUB EFI for Confidential Computing test days, while scheduling an upcoming KDE Plasma 6.8 test week for November 9-15. Infrastructure and CI improvements continued, including fixes for ELN Koji repositories and successful Fedora 45 installations on Beaker hardware. The team also finalized their requirements for the Bugzilla to Forgejo migration.

Decisions

Contribution opportunities

Learn more about the Quality team.

Websites and Apps

This week, the Websites and Apps team resolved an issue where the x86_64 folder was missing from the Fedora 45 Labs download page by syncing the content and rebuilding the site. The team also successfully closed the F45 beta release tracker and opened tickets for UI improvements, including fixing dark-mode logos on the CoreOS page and improving contrast in the Fedora Media Writer section. In addition, a community member reported that the captive portal check URL is on an HSTS-preloaded domain, which breaks Wi-Fi login detection; the infrastructure team plans to move it to another domain in the future. Finally, a bug in Fedocal where events with past repeat-end dates fail to appear was identified and resolved for a user.

Decisions

Contribution opportunities

Learn more about the Websites and Apps team.

Design

The Design team focused on the initial sketches for the F46 wallpaper, discussing the use of alternative geometric shapes for bubbles while prioritizing iridescence. They also reviewed poster designs, noting layout inconsistencies and the need for better text hierarchy and spacing, and successfully closed the F45 Virtual Release Party graphics ticket. Additionally, the team discussed accessibility improvements for international audiences, agreeing to spell out acronyms like DEI. In the Matrix chat, automated alerts indicated that the "Fix time of day path" action failed in both the main and f45-backgrounds branches of the backgrounds repository.

Decisions

Learn more about the Design team.

Docs

The Fedora Docs team successfully navigated the Fedora 45 release, merging numerous release notes covering updates like GNOME 51, KDE Plasma 6.8, and various system changes. Following the release, the team is restructuring the release notes repository to stop versioning; future notes will be built directly from the main branch, displaying the three most recent supported releases on a single page while older notes remain available via the Internet Archive.

Additionally, the team is revamping its infrastructure by transitioning the site-builder repository to build from main rather than prod. They are also evaluating "Bruce," a new broken-link detection script, for CI integration to automatically generate static reports and eventually file issues for broken links. Furthermore, discussions are ongoing regarding Antora component consolidation to allow cross-repository module inclusion and integrating the Fedora Design Suite documentation.

Decisions

Contribution opportunities

Learn more about the Docs team.

Legal

In a discussion regarding the koneko license and copyright, Cristian Le followed up on concerns regarding copyrighted sprites included in the project, specifically characters from Cardcaptor Sakura and the BSD Daemon. Following previous advice to drop the artwork, Cristian confirmed that the issue has been flagged to the upstream developers and that the problematic sprites will be removed via a downstream patch if necessary.

Decisions

Learn more about the Legal team.

COPR

This week, the COPR team successfully completed a scheduled server upgrade on November 3rd, bringing new features and bug fixes to the platform. Following the upgrade, an ongoing data migration to Pulp temporarily affected several projects (alphabetically from "sar" to "siddharthvipul1"), causing some 404 errors and pending builds which are expected to resolve as the migration progresses. Additionally, the team discussed the timeline for IPv6 support on the Pulp instance, estimating a fix for early next year, and provided support for building bleeding-edge Rust packages with vendored crates in Copr.

Decisions

Contribution opportunities

Learn more about the COPR team.

EPEL

This week in EPEL, discussions highlighted a known daily cache delay in the CentOS Stream repo for Fedora's Koji, which temporarily caused scratch build failures in epel9-next (URL). Security updates were a major focus, with uv (v0.13.5) and ruff (v0.17.2) being pushed to stable for the EPEL10 leading branch to address multiple RUSTSEC vulnerabilities and the eMudhra CA compromise (URL). Additionally, pipx is being retired from EPEL9 due to 23 security vulnerabilities that cannot be practically patched on the older Python 3.9 stack (URL). Other activities included the EPEL 10.2 retirement announcement, progress on bringing mailman to EPEL10, and participation in the release party CLE presentation.

Decisions

Learn more about the EPEL team.

ELN

The ELN SIG held a meeting on November 3, 2026 (meeting log). Key updates include the complete removal of dnf-4 from ELN, the completion of rebuilds for libxml2 2.15, and the replacement of perl-Params-Util with perl-Params-SomeUtil. Additionally, the Content Resolver now displays daily diffs. On the RISC-V front, approximately 140 packages have been built, though progress is currently paused pending fixes for toolchains like gcc, golang, and rust. The group also discussed ongoing issues with KDE Discover (Issue #633) and the unmaintained libappstream-glib (Issue #486), as well as upcoming libical4 rebuilds.

Decisions

Learn more about the ELN team.

Atomic

This week, the Atomic group focused on bootable image unification ("Atomic Fusion") with an upcoming presentation to the Workstation WG and a seed proof-of-concept demo (Meeting Agenda). In addition, there are ongoing discussions about rebasing Fedora Atomic Desktops on Fedora Bootc base images, which will modernize the build flow (Issue #88).

Several technical issues were also addressed, including a bug where systemd-oomd fails to intervene during memory exhaustion on Kinoite 44 (Issue #130), a syncing issue with the Fedora Cosmic-Atomic image (Issue #137), and an anomaly where rpm-ostree stable commits occasionally bundle packages from the updates-testing repository (Discussion).

Decisions

Contribution opportunities

Learn more about the Atomic team.

CoreOS

This week, the CoreOS team celebrated the general availability release of Fedora Linux 45. The testing stream has been successfully rebased to version 45.20261030.2.1, bringing notable changes such as native Butane support in Ignition, the use of chunkah for better layer reuse in container images, the relocation of RPM repository configs out of /etc, and the update to Podman 6.0. The team is currently in the post-release cleanup phase and has already opened the tracker for the upcoming Fedora 46 rebase. In addition to the release activities, the team addressed several critical bugs and infrastructure tasks. A fix for the IPv4 TCP use-after-free vulnerability (CVE-2026-98432) was shipped in the stable stream, and workarounds are being tested for an ext4 /boot corruption issue affecting upgrades. The team also approved a proposal to switch Konflux-driven streams to a Jenkins poll-based import model to simplify downstream pipeline management.

Decisions

Contribution opportunities

Learn more about the CoreOS team.

IoT

This week, the IoT group focused on bootable image unification and resolving a system upgrade issue. Laura Santamaria shared the agenda for the "Atomic Fusion" meeting, which included a seed proof-of-concept demo and a presentation to the Workstation Working Group (URL). Additionally, a user reported a bug where upgrading to Fedora 45 fails due to a missing GPG public key in rpm-ostree. The issue was resolved locally by updating the gpgkeypath in the fedora-iot.conf file to point to /usr/share/pki/rpm-gpg/ (URL).

Contribution opportunities

Learn more about the IoT team.

Cloud

This week, the Cloud group focused on image configuration and distribution infrastructure. A key update involves adding the SUSPEND_SAFE_FPR guest OS feature to Fedora Cloud GCP images to address a page reporting suspend UAF vulnerability (CVE-2026-74481), which is now being applied to new nightly builds (Issue 449). Additionally, following the announcement that the HCP Vagrant Registry is shutting down on December 31, the group is discussing setting up a self-hosted Vagrant registry to ensure continued availability of Vagrant boxes, drawing inspiration from AlmaLinux's recent implementation (Issue 450).

Contribution opportunities

Learn more about the Cloud team.

Hummingbird

The Hummingbird group prepared for their upcoming "Atomic Fusion" (bootable image unification) meeting on November 5, 2026. The agenda included a project board review, a potential demo of a seed proof-of-concept, and preparations for presenting to the Workstation Working Group.

Contribution opportunities

Learn more about the Hummingbird team.

AI

The AI/ML SIG discussed new package reviews, notably OpenShell, an NVIDIA-driven tool for agent sandboxing. Packaging updates were announced, with the latest AI and ROCm packages now available in COPRs for released distributions, and new LLM servers like Gufo and Colibri landing in Rawhide. The group is also collaborating on a Fedora Magazine article highlighting the use of the pi-coding-agent to help Fedora contributors, which may evolve into a broader series exploring how AI is utilized within the Fedora ecosystem. Other chat discussions touched on integrating hardware volunteering for AI tasks and addressing Wayland compatibility issues for freelance time-tracking tools.

Decisions

Contribution opportunities

Learn more about the AI team.

RISC-V

The Fedora RISC-V team successfully finalized and announced the Fedora 45 RISC-V GA images, including Server, Container, and Cloud variants. A major focus this cycle was clarifying kernel recommendations: the 'Omni' kernel is highly recommended for most physical hardware to avoid issues like PCIe/NVMe data corruption on JH7110-based boards (e.g., VisionFive 2), while the 'Generic' kernel is primarily targeted at QEMU and a select few boards. Meanwhile, the bootstrap of Fedora ELN (Enterprise Linux Next) for RISC-V is making significant progress, with Koji fully configured for ELN and RVA23 channels, and over 140 packages already built. The team is also actively debugging hardware-specific issues, including GCC build hangs on the SpacemiT K3 and a QEMU KVM guest initialization bug.

Decisions

Contribution opportunities

Learn more about the RISC-V team.

Perl

This week, the Perl group focused heavily on package maintenance, dependency management, and security enhancements. Maintainers implemented source signature verification using openpgpverify for packages like perl-Net-DNS and mod_perl. Several packages received routine version bumps, including perl-Mozilla-CA, perl-CGI, and perl-Tk-Text-SuperText. Additionally, contributors collaborated on adjusting dependencies for downstream distributions, such as adding build conditionals for Lexical::Var in perl-Exporter-Tiny and disabling optional dependencies in RHEL builds for perl-File-ShareDir.

Decisions

Learn more about the Perl team.

Python

The Python group discussed reversing the deprecation of python-dateutil following a new upstream 4.0.0 release. Contributors agreed to undeprecate the package and patch out its new tzdata dependency to rely on the system's time zone data instead. Additionally, a proposal was made to automatically set LD_LIBRARY_PATH in %py3_test_envvars to streamline testing, and feedback is currently being sought on potential breakages.

Decisions

Contribution opportunities

Learn more about the Python team.

Rust

The Rust group focused heavily on security updates and package rebuilds this week, addressing multiple RUSTSEC advisories across crates like zstd, zip, ruzstd, rustls, and webpki-roots. Additionally, there was a mailing list discussion regarding a request to package crubit for Fedora and EPEL to support Chromium builds, though it faces significant hurdles due to its reliance on nightly Rust and unstable compiler internals.

Decisions

Contribution opportunities

Learn more about the Rust team.

Other Discussions

Orphaning packages

Package updates

New contributor introductions

All contribution opportunities

Quality Assurance and testing offer some of the most accessible entry points for community members outside of specific working groups. Contributors can participate in the Linux Kernel 7.3 Test Week and the upcoming KDE Plasma 6.8 Test Week, or help draft test cases for the Fedora Atomic Desktops Test Week. There are also numerous opportunities to test specific system features and provide feedback, such as evaluating "System Resilience Using LVM Snapshots" (Ticket #272), the btrfs-patrol snapshot tool, and the new self-updating kernel hardening feature. Furthermore, testers are needed to reproduce a memory exhaustion bug in Kinoite 44, verify if KDE processes are still crashing on boot, and validate a workaround for an ext4 /boot corruption issue in CoreOS.

For those with skills in technical writing, design, or event organization, there are several ways to make an immediate impact. The community is seeking volunteers to fill Wrangler, Speaker, Design, and Promotion roles for the Virtual F46 Release Party, as well as attendees to connect at SFSCON 2026. Writers can help draft Fedora Magazine articles covering Server Update Resilience and AI in Fedora, or write a how-to guide for post-installation server updates (Ticket #271). Documentation contributors are encouraged to review F45 Release Notes pull requests, replace legacy includes with Antora syntax (Issue #38), and provide feedback on integrating the Design Suite docs. Additionally, general feedback is requested on the proposed transition to Forgejo and agenda topics for the Bootable Image Unification meetings.

Contributors with system administration and infrastructure experience can assist with vital operational tasks, and mentorship is available for newcomers interested in virtualization and infrastructure. Immediate needs include setting up a self-hosted Vagrant registry for the Cloud SIG, configuring Zabbix monitoring for the staging autosign service and Oraculum, and cleaning up NetApp and host storage. Automation enthusiasts can help the COPR team set up PyPI upload automation for copr-cli tags, or assist the Server SIG with creating an Ansible management CLI and configuring CI/CD runners (Ticket #268). There is also an ongoing investigation into persistent login errors on accounts.fedoraproject.org related to FreeIPA OTP modules.

Developers and packagers can contribute by adopting orphaned packages like cmake and c-toxcore, or by helping identify tools that still depend on the legacy DNF4 stack for its planned removal. The Rust SIG needs help rebuilding applications that vendor affected versions of libraries like zstd and rustls, and porting others to secure releases. Web developers can submit fixes for missing dark-mode logos on the CoreOS page and review Maubot plugin pull requests. Finally, systems programmers can tackle complex hardware issues, such as debugging a hard lockup during GCC and Rust builds on RISC-V SpacemiT K3 hardware, or investigating a guest initialization failure on RISC-V KVM hosts.

09 Nov 2026 9:48am GMT

08 Nov 2026

feedFedora People

Fabio Alessandro Locati: On sovereign AI

08 Nov 2026 11:00pm GMT

07 Nov 2026

feedFedora People

Kevin Fenzi: misc fedora bits: first week of november 2026

Kevin Fenzi's avatar Scrye into the crystal ball

Hello everyone. Another week gone by and some longer form recapping.

Fedora 45 released!

Fedora 45 was released on tuesday. Things went mostly smoothly, with just some few things needing tweaking. There was also some Labs missing from the master mirror sync (fixed) and torrents (will be fixed soon).

Our master mirrors were doing 20-25Gbps a second for tuesday and wed, so definitely lots of bits flowing.

I think this is a pretty solid release, I hope you like it too.

Post release unfreeze

After the release was all out, we ended our Infrastructure freeze. I merged/deployed 8 pull requests that were blocked by the freeze, and processed some ticket backlog. More of that next week.

The "AI" security apocolypse

So, there's been a lot of discussion in social media/around about all the new security vulnerabilities that are being found and the effect that has been having on open source projects and maintainers. It's quite relentless over the previous months for many folks, and has a lot of ill effects, including:

  • Always having to be ready for security bugs

  • No more disclosure time/embargoes, so you have to release fast

  • Inability to have time to actually work on features or regular maint, have to focus on security all the time.

Thats all well known, but I thought I would add the effect this has on operations folks. Case in point, late last week anthropic announced they had found a criticial bug in the linux kernel (all versions at the time after 4.14 or so). This became CVE-2026-98432, with a super high CVSS score (9.8 out of 10!).

I looked at it last weekend and anthropic in their announcement said: "In our proof of concept, it takes 48 minutes to leak a kernel pointer and another five minutes to reach the shell command execution." But it doesn't actally provide any details. Whats the connection? whats the kernel? Whats the hardware?

Everything else I saw said no one had seen a public exploit yet. Forgive me for not trusting a company that has a large incentive to talk up their tooling and a track record of breathless announcements that turn out to not be exactly what they say.

In any case, I upgraded most of out public facing servers as soon as their was a RHEL update, along with our openshift clusters. However there were a few that I wanted to actually schedule an outage for just in case there was issues, so I scheduled that for friday. I also had to wait until after release, because I didn't want to break things right before our release went out.

By the time friday rolled around: There were 2 new kernel updates fixing more CVEs and 2 more openshift updates (fixing the same).

Granted that it's nice to be in a state where you can just reboot anything as soon as updates come along, but there's cases where that is just not a very great idea (like if you are about to do a major release and don't want to possibly break things).

Anyhow, I am sure it's not going to get better for a while, but I hold out some hope that someday we will have found all the obvious bugs and it will slow down.

As always, comment on the fediverse: https://fosstodon.org/@nirik/117576954904513971

07 Nov 2026 7:45pm GMT

Akashdeep Dhar: Community Connection Part Two - IndiaFOSS 2026

Akashdeep Dhar's avatar Community Connection Part Two - IndiaFOSS 2026

We took some time to interact with the booth visitors at the IndiaFOSS 2026 conference's Red Hat Community Booth. While representing Fedora Project on the event grounds and handing out special swags, we were the conduits for the community's sentiments both as users and contributors to free and open source software projects like that of ours.

11:44am IST

Community Connection Part Two - IndiaFOSS 2026
Manifest A
  1. Open Alternatives
    LibreOffice Calc could be used as a zero-cost in-place software alternative to Office Excel for taxation, compliance and logistics.
  2. Software Interoperability
    Proprietary formats from Office Excel are a barrier for cross-platform collaboration and open formats should hence be preferred.

12:12pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest B
  1. Beginner Friendly
    Starting from Microsoft Windows, it is crucial to account for a smoother learning curve while seeking next alternatives for operating systems.
  2. Individual Requirements
    Alternatives can be tried in virtual machines and live environments to check if they fit their personal needs or if other variants are required.
  3. Innovative Approach
    The fast release cycle does not necessarily mean that Fedora Linux is unstable as all the updates are duly tested before being published.
  4. Gradual Exploration
    A good starting point with a general purpose GNU/Linux distribution like ours could be helpful in someone learning about the ecosystem.

12:20pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest C
  1. Personal Exploration
    After jumping in the deep end with Arch Linux's installation steps, a CA student found Fedora Linux's installation steps to be refreshing.
  2. Troubleshooting Resources
    The active community helped them resolve software and hardware issues, with Realtek WiFi adapters on their Lenovo LOQ laptop device.
  3. Getting Occupied
    With the information on Join SIG and FAS accounts, they were asked to participate and find their circle of interest within the community.
  4. Desktop Experience
    Their personal usage with i3 window manager and various dotfiles let them to truly make the Fedora Linux experience as their own.

12:36pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest D
  1. EndeavourOS Movement
    Seeking a fresh desktop environment experience from GNOME, they moved from Fedora Linux to EndeavourOS, only come back later.
  2. Positive Experience
    Acknowledging Fedora Linux's capabilities, they admitted it to be mostly GNOME, and hence, the KDE variant was suggested to them.
  3. Encouraging Contributors
    They appreciated how they could get started with contributing meaningfully to Fedora Project with zero technical expertise to begin with.
  4. Software Availability
    Some moved away from Fedora Linux as certain proprietary cyber security tools were not available packaged in the official repositories.
  5. Diverse Opportunities
    Community driven mentorship guidance helped individuals with designing, testing, documenting, triaging etc. to help Fedora Project.
  6. Existing Contributions
    They previously helped with software packaging build systems for 3D modelling tools and libraries, with UPI support for various platforms.
  7. Contribution Motivations
    Their participation was a passion project rooted in community connection and निष्काम सेवा or selfless service, with freedom and sharing.
  8. Maintainer Challenges
    Human reviews for generated contributions made it harder for maintainers to provide meaningful efforts expended to guide contributors.
  9. Controversial Opinions
    Excessive generation significantly undermines meaningful contributions, with constant struggles for finding time to review everything.
  10. Genuine Contributions
    Open source software movement thrives on genuine participation, shared ownership, constructive feedback and welcoming communities.

02:02pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest E
  1. Personal Problems
    The participant shared contributions to basic call conversation recording for Android phones and generic kernel images for Snapdragon.
  2. Appreciating Community
    Without any factors that discouraged them from participation, they had blessings for multimedia suite like VLC and MPV in the open.
  3. Exploring Alternatives
    From Endeavour Linux to Fedora Linux, they experimented with window managers and desktop environments to see what fits the best.
  4. Proprietary Limitations
    Users cannot investigate issues and resolve problems in proprietary codebases, thus making it crucial to explore what everyone uses.

02:10pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest F
  1. Atomic Future
    Immutable distributions are sought to eventually replace traditional installations with package managers leading to greater reliability.
  2. Habitual Transitions
    Widespread adoption would require workflow changes to users habituated to classic commands and hence, this will take some time.
  3. Reproducible Configuration
    Tooling like Ignition and Butane enable shareable customization with recommendation to directly use YAML configuration for processing.
  4. System Provisioning
    While NixOS provides greater advanced controls, the Fedora CoreOS suite covers the requirements without a steep learning curve.
  5. Bootable Containers
    Image mode operating systems are gradually becoming the refreshed normal with the layering packages for purpose specific systems.
  6. Immutable Systems
    Comparing against previous controversial changes that ended up being standards, the immutable systems would soon end up being one.

02:20pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest G
  1. Recommended Discovery
    The participant started using Fedora Linux on their friend's recommendation before moving on to join many parts of the community.
  2. Contemporary Relevance
    For a general purpose operating system, it is important to have access to recent updates in the rapidly evolving software landscape with AI.
  3. Improving Experience
    They sought Fedora Linux as a user friendly operating system and its versatility and stability are what keeps drawing users towards it.
  4. Welcoming Community
    The openness and patience of the mentoring members made them want to stay back in the community and keep helping in their ways.
  5. Friends Foundation
    From Friends, Features, Freedom and First - they preferred the Friends foundation the most as it resonated with why they contribute here.
  6. General Usability
    Instead of treating zero price as an excuse for poor usability, open source should invest more into design thinking and user experience.

02:34pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest H
  1. Better Performance
    A third year engineering student from PES University Bengaluru went from Microsoft Windows to Fedora Linux for its lightweightness.
  2. Installation Experience
    The setup process was relatively straightforward with the Anaconda WebUI but needed more troubleshooting for fingerprint readers etc.
  3. Community Resources
    Using the official subreddit and Fedora Discussions for initial issues, they gradually began answering questions from fellow members.
  4. Contributing Back
    After being introduced to FAS accounts and Join SIG, they intend to contribute more into updating documentation and other resources.
  5. Free Alternatives
    They had found home in the LibreOffice Suite and are appreciative of the open formats to help collaborate with other platforms equally.
  6. Difficult Balance
    From an over-involved experience of Microsoft Windows, they mentioned how Fedora Linux stayed out of their way while they worked.
  7. Exploring Editions
    They were introduced to the multiple variants and distinct editions of Fedora Linux for various purposes like servers and embedded etc.
  8. Encouraging Contributors
    They made it a point to promote Fedora Linux among their circles as a means to give back to the free and open source software resources.
  9. Exploration Decade
    Another participant explored over fifty alternatives in the previous decade before going with a custom build of Manjaro Linux now.
  10. Experienced Perspectives
    With an appreciation for Fedora Linux's overall simplicity and software availability, they are looking forward for image mode.
  11. Immutable Appeal
    Fedora Silverblue and other immutable alternatives helped shape consumer operating systems like SteamOS with a similar architecture.
  12. Problem Solving
    Multiple individuals can come together to solve problems that can be iterated upon by others, thus finding strength in the community.
  13. User Generated
    A great example was that of Arch User Repository (AUR) and Collection of Private Repositories (COPR) to allow for that to happen.
  14. Hardware Compatibility
    When official companies hold back their hardware devices, community members have come together to deliver solutions for the same.
  15. Vendor Partnerships
    Partnering with Slimbook, Lenovo, Framework and others have allowed Fedora Linux to be available out-of-the-box in the laptops.
  16. Innovative Stability
    The conversation concluded with recognizing how Fedora Linux balances innovation and stability at the cost of missing release dates.

03:00pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest I
  1. Developer First
    Since using it for almost over two years now, they appreciated the recent build updates that Fedora Linux provided for development.
  2. Update Frequency
    Frequent updates every after six months can be offputting for some, but that is exactly what makes them recommend Fedora Linux.
  3. Experimental Discovery
    From using GNU/Linux distributions on Raspberry Pi to daily driving Fedora Linux on resource limited hardware devices, they grew.
  4. Community Career
    They plan to make a career in free and open source software communities at some time after learning the ropes from the mentors.

03:08pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest J
  1. Technological Compliance
    The two participants from the legal sector assisted the startups establishing platforms and navigating regulatory challenges.
  2. Legal Oversight
    Software companies sometimes avoid compliance requirements if they comply with one jurisdiction since it costs a fortune.
  3. Generated Misuse
    Generated terms of services without a foundational understanding and substantial review can only end up in a bad manner.
  4. Professional Expertise
    Lawyers invest considerable efforts in deep research and due diligence to understand the clients produce before providing advice.
  5. Limitation Violations
    SaaS providers copy products from competing services by barely making superficial changes rather than addressing issues.
  6. Regulatory Responsibility
    Financial pressure should not be an excuse to minimize necessary legal expenditure, as an oversight could cause great fines later.

07 Nov 2026 6:30pm GMT

Adam Price: Glory or Gold

07 Nov 2026 12:00pm GMT

06 Nov 2026

feedFedora People

Fedora Infrastructure Status: Server reboots

06 Nov 2026 9:00pm GMT

Fedora Infrastructure Status: forge.fedoraproject.org is down

06 Nov 2026 11:00am GMT

Remi Collet: 🎲 PHP version 8.4.28RC1 and 8.5.13RC1

Remi Collet's avatar

Release Candidate versions are available in the testing repository for Fedora and Enterprise Linux (RHEL / CentOS / Alma / Rocky and other clones) to allow more people to test them. They are available as Software Collections, for parallel installation, the perfect solution for such tests, and as base packages.

RPMs of PHP version 8.5.13RC1 are available

RPMs of PHP version 8.4.23RC1 are available

ℹ️ The packages are available for x86_64 and aarch64.

ℹ️ PHP version 8.3 is now in security mode only, so no more RC will be released.

ℹ️ Installation: follow the wizard instructions.

ℹ️ Announcements:

Parallel installation of version 8.5 as Software Collection:

yum --enablerepo=remi-test install php85

Parallel installation of version 8.4 as Software Collection:

yum --enablerepo=remi-test install php84

Update of system version 8.5:

dnf module switch-to php:remi-8.5
dnf --enablerepo=remi-modular-test update php\*

Update of system version 8.4:

dnf module switch-to php:remi-8.4
dnf --enablerepo=remi-modular-test update php\*

ℹ️ Notice:

Software Collections (php84, php85)

Base packages (php)

06 Nov 2026 5:47am GMT

05 Nov 2026

feedFedora People

Fabio Alessandro Locati: Nebula from Ansible

05 Nov 2026 11:00pm GMT