Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

From: Guido Falsi <mad_at_madpilot.net>
Date: Sun, 02 Feb 2025 08:04:00 UTC
On 02/02/25 09:02, Baptiste Daroussin wrote:
> Le 1 février 2025 23:36:12 GMT+01:00, Guido Falsi <mad@madpilot.net> a écrit :
>> On 01/02/25 22:56, Baptiste Daroussin wrote:
>>> On Sat 01 Feb 22:40, Baptiste Daroussin wrote:
>>>> On Fri 31 Jan 19:13, Baptiste Daroussin wrote:
>>>>> On Fri 31 Jan 18:18, Guido Falsi wrote:
>>>>>> On 27/01/25 10:56, Nuno Teixeira wrote:
>>>>>>> Hello Rainer,
>>>>>>>
>>>>>>>    > Wouldn't this be the right time to get Bapt@ involved? After all, he has
>>>>>>>    > worked intensively on the pkg updates.
>>>>>>>
>>>>>>> Yes it is. I'm CC'ing bapt@.
>>>>>>
>>>>>> Since this issue was pestering me while testing multiple ports with
>>>>>> unnecessarily lengthy rebuilds I took a look.
>>>>>>
>>>>>> I have posted a pull request for poudriere [1] with a fix/workaround that
>>>>>> works for me and allows me to have a functional build machine.
>>>>>>
>>>>>> I'm not sure if this fix is completely correct, but maybe it can be useful
>>>>>> to other people as a work around.
>>>>>>
>>>>>>
>>>>>> [1] https://github.com/freebsd/poudriere/pull/1204
>>>>>>
>>>>>> -- 
>>>>>> Guido Falsi <mad@madpilot.net>
>>>>>
>>>>> at quick glance it sounds like a bug in pkg I ll have a look at it next week
>>>>>
>>>>> Bapt
>>>>>
>>>>
>>>> After deeper analysis, I figure pkg is right and each time it claims a need for
>>>> After a deeper analysis:
>>>> 32bits libs, they are actually needed. for reported ports, I think the
>>>> PKG_NO_VERSION_FOR_DEPS=yes does not work yet with newer pkg version.
>>>>
>>>> I have found while analysing to potential bug at pkg install time for people not
>>>> using pkgbase, which I will work on fixing, not nothing wrong regarding the :32
>>>> handling at pkg build time (aka what you face in poudriere).
>>>>
>>>> I may be wrong, but I am not sure I am.
>>>>
>>>> For people who haven't notice one of the major change of pkg 2.x is tracking 32
>>>> bit libraries (and potentially linux one, off for now) AND tracking base
>>>> libraries always.
>>>>
>>>> After a deeper analysis:
>>>> My understanding if poudriere with PKG_NO_VERSION_FOR_DEPS=yes would work ok as
>>>> if, if the building jail was built using pkgbase.
>>>>
>>>> What poudriere lacks for the options if gathering base libaries to consider them
>>>> as provided.
>>>>
>>>> Note that pkg at runtime if not running on a system install using pkgbase, will
>>>> scan for base libraries. (Note this is where I found the bug I am interesting
>>>> in: it does not scan for 32bit libraries yet, which make pkg check -d unhappy)
>>>>
>>>> Best regards,
>>>> Bapt
>>>>
>>>
>>> And I was wrong about the pkg install bug, we do scan for 32bit livraries, so
>>> everything should be fine.
>>
>> Bapt, thanks for the analysis.
>>
>> SO I gather I need to rebuild my jails from scratch, possibly from pkgbase, but I'm not sure what I can do about my head jail which I build from source, and do also use to generate pkgbase packages for my desktops/laptop etc.
>>
>> Or maybe I'm completely missing the point.
>>
> 
> I will look into making poudriere support this properly next week

Thanks a lot for your work on all this!

-- 
Guido Falsi <mad@madpilot.net>