Is pkg site forbidden by brower?

Niclas Zeising zeising+freebsd at
Sun Sep 6 10:00:11 UTC 2020

On 2020-09-06 09:00, grarpamp wrote:
> On 9/6/20, Kevin Oberman <rkoberman at> wrote:
>> On Sat, Sep 5, 2020 at 8:04 PM Yoshihiro Ota <ota at> wrote:
>>> Is "403 Forbidden" an intended response for a brower access to
>>> nowdays?
>>> I used to see available packages with a brower and decided which one to
>>> use.
> Some more people have noted this change
> as breaking tool scripts, etc.
> And useful meta files are unfortunately now invisible:
> packagesite.txz, meta.txz, pkg.txz, pkg.txz.sig
> If someone want to block the '/.../All/' dir full of pkgs,
> maybe, but do not block any other part of the hier.

The reason that folder listing was disabled on the package download 
sites is that it used too much resources.  For every hit on those URLs, 
the web server had to dynamically generate the folder listing, and send 
it.  This caused DDoS-like scenarios, where these were hit repeatedly, 
which caused problems for legitimate traffic.  Since the relevant 
information is available in the txz files above, and also on freshports, 
and since pkg have no need for directory listing, it was disabled.

I would suggest using, which has information on which 
version of a package is available for the various FreeBSD versions and 
architectures, both in the latest and the quarterly branch.

>>> How can I find distributions like "latest", "release_X", etc?
> Yes, there does not appear to be any docs enumerating all
> the available live names for use in PACKAGESITE url.
> Reopening the above dirs would be self documenting.

I am not sure what you are looking for here.  Can you explain the use 
case, what are you trying to accomplish?

> The name for the term in <term> position of /${ABI}/<term>/All/...
> might be "REPOSITORY_ROOT" or "repo-path" or simply "repository",
> but it does not seem defined for users in pkg or pkg.conf manpages.
> "distribution" is unlikely the correct term, "branch" might be
> a useful connotation regarding ports source tree.

Once again, I'm not sure what you are looking for.  Have you looked at 
the manual for pkg.conf, which is fairly extensive and have several 

>> Does have what you
>> want?
> Those names don't correspond 1:1 to anything on

Actually, they do. You can see both the ports tree built (default for 
top of the ports tree, and quarterly for the quarterly branch), as well 
as architecture and FreeBSD version.  You can even see exactly which svn 
revision is used.

>> I can't believe that there is no way to see a log of failed builds,
>> but I can only see the new failures and no information on previous builds.
> Pkg buildlogs are a separate issue.
> They should be available for browsing, same as kernel, base...

Build logs are available, but not all of them are available over IPv4, 
since IPv4 addresses are scarce.  If you open a specific builder, you 
can see a list of new failures, and links to the build logs.  There are 
also links to previous builds, so that you can compare, and find earlier 


More information about the freebsd-current mailing list