From owner-freebsd-current@freebsd.org Sun Sep 6 10:00:11 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DF0093CBECE for ; Sun, 6 Sep 2020 10:00:11 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2607:f740:d:20::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Bkn2y5JH6z3S8W for ; Sun, 6 Sep 2020 10:00:10 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 4Bkn2p1QGGz3n4g; Sun, 6 Sep 2020 10:00:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([IPv6:::1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [IPv6:::1]) (amavisd-new, port 10587) with ESMTPS id nmoT4S7Fzoxt; Sun, 6 Sep 2020 10:00:01 +0000 (UTC) Received: from garnet.daemonic.se (unknown [IPv6:2001:470:dca9:1201:44b0:ac37:f76c:1e53]) by mail.daemonic.se (Postfix) with ESMTPSA id 4Bkn2n2QNTz3myt; Sun, 6 Sep 2020 10:00:01 +0000 (UTC) Subject: Re: Is pkg site forbidden by brower? To: grarpamp , freebsd-current@freebsd.org References: <20200905230416.56a9810dae8736dc9a7839bd@j.email.ne.jp> From: Niclas Zeising Message-ID: Date: Sun, 6 Sep 2020 11:59:59 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Bkn2y5JH6z3S8W X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.53 / 15.00]; RCVD_TLS_LAST(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[daemonic.se:s=20151023]; FREEFALL_USER(0.00)[zeising]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; NEURAL_HAM_LONG(-0.97)[-0.968]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[daemonic.se:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[daemonic.se,none]; NEURAL_HAM_SHORT(-1.53)[-1.527]; NEURAL_HAM_MEDIUM(-1.03)[-1.031]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:36236, ipnet:2607:f740:d::/48, country:US]; TAGGED_FROM(0.00)[freebsd]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Sep 2020 10:00:11 -0000 On 2020-09-06 09:00, grarpamp wrote: > On 9/6/20, Kevin Oberman wrote: >> On Sat, Sep 5, 2020 at 8:04 PM Yoshihiro Ota wrote: >>> Is "403 Forbidden" an intended response for a brower access to >>> http://pkg.freebsd.org/FreeBSD:12:i386/ 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 freshports.org, 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 position of /${ABI}//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 examples. > >> Does https://pkg-status.freebsd.org/builds?jailname=121amd64 have what you >> want? > > Those names don't correspond 1:1 to anything on pkg.freebsd.org. 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 failures. Regards -- Niclas