Date: Sun, 5 Apr 2026 18:58:38 -0700 From: Mark Millard <marklmi@yahoo.com> To: Philip Paeps <philip@freebsd.org> Cc: freebsd-pkgbase@freebsd.org Subject: Re: 3 platform combinations not having base_latest built [the 3 stayed old, not updating] Message-ID: <a4a9c0cc-39a2-407c-91c6-2533661822f7@yahoo.com> In-Reply-To: <9E4A38C6-5F7D-407B-8263-23C54D49FE5E@freebsd.org> References: <dd594c24-1cd6-4cce-8045-1105330814e4@yahoo.com> <A9E3EB07-9F11-4065-9BFF-B332BAC36C42@freebsd.org> <09A82CF6-53B2-4513-B7F8-7FCD6EEF72C2@freebsd.org> <4f3698cf-b5e5-4fe8-9493-2a7977d0d224@yahoo.com> <9E4A38C6-5F7D-407B-8263-23C54D49FE5E@freebsd.org>
index | next in thread | previous in thread | raw e-mail
On 4/5/26 16:36, Philip Paeps wrote: > On 2026-04-06 01:07:39 (+0800), Mark Millard wrote: >> On 4/5/26 01:56, Philip Paeps wrote: >>> On 2026-04-05 14:46:12 (+0800), Philip Paeps wrote: >>>> On 2026-04-05 12:46:33 (+0800), Mark Millard wrote: >>>>> https://people.freebsd.org/~dbaio/pkg-master-report.html does not >>>>> show any "missing" rows for any of the 3. >>>>> >>>>> Most recent (the only) updates listed for the 3: >>>>> >>>>> 2026-03-20 12:00:02Z freebsd:16:powerpc:64:eb >>>>> 2026-03-27 00:00:01Z freebsd:15:x86:32 >>>>> 2026-03-27 00:00:02Z freebsd:15:armv7:32:el:eabi:hardfp >>>> >>>> One of our mirrors broke and builds are not being made visible until >>>> it's fixed. >> >> I expect that is why everything else other than the 3 had multiple >> rows of "missing" categorizations. (They also had more recent >> "present" base_latest rows than the 3 listed above.) >> >> I expect that the 3 are a different issue of failed/lack-of newer builds. > > Right. Sorry. I misread your email. :) > >>>> I'm working on it. >>> >>> The broken mirror is no longer broken. It'll take a bit of time to >>> catch up but builds are being pushed and made visible again. >> >> All the base_latest rows now indicate "present", no examples of >> "missing". >> >> But the 3 that I reported still have only the old dates/times, same >> dates/times as indicated above in my original note. Not your problem >> to solve as far as I can tell. > > Mhm. Yes. I think this is more a matter of they're simply not being > built than that they're not syncing. > > freebsd:15:x86:32 is normal: we don't support FreeBSD 15.x on i386. pkgbase has been unofficially building some stable/{15,16}/ builds that have had no referencing material on https://www.freebsd.org/platforms/ or on https://pkg.freebsd.org/ for some time. https://pkg.freebsd.org/FreeBSD:15:i386/ is still populated. I assume such is deliberate for development testing or such reasons while avoiding messing up official distributions, not for release reasons. So I reported freebsd:15:x86:32 since the 2026-03-27 build is a recent and lack of updates is a change, just to make sure it was noticed. I've no means of knowing on my own if it was a deliberate stop of the build. freebsd:16:x86:32 is still being built with the other freebsd:16:* and is also not listed on https://www.freebsd.org/platforms/ or on https://pkg.freebsd.org/ . But it does not have a populated/accessible https://pkg.freebsd.org/FreeBSD:16:i386/ . I was not trying to object to the status either, just noting changes of recent status to freebsd:15:x86:32 . I do not use either one. > freebsd:15:armv7:32:el:eabi:hardfp and freebsd:16:powerpc:64:eb are > still Tier 2 so they ought to be built. Yep. The expected status for these two is clear, given https://www.freebsd.org/platforms/ and https://pkg.freebsd.org/ . > > Philip > > -- === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a4a9c0cc-39a2-407c-91c6-2533661822f7>