Bug 291344 - 15.0-RELEASE install with freebsd-update fails badly when installing on top of previous major version - 14.3
Summary: 15.0-RELEASE install with freebsd-update fails badly when installing on top o...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 15.0-RELEASE
Hardware: arm64 Any
: --- Affects Many People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: install
Depends on:
Blocks:
 
Reported: 2025-12-02 10:32 UTC by vova
Modified: 2025-12-02 15:00 UTC (History)
2 users (show)

See Also:


Attachments
full log of frebsd-install (204.73 KB, text/plain)
2025-12-02 10:32 UTC, vova
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description vova 2025-12-02 10:32:36 UTC
Created attachment 265771 [details]
full log of frebsd-install

Install on top of 

14.3:

# freebsd-update upgrade -r 15.0-RELEASE
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 14.3-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Fetching 2 metadata patches.. done.
Applying metadata patches... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic kernel/generic-dbg src/src world/base world/lib32

The following components of FreeBSD do not seem to be installed:
world/base-dbg world/lib32-dbg

Does this look reasonable (y/n)? y

Fetching metadata signature for 15.0-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Fetching 1 metadata patches. done.
Applying metadata patches... done.
Fetching 1 metadata files... done.
Inspecting system... done.
Fetching files from 14.3-RELEASE for merging... done.
Preparing to download files... done.
Fetching 30696 patches.....10....20....30 ..... done.
Applying patches... done.
Fetching 10867 files... ...
.10860... done.
Attempting to automatically merge changes in files... done.

The following changes, which occurred between FreeBSD 14.3-RELEASE and
FreeBSD 15.0-RELEASE have been merged into /etc/ttys:
--- current version
+++ new version
@@ -1,8 +1,5 @@
-#
-#	@(#)ttys	5.1 (Berkeley) 4/17/89
-#
 # This file specifies various information about terminals on the system.
 # It is used by several different programs.  Common entries for the
 # various columns include:
 #
 # name  The name of the terminal device.
Does this look reasonable (y/n)? y
The following files will be removed as part of updating to
15.0-RELEASE-p0:
/.cshrc
...
/var/db/etcupdate/current/etc/rc.d/virtual_oss
/var/db/krb5kdc
The following files will be updated as part of updating to
15.0-RELEASE-p0:
/COPYRIGHT
/bin/[
/bin/cat
...
/var/db/etcupdate/current/root/.shrc
To install the downloaded upgrades, run 'freebsd-update [options] install'.
root@freebsd-14-3:/home/vova # freebsd-update install
Creating snapshot of existing boot environment... done.
Installing updates...
Kernel updates have been installed.  Please reboot and run
'freebsd-update [options] install' again to finish installing updates.
root@freebsd-14-3:/home/vova # shutdown -r now
Shutdown NOW!
shutdown: [pid 55483]
root@freebsd-14-3:/home/vova #
*** FINAL System shutdown message from vova@freebsd-14-3 ***

System going down IMMEDIATELY



*** FINAL System shutdown message from vova@freebsd-14-3 ***

System going down IMMEDIATELY



System shutdown time has arrived
# freebsd-update install
Creating snapshot of existing boot environment... done.
Installing updates...ld-elf.so.1: Shared object "libsys.so.7" not found, required by "libc.so.7"
ld-elf.so.1: Shared object "libsys.so.7" not found, required by "libc.so.7"
ld-elf.so.1: Shared object "libsys.so.7" not found, required by "libc.so.7"
ld-elf.so.1: Shared object "libsys.so.7" not found, required by "libc.so.7"
ld-elf.so.1: Shared object "libsys.so.7" not found, required by "libc.so.7"
ld-elf.so.1: Shared object "libsys.so.7" not found, required by "libc.so.7"
ld-elf.so.1: Shared object "libsys.so.7" not found, required by "libc.so.7"
ld-elf.so.1: Shared object "libsys.so.7" not found, required by "libc.so.7"
ld-elf.so.1: Shared object "libsys.so.7" not found, required by "libc.so.7"
ld-elf.so.1: Shared object "libsys.so.7" not found, required by "libc.so.7"
Comment 1 vova 2025-12-02 10:34:17 UTC
that gives me second-hand cringe
Comment 2 ivy freebsd_committer freebsd_triage 2025-12-02 10:34:31 UTC
did you apply the freebsd-update errata https://www.freebsd.org/security/advisories/FreeBSD-EN-25:18.freebsd-update.asc before upgrading?
Comment 3 vova 2025-12-02 10:40:42 UTC
(In reply to ivy from comment #2)

I did not, 

But what was the point to allow freebsd-update to break the system?
A bet a lot of ppl who doing binary updates will hit this wall!?
Comment 4 vova 2025-12-02 10:42:18 UTC
before updating:

% uname -UK
1403000 1403000
% uname -a
FreeBSD freebsd-14-3 14.3-RELEASE FreeBSD 14.3-RELEASE releng/14.3-n271432-8c9ce319fef7 GENERIC arm64
Comment 5 vova 2025-12-02 11:05:46 UTC
for the truth, handbook ecourages to install security/errata first:

https://docs.freebsd.org/en/books/handbook/cutting-edge/#freebsdupdate-upgrade
```
Before upgrading to a new version, ensure the existing FreeBSD installation is up to date with respect to security and errata patches:

# freebsd-update fetch
# freebsd-update install
The following command, when run on a FreeBSD 13.1 system, will upgrade it to FreeBSD 13.2:

# freebsd-update -r 13.2-RELEASE upgrade
...
```
Comment 6 vova 2025-12-02 11:13:10 UTC
Installing 15.0-RELEASE on top of 14.3 with all updates installed went fine.

but newertheless, freebsd-update as minimum should warn about such breaking changes, better require enforcement with --currently-running
Comment 7 ivy freebsd_committer freebsd_triage 2025-12-02 11:14:05 UTC
to be honest, i can't take this PR seriously when you put "kindergarten" in the title.  what is your point there?
Comment 8 vova 2025-12-02 11:23:43 UTC
(In reply to ivy from comment #7)

I would consider this installation scenario quite likely for FreeBSD users. Given that it can break the entire installation process and require recovery, it would be very helpful if freebsd-update included safeguards to prevent such issues.

as for title, I've removed non-relevant "kindergarten", which just expressed my distress - I’ve always known FreeBSD as a very reliable OS, so discovering such an easy way to break upgrade was quite upsetting for me. I’m sorry if I unintentionally offended anyone.
Comment 9 vova 2025-12-02 12:02:35 UTC
Also, the issue mentioned on webpage: https://www.freebsd.org/releases/15.0R/installation/

but I can't find any mentions in /usr/src/UPDATING - what I usually read before rollout new version ...