• upgrades and issues wrt to FreeBSD-SA-25:09.netinet

    From Erichans@erichanskrs@gmail.com to muc.lists.freebsd.stable on Thu Oct 23 04:23:56 2025
    From Newsgroup: muc.lists.freebsd.stable

    Below is a report of my findings, I also have a few questions.

    On my laptop (14.2-RELEASE, amd64, UFS); I performed the following
    steps:

    1) executed freebsd-update -r 15.0-BETA1;
    set quarterly back to latest manually
    2) executed pkgbasify
    3) executed pkg upgrade -r FreeBSD-base to advance to 15.0-BETA2
    4) applied pkg upgrade -r FreeBSD-base wrt FreeBSD-SA-25:09.netinet

    ad 1) - 3)
    These were successfully with minor adjustments. At step 1) I've
    experienced unexpected behaviour just after the upgrade to
    15.0-BETA1 (before executing pkgbasify). I had to recover all
    my comments in /usr/local/etc/pkg/repos/FreeBSD.conf

    as these were apparently deleted during the upgrade process. IIRC, user
    created config files as this one is usually "left alone". After the
    upgrade the new name repository tag names appeared, as a result of
    the announced changes:
    FreeBSD -> FreeBSD-ports
    FreeBSD-kmods -> FreeBSD-ports-kmods

    The old repository tag names were disabled by the upgrade.

    Question:
    Is it intended behaviour that comments are deleted by
    freebsd-update in the user created file
    /usr/local/etc/pkg/repos/FreeBSD.conf ?


    ad 4)
    If I read the SA correctly, there is no binary upgrade path provided
    for a 15.0 "on releng", in my case 15.0-BETA2 (not being an
    official RELEASE version) in a fully package-based OS environment. freebsd-update fetch is blocked, as expected:
    BEGIN_CODE
    [3-0] # freebsd-update fetch
    freebsd-update is incompatible with the use of packaged base. Please see https://wiki.freebsd.org/PkgBase for more information.
    END_CODE

    Question:
    Is the absence of an option in the SA for a binary update of
    15.0-BETA2 intentional?


    I tried pkg upgrade -r FreeBSD-base as a workaround for the SA.
    The output was:
    BEGIN_CODE
    [1-0] # pkg upgrade -r FreeBSD-base
    Updating FreeBSD-base repository catalogue...
    FreeBSD-base is up to date.
    Checking for upgrades (12 candidates): 100%
    Processing candidates (12 candidates): 100%
    The following 12 package(s) will be affected (of 0 checked):

    Installed packages to be UPGRADED:
    FreeBSD-bhyve: 15.0.b1.20251012072228 ->
    15.0.b2.20251019235946 [FreeBSD-base]
    FreeBSD-clibs-dev: 15.0.b2.20251017190138 ->
    15.0.b2.20251019235946 [FreeBSD-base]
    FreeBSD-kernel-generic: 15.0.b2.20251017190138 -> 15.0.b2.20251019235946 [FreeBSD-base]
    FreeBSD-kernel-generic-dbg: 15.0.b2.20251017190138 -> 15.0.b2.20251019235946 [FreeBSD-base]
    FreeBSD-kernel-generic-mmccam: 15.0.b2.20251017190138 -> 15.0.b2.20251019235946 [FreeBSD-base]
    FreeBSD-kernel-generic-mmccam-dbg: 15.0.b2.20251017190138 -> 15.0.b2.20251019235946 [FreeBSD-base]
    FreeBSD-kernel-man: 15.0.b1.20251012072228 ->
    15.0.b2.20251019010906 [FreeBSD-base]
    FreeBSD-kernel-minimal: 15.0.b2.20251017190138 -> 15.0.b2.20251019235946 [FreeBSD-base]
    FreeBSD-kernel-minimal-dbg: 15.0.b2.20251017190138 -> 15.0.b2.20251019235946 [FreeBSD-base]
    FreeBSD-src: 15.0.b2.20251017190138 -> 15.0.b2.20251019235946 [FreeBSD-base]
    FreeBSD-src-sys: 15.0.b2.20251017190138 ->
    15.0.b2.20251019235946 [FreeBSD-base]
    FreeBSD-utilities: 15.0.b2.20251017190138 ->
    15.0.b2.20251019010906 [FreeBSD-base]

    Number of packages to be upgraded: 12

    748 MiB to be downloaded.

    Proceed with this action? [y/N]: y
    21<] # freebsd-version -kru
    15.0-BETA2
    15.0-BETA2
    15.0-BETA2
    [3-0] # uname -apUK
    FreeBSD q210 15.0-BETA2 FreeBSD 15.0-BETA2
    releng/15.0-n280707-3edefa72bc4e GENERIC amd64 amd64 1500067 1500067
    END_CODE

    No error message is displayed, the only hint is the result
    code 21 shown in my prompt:
    21<] #

    I could not find any documentation what this result code means.
    IMO, an explanatory error message should have been printed.


    I did find that my FreeBSD-base repository was disabled;
    This shouldn't matter, pkg-upgrade(8):
    -r reponame, --repository reponame
    Install packages from only the named repository, irrespec-
    tive of the configured "enabled" status from repo.conf.

    This is for the first time that I've experienced improper pkg
    behaviour impacting the management of FreeBSD's base install.
    This is what I mentioned as a possibility in my earlier https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289455


    After enabling the FreeBSD-base repository, packages from that
    repository were upgraded. However, after a reboot
    freebsd-version didn't show any patch level p1; note that I have
    only one configuration file:
    /usr/local/etc/pkg/repos/FreeBSD.conf

    It took ca. 6 hours until the final collection of base packages
    were available and I was able to install them. In the end I got,
    after the reboot:
    BEGIN_CODE
    [1-0] % freebsd-version -kru
    15.0-BETA2-p1
    15.0-BETA2-p1
    15.0-BETA2-p1
    [2-0] % uname -apKU
    FreeBSD q210 15.0-BETA2-p1 FreeBSD 15.0-BETA2-p1 releng/15.0-n280735-f138688ea41a GENERIC amd64 amd64 1500067 1500067
    [3-0] %
    END_CODE


    Eric


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Graham Perrin@grahamperrin@gmail.com to muc.lists.freebsd.stable on Thu Oct 23 05:32:39 2025
    From Newsgroup: muc.lists.freebsd.stable

    On 23/10/2025 03:23, Erichans wrote:

    Is it intended behaviour that comments are deleted by
    freebsd-update in the user created file
    /usr/local/etc/pkg/repos/FreeBSD.conf ?


    I wonder.

    ll /usr/local/etc/pkg/repos

    Please share the listing.

    (Is there a .pkgnew file?)

    Thanks



    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Erichans@erichanskrs@gmail.com to muc.lists.freebsd.stable on Thu Oct 23 21:09:56 2025
    From Newsgroup: muc.lists.freebsd.stable

    After the upgrade from 14.2-R to 15.0-BETA1, I only had two
    .conf files. One that contained the FreeBSD-base and the
    other the old and newly named repositories. I moved everything
    to the FreeBSD.conf file and deleted the other one. No *new
    or other file was generated.
    Eric
    On Thu, Oct 23, 2025 at 6:32rC>AM Graham Perrin <grahamperrin@gmail.com> wrote:

    On 23/10/2025 03:23, Erichans wrote:

    Is it intended behaviour that comments are deleted by
    freebsd-update in the user created file /usr/local/etc/pkg/repos/FreeBSD.conf ?


    I wonder.

    ll /usr/local/etc/pkg/repos

    Please share the listing.

    (Is there a .pkgnew file?)

    Thanks


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2