From nobody Fri Dec 12 10:38:55 2025 X-Original-To: freebsd-pkgbase@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4dSQtW42w1z6Khwx for ; Fri, 12 Dec 2025 10:39:15 +0000 (UTC) (envelope-from peter@pean.org) Received: from helix.jails.se (helix.jails.se [34.246.59.0]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4dSQtW0x7Zz44pQ; Fri, 12 Dec 2025 10:39:14 +0000 (UTC) (envelope-from peter@pean.org) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (host-95-203-12-41.mobileonline.telia.com [95.203.12.41]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by helix.jails.se (Postfix) with ESMTPSA id BD5DA19688; Fri, 12 Dec 2025 11:39:03 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pean.org; s=856eb2587895cefc; t=1765535944; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xe2awEjrQ08QcpH4CH/qjEMEBW4XRGhoZul3NvNAS6A=; b=xGkIxkFox0PvKjeVho0Vpm7diJxdCD9iRjmIBk9qpjSawhEpl+7+6STKk9wnXbWtkSX/I/ ulDOrTzdvUMmdETjMXoRFgIXxi5gkOE3MVPEkzLFvl5HCS5RMxRxJTzMGsUIzxQIW+TUyf Xs0SDBKFSCot3veaEf50aEyeOS7gzNAG97CyI4gIpv5o/aEBzgO3zWbIQ00rrGqH6jdj2L wFMX9iH0YNay7A+lyWsKGQKKIwHavDw3cm+I5PsLvQsnrubXkuqt1nJMs6Wdsuwh+K+UUF S3VB8uQOCLxfX6k5+QFSGF9NKqU7cIPph5WDzwH0UZ9pXfeAaBHX1MzGsqxbzdjgJ2XR+j xT5JtI+tDVX7yG4Opft4Ds860miONkVN5dSgWDusYYcSDg2TMIpMvRoCqy3cxpRL9r4OeS erFdDtJnNfwKNrVwVsH+ryV9qxOYQ4pxRgA/Su7yUl8TwPOSs9f+qD3EApVzmsECbvEdpL iiLsgp4ZMcKxVqYpeQ4Gzub4916ZaRD7TcboodpWcSD9WFAAfvUrUXenwy3asE1dJjDxfN cmvxrY2mHk0jfGMzhrYHdCMcI++iJ9QhKVh1LQ/fzVK47VtFG/iuR3V1vE2RjZe+9+dhWE 5BEOYCcYadbgnA0te+yt7NtUbNvrvOiEtTkFOUYiS2OOMxrHrBhS8= Content-Type: multipart/alternative; boundary=Apple-Mail-5A5B9FF9-FFE4-41C2-B343-F7FA49B17367 Content-Transfer-Encoding: 7bit From: =?utf-8?Q?Peter_Ankerst=C3=A5l?= List-Id: Packaging the FreeBSD base system List-Archive: https://lists.freebsd.org/archives/freebsd-pkgbase List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkgbase@FreeBSD.org Mime-Version: 1.0 (1.0) Subject: Re: Customize what packages get installed Date: Fri, 12 Dec 2025 11:38:55 +0100 Message-Id: <971EEA4E-BCC6-46F3-8AF1-67C8B6F6B282@pean.org> References: Cc: freebsd-pkgbase@freebsd.org In-Reply-To: To: Lexi Winter X-Mailer: iPhone Mail (23B85) X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:34.240.0.0/13, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dSQtW0x7Zz44pQ --Apple-Mail-5A5B9FF9-FFE4-41C2-B343-F7FA49B17367 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On 12 Dec 2025, at 00:48, Lexi Winter wrote: >=20 > =EF=BB=BFPeter Ankerst=C3=A5l wrote in : >> When using freebsd-update and there is a new patchlevel only the >> affected files are updated. Lets say the patchlevel only contains a >> fix for unbound. Then freebsd-update will only download and install >> unbound-files. >>=20 >> But when moving from one patchlevel to another using pkgbase all >> installed packages from FreeBSD-base will be updated. But it would >> have been enough to just upgrade the FreeBSD-unbound package. >=20 > no, this isn't how it works. are you using pkg.freebsd.org packages > or building your own packages? >=20 > if you're building your own packages, use "make update-packages", > not "make packages". that will copy unchanged packages from the > previous build, so that the version number doesn't change and > pkg won't upgrade them. >=20 > if you're using pkg.freebsd.org packages, there are only two > explanations i can think of for this behaviour: >=20 > - you are tracking CURRENT, and only update relatively infrequently; > because the value of __FreeBSD_version is encoded in the ELF header > of every executable, any time that value is bumped, you will need > to update nearly all packages. this can happen several times per > week during periods of high code churn. >=20 > this is correct behaviour, because the executables have changed > and need to be updated. (you could debate whether it's really > necessary to encode this particular value in the ELF header, > though; but that's not a pkgbase issue.) >=20 > - you updated past a point where the pkg.freebsd.org repository was > rebuilt from scratch. as far as i know, this has only happened > once in recent memory, and that was a couple of months ago, so > this would only be the cause of your issue if you almost never > update and ignore security issues. >=20 > if neither of these explanations seem plausible, please record the > output of 'pkg upgrade' the next time you run it, and post it here, > because the behaviour you are observing is not intentional. > Thanks for your thorough explanation! Im using pkg.freebsd.org but I dont ha= ve the logs from the particular upgrade. It was 14.3pX -> 14.3p6 at least. =20 I will keep track of how upgrades behave in the future and post them here if= I observe the same behavior again. =20 /Peter= --Apple-Mail-5A5B9FF9-FFE4-41C2-B343-F7FA49B17367 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
On 12 Dec 2025, at 00:48, Lexi Winter <ivy@freebsd.org&g= t; wrote:

=EF=BB=BFPeter Ankerst=C3=A5l wrote in <A83ED87A-DA17-4B44-803B-= A7EEC5176634@pean.org>:
When us= ing freebsd-update and there is a new patchlevel only the
affected files are updated. Lets say th= e patchlevel only contains a
fix for unbound. Then freebsd-update will only download and install<= /span>
unbound-files.=

But when moving from one patchlevel to another u= sing pkgbase all
inst= alled packages from FreeBSD-base will be updated. But it would
have been enough to just upgrade t= he FreeBSD-unbound package.

no= , this isn't how it works.  are you using pkg.freebsd.org packages
or building your own packages?

= if you're building your own packages, use "make update-packages",
= not "make packages".  that will copy unchanged packages from the<= /span>
previous build, so that the version number doesn't change an= d
pkg won't upgrade them.

i= f you're using pkg.freebsd.org packages, there are only two
= explanations i can think of for this behaviour:

<= span>- you are tracking CURRENT, and only update relatively infrequently;
 because the value of __FreeBSD_version is encoded in th= e ELF header
 of every executable, any time that value= is bumped, you will need
 to update nearly all packag= es.  this can happen several times per
 week duri= ng periods of high code churn.

 this i= s correct behaviour, because the executables have changed
&= nbsp;and need to be updated.  (you could debate whether it's really
 necessary to encode this particular value in the ELF hea= der,
 though; but that's not a pkgbase issue.)<= br>
- you updated past a point where the pkg.freebsd.o= rg repository was
 rebuilt from scratch.  as far a= s i know, this has only happened
 once in recent memor= y, and that was a couple of months ago, so
 this would= only be the cause of your issue if you almost never
 = update and ignore security issues.

if neith= er of these explanations seem plausible, please record the
o= utput of 'pkg upgrade' the next time you run it, and post it here,because the behaviour you are observing is not intentional.
<signature.asc>

Thanks f= or your thorough explanation! Im using pkg.freebsd.or= g but I dont have

the logs from the= particular upgrade. It was 14.3pX -> 14.3p6 at least.<= /p>

 

I will keep track of how upgrades behave= in the future and post them here if I observe the same behavior again.=

 

/Peter

= --Apple-Mail-5A5B9FF9-FFE4-41C2-B343-F7FA49B17367--