Date: Wed, 20 Sep 2023 10:18:32 +0200 From: Franco Fichtner <franco@lastsummer.de> To: ports@freebsd.org Subject: Re: security/ca_root_nss: Remove duplicate PLIST entry Message-ID: <3C85B95F-A41E-4859-9D27-61D414AFC833@lastsummer.de> In-Reply-To: <44a681dd-71cf-4946-bcdc-4928aeb02fd5@FreeBSD.org> References: <EAE8891D-0168-4879-BA59-067FAE37623F@lastsummer.de> <44a681dd-71cf-4946-bcdc-4928aeb02fd5@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. ;) Cheers, Franco > On 19. Sep 2023, at 1:42 PM, Renato Botelho <garga@FreeBSD.org> wrote: >=20 > 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: >> = https://cgit.freebsd.org/ports/commit/security/ca_root_nss?id=3D574c939ecc= d322 >> The relevant bug was reported here: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262755 >> And I'd suggest rolling back that recent change or making a better = effort at explaining the >> problem it solves. >=20 > According to the commit log, those files are already handled by = @sample entries on pkg-plist so nothing is gonna change on final = package. > --=20 > Renato Botelho >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C85B95F-A41E-4859-9D27-61D414AFC833>