Planned Outage - updates / reboots - 2025-04-24 20:00UTC
There will be an outage starting at 2025-04-24 20:00UTC
which will last approximately an hour.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2025-04-24 20:00UTC'
Reason for outage:
We will be applying a change to the firewall on most of our servers and
possibly rebooting.
Services may go down during the outage window, more likely some
dropped/denied packets.
Affected Services:
Many services will be affected, but most should only be down for a
short time.
Ticket Link:
https://pagure.io/fedora-infrastructure/issue/12510
Please join #admin:fedoraproject.org / #noc:fedoraproject.org on
matrix.
Please add comments to the ticket for this outage above.
Updated status for this outage may be available at
https://www.fedorastatus.org/
Wiki - https://fedoraproject.org/wiki/Changes/WaylandOnlyGNOME
Discussion thread -
https://discussion.fedoraproject.org/t/f43-change-proposal-wayland-only-gno…
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
== Summary ==
Remove the GNOME X11 packages from the Fedora repositories. All users
of the GNOME X11 session will be migrated to the GNOME Wayland
session.
== Owner ==
* Name: [[User:Ngompa| Neal Gompa]]
* Email: ngompa13(a)gmail.com
== Detailed Description ==
As part of the upstream effort to remove X11 support from GNOME,
Fedora will no longer include the GNOME X11 packages. The GNOME X11
session receives virtually no testing and little to no development.
There has been active effort upstream for several years now to close
out the remaining user experience blockers to dropping the X11 session
code, and that work completed with GNOME 48. The upstream target is to
[https://gitlab.gnome.org/GNOME/gnome-session/-/merge_requests/99 drop
it for GNOME 50], with it being
[https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/277 disabled by
default at compile time for GNOME 49].
This Change effectively implements the GNOME 50 target in GNOME 49
because there is no one to support any issues with GNOME X11 upstream.
The X11 session is already quite buggy, with serious unfixed issues in
Mutter (like [https://bugzilla.redhat.com/2179566 rhbz#2179566] and
[https://gitlab.gnome.org/GNOME/mutter/-/issues/3868
glgo#GNOME/mutter#3868]) and recently
[https://www.phoronix.com/review/ubuntu-2504-x11-gaming Phoronix could
not benchmark GNOME X11 vs Wayland] because "GNOME on X11 wasn't even
working due to bugs".
Dropping the GNOME X11 now allows us to reconcile with reality that
the GNOME X11 session is simply not supported anymore (either by us or
upstream GNOME).
== Benefit to Fedora ==
This aligns us with the effort going on upstream to retire the GNOME
X11 session. It also aligns us with Fedora KDE. Like the Fedora KDE
SIG, the Fedora Workstation WG recommends and supports the Wayland
platform for graphics.
Fedora Workstation has a long history of developing and promoting the
Wayland experience for GNOME, and
[https://fedoraproject.org/wiki/Changes/WaylandByDefaultOnNVIDIA it
has been the primary experience for all users (including those with
NVIDIA cards) since Fedora Linux 36]. This continuation of
[[WaylandOnlyGNOMEWorkstationMedia|the work in Fedora Linux 41 to drop
the X11 session from the media]] reaffirms our commitment to the
Wayland GNOME experience in furtherance of the goal to provide the
highest quality GNOME experience through Fedora Workstation.
== Scope ==
* Proposal owners: Drop the GNOME X11 packages and have the Wayland
versions obsolete them
* Other developers: N/A (not needed for this Change)
* Release engineering: N/A (not needed for this Change)
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with the Fedora Strategy: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
Systems upgrading from older releases of Fedora Workstation using the
X11 session will be automatically transitioned to the GNOME Wayland
session. GDM will no longer support launching X11 sessions. Users of
X11 will need to select another login manager and desktop environment
that continues to offer X11 (such as LightDM with Cinnamon or MATE).
== Early Testing (Optional) ==
Not applicable to this change.
== How To Test ==
For users with GNOME X11 installed and have it selected, uninstall
<code>gnome-session-xsession</code> and
<code>gnome-classic-session-xsession</code> packages and reboot to see
GDM automatically switch you to GNOME Wayland.
== User Experience ==
Users will no longer have the "GNOME on Xorg" session as an option for
the GNOME desktop.
== Dependencies ==
Not applicable for this change.
== Contingency Plan ==
* Contingency mechanism: Restore the GNOME X11 packages and re-enable
GDM's X11 support.
* Contingency deadline: Final freeze
* Blocks release? Yes.
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
The GNOME X11 session has been removed from Fedora Linux. Users
previously using GNOME on X11 will be transparently upgraded to the
GNOME Wayland session. X11 applications are still supported on GNOME.
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
Wiki - https://fedoraproject.org/wiki/Changes/perl5.42
Discussion thread -
https://discussion.fedoraproject.org/t/f43-change-proposal-perl-5-42-system…
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
== Summary ==
A new ''perl 5.42'' version brings a lot of changes done over a year
of development. Perl 5.42 will be released on May 2025. See
[https://metacpan.org/release/ETHER/perl-5.41.12/view/pod/perldelta.pod
perldelta for 5.41.12] for more details about new release.
=== Completed Items ===
=== Items in Progress ===
=== Items to Be Done ===
* Get dedicated build-root from rel-engs <''f43-perl''>
* Upstream to release Perl 5.42
* Define perl_bootstrap in perl-srpm-macros
* Rebase perl to 5.42.0
* Rebuild all dual-lived packages (84) - otherwise dnf recommends
--skip-broken and fails
* Rebuild packages needed for minimal build-root
* Rebuild packages needed for building source packages from git repository
* Rebuild packages requiring ''libperl.so'' or versioned
''perl(:MODULE_COMPAT)'': Use Fedora::Rebuild dependency solver
* Undefine perl_bootstrap
* Rebuild packages having perl_bootstrap condition in spec file (54 packages)
* Rebuild packages requiring ''libperl.so'' or versioned
''perl(:MODULE_COMPAT)'': Use Fedora::Rebuild dependency solver
* Rebuild all updated packages
* [https://jplesnik.fedorapeople.org/5.42/ Final lists of results]
* Merge dedicated build-root to rawhide and remove the dedicated one by rel-engs
* Synchronize packages upgraded in ''f43'' build root
* Rebuild Perl packages: 0 of 601 done (0.00 %)
* Failed packages (0):
* Unsatisfy dependencies (0):
== Detailed Description ==
New perl is released every year and updates containing mainly bug
fixes follow during the year. The 5.42.0 version is stable release
this year.
== Benefit to Fedora ==
Up-to-date and latest perl release will be delivered to Fedora users.
== Scope ==
Every Perl package will be rebuilt in a dedicated ''f43-perl''
build-root against perl 5.42.0 and then if no major problem emerges
the packages will be merged back to ''f43'' build-root.
* Proposal owners: New perl and all packages requiring ''libperl.so''
or versioned ''perl(MODULE_COMPAT)'' will be rebuilt into ''f43-perl''
build-root.
* Other developers: Owners of packages that fail to rebuild, mainly
perl-sig users, will be asked using Bugzilla to fix or remove their
packages from the distribution.
* Release engineering: [https://pagure.io/releng/issues #Releng issue
number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Release engineers will be asked for new ''f43-perl'' build-root
inheriting from ''f43'' build-root. After successful finishing the
rebuild, they will be asked to merge ''f43-perl'' packages back to
''f43'' build-root.
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Community Initiatives:
== Upgrade/compatibility impact ==
Vast majority of functionality will be preserved. Only the packages
that failed to build against perl 5.42 will be removed from the
distribution. That will require to remove those packages from the
existing systems otherwise a package manager will encounter
unsatisfied dependencies. The developers in Perl language are advised
to install ''perl-doc'' and ''perl-debugger'' packages.
== How To Test ==
Try upgrading from Fedora 42 to 43. Try some Perl application to
verify they work as expected. Try embedded perl in
[https://src.fedoraproject.org/rpms/openldap slapd] or
[https://src.fedoraproject.org/rpms/net-snmp snmpd].
== User Experience ==
There should not be any remarkable change in user experience. With the
exception that previously locally installed modules with a CPAN
clients will need a reinstallation.
== Dependencies ==
There is more than 3500 packages depending on perl. We will rebuild
only all dual-lived packages and packages which require ''libperl.so''
or versioned ''perl(MODULE_COMPAT)''. It means only about 600 packages
needs to rebuild. Most of them are expected not to break. Finishing
this change can be endangered only by critical changes in a toolchain.
''noarch'' packages don't need to be rebuilt now.
== Contingency Plan ==
* Contingency mechanism: If we find perl 5.42 is not suitable for
Fedora 43, we will revert back to perl 5.40 and we drop the temporary
build-root with already rebuilt packages.
* Contingency deadline: branching Fedora 43 from Rawhide.
* Blocks release? No.
== Documentation ==
* 5.42.0 perldelta
* An announcement on perl-devel mailing list
* An announcement on fedora-devel mailing list
== Release Notes ==
TBD
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
Wiki - https://fedoraproject.org/wiki/Changes/Use_COLR_for_Noto_Color_Emoji
Discussion thread -
https://discussion.fedoraproject.org/t/f43-change-proposal-use-colr-for-not…
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
== Summary ==
The Noto Color Emoji fonts have released some new files with the COLRv1 format.
The COLRv1 format is a color scalable font compared with the previous
color bitmap fonts.
== Owner ==
* Name: [[User:pwu| Peng Wu]]
* Email: pwu(a)redhat.com
== Detailed Description ==
The new Noto Color Emoji font uses the new COLRv1 format.
The COLRv1 format provides the color scalable emoji glyphs with
smaller file size.
== Feedback ==
== Benefit to Fedora ==
This new font format provides better scalable color emoji rendering
results and smaller file size.
== Scope ==
* Proposal owners: google-noto-emoji-fonts
* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: [https://pagure.io/releng/issues #Releng issue
number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines: N/A (not needed for this Change) <!--
REQUIRED FOR SYSTEM WIDE CHANGES -->
* Trademark approval: N/A (not needed for this Change)
* Alignment with the Fedora Strategy:
== Upgrade/compatibility impact ==
The Noto Color Emoji font will switch to use COLRv1 font format.
== Early Testing (Optional) ==
== How To Test ==
After upgrading to Fedora 43, the new color scalable emoji fonts will
replace the old color bitmap emoji font.
Please open some documents or web pages which contain the emoji
character sequence to check the emoji rendering results.
== User Experience ==
The new scalable font format should have better or similar rendering
results compared to the old bitmap font format.
== Dependencies ==
== Contingency Plan ==
* Contingency mechanism: If the new font format has some issues with
some applications, plan to provide another
google-noto-color-bitmap-emoji-fonts sub package for compatibility.
* Contingency deadline: Fedora Beta Freeze
* Blocks release? No
== Documentation ==
Spec: https://learn.microsoft.com/en-us/typography/opentype/spec/colr
== Release Notes ==
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
Wiki - https://fedoraproject.org/wiki/Changes/Modular_GnuPG_Packaging
Discussion thread -
https://discussion.fedoraproject.org/t/f43-change-proposal-modular-gnupg-pa…
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
== Summary ==
Currently GnuPG is packaged in a way that puts almost all tools and
services into a single, monolithic RPM package. However, only few
tools from the gnupg2 package are actually used by other tools and
users. With this change, core tools and optional utilities are split
off into separate packages.
== Owner ==
* Name: [[User:Decathorpe| Fabio Valentini]]
* Email: <decathorpe AT gmail DOT com>
* Name: [[User:Jjelen| Jakub Jelen]]
* Email: <jjelen AT redhat DOT com>
== Detailed Description ==
Currently GnuPG is packaged as a monolithic RPM that contains all
tools and services (except the S/MIME support, which is in
gnupg2-smime, but which is also pulled in by default).
This Change proposes to split the tools provided by the monolithic
gnupg2 package into different subpackages, in part based on in how
GnuPG 2.4 is packaged in debian:
* gnupg2: gpg executable
* gnupg2-dirmngr: certificate management service
* gnupg2-g13: encrypted file system containers
* gnupg2-gpgconf: core configuration utilities
* gnupg2-gpg-agent: cryptographic agent
* gnupg2-keyboxd: public key material service
* gnupg2-scdaemon: SmartCard daemon
* gnupg2-smime: S/MIME support
* gnupg2-wks: Web Key Service (WKS) client and server
* gnupg2-utils: non-essential utilities
* gnupg2-verify: gpgv executable
By default, all new subpackages except those for WKS client/server
(`-wks`) will get installed when gnupg2 is installed -- with
non-essential utilities in `-utils` being a weak dependency, like the
existing S/MIME `-smime` package.
This results in fewer unused programs and / or services being
installed and running, and would allow a more minimal install for
scenarios where only `gpg` or `gpgv` are needed, for example, for
signature verification during package builds.
Additionally, it allows swapping out the actual GnuPG implementation
with the one based on Sequoia-PGP, which only depends on `gpgconf` and
`gpg-agent` being present, but can otherwise function as a drop-in
replacement for `gpg` and `gpgv` (even via the GPGME library).
Draft implementation of this change is available in pull request:
https://src.fedoraproject.org/rpms/gnupg2/pull-request/23
Test builds are available in COPR:
https://copr.fedorainfracloud.org/coprs/decathorpe/gnupg2-split/
== Feedback ==
N/Y
== Benefit to Fedora ==
This change results in fewer unused executables and running services
being installed by default, making more components optional. It also
allows users to swap the gpg implementation on the system based on
their needs.
== Scope ==
* Proposal owners:
Packaging changes to the `gnupg2` package to introduce new subpackages.
Adapt packages that require utilities that have moved to other
subpackages of gnupg2 (TBD), file pull requests.
* Other developers:
Review and merge pull requests.
* Release engineering:
N/A (not a System-Wide Change)
* Policies and guidelines:
N/A (not a System-Wide Change)
* Trademark approval:
N/A
* Alignment with the Fedora Strategy:
N/A
== Upgrade/compatibility impact ==
On upgrade to Fedora 43, some non-essential GnuPG utilities will no
longer be available by default, and instead moved to the optional
`gnupg2-g13`, `gnupg2-utils`, and `gnupg2-wks` packages.
Alternatively, these optional packages could get pulled in on upgrade,
but not for "fresh" installs.
== How To Test ==
After upgrading to a Fedora version that has this change implemented,
most `gnupg2-` subpackages should get installed, except for those
noted in "Upgrade/compatibility impact" above. OpenPGP related
functionality of the system should continue working as expected (note
that this does *not* impact package management, which no longer uses
GnuPG in any way).
== User Experience ==
This Change should not affect most users. On a default install, some
non-essential GnuPG tools will no longer be included by default.
== Dependencies ==
N/A
== Contingency Plan ==
* Contingency mechanism:
The Change Owners will revert the changes to the gnupg2 package and
ensure an upgrade path for users who have already have the new
subpackages installed on their systems.
* Contingency deadline:
N/A (not a System Wide Change)
* Blocks release?
N/A (not a System Wide Change)
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
The previously monolithic GnuPG package (`gnupg2`) was modularized,
with several tools and non-essential utilities having been split into
separate subpackages. The non-essential utilities (in `gnupg2-utils`)
and some services that are unused on most systems are no longer
installed by default.
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
Wiki - https://fedoraproject.org/wiki/Changes/CoreOSStopPublishingOSTree
Discussion thread -
https://discussion.fedoraproject.org/t/f43-change-proposal-stop-publishing-…
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
== Summary ==
Stop publishing new updates for Fedora CoreOS to the cannonical OStree
repository at ostree.fedoraproject.org.
Instead, rely on OCI Images from the fedora quay.io repository.
== Owners ==
* Name: [[User:jbtrystram| Jean-Baptiste Trystram]] <jbtrystram(a)redhat.com>
* Name: [[User:Dustymabe| Dusty Mabe]] <dmabe(a)redhat.com>
== Detailed Description ==
With the rebase to Fedora 42 for Fedora CoreOS, we changed the source
of updates from the OSTree repository to OCI containers from
quay.io/fedora/fedora-coreos.
During the Fedora 42 release cycle, we will migrate existing Fedora
CoreOS nodes to use OCI images as well.
See https://fedoraproject.org/wiki/Changes/CoreOSOstree2OCIUpdates for
more details
As a continuation of that change, we will stop publishing updates to
the CoreOS branches built on Fedora 43 content in the OSTree
repository as they will no longer be used.
== Feedback ==
None yet.
== Benefit to Fedora ==
This will reduce releases workload and use less resources from Fedora
Infrastructure.
== Scope ==
* Proposal owners:
** Will update Fedora CoreOS release pipeline to stop publishing data
to the OSTree repository.
** Will update relevant documentation in Fedora CoreOS docs.
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with the Fedora Strategy: This align with the bootable
containers initiative.
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had a previous versions of
Fedora installed and are updated to the version containing this
change? Will anything require manual configuration or data migration?
Will any existing functionality be no longer supported? -->
== How To Test ==
New images of Fedora CoreOS next are already set to be deployed from
containers since the rebase to Fedora 42.
You can start a 42.20250316.1.0 image and watch it update from quay.io
instead of the usual OSTree repository.
== User Experience ==
Users who have not opted out of the OCI migration in Fedora 42 will
experience no change. Users who have opted out of the OCI migration
and are still using the OSTree repo for updates will need to migrate
to OCI to continue to receive updates for Fedora 43+.
== Contingency Plan ==
Keep releasing to the OSTree repository.
== Documentation ==
To be written. Tracked in:
https://github.com/coreos/fedora-coreos-tracker/issues/1895
== Release Notes ==
To be written. Tracked in:
https://github.com/coreos/fedora-coreos-tracker/issues/1895
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney