https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291344

Graham Perrin <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Open
           Keywords|install                     |
           Severity|Affects Many People         |Affects Some People
            Summary|15.0-RELEASE install with   |Outdated freebsd-update
                   |freebsd-update fails badly  |does not forewarn of
                   |when installing on top of   |FreeBSD-EN-25:18.freebsd-up
                   |previous major version -    |date when performing a
                   |14.3                        |major upgrade

--- Comment #10 from Graham Perrin <[email protected]> ---
<https://www.freebsd.org/releases/15.0R/installation/#upgrade-binary> mentions: 

    FreeBSD-EN-25:18.freebsd-update

– I was the reporter. 

Re: comment 9

> /usr/src/UPDATING

More specifically: 

- <https://github.com/freebsd/freebsd-src/blob/releng/14.3/UPDATING>
- <https://github.com/freebsd/freebsd-src/blob/releng/15.0/UPDATING>

EN-25:18.freebsd-update is in the former. base 7f1785f09fb2

IMHO the simplest explanation of this bug report is that an outdated
freebsd-update does not check for updates to itself. 

freebsd-update checks for updates to the base operating system of which it is a
part, and there's a widely-communicated routine for major upgrades. 

Whilst freebsd-update(8)
<https://man.freebsd.org/cgi/man.cgi?query=freebsd-update&sektion=8&manpath=freebsd-release>
lacks a section for examples, it is quite commonly understood that release
documentation should be a starting point. In this case: 

<https://www.freebsd.org/releases/15.0R/> 

The first link in the announcement is to release notes, where
<https://www.freebsd.org/releases/15.0R/relnotes/#upgrade> leads to: 

<https://www.freebsd.org/releases/15.0R/installation/#upgrade-binary>

HTH
Graham

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

Reply via email to