Date: Sat, 17 Jan 2026 05:22:59 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 247998] pkg.freebsd.org subfolders indexes are forbidden Message-ID: <bug-247998-9-hx8Z6Z4oEZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-247998-9@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247998 --- Comment #10 from Alexey Dokuchaev <danfe@FreeBSD.org> --- (In reply to Dag-Erling Smørgrav from comment #8) > the simple answer is to look up the port on freshports.org, which > provides a table of available packages for each port. That table works as a way to check package availability for a particular architecture (it even provides some timestamps), but to download the actual *.pkg files one still has to know the direct URL. Doing this via `pkg fetch' is not always feasible, esp. on non-bootstrapped machine without super-user permissions: $ pkg fetch bash pkg: . wrong user or group ownership (expected 0/0 versus actual 1000/1000) $ pkg fetch --show-me-the-url --do-not-download bash pkg: unrecognized option `--show-me-the-url' ¯\_(ツ)_/¯ (In reply to Serge Volkov from comment #0) > For example https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/ now > returns 403/Forbidden. Apparently it got only worse, they reconfigured the server so it no longer returns 403 for a package directory, but hides it ("All") from the index. In 2026, direct URLs look like this: $ curl -I http://pkg.FreeBSD.org/FreeBSD:15:amd64/latest/All/bash-5.3.9.pkg HTTP/1.1 200 OK ... -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-247998-9-hx8Z6Z4oEZ>