Date: Mon, 13 Jun 2022 22:44:29 -0700 From: Mark Millard <marklmi@yahoo.com> To: Philip Paeps <philip@freebsd.org> Cc: freebsd-current <freebsd-current@freebsd.org>, "clusteradm@freebsd.org" <clusteradm@FreeBSD.org> Subject: Re: ampere3 activity is not showing up on https://pkg-status.freebsd.org/?all=1&type=package Message-ID: <8B511C8C-8E7F-465D-8B70-447EB34DD1EA@yahoo.com> In-Reply-To: <BAE44BE8-B1AB-413D-8562-B728685C9BEF@freebsd.org> References: <E0D13EBE-F9A9-455A-ACB3-1795318B1BFA@yahoo.com> <BAE44BE8-B1AB-413D-8562-B728685C9BEF@freebsd.org>
index | next in thread | previous in thread | raw e-mail
On 2022-Jun-13, at 22:14, Philip Paeps <philip@freebsd.org> wrote: > On 2022-06-13 00:16:55 (+0800), Mark Millard wrote: >> ampere3's activity is not showing up on the page: >> https://pkg-status.freebsd.org/?all=1&type=package >> >> but: >> >> http://ampere3.nyi.freebsd.org/#latest_builds >> and: >> http://ampere3.nyi.freebsd.org/build.html?mastername=130arm64-default&build=b44e82e7d313 >> >> shows a currently active build (but with only 2 ports remaining). > > pkg-status.freebsd.org is maintained on GitHub, outside the clusteradm automation. I sent in this patch a couple of months ago, when I set up ampere3: > > https://github.com/bdrewery/pkg-status.freebsd.org/pull/12/files > > This was merged last week but it doesn't look like there's any automation to keep the running infrastructure in sync with that repository. There were some reassuring screams in a logfile after I chanted some incantations in a the jail running pkg-status.freebsd.org. > > Let me know if that fixed it. > Well, I now see 34 builds that were via ampere3. This was via use of: https://pkg-status.freebsd.org/?all=1&type=package They go back to 2022-Feb-26, with the most recent still in progress (371 remaining). Thanks. === Mark Millard marklmi at yahoo.comhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8B511C8C-8E7F-465D-8B70-447EB34DD1EA>