Date: Fri, 28 Jun 2024 20:26:45 -0700 From: Mark Millard <marklmi@yahoo.com> To: Colin Percival <cperciva@freebsd.org>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: New FreeBSD snapshots available: stable/14 (20240606 e77813f7e4a3) [ bad stable/14 info for 21 Jun 2024, empty snapshots/ISO-IMAGES/14.1/ ] Message-ID: <A044DF38-6082-44A3-9DF5-2B6115A2C06F@yahoo.com> In-Reply-To: <0D0E981F-6A25-4EBE-86BE-9C6E89894E4C@yahoo.com> References: <0D0E981F-6A25-4EBE-86BE-9C6E89894E4C@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 28, 2024, at 19:32, Mark Millard <marklmi@yahoo.com> wrote: > Looking at: > > https://lists.freebsd.org/archives/freebsd-snapshots/2024-June/000419.html > ( Date: Fri, 21 Jun 2024 00:42:00 UTC ) > > and at: > > https://lists.freebsd.org/archives/freebsd-snapshots/2024-June/000414.html > ( Date: Fri, 07 Jun 2024 00:37:56 UTC ) > > they both indicate: > > 0240606 e77813f7e4a3 > > Also: > > http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/14.1/ > > is empty. This prevents me from suggesting a test if a bug > report is reproducible from an official stable/14 snapshot > instead of just from someone's personal build of stable/14 > (for a RPi3B failure context). There are more issues but for stable/13 : while http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.3/ is populated with 2024-Jun-28 and 2024-Jun-20 materials, Fri, 21 Jun 2024's: https://lists.freebsd.org/archives/freebsd-snapshots/2024-June/000418.html says: 20240613 f9ac06af3b2d That is just like the earlier: https://lists.freebsd.org/archives/freebsd-snapshots/2024-June/000416.html that really was for that 13 Jun 2024 date. === Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A044DF38-6082-44A3-9DF5-2B6115A2C06F>