Date: Tue, 28 May 2024 21:03:52 -0700 From: Mark Millard <marklmi@yahoo.com> To: Philip Paeps <philip@freebsd.org> Cc: FreeBSD Mailing List <freebsd-ports@freebsd.org>, "Danilo G. Baio" <dbaio@freebsd.org> Subject: Re: FYI: https://pkg-status.freebsd.org/?all=1&type=package does not cover beefy20 , beefy21 , or beefy22 yet Message-ID: <04400C58-FF6A-4586-BA08-C3EED34D952D@yahoo.com> In-Reply-To: <7F7175E9-35F6-4B07-B991-C7A87A5B5733@freebsd.org> References: <DAE4B13A-A433-496C-8B24-7560695C5796.ref@yahoo.com> <DAE4B13A-A433-496C-8B24-7560695C5796@yahoo.com> <7F7175E9-35F6-4B07-B991-C7A87A5B5733@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 28, 2024, at 20:45, Philip Paeps <philip@freebsd.org> wrote: > On 2024-05-29 11:37:04 (+0800), Mark Millard wrote: >> In the mean time: The "IPv4 Proxy" buttons/links on the lines for = beefy2[012] at https://portsfallout.com/server allow looking at the = build activity on those machines. The lines also show which build = environment (such as "140amd64-default" or "140amd64-quarterly"). The = "IPv4 Proxy" buttons/links in question translate to: >>=20 >> https://pkg-status.freebsd.org/beefy20/ >> https://pkg-status.freebsd.org/beefy21/ >> https://pkg-status.freebsd.org/beefy22/ >>=20 >> After that click the Build link on the page that is shown. >=20 > The package builders live in an IPv6-only VLAN. The reverse proxy on = https://pkg-status.freebsd.org is for the convenience of users who are = only connected to the legacy 20th century IPv4 internet. >=20 > If you are on the 21st century internet, you can get directly to e.g. = http://beefy18.nyi.freebsd.org. http://beefy18.nyi.freebsd.org/ works for me. http://beefy21.nyi.freebsd.org/ "Can't Fine the Server" for me. but . . . https://pkg-status.freebsd.org/beefy21/ works for me. The system I'm using has IPv6 addresses. >> https://portsfallout.com/server is somewhat messy for the beefy* = "IPv4 Proxy" examples with lines that list multiple build environments = or just a rather old build environment: >>=20 >> Some links involved, like https://pkg-status.freebsd.org/beefy2/ , no = longer lead to someplace specific to the machine name. >=20 > beefy2 was decommissioned. >=20 >> Some links, like https://pkg-status.freebsd.org/beefy11/ , lead to = the old place for a type of build, not to the modern place that is on a = newer machine. >=20 > As far as I can tell, beefy11 and beefy18 show similar pages. I can't = tell which is "older" and "newer". Am I misunderstanding something? https://pkg-status.freebsd.org/beefy11/ shows "140i386-default = 804916ac9382" (Master and Build). https://pkg-status.freebsd.org/beefy18/ shows "main-amd64-default = pb6f9255af153_sdeab57178f0" I think you meant 21 instead of 18: https://pkg-status.freebsd.org/beefy21/ shows "140i386-default = b6f9255af153". "140i386-default 804916ac9382" is older (last build done on beefy18, = most likely). "140i386-default b6f9255af153" is newer (most recent build = in-progress/done on beefy21). >> There a lot of lines where the "build environment" list overall does = not match what the modern "IPv4 Proxy" buttons/links displays (when it = does for the machine name). >>=20 >> Note: the plain IPv4 and IPv6 icons do not link anywhere currently, = just the "IPv4 Proxy" of the 3 does. >=20 > Cc:ing dbaio, since he maintains portsfallout. :) Thanks. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?04400C58-FF6A-4586-BA08-C3EED34D952D>