Date: Tue, 28 May 2024 20:37:04 -0700 From: Mark Millard <marklmi@yahoo.com> To: FreeBSD Mailing List <freebsd-ports@freebsd.org> Cc: Philip Paeps <philip@freebsd.org> Subject: FYI: https://pkg-status.freebsd.org/?all=1&type=package does not cover beefy20 , beefy21 , or beefy22 yet Message-ID: <DAE4B13A-A433-496C-8B24-7560695C5796@yahoo.com> References: <DAE4B13A-A433-496C-8B24-7560695C5796.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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: https://pkg-status.freebsd.org/beefy20/ https://pkg-status.freebsd.org/beefy21/ https://pkg-status.freebsd.org/beefy22/ After that click the Build link on the page that is shown. 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: Some links involved, like https://pkg-status.freebsd.org/beefy2/ , no = longer lead to someplace specific to the machine name. 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. 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). Note: the plain IPv4 and IPv6 icons do not link anywhere currently, just = the "IPv4 Proxy" of the 3 does. =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?DAE4B13A-A433-496C-8B24-7560695C5796>