Date: Thu, 28 May 2026 07:30:46 -0700 From: Mark Millard <marklmi@yahoo.com> To: Daniel Haryo Sugondo <sugondo@hlrs.de>, pkgbase@freebsd.org Subject: Re: ERROR 403: Forbidden for base_release_0 and 1 Message-ID: <3e5609ba-42a6-4a60-938d-ae8d57e016b7@yahoo.com> In-Reply-To: <934572829.325153.1779951488957.JavaMail.zimbra@hlrs.de> References: <b7f575e3-05ed-4b34-9695-379b818f5fd5@hlrs.de> <bdd429e6-a0bf-4117-af0a-a8783102fe3b@yahoo.com> <934572829.325153.1779951488957.JavaMail.zimbra@hlrs.de>
index | next in thread | previous in thread | raw e-mail
On 5/27/26 23:58, Daniel Haryo Sugondo wrote: > 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. What does the likes of the below show for each "enabled: ???" (my example is from one of my 15.*-STABLE contexts): # pkg repos FreeBSD-ports: { url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/latest", enabled : yes, priority : 0, mirror_type : "SRV", signature_type : "FINGERPRINTS", fingerprints : "/usr/share/keys/pkg" } FreeBSD-ports-kmods: { url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/kmods_latest", enabled : no, priority : 0, mirror_type : "SRV", signature_type : "FINGERPRINTS", fingerprints : "/usr/share/keys/pkg" } FreeBSD-base: { url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/base_latest", enabled : yes, priority : 0, mirror_type : "SRV", signature_type : "FINGERPRINTS", fingerprints : "/usr/share/keys/pkg" } (I do not use any kmods.) For the command that you used: pkg version -vL= Any repositories that indicate 'enabled : no' would have all its installed packages (if any) show up as: orphaned: . . . One can be explicit about the set of repos to consider as enabled for the specific version command, s[pecifying exactly the set of repos to have enabled. For example: # pkg version -rFreeBSD-base -rFreeBSD-ports -vL= One can look at version information for just pkgbase packages via the likes of: # pkg version -rFreeBSD-base -vL= -g FreeBSD-\* You could instead change the enabled status in a file in /usr/local/etc/pkg/respos/ and then use your original command. > > 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?3e5609ba-42a6-4a60-938d-ae8d57e016b7>