Re: pkg-static: Warning: Major OS version upgrade detected.

From: Ian FREISLICH <ianfreislich_at_gmail.com>
Date: Tue, 09 Sep 2025 19:01:22 UTC
On 2025-09-09 14:58, Kyle Evans wrote:
> On 9/9/25 13:33, Ian FREISLICH wrote:
>> On 2025-09-09 14:29, Kyle Evans wrote:
>>> On 9/9/25 13:27, Patrick M. Hausen wrote:
>>>> Hi!
>>>>
>>>>> Am 09.09.2025 um 20:11 schrieb Ian FREISLICH <ianfreislich@gmail.com>:
>>>>> Every release this happens. pkg bootstrap -f doesn't fix it either 
>>>>> because there's no FreeBSD:16:amd64/latest.
>>>>
>>>> There is no release 16 (yet), so there are no packages.
>>>>
>>>> You have to build from ports of you run -current.
>>>>
>>>> HTH,
>>>> Patrick
>>>
>>> We certainly build packages for -current, but the branch happened 
>>> only a little bit ago; it's another 12-14+ day
>>> cycle to get a fresh package set and alleviate the above condition.
>>
>> In fairness, at the branch point, 15-prerelease and 16-current ports 
>> trees are the same. Can't the whole set just be copied with the index 
>> updated to 16?
>>
>> Ian
>>
> 
> You could maybe make that assumption, but it's not really that easy; the 
> ABI ("FreeBSD:15:amd64") is encoded in each pkg itself along with a 
> FreeBSD_version annotation for the exact version from sys/param.h at the 
> time of the build.  You'd also have new failures from bad version checks 
> that will be ignored because we just copied the previous version's set, 
> which then gets a bit confusing if we suddenly lose them in an actual - 
> CURRENT build ("Well, we had 16-CURRENT packages for them before, why 
> don't we now?").

Thanks for the explanation.

Ian