Re: FYI: All but armv7 for https://pkg.freebsd.org/FreeBSD:15:*/base_release_0/ get "code" AccessDenied and "Message" Access Denied
- Reply: Colin Percival : "Re: FYI: All but armv7 for https://pkg.freebsd.org/FreeBSD:15:*/base_release_0/ get "code" AccessDenied and "Message" Access Denied"
- In reply to: Colin Percival : "Re: FYI: All but armv7 for https://pkg.freebsd.org/FreeBSD:15:*/base_release_0/ get "code" AccessDenied and "Message" Access Denied"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 28 Nov 2025 19:43:36 UTC
On Nov 28, 2025, at 10:46, Colin Percival <cperciva@freebsd.org> wrote: > On 11/28/25 10:27, Mark Millard wrote: >> On Nov 28, 2025, at 10:03, Colin Percival <cperciva@freebsd.org> wrote: >>> On 11/28/25 09:55, Mark Millard wrote: >>>> Also: Is there another way to check on the status of >>>> future pending updates to the files (new times)? >>> >>> These repositories will be updated when there is a security advisory or >>> errata notice. >> The actual available for download time for a distribution >> server and the notice time about the update need not >> be identical. > > They will be for these files. This is why I created the separate > pkgbase.freebsd.org infrastructure; clusteradm decided at the last > minute that it should be exposed via pkg.freebsd.org but those > systems just 302 requests over to the "real" servers which are > guaranteed to lag no more than 60 seconds. > > By the time a security advisory goes out, pkgbase bits will be > available for download. As release engineer and former security > officer, this was my #1 design requirement for pkgbase. :-) Cool. Good to know. I assume that, for now, that does not apply to armv7, given its currently different (more historical style) behavior where I can look at the dates/times for the 5.0-RELEASE build now. === Mark Millard marklmi at yahoo.com