Solved FreeBSD 14 is ready?

I used the 14.0-RELEASE and it worked.
There's something weird here after
# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 14.0-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 14.0-RELEASE-p0.

WARNING: FreeBSD 14.0-RELEASE is approaching its End-of-Life date. <<< WHAT?!?!?!
It is strongly recommended that you upgrade to a newer
release within the next 2 months.

Lost some software:
firefox was gone after restart
sudo was gone also... why?!?!

Still testing

Screenshot_2023-11-14_18-21-11.png
 
dbdemon said:
I tried 14.0-RELEASE unsuccessfully multiple times over the weekend. Maybe it's just 14.0 now, as tho seems to say? Or maybe I was just too early. I guess I will find out.
Click to expand...
I just tried this:
freebsd-update -r 14.0-RELEASE upgrade src component not installed, skipped freebsd-update: Cannot upgrade from 14.0-RELEASE to itself

seems like freebsd-update -r 14.0 upgrade does the job? I am not an expert on FreeBSD so you might wait until official release...
 
rmomota said:
Lost some software:
firefox was gone after restart
sudo was gone also... why?!?!
Click to expand...

Most likely because not all ports have been successfully built for 14.0-RELEASE yet, especially from the quarterly branch.
That's why you usually sanity-check what pkg wants to remove during an pkg upgrade


CuatroTorres said:
The day is beginning in the western part of the U.S. Everything will be ready by lunchtime.
Click to expand...
From: Glen Barber <gjb_at_freebsd.org>
Date: Tue, 14 Nov 2023 20:36:54 UTC
We are still waiting for a few (non-critical) things to complete before
the announcement of 14.0-RELEASE will be ready.

It should only be another day or so before these things complete.

Thank you for your understanding.

Glen
On behalf of: re@
Click to expand...
 
rmomota said:
WARNING: FreeBSD 14.0-RELEASE is approaching its End-of-Life date. <<< WHAT?!?!?!
It is strongly recommended that you upgrade to a newer
release within the next 2 months.
Click to expand...
looks like somebody forgot to double-check the text of that warning before the -RELEASE drop... ?

rmomota said:
Lost some software:
firefox was gone after restart
sudo was gone also... why?!?!
Click to expand...
this is why I stick with ports, rather than packages - ports have less of that nonsense, and can be re-compiled against the newly upgraded stuff.
 
SirDice said:
Probably all the previous beta and release candidates. All those are EoL as soon as the release is official.
Click to expand...
Sorry, I missed adding the sarcasm tags/emojis to that. It's mostly because I've never thought about it because "Current is current"
 
After some hours of testing seems the upgrade was success.

After upgrade I lost
Firefox
Thunderbird
sudo
networkmgr
cmake
cmake-core
all these I reinstalled after the upgrade to get it back

but
vscode - it's no longer in the repo.... oh nooooo I need this one
and these 2 have no idea what those are for
llvm90
libdmx

But everything seems to be just fine.

Thank you!!
 
just upgraded from 14.0 RC-4 and all is fine except /etc/os-release still shows rc4 even uname -a shows release!!
 
dr3mro said:
just upgraded from 14.0 RC-4 and all is fine except /etc/os-release still shows rc4 even uname -a shows release!!
Click to expand...
That is strange.
The upgrade I did from 13.2p5 to 14.0p0, 13.2-RELEASE to 14.0-RELEASE, I just had to resolve some easy conflicts on some files in /etc/ but everything was just perfect.
The fist boot just failed to start X11 because it couldn't yet load the graphics card driver.
Completed the pkg upgrade steps in console and after restarting the system was just fine.
All files and tools show the correct FreeBSD version.
 
rmomota said:
The fist boot just failed to start X11 because it couldn't yet load the graphics card driver.
Click to expand...
It's best to disable these before starting the upgrade. Just do this on the console. Same goes for the Virtualbox kernel modules. Those are finicky with any version upgrade. Just disable them until you have completed the entire upgrade procedure (that includes rebuilding/reinstalling all ports/packages).

Especially with the reboots at various stages, things might throw errors during that time. Go through rc.conf and temporarily disable everything you don't strictly need during the upgrade. Finish the entire upgrade procedure first, then enable them again.
 
A message from freebsd-stable mailing list.
We are still waiting for a few (non-critical) things to complete before
the announcement of 14.0-RELEASE will be ready.

It should only be another day or so before these things complete.

Thank you for your understanding.

Glen
On behalf of: re@
Click to expand...
 
RE those messages about "EOL" and wrong version in os-release:

From: Glen Barber <gjb_at_freebsd.org>
Date: Wed, 15 Nov 2023 04:52:31 UTC

That does not say that the freebsd-update bits will not change *until*
the official release announcement has been sent.

In my past 15 years involved in the Project, I think we have been very
clear on that.

A RELEASE IS NOT FINAL UNTIL THE PGP-SIGNED ANNOUNCEMENT IS SENT.

I mean, c'mon, dude.

We really, seriously, for all intents and purposes, cannot be any more
clear than that.

So, yes, *IF* an update necessitates a new freebsd-update build, what
you are running is *NOT* official.

For at least 15 years, we have all said the same entire thing.

Glen
Click to expand...

and
From: Graham Perrin <grahamperrin_at_gmail.com>
Date: Wed, 15 Nov 2023 07:31:13 UTC
On Tue, 14 Nov 2023 at 23:05, Glen Barber <gjb@freebsd.org> wrote:
[...]
I'm encouraging people to wait, because the presence of the
'installation information' page will be quite critical (we're already
seeing problems through people missing an essential step).
Click to expand...


So there seem to be some caveats to the upgrade which will be laid out in the release announcement/installation information.
Maybe even a required update to freebsd-update? Thinking about that "file became a directory" change lately...
 
rmomota said:
Ok but I now did the
# freebsd-update -r 14.0-RELEASE upgrade what will be the next release name?
Click to expand...

as I already quoted:
So, yes, *IF* an update necessitates a new freebsd-update build, what
you are running is *NOT* official.
Click to expand...



Why not just wait until 14.0 gets released?

And if not: it is not an official release yet, so by the forum rules its *NOT* supported here. (RE all those "upgrade to 14.0 broke my XY" threads the last few days...)
 
sko said:
as I already quoted:



Why not just wait until 14.0 gets released?

And if not: it is not an official release yet, so by the forum rules its *NOT* supported here. (RE all those "upgrade to 14.0 broke my XY" threads the last few days...)
Click to expand...
I can live with that, the system works fine so no problem to me.
I just wanted to know what to do when it finally gets released how can I re-upgrade to the same release, but thanks.
Quick reminder: 14.0-RELEASE was available that's why I upgraded.
 
You must log in or register to reply here.
Back
Top