On May 23, 2022, at 18:35, Jim DeLaHunt wrote:
> 1. port curl-ca-bundle is a subport of port curl[2],
> 2. it looks to me like port curl-ca-bundle only got updated about 7 times in
> the last 43 months[3]
> 3. it looks as if port curl-ca-bundle updates a file within curl,
>
On May 23, 2022, at 21:16, Chris Jones wrote:
> On 23 May 2022, at 9:59 pm, Steven Smith wrote:
>
>>> What has changed between the time that the buildbot built the package and
>>> the time that the user installs it?
>>
>> The certs in curl-ca-bundle are updated regularly to clear out expired
> On 23 May 2022, at 9:59 pm, Steven Smith wrote:
>
>
>>
>> What has changed between the time that the buildbot built the package and
>> the time that the user installs it?
>
> The certs in curl-ca-bundle are updated regularly to clear out expired certs.
>
> Per the previous discussion,
On 2022-05-23 13:59, Steven Smith wrote:
...
The certs in curl-ca-bundle are updated regularly to clear out expired certs.
...> The “solution” appears to be to bump the revision of
privoxy-pki-bundle by hand whenever curl-ca-bundle is updated
And how often is port curl-ca-bundle updated?
> What has changed between the time that the buildbot built the package and the
> time that the user installs it?
The certs in curl-ca-bundle are updated regularly to clear out expired certs.
Per the previous discussion, privoxy-pki-bundle uses these certs via a
depends_lib, and unless a port
On May 22, 2022, at 13:43, Steven Smith wrote:
> A standard install command grabs pre-built stuff from
> https://packages.macports.org/privoxy-pki-bundle. This pre-built stuff is
> inevitably stale because it inevitably contains expired certs.
Again, why is it the case that what we built on
