Re: FYI: All but armv7 for https://pkg.freebsd.org/FreeBSD:15:*/base_release_0/ get "code" AccessDenied and "Message" Access Denied

On Nov 28, 2025, at 10:03, Colin Percival <cperciva@freebsd.org> wrote:

> On 11/28/25 09:55, Mark Millard wrote:
>> On Nov 28, 2025, at 09:34, Colin Percival <cperciva@freebsd.org> wrote:
>>> On 11/28/25 09:28, Mark Millard wrote:
>>>> Using https://pkg.freebsd.org/FreeBSD:15:amd64/ to select:
>>>> https://pkg.freebsd.org/FreeBSD:15:amd64/base_release_0/
>>>> gets to:
>>>> https://cloudfront.aws.pkgbase.freebsd.org/FreeBSD:15:amd64/base_release_0/
>>>> which displays (in my context):
>>>> This XML file does not appear to have any style information associated with it. The document tree is shown below.
>>>> <Error>
>>>> <Code>AccessDenied</Code>
>>>> <Message>Access Denied</Message>
>>>> </Error>
>>> 
>>> What's the problem?  The repositories work.  They just don't have index pages.
>> So the https://pkg.freebsd.org/FreeBSD:15:*/ are deliberately
>> providing links that can not be used for anything useful,
>> such as seeing if any files have been updated (new dates/times)?
>> Is there some way to give enough notice to likely avoid
>> the kind of message that I sent? Otherwise people will
>> continue to be astonished by the result and ask about
>> things appearing to be broken.
> 
> I can probably hand-write some index.html files to put in there.

Sounds good.

>> 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. What I've seen looking at:

https://people.freebsd.org/~dbaio/pkg-master-report.html

vs. (for various *'s and using base_latest/ as an
example context):

https://pkg.freebsd.org/FreeBSD:15:*/base_latest/

has tended to have me confirm availability by checking
the https://pkg.freebsd.org/FreeBSD:15:*/base_latest/
dates/times and only trying to update when those times
indicated the update was available for download.
(Clearly: I've had contexts were I'm trying to get a
version that contains something specific and am avoiding
update attempts that are too early for such to result
from the attempt in my context.)

===
Mark Millard
marklmi at yahoo.com