Hello,
The system is FreeBSD 13.1-STABLE #0 3f908eed2:
# make
===> License APACHE20 accepted by the user
===> ninja-1.11.1,2 depends on file: /usr/local/sbin/pkg - found
=> ninja-build-ninja-v1.11.1_GH0.tar.gz doesn't seem to exist in
/usr/ports/distfiles/.
=> Attempting to fetch
https://cod
Given /usr/share/certs exists for all supported releases, is there any
reason to keep the ca_root_nss port?
On Thu, 19 Jan 2023 03:13:48 -0800
Mel Pilgrim wrote:
> Given /usr/share/certs exists for all supported releases, is there any
> reason to keep the ca_root_nss port?
If everyone in the world uses LATEST main only, yes.
But the assumption is clearly nonsense.
Basically, commits to main are sett
On 2023-01-19 4:08, Tomoaki AOKI wrote:
On Thu, 19 Jan 2023 03:13:48 -0800
Mel Pilgrim wrote:
Given /usr/share/certs exists for all supported releases, is there any
reason to keep the ca_root_nss port?
If everyone in the world uses LATEST main only, yes.
But the assumption is clearly nonsens
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
19.01.2023 18:13, Mel Pilgrim wrote:
> Given /usr/share/certs exists for all supported releases, is there any reason
> to keep the ca_root_nss port?
Single port may be updates more frequently and easily than base system.
On Thu, 19 Jan 2023 05:58:12 -0800
Mel Pilgrim wrote:
> On 2023-01-19 4:08, Tomoaki AOKI wrote:
> > On Thu, 19 Jan 2023 03:13:48 -0800
> > Mel Pilgrim wrote:
> >
> >> Given /usr/share/certs exists for all supported releases, is there any
> >> reason to keep the ca_root_nss port?
> >
> > If eve
> On 19. Jan 2023, at 23:09, Tomoaki AOKI wrote:
>
> On Thu, 19 Jan 2023 05:58:12 -0800
> Mel Pilgrim wrote:
>
>>> On 2023-01-19 4:08, Tomoaki AOKI wrote:
>>> On Thu, 19 Jan 2023 03:13:48 -0800
>>> Mel Pilgrim wrote:
>>>
Given /usr/share/certs exists for all supported releases, is th
On Fri, 20 Jan 2023 00:04:21 +0700
Eugene Grosbein wrote:
> 19.01.2023 18:13, Mel Pilgrim wrote:
>
> > Given /usr/share/certs exists for all supported releases, is there any
> > reason to keep the ca_root_nss port?
>
> Single port may be updates more frequently and easily than base system.
Ex
On Thu, 19 Jan 2023 23:16:46 +0100
Michael Gmelin wrote:
> > On 19. Jan 2023, at 23:09, Tomoaki AOKI wrote:
> >
> > On Thu, 19 Jan 2023 05:58:12 -0800
> > Mel Pilgrim wrote:
> >
> >>> On 2023-01-19 4:08, Tomoaki AOKI wrote:
> >>> On Thu, 19 Jan 2023 03:13:48 -0800
> >>> Mel Pilgrim wrote:
>
On 2023-01-19 14:09, Tomoaki AOKI wrote:
On Thu, 19 Jan 2023 05:58:12 -0800
Mel Pilgrim wrote:
I wonder if the script secteam uses to update the trust store in the src
tree could be turned into a periodic script that automatically updates
the trust store? Side-step the release engineering dela
> On 20. Jan 2023, at 07:45, free...@oldach.net wrote:
>
> Mel Pilgrim wrote on Thu, 19 Jan 2023 14:58:12 +0100 (CET):
>>> On 2023-01-19 4:08, Tomoaki AOKI wrote:
>>> On Thu, 19 Jan 2023 03:13:48 -0800
>>> Mel Pilgrim wrote:
>>>
Given /usr/share/certs exists for all supported releases,
12 matches
Mail list logo