Dear port maintainers,
The portscout new distfile checker has detected that one or more
unmaintained ports appears to be out of date. Please take the opportunity
to check each of the ports listed below, and if possible and appropriate,
submit/commit an update. Please consider also adopting this po
On Sep 20, 2023, at 11:07, Mark Millard wrote:
>> author Brooks Davis 2023-09-20 15:55:42 +
>> committer Brooks Davis 2023-09-20 17:02:00 +
>> commit e46126d5d35bf996048bcaa47d4de3a7fc7aa75d (patch)
>> tree ad9e142ec89607785e47de0e055d740c4a94afbe
>> parent 50e51d2680b46371c9d29c1b02fdd
> authorBrooks Davis2023-09-20 15:55:42
> +
> committer Brooks Davis2023-09-20 17:02:00
> +
> commite46126d5d35bf996048bcaa47d4de3a7fc7aa75d (patch)
> tree ad9e142ec89607785e47de0e055d740c4a94afbe
> parent50e51d2680b46371c9d29c1b02fdd51aac17a86
Hi,
> On 20. Sep 2023, at 1:17 PM, Bernhard Froehlich wrote:
>
> Before anyone is going to revert this I'd like to add that it seems to fix a
> bug with Custom Root CA for me.
Thanks, would have been nice to have this on record.
> Up to now whenever I have a box with an additional Private Root
On Wed, 20 Sep 2023 10:18:32 +0200 Franco Fichtner wrote ---
> > On 19. Sep 2023, at 1:42 PM, Renato Botelho ga...@freebsd.org> 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
Hi!
> So what's the process here?
>
> Contacted committer: no response
> Contacted ports mailing list: no technical discussion
It looks like it is really a non-trivial topic, so people
probably still think about it.
> Should I raise a bug ticket for the bug ticket with the patch
> that I wrote?
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 ab
