Re: git: 6ff5f81bfc26 - main - devel/pkgconf: incorporate a patch from upstream

On 1/29/2024 12:07 PM, Bryan Drewery wrote:
> On 11/8/2023 5:17 AM, Baptiste Daroussin wrote:
>> The branch main has been updated by bapt:
>>
>> URL:https://cgit.FreeBSD.org/ports/commit/?id=6ff5f81bfc266f904a6f84e794898e29f1f6a6f5
>>
>> commit 6ff5f81bfc266f904a6f84e794898e29f1f6a6f5
>> Author:     Baptiste Daroussin<bapt@FreeBSD.org>
>> AuthorDate: 2023-11-08 13:13:49 +0000
>> Commit:     Baptiste Daroussin<bapt@FreeBSD.org>
>> CommitDate: 2023-11-08 13:16:59 +0000
>>
>>      devel/pkgconf: incorporate a patch from upstream
>>      without this patch pkgconf will process PKG_CONFIG_PATH and 
>> PKG_CONFIG_LIBDIR
>>      backwards.
> 
> Poudriere currently would rebuild anything depending on pkgconf due to 
> this, but pkg will not reinstall the packages. The new Poudriere build 
> algorithm I haven't pushed to git yet would not rebuild the packages 
> anymore either.
> 
> I think next time is a PORTREVISION chase for compile-time effects 
> should be done. Something we need to keep in mind for compiler packages 
> like this or cffi or such that change the build output without metadata 
> that is trackable in Poudriere and Pkg.
> 
> I ran into an issue with py-cryptography that I think this change fixes. 
> Rebuilding it now to check, with a planned pkg install -f to check on it.
> 

I was wrong; Pkg does handle Poudriere's rebuild currently since it has 
a shlib change. Not sure how to address this in the new build algorithm 
without a PORTREVISION chase. I manually deleted packages using ports 
openssl (I am on a custom 2023Q4 branch but I'm sure this problem is a 
real one. The rebuild did fix my issue.).

Installed packages to be UPGRADED:
         pkgconf: 2.0.3,1 -> 2.0.3_1,1

Installed packages to be REINSTALLED:
         libevent-2.1.12 (required shared library changed)
         py39-cryptography-41.0.7,1 (required shared library changed)

-- 
Bryan Drewery