Re: git: 433bef0946b9 - main - textproc/libxml2: update to 2.15.3

On 2026-04-26 13:12, Mathieu Arnold wrote:
> On Sun, Apr 26, 2026 at 01:00:24PM +0200, Daniel Engberg wrote:
>> This is been brought up twice by now (even with a working example), if one
>> committer intends to hold it "hostage" at least give it proper attention
>> being a crucial port.
>>
>> Best regards,
>> Daniel
>>
> 
> Hi,
> 
> I want to address the language here. "Hostage" implies bad faith, and I
> think we can reject that characterization.
> 
> Vague accusations paired with vague requests for "proper attention" do
> not move things forward, they just raise the temperature.
> 
> This kind of framing makes it harder for others to engage with your
> concerns, even when those concerns may be legitimate
> 
> As a side note, signing off with 'Best regards' does not soften the
> aggressiveness before it.
> 
> Thanks
> 

Hi,

You're referring to one committer blocking security updates for weeks, 
multiple committers (including on the same team) are questioning it 
including ports-secteam? Yes, that makes it indeed very hard for "others 
to engage".

Other PRs of interest,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294260
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294696

Unit tests are still not working (reported several weeks ago) and/or 
upstream project repo isn't carefully reviewed. 
https://docs.freebsd.org/en/books/porters-handbook/book/#makefile-maintainer 
--> 
https://docs.freebsd.org/en/articles/contributing/#_keep_your_ports_up_to_date 
"Thoroughly review and test your changes"

Security updates for what one would classify as a "critical" port lands 
slowly overall. There's even a section in Porters Handbook which is 
titled "Why Security is So Important"
https://docs.freebsd.org/en/books/porters-handbook/book/#security-intro

Is there any work being done / or plans on portmgr's side to improve the 
situation as we're clearly not performing great overall?

Best regards,
Daniel