Date: Fri, 22 May 2026 11:05:45 -0700 From: Mark Millard <marklmi@yahoo.com> To: Colin Percival <cperciva@tarsnap.com>, daniel.sugondo@hlrs.de, pkgbase@freebsd.org Subject: Re: ERROR 403: Forbidden for base_release_0 and 1 Message-ID: <b8f332a6-47e2-4bfa-94a8-2d7fd43285a8@yahoo.com> In-Reply-To: <0100019e50c1b598-883dd9e1-cf40-4f35-bbac-f2a40cb9cbb1-000000@email.amazonses.com> References: <b7f575e3-05ed-4b34-9695-379b818f5fd5@hlrs.de> <0100019e4e6ab8f5-a1616d46-6a9f-4891-80e4-4898c23e2235-000000@email.amazonses.com> <887f0791-8acf-4577-9a52-23b8dc4d57df@yahoo.com> <0100019e50c1b598-883dd9e1-cf40-4f35-bbac-f2a40cb9cbb1-000000@email.amazonses.com>
index | next in thread | previous in thread | raw e-mail
On 5/22/26 10:35, Colin Percival wrote: > On 5/22/26 09:15, Mark Millard wrote: >> On 5/21/26 23:41, Colin Percival wrote: >>> On 5/21/26 23:14, Daniel Haryo Sugondo wrote: >>>> the base_release_0 and base_release_1 aren't accessible. >>>> [...] >>>> >>>> Should it be so? >>> The raw directories aren't accessible. But the files are there, e.g. >>> https://pkg.freebsd.org/FreeBSD:15:amd64/base_release_0/meta.conf >>> should load just fine. >>> >> >> So one needs to already know the file names and to list them all >> explicitly? >> >> Is there an appropriate, systematic way to discover all the file names >> and then list them all? > The pkg tool can fetch packages. > > Making a directory listing available would just be begging LLM scrapers to > waste our bandwidth. > If that is why for 15.0-* and 15.1-* (non-armv7), then why are the non-15.*'s exposed? For example: https://pkg.freebsd.org/FreeBSD:14:aarch64/base_release_0/ shows the list of *.pkg files. Other than 15.* (non-armv7), all the https://pkg.freebsd.org/FreeBSD:*:*/base_*/ show each pkg (and more). (It is understandable if this is to be avoided.) -- === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b8f332a6-47e2-4bfa-94a8-2d7fd43285a8>