Re: New pkg 2.1.1 used wrong version of pkg/libpkg/pkg_abi.c [WARNING: some build servers now using the bad pkg 2.1.1]

On Apr 23, 2025, at 19:25, Mark Millard <marklmi@yahoo.com> wrote:

> On Apr 23, 2025, at 15:22, Mark Millard <marklmi@yahoo.com> wrote:
> 
>> On Apr 23, 2025, at 14:38, Einar Bjarni Halldórsson <einar@isnic.is> wrote:
>>> 
>>> On 23 Apr 2025, at 18:44, Mark Millard <marklmi@yahoo.com> wrote:
>>>> 
>>>> pkg 2.1.1          used: 0e22efc407eaaaf0154cde4507fba27c9e3ca237
>>>> 
>>>> The prior 2.1.99.2 used: 01165121d076dfd090b101ce2915d786fea85381
>>>> (which is newer and has the fix that avoids the recursive install
>>>> of the same port indefinately)
>>>> 
>>> 
>>> I had to downgrade to pkg 2.1.0 from 2.1.1 to get poudriere to possibly finish building some
>>> R-cran-* ports (fingers crossed!).
>>> 
>>> It looks like the recursive install bug you mentioned.
>> 
>> pkg 2.1.1 generates .pkg files with incorrect content.
>> (That is what can later lead to the recursive
>> addition-start sequence.)
>> 
>> So you likely will want to regenerate any .pkg file that
>> pkg 2.1.1 generated.
> 
> WARNING:
> 
> Given the above, my expectation is that any build
> server that is not using pkg 2.1.0 or before, should
> be prevented from (continuing) to use pkg 2.1.1 . So:
> stop any pkg 2.1.1 based build and prevent more
> builder runs until there is a fixed pkg with a later
> version number, even for any between-builds machines.
> Needing to be stopped includes (as I write this):
> 
> beefy16's 134amd64-default
> beefy15's 134i386-default
> beefy22's 142amd64-default
> beefy21's 142i386-quarterly
> beefy20's 142amd64-quarterly
> 
> Any .pkg files created by these should be regenerated
> with an fixed pkg. So "poudriere bulk -c -a" (from
> scratch) based builds would seem likely.
> 

I probably should also have explicitly mentioned that pkg's
built by pgk 2.1.1 should probably not be distributed
to anywhere (if that can be avoided).

===
Mark Millard
marklmi at yahoo.com