Hello all,
Fedora Linux 39 is going end of life for updates and support today,
2024-11-26.
No more updates of any kind, including security updates or security
announcements, will be available for Fedora Linux 39 after today. No
more pending updates for Fedora Linux 39 will be pushed to stable.
Fedora Linux 40 will continue to receive updates until approximately
one month after the release of Fedora Linux 42. The maintenance
schedule of Fedora Linux releases is documented on the Fedora Project
docs[1]. The docs also contain instructions[2] on how to upgrade from a
previous release of Fedora Linux to a version receiving updates.
Regards,
Fedora Release Engineering
[1] https://docs.fedoraproject.org/en-US/releases/lifecycle/#_maintenance_sched…
[2] https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-new-releas…
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
Hey folks,
Now that Fedora Linux 41 is out the door and Fedora Linux 39 will be
EOL next Tuesday, it's now time to continue down the path that was
outlined[1] when the Fedora Linux 40 Change to use KIWI for images[2]
was approved.
The Fedora Cloud Working Group is not interested in continuing to prop
up ImageFactory and as part of the agreement with Release Engineering,
the intent is to discontinue ImageFactory in Fedora infrastructure
during the Fedora Linux 42 development cycle.
Prior to Fedora Linux 40, ImageFactory was used to build Fedora Cloud
images, Fedora container images, and Fedora Cloud Vagrant images.
These have migrated to being built with KIWI under the aegis of the
Fedora Cloud WG. With Fedora Linux 41, two new spins were introduced
that use KIWI to build their images: Fedora MiracleWM[3] and Fedora
KDE Mobile[4] (both ARM disk images and live media ISOs). At this
point, we have confidence that every artifact currently being produced
by ImageFactory right now can be moved over to something we can
support.
Now, with ImageFactory being retired, you as image maintainers have two choices:
* Switch over to KIWI (using fedora-kiwi-descriptions[5]) for building
your images. This is what the Fedora Server WG[6][7] and Fedora KDE
SIG[8] have done. If you need help with doing this, the Cloud WG and
the KDE SIG are happy to assist in porting efforts. Upstream
developers of KIWI are also very responsive and able to assist if you
encounter issues in their Matrix room[9]. Efforts are also ongoing to
make it possible for the Respins SIG to continue to produce respins
using KIWI.
* Retire the ImageFactory-based artifacts. If you find you no longer
wish to produce the images that are built with ImageFactory anymore,
we can simply discontinue their production.
I and other members of the Fedora Cloud WG are identifying the
remaining users of ImageFactory and will be reaching out to each
stakeholder individually to help them make a choice for this
transition.
[1]: https://discussion.fedoraproject.org/t/f40-change-proposal-build-fedora-clo…
[2]: https://fedoraproject.org/wiki/Changes/KiwiBuiltCloudImages
[3]: https://fedoraproject.org/spins/miraclewm
[4]: https://fedoraproject.org/spins/kde-mobile
[5]: https://pagure.io/fedora-kiwi-descriptions
[6]: https://pagure.io/fedora-kiwi-descriptions/pull-request/97
[7]: https://pagure.io/pungi-fedora/pull-request/1404
[8]: https://pagure.io/pungi-fedora/pull-request/1412
[9]: https://matrix.to/#/#kiwi:matrix.org
--
Neal Gompa (FAS: ngompa)
Hello everyone,
With the advent of Fedora Linux 41 comes a new election cycle! This cycle
we have seats open in both the Mindshare Committee and the Fedora
Engineering Steering Committee (FESCo). We are now in the nominations
period, where you can nominate yourself, or someone you know to run for
election to one or both of these governing bodies of the project. If you
are nominating someone else, please make sure to get their permission. Each
term is for ~12 months.
To nominate yourself or someone else (with their a-ok), please visit the
following nominations pages:
FESCo
<https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations> -
five seats open
Mindshare Committee <https://fedoraproject.org/wiki/Mindshare/Nominations> -
one seat open
The nominations period will close on 2024-11-27 at 23:59:59 UTC.
As a reminder, the Fedora Council has moved to an annual election. There
will be two open seats for Fedora Council after the F42 release. The EPEL
Steering Committee also has an annual election cycle, and their open seats
are volunteer-based and their election cycle is in May.
If you have any questions, please dont hesitate to reach out.
Kindest regards,
Aoife
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
Planned Outage - Server update/reboots - 2024-11-20 21:00 UTC
There will be an outage starting at 2024-11-20 21:00 UTC,
which will last approximately 5 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2024-11-20 21:00 UTC'
Reason for outage:
We will be updating and rebooting servers to pick up the recent
RHEL 9.5 release as well as to move a number of instances to
Fedora 41 (including hopefully builders/koji hubs)
Affected Services:
Most maintainer / contributor services will be affected for some short windows during the outage.
Package maintainers are advised to wait for the outage to be over to launch any builds.
Ticket Link:
https://pagure.io/fedora-infrastructure/issue/12293
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/Xfce-4.20
Discussion Thread -
https://discussion.fedoraproject.org/t/f42-change-proposal-xfce-4-20-self-c…
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
== Summary ==
Xfce 4.20 is a stable release with proven components, provide features
to both new and power users alike. This change proposal is submitted
to sync fedora packages with the latest upstream release.
== Owners ==
* Name: [[User:nonamedotc| Mukundan Ragavan]], [[User:kevin| Kevin Fenzi]]
* Email: nonamedotc(a)fedoraproject.org, kevin(a)scrye.com
== Detailed Description ==
This change migrates Xfce desktop environment (DE) to the latest
version provided by upstream developers. This release brings, amongst
others, experimental support for Wayland.
Xfce 4.20 is expected to be released on 2024-12-15.
Xfce 4.20 roadmap: https://wiki.xfce.org/releng/4.20/roadmap
Some notes about Xfce 4.20 pre1 release -
https://alexxcons.github.io/blogpost_11.html
== Benefit to Fedora ==
Updating Xfce to 4.20 will provide Fedora Xfce users stable but latest
versions of upstream software. We will also be able to provide timely
bug fixes.
== Scope ==
* Proposal owners:
** Update core xfce packages to 4.20
** Rebuild plugins once core packages are build
* Other developers: N/A
* Release engineering: [https://pagure.io/releng/issues]
** List of deliverables: N/A
* Policies and guidelines: N/A
* Trademark approval: N/A
== Upgrade/compatibility impact ==
N/A
== How To Test ==
Users and testers can report bugs that they encounter based on
day-to-day usage. No special tests needed.
== User Experience ==
* A fresh install should have fully functional Xfce DE
* Upgrade from Fedora 41 or older should be mostly seamless
No special configuration or hardware needed.
== Dependencies ==
N/A
== Contingency Plan ==
* Contingency mechanism: N/A
* Contingency deadline: N/A
* Blocks release? N/A
* Blocks product? N/A
== Documentation ==
N/A
== Release Notes ==
Fedora 42 ships with Xfce 4.20.
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
Hi folks!
Tomorrow we will be hosting a few 'watch parties' in lieu of our
traditional release party. This is a trial effort to see if this works
better for our global community to enjoy these celebrations together.
Please check out the blog post on the rationale, and more importantly,
how to register for a watch party happening in your timezone, in the
blog post that just went live about it.
https://communityblog.fedoraproject.org/announcing-the-fedora-41-global-wat…
A big thank you to all the people who helped pull this together - most
especially the folks who pre-recorded the content on such a short
turnaround time!
Hope to see you tomorrow and enjoy the watch party of your choice :)
Aoife
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
Wiki - https://fedoraproject.org/wiki/Changes/RemovalPostgreSQL15
Discussion Thread -
https://discussion.fedoraproject.org/t/f42-change-proposal-retirement-of-po…
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 ==
PostgreSQL version 15 will be retired from Fedora 42 since there are
newer versions like 16 and 17. Version 16 is already the default
version (announced in [[Changes/PostgreSQL 16|PostgreSQL16 change]]),
and version 17 would be the alternative.
== Owner ==
* Name: [[User:ljavorsk| Lukas Javorsky]], [[User:fjanus| Filip Janus]]
* Email: ljavorsk(a)redhat.com, fjanus(a)redhat.com
== Detailed Description ==
With the addition of PostgreSQL-17 to Fedora 42, maintaining PG15 is
no longer necessary and creates a significant capacity burden.
This will also mean the retirement of the dependent components like
`postgresql15-pgaudit`, `postgresql15-pg_repack`, and
`postgresql15-decoderbufs`.
== Feedback ==
== Benefit to Fedora ==
Lesser PostgreSQL versions to maintain and newer versions with
additional features.
== Scope ==
* Proposal owners:
** Follow the [https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement…
Package Retirement Process]
* Other developers:
* Release engineering: [https://pagure.io/releng/issues #Releng issue number]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with the Fedora Strategy:
== Upgrade/compatibility impact ==
In the case user's still didn't upgrade to the default stream 16, the
standard upgrade strategy should be followed:
# Dump and restore upgrade
## Stop the `postgresql` service
## Dump the databases using `su - postgres -c "pg_dumpall >
/PATH/TO/pgdump_file.sql"`
## Backup all of the data in `/var/lib/pgsql/data/`
## Enumerate all postgresql-based packages by `rpm -qa | grep postgresql`
## Upgrade all installed (enumerated in the previous step) PostgreSQL
packages using (e.g. for upgrading to PG-16) `dnf install
PACKAGE_NAMES --allowerasing`
## Copy the old configuration files to the `/var/lib/pgsql/data/`
## Start the `postgresql` service
## Import data from the dumped file using `su - postgres -c 'psql -f
/PATH/TO/pgdump_file.sql postgres'`
# Fast upgrade using the pg_upgrade utility
## Stop the `postgresql` service
## Backup all of the data in `/var/lib/pgsql/data/`
## Enumerate all postgresql-based packages by `rpm -qa | grep postgresql`
## Upgrade all installed (enumerated in the previous step) PostgreSQL
packages using (e.g. for upgrading to PG-16) `dnf install
PACKAGE_NAMES --allowerasing`
## Install the upgrade package `dnf install postgresql-upgrade`
## Run `postgresql-setup --upgrade`
## Copy the old configuration files to the `/var/lib/pgsql/data/`
## Run `# systemctl start postgresql.service`
== Early Testing (Optional) ==
== How To Test ==
The `postgresql15*` RPMs should not be in the Fedora mirrors and
should not be installed.
== User Experience ==
== Dependencies ==
The following dependencies (stand-alone packages) will be retired
alongside the postgresql15:
*`postgresql15-pgaudit`, `postgresql15-pg_repack`, and
`postgresql15-decoderbufs`
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) N/A (not a
System Wide Change)
* 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 ==
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
Wiki - https://fedoraproject.org/wiki/Changes/NumPy2
Discussion Thread -
https://discussion.fedoraproject.org/t/f42-change-proposal-numpy-2-system-w…
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 ==
Update the numpy package from 1.x to 2.x (1.26.4 to 2.1.3 currently).
== Owner ==
* Name: [[User:Limb| Gwyn Ciesla]]
* Email: gwync(a)protonmail.com
== Detailed Description ==
Updating numpy from the 1.x to 2.x series will Just Work for some
packages. Those using the C API will need to be rebuilt. Additionally,
many packages are pinned to numpy < 2, and these will need to be
loosened.
== Feedback ==
I've experimented with this in copr, as well as tracked updates to a
few packages in preparation for this. One example is scipy, which was
recently updated to a version supporting numpy2, and this will reduce
the number of impacted packages.
== Benefit to Fedora ==
In addition to tracking upstream and receiving more up-to-date fixes
and security updates, numpy2 brings many improvements to the library:
https://numpy.org/devdocs/release/2.0.0-notes.htmlhttps://blog.scientific-python.org/numpy/numpy2/
== Scope ==
* Proposal owners:
Update numpy2 package to 2.1.x in f43 immediately after f42 mass branching.
Help rebuild and patch impacted packages as needed.
* Other developers:
Rebuild and patch impacted packages. Most will only require a pin
adjustment and/or rebuild.
* Release engineering: [https://pagure.io/releng/issues #Releng issue number]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with the Fedora Strategy:
== Upgrade/compatibility impact ==
Successfully rebuilt packages should not have any compatibility issues.
== Early Testing (Optional) ==
== How To Test ==
Run applications that use numpy or one of it's dependencies.
== User Experience ==
End users should not notice any changes.
Python developers will need to rebuild C API code against numpy2, and
can then take advantage of new features.
== Dependencies ==
apbs
APLpy
arbor
astrometry
asv
aubio
blender
boost
bout++
cantera
coin-or-HiGHS
Cython
DisplayCAL
dolfin
espresso
flatbuffers
gau2grid
gdal
gdl
ginga
gnuradio
gr-air-modes
grass
h5py
ipython
lammps
libarrow
libcint
libfreenect
libxc
mathgl
Mayavi
mlir
mlir17
mlpack
moose
mopac
morphio
mypaint
myst-nb
nanovna-saver
netcdf4-python
nfsometer
NLopt
ocaml-pyml
onnx
onnxruntime
opencv
openmeeg
openms
openshadinglanguage
openvdb
paraview
PDAL
petsc
pgzero
plplot
ProDy
psi4
pybind11
pygame
pygrib
pygsl
PyMca
pymol
pyplane
pyproj
pytest
python-adjustText
python-animatplot
python-annarchy
python-array-api-strict
python-arviz
python-ase
python-astroML
python-astroplan
python-astropy
python-astropy-healpix
python-astroquery
python-astroscrappy
python-autograd
python-basemap
python-bioframe
python-biopython
python-bioread
python-blosc
python-blosc2
python-bluepyopt
python-Bottleneck
python-boutdata
python-boututils
python-branca
python-brian2
python-brukerapi
python-cairocffi
python-calcephpy
python-cartopy
python-ccdproc
python-cclib
python-cftime
python-chaospy
python-cma
python-cmake-build-extension
python-cmap
python-collada
python-colormath2
python-colorspacious
python-contextualbandits
python-contourpy
python-cramjam
python-crick
python-cro
python-cyipopt
python-dask
python-deap
python-deepdiff
python-dijitso
python-dipy
python-distributed
python-ducc0
python-duecredit
python-earthpy
python-eccodes
python-efel
python-elasticsearch
python-elephant
python-emcee
python-ephyviewer
python-exdir
python-ezdxf
python-fastavro
python-fast-simplification
python-ffc
python-fiat
python-fiona
python-fireflyalgorithm
python-fisx
python-fitsio
python-folium
python-formulaic
python-fsleyes
python-fsleyes-props
python-fsleyes-widgets
python-fslpy
python-fsspec
python-geomdl
python-geopandas
python-geotiler
python-glymur
python-gradunwarp
python-graph-tool
python-gsd
python-h5io
python-hamcrest
python-hdf5storage
python-hdmf
python-healpy
python-hypothesis
python-igraph
python-imagecodecs
python-imageio
python-imbalanced-learn
python-img2pdf
python-indexed_gzip
python-inkex
python-inspyred
python-intern
python-joblib
python-jsonpickle
python-klusta
python-lazyarray
python-lazy-loader
python-lazy-ops
python-lfpy
python-lfpykit
python-libNeuroML
python-libpysal
python-llama-cpp-python
python-logdetective
python-lqrt
python-lsp-server
python-mapbox-earcut
python-mapclassify
python-matplotlib
python-meautility
python-meshio
python-missingno
python-mizani
python-mmtf
python-mne
python-mne-bids
python-mockito
python-mrcfile
python-multiecho
python-music21
python-nashpy
python-ndindex
python-neatdend
python-neo
python-netpyne
python-neurodsp
python-neurom
python-neurosynth
python-niaaml
python-niaarm
python-niaclass
python-niapy
python-nibabel
python-nifti-mrs
python-nilearn
python-nipy
python-nixio
python-nmrglue
python-nptyping
python-numcodecs
python-numexpr
python-numpoly
python-numpy-stl
python-openctm
python-opfunu
python-optking
python-optuna
python-opytimark
python-opytimizer
python-orjson
python-pandas
python-pandas-datareader
python-partd
python-periodictable
python-photutils
python-pillow
python-pingouin
python-pint
python-plotnine
python-probeinterface
python-pyABF
python-pyairvisual
python-pybbi
python-pybids
python-pybv
python-pydantic-core
python-pydapsys
python-pydicom
python-pyedflib
python-pyelectro
python-pyemd
python-pyerfa
python-pyface
python-pygmtools
python-pykdtree
python-pymapvbvd
python-pymatreader
python-pynn
python-pynwb
python-pyongc
python-pyopencl
python-pyopengl
python-pypet
python-pyphi
python-pyqtgraph
python-pyriemann
python-pyscf
python-pyshtools
python-pyside6
python-pyspike
python-pytest7
python-pytest-arraydiff
python-pytest-doctestplus
python-pytest-randomly
python-pytest-regressions
python-python-fcl
python-pytools
python-pyunicorn
python-pywt
python-pyxdf
python-qcelemental
python-quantities
python-qudida
python-rapidfuzz
python-rasterio
python-ratinabox
python-redis
python-reproject
python-Rtree
python-SALib
python-scikit-image
python-scikit-learn
python-scikit-misc
python-seaborn
python-sep
python-sgp4
python-shapely
python-simframe
python-sklearn-genetic
python-sklearn-genetic-opt
python-sklearn-nature-inspired-algorithms
python-smart_open
python-snuggs
python-sortedcontainers
python-sphinx-gallery
python-sport-activities-features
python-spyking-circus
python-stackprinter
python-statsmodels
python-steps
python-stochastic
python-succulent
python-superqt
python-supersmoother
python-tables
python-tabulate
python-textdistance
python-tifffile
python-tinygrad
python-toml
python-torch
python-torchvision
python-tqdm
python-Traits
python-traitsui
python-transforms3d
python-trimesh
python-trx-python
python-tvb-gdist
python-typish
python-uranium
python-vedo
python-vhacdx
python-wavio
python-wordcloud
python-wxpython4
python-xarray
python-xarray-einstats
python-yfinance
python-zarr
python-zmq
python-zoidberg
pythran
quantum-espresso
root
R-reticulate
scipy
setzer
shybrid
SoapySDR
spec2nii
spglib
stats-collect
sympy
uhd
urh
veusz
vigra
wult
xcfun
xtensor
xtensor-python
== Contingency Plan ==
* Contingency mechanism: Depending on scope of packages not fixed,
Gwyn will either help fix those packages, or create a compat package
and patch packages to use that.
* Contingency deadline: Beta Freeze
* Blocks release? No
== Documentation ==
Links provided above to upstream release notes. Document compat
package if applicable.
== Release Notes ==
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
Wiki - https://fedoraproject.org/wiki/Changes/LXQt_2.1
Discussion Post -
https://discussion.fedoraproject.org/t/f42-change-proposal-lxqt-2-1-self-co…
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 ==
Upgrade LXQt in Fedora to version 2.1.
== Owner ==
* Name: [[User:farchord| Steve Cossette]], [[User:Ngompa| Neal
Gompa]], [[User:Sfaulken| Shawn W Dunn]]
* Email: farchord(a)gmail.com, ngompa13(a)gmail.com, sfalken(a)cloverleaf-linux.org
== Detailed Description ==
LXQt in Fedora will be upgraded to v2.1 and will default to Wayland,
leveraging {{package|miriway}} by default for the Wayland experience.
More details on LXQt 2.1 are available from
[https://lxqt-project.org/release/2024/11/05/release-lxqt-2-1-0/ the
upstream release announcement].
== Feedback ==
== Benefit to Fedora ==
Fedora includes the latest version of LXQt and one more desktop spin
offering a Wayland-based experience.
== Scope ==
* Proposal owners:
** Upgrade all related LXQt packages
*** Incorporate pending upstream changes to support
{{package|miriway}} as a Wayland compositor for LXQt
** Adjust comps and live image to use Wayland by default
* Other developers: N/A
* Release engineering: [https://pagure.io/releng/issue/12455 #12455]
* 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
== Upgrade/compatibility impact ==
Users will be upgraded to LXQt 2.1, though no major configuration or
user experience changes are expected.
== How To Test ==
Install using the spin, netinstall or DVD. Or upgrade from older
release. Then users should be able to test by doing any daily work.
== User Experience ==
The user experience is not expected to change significantly with this upgrade.
== Dependencies ==
None outside of this Change.
== Contingency Plan ==
* Contingency mechanism: Roll back the LXQt packages. It will require
an Epoch bump.
* Contingency deadline: Beta freeze
* Blocks release? No.
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
LXQt in Fedora has been upgraded to version 2.1 and now defaults to Wayland.
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney