Date: Mon, 5 Jan 2026 17:08:40 -0800 From: Mark Millard <marklmi@yahoo.com> To: freebsd-pkgbase@freebsd.org Subject: Re: pkgbase updates for FreeBSD:14:x86:32 base_* and kmods_* stopped after 2025-12-11 00:00:04Z Message-ID: <bfe511f1-0c3c-4302-9b85-2bb3bf02a2a1@yahoo.com> In-Reply-To: <5E6459AC-56A0-4E28-A2D4-E5F9A4DF05E5@yahoo.com>
index | next in thread | previous in thread | raw e-mail
On 12/31/25 17:54, Mark Millard wrote: > https://people.freebsd.org/~dbaio/pkg-master-report.html > > does not indicate anything after 2025-12-11 00:00:04Z for > FreeBSD:14:x86:32's base_* and kmods_* , not even a > missing status. > > === > Mark Millard > marklmi at yahoo.com > > > https://pkg.freebsd.org/FreeBSD:14:i386/?C=M&O=D agrees. Does anyone know if the above is deliberate and so report if it is vs. is not? I'll note that the 2025-Dec-16 Security updates: FreeBSD Security Advisory FreeBSD-SA-25:11.ipfw FreeBSD-SA-25:12.rtsold are apparently not available from pkgbase for FreeBSD:14:i386 for base_{latest,release_3} . Admittedly, FreeBSD:14:i386 is tier 2. But it is getting new snapshots for 14.3-STABLE, for example, as listed in: https://lists.freebsd.org/archives/freebsd-snapshots/2026-January/000691.html It could be that the intent is for pkgbase FreeBSD:14:i386 systems to have: # pkg unregister -fg FreeBSD-\* done as a means of disabling pkgbase and then having freebsd-update style updating used instead. But, if so, I've not seen a notice about such. -- === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bfe511f1-0c3c-4302-9b85-2bb3bf02a2a1>