From Newsgroup: muc.lists.freebsd.stable

--Sig_/FqKjTGLDiSo7otM+i0S0ud.
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Am 05.12.2025 um 16:06:27 Uhr schrieb Kurt Jaeger:

This makes me wonder if 14.3 is the only version where upgrading to
15.0 via freebsd-upgrade is supported, or if, e.g., 14.2 or 13.5
would be valid (and supported) starting points for the direct
upgrade process to 15.0, too. =20

=20
I did two updates 14.3p6 to 15.0 already.
=20
From what I understand, only updates from 14.3p6 to 15.0 are possible, because there were recent updates to freebsd-update itself to make
it work.

https://www.freebsd.org/security/advisories/FreeBSD-EN-25:18.freebsd-update= .asc


|1) To update your system via a binary patch:
|
|Systems running a RELEASE version of FreeBSD on the amd64 or arm64
|platforms, or the i386 platform on FreeBSD 13, can be updated via the |freebsd-update(8) utility:
|
|# freebsd-update fetch
|# freebsd-update install

That sounds like if you have a current OS version, you can upgrade.

Is that guess right?

--=20
Gru=C3=9F
Marco

Send unsolicited bulk mail to 1764947187muell@cartoonies.org

--Sig_/FqKjTGLDiSo7otM+i0S0ud.
Content-Type: application/pgp-signature
Content-Description: Digitale Signatur von OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEpXefSZn9R6zNZtTQE76RLz2tRfAFAmkzC2QACgkQE76RLz2t RfCB7Q//Ybt78DshbwKpnmC/kpmjDayWQJU1d+okZjMuulF6r61tKx6/QcUv+bOD 2ddxcyVAZftV6BwVFFgRfo52SaRFtyZ1db5HmeyL5XhIpPbCuypthLNY3vLGipfv HJGUx7Lczwzoyx5N6gKuVjG+Fmt+DjznFh5gBxXiUSY/AY4Iq0pHpwLtYaCfHyjv 29BNxEkxTsrRsrICnz7FjN2R6jyz4qWfdVelDbSfIilDKMXeUALw4mCrRpi+n05O NpusRsL10Ck+1EWK4Miq2k2hadYb012fmCdhVFAjyhs8GR97HFJ1rB5+CqoCG6iA GUpQGIDD+hpp3mwnQNKHgd47ujEYTjV2a5rUCnShOPe9vxt96jQ8OY32Sd9r0BDV +dABOmnlslIEVQPeQV/Bg/6emOTz7pzsSAx72yHiIWJq/NXxOgmln+r+0bHzvskh BifxXwwF8o2c4el7GidWZRndNteY/nuEolGWfpMY4XMrwznrRo46fUxR6L+t4UHn K6MbCQ66Szq1WngZf+qG9qbrL6SVh89BxP26HY3CM7FZoQ5LpEhiyTM0UXK5Tpgq 2LEO6FlrEmL97clnyzbnwkRw/0bcQgtAny1z9GjBbu44B43FJKKPtm3CL0HyiEWy xtw6gUVeJibpULwzGwHc16Pb9UkcMExq6Y6CiJo9gnCxZCfE5LI=
=jSoQ
-----END PGP SIGNATURE-----

--Sig_/FqKjTGLDiSo7otM+i0S0ud.--


--
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 Newsgroup: muc.lists.freebsd.stable

--Sig_/o7ldHAr_s6EU0Uei1O4/Zy7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Am 05.12.2025 um 17:42:12 Uhr schrieb Marco Moock:

|1) To update your system via a binary patch:
|
|Systems running a RELEASE version of FreeBSD on the amd64 or arm64 |platforms, or the i386 platform on FreeBSD 13, can be updated via the |freebsd-update(8) utility:
|
|# freebsd-update fetch
|# freebsd-update install
=20
That sounds like if you have a current OS version, you can upgrade.

I've now tried that from 14.3-p6 and that failed.
libutil.so.9 is missing and that breaks sudo. su is working, so I was
able to run pkg bootstrap -f and then pkg upgrade - this fixed the
issue.

TLDR: It is recommended to test root login without sudo before starting
the upgrade.

--=20
Gru=C3=9F
Marco

Send unsolicited bulk mail to 1764952932muell@cartoonies.org

--Sig_/o7ldHAr_s6EU0Uei1O4/Zy7
Content-Type: application/pgp-signature
Content-Description: Digitale Signatur von OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEpXefSZn9R6zNZtTQE76RLz2tRfAFAmkzMUgACgkQE76RLz2t RfDbwA/7BSc5s2mnNnipdIQ0BMzXZuLBAdgqI9f/WWGrKdL6rZhnmMoeLLje05FR qUMd6n0i/w/Q4uN4EcCT3KQS0TqqF9QwJ3B/VGH9IondmiIdbvllCKEnE8XZp9Nd pl2tP4bhMazCFZ2r7hk1GiKM58/MjqePDC0oA+TnqF4O3qdlUiFeH3jiofjeFTNN np33gvUCIB2kin6FDUlXY0aFP/AWqQh/xAwjC10k7OODyP+zdK74iDJGFdN+bX37 tUqBoV0Nx2yvFlxG01wYOwOijt9DLNb4BUaqNIx3tfLzQYd8pT9m2PFjXY2yD4m5 qmWHIPw+eJpbOwgWdHYVZZA58G48GsY6xUjO7X12lWJLlu9p+8fSlFAkDYYmx2wf bXfe4uIaM4R431xUEOKHVTxo0bGHtoKG4MeLVFdeX7LS+IvbAhwQdg1ZlrsNvi7G d2RYVvhfApRxEIc5P0V9Lrd3B4NbEAkmXM+EANn/sCiEwHsMtM73DgzTeP2FHzOK /isyPnMRKZUhvy8HAeknAy5cDnCTqwK1APnOqeAHH4Xfl4qJNrAH9mfd2lwCioaa V+KnBfJj9BSM6HtmFCvdeETrBeO2rmIU15pSqDCS7IUj6XYAVr75UP1XO3XtYDii Ap2NYpZXXHq+gmykmS0z5hOKgmm5J7Jjc0LaCq3H2Xa9u97oxX4=
=O7nu
-----END PGP SIGNATURE-----

--Sig_/o7ldHAr_s6EU0Uei1O4/Zy7--


--
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 Newsgroup: muc.lists.freebsd.stable

Hello,
I updated from 13.5 to 15 on amd64 with freebsd-update fine.
Regards,
Nathan

On 6 Dec 2025, at 1:30rC>am, Gerrit K|+hn <gerrit.kuehn@aei.mpg.de> wrote:

N++Hello,

I just read the friendly reminder
on https://www.freebsd.org/releases/15.0R/installation/ that FreeBSD-EN-25:18.freebsd-update errata update should be followed.

That errata is, among other versions like stable/14, stable/13, avilable
for 13.5 releng and 14.2 releng: https://www.freebsd.org/security/advisories/FreeBSD-EN-25:18.freebsd-update.asc
It says in its "Impact" section "When using freebsd-update(8) to upgrade a> system from FreeBSD 13.x or 14.x to FreeBSD 15.0..."

However, when looking at the installation instructions for 15.0 above,
these state "Systems running 14.3-RELEASE can upgrade as follows:"

This makes me wonder if 14.3 is the only version where upgrading to 15.0
via freebsd-upgrade is supported, or if, e.g., 14.2 or 13.5 would be valid> (and supported) starting points for the direct upgrade process to 15.0,
too.

cu
Gerrit

--
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 Newsgroup: muc.lists.freebsd.stable

--000000000000001a6606453b2790
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Dec 5, 2025 at 12:24=E2=80=AFPM Marco Moock <mm@dorfdsl.de> wrote:

Am 05.12.2025 um 17:42:12 Uhr schrieb Marco Moock:

|1) To update your system via a binary patch:
|
|Systems running a RELEASE version of FreeBSD on the amd64 or arm64 |platforms, or the i386 platform on FreeBSD 13, can be updated via the |freebsd-update(8) utility:
|
|# freebsd-update fetch
|# freebsd-update install

That sounds like if you have a current OS version, you can upgrade.

I've now tried that from 14.3-p6 and that failed.
libutil.so.9 is missing and that breaks sudo. su is working, so I was
able to run pkg bootstrap -f and then pkg upgrade - this fixed the
issue.

TLDR: It is recommended to test root login without sudo before starting
the upgrade.

You should update all packages immediately before rebooting when upgrading major releases.

Warner

--
Gru=C3=9F
Marco

Send unsolicited bulk mail to 1764952932muell@cartoonies.org

--000000000000001a6606453b2790
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g= mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Dec 5, = 2025 at 12:24=E2=80=AFPM Marco Moock &lt;<a href=3D"mailto:mm@dorfdsl.de">m= m@dorfdsl.de</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl= e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin= g-left:1ex">Am 05.12.2025 um 17:42:12 Uhr schrieb Marco Moock:<br>

&gt; |1) To update your system via a binary patch:<br>
&gt; |<br>
&gt; |Systems running a RELEASE version of FreeBSD on the amd64 or arm64<br=

&gt; |platforms, or the i386 platform on FreeBSD 13, can be updated via the=

&gt; |freebsd-update(8) utility:<br>
&gt; |<br>
&gt; |# freebsd-update fetch<br>
&gt; |# freebsd-update install<br>
&gt; <br>
&gt; That sounds like if you have a current OS version, you can upgrade.<br=


I&#39;ve now tried that from 14.3-p6 and that failed.<br>
libutil.so.9 is missing and that breaks sudo. su is working, so I was<br>
able to run pkg bootstrap -f and then pkg upgrade - this fixed the<br> issue.<br>

TLDR: It is recommended to test root login without sudo before starting<br>
the upgrade.<br></blockquote><div><br></div><div>You should update all pack= ages immediately before rebooting when upgrading major releases.</div><div>= <br></div><div>Warner</div><div>=C2=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)= ;padding-left:1ex">
-- <br>
Gru=C3=9F<br>
Marco<br>

Send unsolicited bulk mail to <a href=3D"mailto:1764952932muell@cartoonies.= org" target=3D"_blank">1764952932muell@cartoonies.org</a><br> </blockquote></div></div>

--000000000000001a6606453b2790--


--
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 Newsgroup: muc.lists.freebsd.stable

--Sig_/Yj3vjFk=DGuENXvcDCSarHa
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Am 05.12.2025 um 14:30:08 Uhr schrieb Warner Losh:

On Fri, Dec 5, 2025 at 12:24=E2=80=AFPM Marco Moock <mm@dorfdsl.de> wrote:
=20

Am 05.12.2025 um 17:42:12 Uhr schrieb Marco Moock:
=20

|1) To update your system via a binary patch:
|
|Systems running a RELEASE version of FreeBSD on the amd64 or
arm64 |platforms, or the i386 platform on FreeBSD 13, can be
updated via the |freebsd-update(8) utility:
|
|# freebsd-update fetch
|# freebsd-update install

That sounds like if you have a current OS version, you can
upgrade. =20

I've now tried that from 14.3-p6 and that failed.
libutil.so.9 is missing and that breaks sudo. su is working, so I
was able to run pkg bootstrap -f and then pkg upgrade - this fixed
the issue.

TLDR: It is recommended to test root login without sudo before
starting the upgrade.
=20

=20
You should update all packages immediately before rebooting when
upgrading major releases.

IIRC after the kernel update freebsd-update suggests to reboot and then
it installs the base packages. After that it recommended to run pkg
bootstrap -f.
It didn't say explicitly that upgrading all the packages with pkg is a necessary step before the reboot.

--=20
Gru=C3=9F
Marco

Send unsolicited bulk mail to 1764941408muell@cartoonies.org

--Sig_/Yj3vjFk=DGuENXvcDCSarHa
Content-Type: application/pgp-signature
Content-Description: Digitale Signatur von OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEpXefSZn9R6zNZtTQE76RLz2tRfAFAmkzypsACgkQE76RLz2t RfD9SQ/7BpAOIi+6IwVr2EW0Yv/fC4Noc7ssjYYgODQW8AHLIKhdBbpCe8QRtnx9 Bjmyx283NcW23ofc+Bg7rQb+aE5YmJwZ1nNQ/+FnkNyP+IJuid+5fGX1UMgoOwMt qyIVn0RmLD892TtmquZvWLLFiz1YUvmGJyoF/u4Dsp2SOQr0RcfN3RXO1J60bjwC JXhgcgSqi3Wmc6jXPguOqwqtXpxqQzqmvqjYRuy9m55GvoXjvuL9M9nzzbEqq5go RY6kPb+WgMB+4VufdCQk0eZm++wwY9UUOcZmePD+yteEL+b5cNRSfdroHyiqy76n e1ZykKpHa6u27poAd8Qhsq1+Htus/FwTgIGc+w/NFPlN2OHkOJ/gIK6Wqb/XPFO0 BQebld2xL5MAUK4EFh4U+mom+zDTQszB6YM0zcWAbfRdfGmMk8WlTR52yfW1xdZB 85elznGYupxFG+FRAw1osoWMUfJ0zYpCmTaUoQzBDMrwpqy6NWTv4KWfmUfE9F8F A6Zat/kujAY/AjkCJCnXssE4She3pmKUmaUd555ZSGjuGL7DWIQOfUz1akTiiVqU p1QktiXtJCPv4S60e5vi6ghrm3kUJhjtBaMOdeIPo5n+RkbHbxRvAoDV4sBRZhVt d+8YvWJXlT7vhTfC2kJg099rOEg3z0vA05nCyJBux2J7lfHFiIY=
=tr8W
-----END PGP SIGNATURE-----

--Sig_/Yj3vjFk=DGuENXvcDCSarHa--


--
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 Newsgroup: muc.lists.freebsd.stable

Marco Moock <mm@dorfdsl.de> writes:

I've now tried that from 14.3-p6 and that failed. libutil.so.9 is
missing and that breaks sudo.

After running `freebsd-update install` twice, you were warned to upgrade
all your ports and packages before running it a third time. You ignored
that warning, and have now discovered the reason for it. Installing the misc/compat14x port or package (which can be done prior to upgrading)
will fix your system.
That aside, upgrading to 15.0-RELEASE using freebsd-update should work
if your starting point is 13.5-RELEASE-p5 or newer, 14.2-RELEASE-p7 or
newer, or 14.3-RELEASE-p4 or newer.
DES
--
Dag-Erling Sm|+rgrav - des@FreeBSD.org
--
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 Newsgroup: muc.lists.freebsd.stable

Marco Moock <mm@dorfdsl.de> writes:

IIRC after the kernel update freebsd-update suggests to reboot and then
it installs the base packages. After that it recommended to run pkg
bootstrap -f.
It didn't say explicitly that upgrading all the packages with pkg is a necessary step before the reboot.

Here is the exact text that it prints:
Completing this upgrade requires removing old shared object files.
Please rebuild all installed 3rd party software (e.g., programs
installed from the ports tree) and then run
'freebsd-update [options] install' again to finish installing updates.
DES
--
Dag-Erling Sm|+rgrav - des@FreeBSD.org
--
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 Newsgroup: muc.lists.freebsd.stable

--Sig_/Ek+ok9D1NPCkWI27r5JjOLO
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 06.12.2025 15:15 Dag-Erling Sm=C3=B8rgrav <des@FreeBSD.org> wrote:

Marco Moock <mm@dorfdsl.de> writes:

IIRC after the kernel update freebsd-update suggests to reboot and
then it installs the base packages. After that it recommended to
run pkg bootstrap -f.
It didn't say explicitly that upgrading all the packages with pkg
is a necessary step before the reboot. =20

=20
Here is the exact text that it prints:
=20
Completing this upgrade requires removing old shared object files.
Please rebuild all installed 3rd party software (e.g., programs
installed from the ports tree) and then run
'freebsd-update [options] install' again to finish installing
updates.

I read that and thought this only applies to manually installed stuff
from the ports tree, not packages installed via pkg.


--=20
kind regards
Marco

Send spam to abfall1765030538@stinkedores.dorfdsl.de

--Sig_/Ek+ok9D1NPCkWI27r5JjOLO
Content-Type: application/pgp-signature
Content-Description: Digitale Signatur von OpenPGP

-----BEGIN PGP SIGNATURE-----

iQJPBAEBCAA5FiEEpXefSZn9R6zNZtTQE76RLz2tRfAFAmk0QCkbFIAAAAAABAAO bWFudTIsMi41KzEuMTEsMiwyAAoJEBO+kS89rUXwxG4P+wVgn/y0P0K5ZztBPoHM b3D/+68pKAJ41MOYB4Cv7dsra745IJ3u1+YLg7wAtE4Ks3pR7iP6E4WYX/nIvemN oCZwya27f1wRTUCMFsCUOaMS970029qYCDid4NM6DOwwy8KvKAUPjJLVQczZ15n0 28ITPukXhZCM2dpHKRjSpPzC83D46GZKwHya9lhZl6Y0LAAQwLKG5P7OPTLe9PK0 M932AG+WUf4AraT13o/L/fuQ1m0g1BwpPwdirHnxUl+cE2IkapFI6fHVMqBvN4BN 36kKrugpz04lX3CB6k6QOrLekebi6RtGyNmY0uhKcMMQMxPNlzXmc35uB1KT7cdX Y6TmXAvyUWuP3FvbSkkUA23/uRqYyPs3JZALp7kJRZGBuqgs/6c5JjWkmsDF8W0x 5Gcy3Kg5oxyKxsqIA4Qy6nzwTPiMn76zpMIcM7qYjIJbBrTfECKdYpSeDXo5XKyV rbikDXOnL7H59lsDMmpulNX0PyaHjbaDkaBjOHZA9RvJb49cnGB6PKziwyzlDSkl lWfc6Vh4I2f8CCPWzpE8Q2rbOqYH4zLlSZXohIEbkhMu6zfx5dvWwVFIRuyjphe8 wU1J4q9hTmgRr218cQMHG780ohrZUm85fbX0VNwKEEMve/FIWO/+hp1OLln//u3y DbpjPdXRqJlXIM7U7rf/xfx2
=eSAF
-----END PGP SIGNATURE-----

--Sig_/Ek+ok9D1NPCkWI27r5JjOLO--


--
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 Newsgroup: muc.lists.freebsd.stable

Marco Moock <mm_at_dorfdsl.de> wrote on
Date: Sat, 06 Dec 2025 14:39:37 UTC :

On 06.12.2025 15:15 Dag-Erling Sm|+rgrav <des@FreeBSD.org> wrote:

Marco Moock <mm@dorfdsl.de> writes:

IIRC after the kernel update freebsd-update suggests to reboot and
then it installs the base packages. After that it recommended to
run pkg bootstrap -f.
It didn't say explicitly that upgrading all the packages with pkg
is a necessary step before the reboot.

Here is the exact text that it prints:

Completing this upgrade requires removing old shared object files.
Please rebuild all installed 3rd party software (e.g., programs
installed from the ports tree) and then run
'freebsd-update [options] install' again to finish installing
updates.

I read that and thought this only applies to manually installed stuff
from the ports tree, not packages installed via pkg.

Installing port-packages is an alternate way of installing ports
without having to build them: building the package on the FreeBSD
build server used involved building the port.
But main now has an adjusted wording that will be MFC'd to stable:
-Please rebuild all installed 3rd party software (e.g., programs
-installed from the ports tree) and then run
+Please upgrade or rebuild all installed 3rd party software (e.g.,
+programs installed with pkg or from the ports tree) and then run
So freebsd-update will be more explicit in the future.
===
Mark Millard
marklmi at yahoo.com
--
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 Newsgroup: muc.lists.freebsd.stable

On 12/5/25 15:55, Nathan Reilly-list wrote:

Hello,

I updated from 13.5 to 15 on amd64 with freebsd-update fine.]

I've gone from 13.5 and 14.3 to 15.0 following the freebsd-update methods.

The only thing I got bit by is that afer the first "freebsd-update
install" and subsequent reboot for the new kernel if you're using ipfw
you're going to have issues until the new userland gets installed.

Best advice would be to disable ipfw before the first reboot, install
the new userland, re-enable ipfw and reboot again.

To be safe you could just do it completely from the console. But for
remote installs if you don't disable ipfw first and it's not set to
default allow, it'll be an issue.
--
inoc.net!rblayzor
PGP: https://pgp.inoc.net/rblayzor/


--
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