Date: Fri, 05 Jul 2024 18:04:47 +0100 From: Jamie Landeg-Jones <jamie@catflap.org> To: philip@FreeBSD.org, marklmi@yahoo.com Cc: karl@denninger.net, freebsd-stable@FreeBSD.org, bapt@FreeBSD.org Subject: Re: pkg_https:// failures related to, for example, "SSL certificate problem: certificate is not yet valid" Message-ID: <202407051704.465H4lPN069136@donotpassgo.dyslexicfish.net> In-Reply-To: <2AFD1E26-C71D-41D0-BA46-E64DFCE5C8EC@freebsd.org> References: <5667D5C0-44F7-4B40-8F63-50D5973D220D.ref@yahoo.com> <5667D5C0-44F7-4B40-8F63-50D5973D220D@yahoo.com> <0377045B-3DF8-4B25-9075-6F67F9E7194B@freebsd.org> <769FF550-3F6F-4825-ACF5-6E9043D7F1C7@yahoo.com> <2AFD1E26-C71D-41D0-BA46-E64DFCE5C8EC@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Philip Paeps <philip@FreeBSD.org> wrote: > > It does seem that /etc/pkg/FreeBSD.conf should avoid > > the https notation so that it presents an appropriate > > default. > > I agree. Adding bapt@ to Cc:. I think this needs to be reverted. It > should probably also be an errata candidate so folks running releases > can update packages even when their clocks get out of sync. I can confirm. A fresh standard install I did a few months ago (14.0-release probably) failed to install packages due to https errors. I knew packages were signed, so didn't investigate the cause of the failure, just changed pkg+https to pkg+http and all worked ok. pkg+https was definitely the installed default. Cheers, Jamie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202407051704.465H4lPN069136>