Fedora Linux 40 Final Freeze


Sorry why did not possible to add answer here? and create new question?
Because i did not undestand what difference with fedora 40 beta\ fedora 41\Red Hat Enterprise Linux (RHEL) but i tryed to test as much as possible.

Is a way without

sudo dnf upgrade --refresh
sudo dnf install dnf-plugin-system-upgrade
sudo dnf system-upgrade download --releasever=41
sudo dnf system-upgrade reboot

this failed every time from fedora 36 its come up to 50% and completly frize or get not possible to boot. before i get some issue package that did not support upgrade but later i did not.

Why is not possible to add https://discussion.fedoraproject.org/u/larsmartin4/preferences/account
facebook\github and instagram or skype\IRC sharing?

Two issues.

  1. Fedora does not support upgrading more than 2 release versions at a time, so for upgrading from f36 the latest supported upgrade version would be f38.

  2. Fedora 41 is not released nor currently in the release track. Rawhide is AKA fedora 41 and is only a testing and development version

Your link about the final freeze is an announcement and not a discussion thread.


You would have to go F36>F37>F38>F39>F40 to get it to go through safely. I wouldn’t even attempt an inplace update from a release that far out, too much risk in mismatched packages.

I’ve seen several post/people having trouble updating from releases older than F38, so going up one by one would be a better move IMO.


Hello @larsmartin4 ,
Welcome to :fedora: !
As @computersavvy mentions, F41 is a testing version of Fedora and currently is rawhide (Fedora’s Alpha if you like). The beta release is F40, and is still a testing release, since it may/will have some blocker bugs/issues. Unless you’re interested in testing fedora releases prior to release, I would avoid ever installing them on a system I relied on for my income or even if it was merely important for it to be reliable.
It is advisable, as noted by @hamrheadcorvette , to update through the releases to your desired release. If you desire F40, wait until it reaches release date, currently April 16 if the blocker meeting gives it the go ahead. You can, of course, upgrade through the current releases to F39 to be ready, F36 is end of life, but F37 is still available.
Fedora is a pretty fast moving release cadence which is continuous. As there are frequently changes, and some that “break” apps expected behaviour at times, it is advisable to keep current with the latest Fedora releases as they become available. There is no Long Term Release in Fedora.

Sorry, but F37 is also EOL and has been since December.

1 Like

Quite likely but it is still showing on the schedule as current.

F37 shows as EOL since 12/5/2023 according to

1 Like

I believe you, I didn’t look at that link, the one I was on had older releases listed too. The link … Fedora Project schedules

Your link is on fedorapeople.org and is not up to date. The one I listed is docs.fedoraproject.org and is kept current. In fact you can go up one level from what I linked and find the official schedule for F40.

1 Like

But what is pre alpha? did not make sence, its more stabile than a lot other distribution.
But its have few bug hardware compactiblity mellanox connect x2, brother printer ( Brother HL-2060 - CUPS+Gutenprint v5.3.4 Simplified ) \ wine compactbility?.

Its also issue with abrt " issue not enoth information detected"

Issue with virtualbox need RMS fusion to be installed, and vmware player did not have compactible kernel to run. But this issue is not very hard to fix.

You are lucky that system are stable but if broke you are on your own to fix bits and peaces.Good luck fingers cross :crossed_fingers:

Then that link I posted should have indication on the page that Clearly states it is out of date and no longer being used with a link to the correct page with the pertinent info. Who deprecated the page I linked? They should update it to reflect the change to the new page. This is the documentation problem in a nutshell that Fedora suffers.

Rawhide would be considered pre-alpha in its entirety.

When a version is initially branched for final updates it would be considered alpha, which then after a time of updates and testing becomes beta, which then becomes the final release for that version.

At the time one version is branched then rawhide would become the pre-alpha for the next version being developed.

This all means that Rawhide is never considered to be even remotely stable since there are constant development processes occurring.

Actually since we stopped doing Alphas, the idea is that Rawhide is
always at at least Alpha level. This is done via gating of updates,
compose checking, etc. Of course sometimes things get though, but much
less than in the past, and those tests/checks are by no means covering
everything, just the basic critera.

I think it’s better to look at rawhide based on it’s target audience:

If you’re willing and able to do those things, then great… but if
you’re not, a stable release would likely be much better for you.

1 Like