Re: security/ca_root_nss: Remove duplicate PLIST entry

From: Franco Fichtner <>
Date: Wed, 20 Sep 2023 08:18:32 UTC
So what's the process here?

Contacted committer: no response
Contacted ports mailing list: no technical discussion

Should I raise a bug ticket for the bug ticket with the patch
that I wrote?  Should the ca_root_nss maintainer take a look
who wasn't involved in the change that I raised concerns about?
Do we not want to avoid further bug reports by doing review
which wasn't possible for this blanket change in pahbricator?

I'm highly confused about the "open source" participation
that is required of non-committers.  ;)


> On 19. Sep 2023, at 1:42 PM, Renato Botelho <> wrote:
> On 19/09/23 05:58, Franco Fichtner wrote:
>> Hi,
>> Looking at this "blanket" change I'm not sure this is a good way to bring in without discussion
>> and especially without a revision change:
>> The relevant bug was reported here:
>> And I'd suggest rolling back that recent change or making a better effort at explaining the
>> problem it solves.
> According to the commit log, those files are already handled by @sample entries on pkg-plist so nothing is gonna change on final package.
> -- 
> Renato Botelho