Date: Fri, 12 Dec 2025 11:38:55 +0100 From: =?utf-8?Q?Peter_Ankerst=C3=A5l?= <peter@pean.org> To: Lexi Winter <ivy@freebsd.org> Cc: freebsd-pkgbase@freebsd.org Subject: Re: Customize what packages get installed Message-ID: <971EEA4E-BCC6-46F3-8AF1-67C8B6F6B282@pean.org> In-Reply-To: <aTtYD8eSaBRL46VY@amaryllis.le-fay.org> References: <aTtYD8eSaBRL46VY@amaryllis.le-fay.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] > On 12 Dec 2025, at 00:48, Lexi Winter <ivy@freebsd.org> wrote: > > Peter Ankerstål wrote in <A83ED87A-DA17-4B44-803B-A7EEC5176634@pean.org>: >> 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. >> >> 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. > > 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 > previous build, so that the version number doesn't change and > pkg won't upgrade them. > > if you're using pkg.freebsd.org packages, there are only two > explanations i can think of for this behaviour: > > - 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. > > 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.) > > - 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. > > 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. > <signature.asc> Thanks for your thorough explanation! Im using pkg.freebsd.org but I dont have the logs from the particular upgrade. It was 14.3pX -> 14.3p6 at least. I will keep track of how upgrades behave in the future and post them here if I observe the same behavior again. /Peter [-- Attachment #2 --] <html class="apple-mail-supports-explicit-dark-mode"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br id="lineBreakAtBeginningOfSignature"><div dir="ltr"><blockquote type="cite">On 12 Dec 2025, at 00:48, Lexi Winter <ivy@freebsd.org> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>Peter Ankerstål wrote in <A83ED87A-DA17-4B44-803B-A7EEC5176634@pean.org>:</span><br><blockquote type="cite"><span>When using freebsd-update and there is a new patchlevel only the</span><br></blockquote><blockquote type="cite"><span>affected files are updated. Lets say the patchlevel only contains a</span><br></blockquote><blockquote type="cite"><span>fix for unbound. Then freebsd-update will only download and install</span><br></blockquote><blockquote type="cite"><span>unbound-files.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>But when moving from one patchlevel to another using pkgbase all</span><br></blockquote><blockquote type="cite"><span>installed packages from FreeBSD-base will be updated. But it would</span><br></blockquote><blockquote type="cite"><span>have been enough to just upgrade the FreeBSD-unbound package.</span><br></blockquote><span></span><br><span>no, this isn't how it works. are you using pkg.freebsd.org packages</span><br><span>or building your own packages?</span><br><span></span><br><span>if you're building your own packages, use "make update-packages",</span><br><span>not "make packages". that will copy unchanged packages from the</span><br><span>previous build, so that the version number doesn't change and</span><br><span>pkg won't upgrade them.</span><br><span></span><br><span>if you're using pkg.freebsd.org packages, there are only two</span><br><span>explanations i can think of for this behaviour:</span><br><span></span><br><span>- you are tracking CURRENT, and only update relatively infrequently;</span><br><span> because the value of __FreeBSD_version is encoded in the ELF header</span><br><span> of every executable, any time that value is bumped, you will need</span><br><span> to update nearly all packages. this can happen several times per</span><br><span> week during periods of high code churn.</span><br><span></span><br><span> this is correct behaviour, because the executables have changed</span><br><span> and need to be updated. (you could debate whether it's really</span><br><span> necessary to encode this particular value in the ELF header,</span><br><span> though; but that's not a pkgbase issue.)</span><br><span></span><br><span>- you updated past a point where the pkg.freebsd.org repository was</span><br><span> rebuilt from scratch. as far as i know, this has only happened</span><br><span> once in recent memory, and that was a couple of months ago, so</span><br><span> this would only be the cause of your issue if you almost never</span><br><span> update and ignore security issues.</span><br><span></span><br><span>if neither of these explanations seem plausible, please record the</span><br><span>output of 'pkg upgrade' the next time you run it, and post it here,</span><br><span>because the behaviour you are observing is not intentional.</span><br><div><signature.asc></div></div></blockquote><br><div><p class="MsoNormal" style="font-size: 12pt; -webkit-text-size-adjust: auto; margin: 0cm; font-family: Aptos, sans-serif;"><span style="font-size: 10pt;">Thanks for your thorough explanation! Im using <span dir="ltr">pkg.freebsd.org</span> but I dont have<o:p></o:p></span></p><p class="MsoNormal" style="font-size: 12pt; -webkit-text-size-adjust: auto; margin: 0cm; font-family: Aptos, sans-serif;"><span style="font-size: 10pt;">the logs from the particular upgrade. It was 14.3pX -> 14.3p6 at least.<o:p></o:p></span></p><p class="MsoNormal" style="font-size: 12pt; -webkit-text-size-adjust: auto; margin: 0cm; font-family: Aptos, sans-serif;"><span style="font-size: 10pt;"> </span></p><p class="MsoNormal" style="font-size: 12pt; -webkit-text-size-adjust: auto; margin: 0cm; font-family: Aptos, sans-serif;"><span style="font-size: 10pt;">I will keep track of how upgrades behave in the future and post them here if I observe the same behavior again.<o:p></o:p></span></p><p class="MsoNormal" style="font-size: 12pt; -webkit-text-size-adjust: auto; margin: 0cm; font-family: Aptos, sans-serif;"><span style="font-size: 10pt;"> </span></p><p class="MsoNormal" style="font-size: 12pt; -webkit-text-size-adjust: auto; margin: 0cm; font-family: Aptos, sans-serif;"><span style="font-size: 10pt;">/Peter</span></p></div></body></html>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?971EEA4E-BCC6-46F3-8AF1-67C8B6F6B282>