[Bug 264075] freebsd-update in 13.1-RELEASE detects an installed kernel when it shouldn't

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 27 Sep 2023 20:36:45 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264075

Ed Maste <emaste@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |emaste@freebsd.org

--- Comment #1 from Ed Maste <emaste@freebsd.org> ---
I presume "upgrade" is missing from step 3 in your reproduction steps.

Using freebsd-update from main,

# ./freebsd-update -b /root/13.1/ --currently-running 13.1-RELEASE
-r 13.2-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 2 mirrors found.
Fetching metadata signature for 13.1-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Fetching 2 metadata patches.. done.
Applying metadata patches... done.
Fetching 1 metadata files... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic world/base

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

Does this look reasonable (y/n)? 

> Normally when running freebsd-update on a jail using the -b switch it should
> not detect a kernel in that folder (because there isn't one). However, the
> version of freebsd-update in 13.1-RELEASE detects a kernel and wants to
> install files to /boot/kernel in the jail.

I believe the claim here is that this is a regression, but I didn't see any
recent changes that would be obviously responsible for this. Which version
worked correctly for this case, in your experience?

-- 
You are receiving this mail because:
You are the assignee for the bug.