Date: Thu, 28 May 2026 08:58:08 +0200 (CEST) From: Daniel Haryo Sugondo <sugondo@hlrs.de> To: Mark Millard <marklmi@yahoo.com>, pkgbase@freebsd.org Subject: Re: ERROR 403: Forbidden for base_release_0 and 1 Message-ID: <934572829.325153.1779951488957.JavaMail.zimbra@hlrs.de> In-Reply-To: <bdd429e6-a0bf-4117-af0a-a8783102fe3b@yahoo.com> References: <b7f575e3-05ed-4b34-9695-379b818f5fd5@hlrs.de> <bdd429e6-a0bf-4117-af0a-a8783102fe3b@yahoo.com>
index | next in thread | previous in thread | raw e-mail
My question was triggered by the command "pkg version -vL=", why this command shows all packages with prefix FreeBSD- as orphaned. The system is a direct or new installation for the 15.0, not an upgrade from prior version. Then I saw that the access to base_release_0 and 1 are forbidden. But the access to https://pkg.freebsd.org/FreeBSD:15:amd64/base_release_0/meta.conf as Colin wrote, works fine. # pkg version -vL= FreeBSD-acct-15.0 ? orphaned: base/FreeBSD-acct FreeBSD-acpi-15.0 ? orphaned: base/FreeBSD-acpi FreeBSD-apm-15.0 ? orphaned: base/FreeBSD-apm FreeBSD-at-15.0 ? orphaned: base/FreeBSD-at FreeBSD-atf-15.0 ? orphaned: base/FreeBSD-atf FreeBSD-atf-dev-15.0 ? orphaned: base/FreeBSD-atf-dev FreeBSD-atf-lib-15.0 ? orphaned: base/FreeBSD-atf-lib FreeBSD-audit-15.0 ? orphaned: base/FreeBSD-audit FreeBSD-audit-dev-15.0 ? orphaned: base/FreeBSD-audit-dev FreeBSD-audit-dev-lib32-15.0 ? orphaned: base/FreeBSD-audit-dev-lib32 FreeBSD-audit-lib-15.0 ? orphaned: base/FreeBSD-audit-lib FreeBSD-audit-lib32-15.0 ? orphaned: base/FreeBSD-audit-lib32 ... I'm still on investigation, what's happen. Regards, Daniel. -- Mit freundlichen Grüßen! Daniel Haryo Sugondo ----- Original Message ----- From: "Mark Millard" <marklmi@yahoo.com> To: "Daniel Haryo Sugondo" <daniel.sugondo@hlrs.de>, pkgbase@freebsd.org Sent: Friday, May 22, 2026 8:26:41 PM Subject: Re: ERROR 403: Forbidden for base_release_0 and 1 On 5/21/26 23:14, Daniel Haryo Sugondo wrote: > Dear pkgbase maintainer, > > the base_release_0 and base_release_1 aren't accessible. > > Yesterday > $ wget https://pkg.FreeBSD.org/FreeBSD:15:amd64/base_release_0 . . . > 2600:9000:2013:d000:14:fc66:e9c0:93a1|:443... connected. > HTTP request sent, awaiting response... 403 Forbidden > 2026-05-21 14:59:55 ERROR 403: Forbidden. > > Today > $ date > Fri May 22 08:08:10 AM CEST 2026 > $ wget https://pkg.FreeBSD.org/FreeBSD:15:amd64/base_release_0 > . . . > HTTP request sent, awaiting response... 403 Forbidden > 2026-05-22 08:08:13 ERROR 403: Forbidden. > > Should it be so? > > Regards, > > Daniel Sugondo. > For official pkgbase releases, there are the likes of: <https://download.freebsd.org/releases/PKGBASE-REPOS/15.1-BETA3/amd64/Latest/FreeBSD-15.1-BETA3-amd64-pkgbase-repo.tar>; (Also: CHECKSUM.SHA* files.) So, the suggestive pattern: <https://download.freebsd.org/releases/PKGBASE-REPOS/*.*-*/*/Latest/FreeBSD-*-pkgbase-repo.tar>; gives an idea where to get tar files that would contain the *.pkg files (and likely more). There are also snapshots in pkgbase form for 15.* and main [so: 16 as stands], such as: <https://download.freebsd.org/snapshots/PKGBASE-REPOS/15.1-STABLE/aarch64/20260521/FreeBSD-15.1-STABLE-arm64-aarch64-pkgbase-repo-20260521-b718f7d88157-283647.tar>; (Also: CHECKSUM.SHA* files.) Suggestive pattern: <https://download.freebsd.org/snapshots/PKGBASE-REPOS/*.*-*/*/YYYYMMDD/FreeBSD-*.*-*-*-*-pkgbase-repo-YYYYMMDD-*-*.tar>; Note: 15.0 does not look to have any snapshots. But there being only one active 15.*-STABLE for stable/15 makes sense. I do not know why the: https://download.freebsd.org/snapshots/PKGBASE-REPOS/15.0-STABLE/ continues to exist after the files were depopulated from below there. -- === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?934572829.325153.1779951488957.JavaMail.zimbra>