From owner-freebsd-current@freebsd.org Sun Jun 19 20:08:58 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCA6AA7966C; Sun, 19 Jun 2016 20:08:58 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id A2EF21A4E; Sun, 19 Jun 2016 20:08:58 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 4E04F162C; Sun, 19 Jun 2016 20:08:58 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Sun, 19 Jun 2016 20:08:57 +0000 From: Glen Barber To: Ivan Klymenko Cc: freebsd-snapshots@freebsd.org, freebsd-current@freebsd.org, FreeBSD Release Engineering Team Subject: Re: New FreeBSD snapshots available: head (20160617 r301975) Message-ID: <20160619200857.GI28666@FreeBSD.org> References: <20160618055811.GA35283@FreeBSD.org> <1466233842.650879797.mfv3fjy1@frv33.fwdcdn.com> <20160618140250.GB28666@FreeBSD.org> <20160618230722.GC28666@FreeBSD.org> <20160619104802.236aa92b@nonamehost.local> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cf0hFtnykp6aONGL" Content-Disposition: inline In-Reply-To: <20160619104802.236aa92b@nonamehost.local> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jun 2016 20:08:58 -0000 --cf0hFtnykp6aONGL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 19, 2016 at 10:48:02AM +0300, Ivan Klymenko wrote: > On Sat, 18 Jun 2016 23:07:22 +0000 > Glen Barber wrote: >=20 > > On Sat, Jun 18, 2016 at 02:02:50PM +0000, Glen Barber wrote: > > > On Sat, Jun 18, 2016 at 10:12:07AM +0300, fidaj wrote: =20 > > > > =3D=3D=3D Installation ISOs =3D=3D=3D > > > >=20 > > > > Installation images are available for: > > > >=20 > > > > o 11.0-ALPHA4 amd64 GENERIC > > > > o 11.0-ALPHA4 i386 GENERIC > > > > o 11.0-ALPHA4 powerpc GENERIC > > > > o 11.0-ALPHA4 powerpc64 GENERIC64 > > > > o 11.0-ALPHA4 sparc64 GENERIC > > > > o 11.0-ALPHA4 armv6 BANANAPI > > > > o 11.0-ALPHA4 armv6 BEAGLEBONE > > > > o 11.0-ALPHA4 armv6 CUBIEBOARD > > > > o 11.0-ALPHA4 armv6 CUBIEBOARD2 > > > > o 11.0-ALPHA4 armv6 CUBOX-HUMMINGBOARD > > > > o 11.0-ALPHA4 armv6 GUMSTIX > > > > o 11.0-ALPHA4 armv6 RPI-B > > > > o 11.0-ALPHA4 armv6 RPI2 > > > > o 11.0-ALPHA4 armv6 PANDABOARD > > > > o 11.0-ALPHA4 armv6 WANDBOARD > > > > o 11.0-ALPHA4 aarch64 GENERIC > > > > =20 > > > > Hello.=20 > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/11.0-ALPHA4/ > > > > not have manifest file.=20 > > >=20 > > > Huh. Yep, this is a problem. > > >=20 > > > Thank you for the report. I'll investigate what happened here. > > > =20 > >=20 > > This doesn't make sense. The MANIFEST exists on the build machine, > > and should have been copied as result of the distribution to the > > mirrors. > >=20 > > I don't understand how it did not make it to the mirrors. > >=20 > > So I know, how did you discover this? > >=20 > > I *do* see the MANIFEST for amd64, so something very bizarre happened > > here. > >=20 > > Glen > >=20 >=20 > It breaks my poudriere. > poudriere jail -c -v 11.0-ALPHA4 -a i386 -j 11_ALPHA4_i386 -m > url=3Dftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/11.0-ALPHA4/ This is even stranger than originally thought. The MANIFEST file *does* exist now, but I did not manually put it there. I don't think anyone else did either. So, I have no idea what happened, but thank you for this report. One more thing to double-check before sending these emails. Glen --cf0hFtnykp6aONGL Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXZvvZAAoJEAMUWKVHj+KTNDwP/j/2wmRecfr+pHBhnslHwPBJ UWDKqYmbEtfLthSvoWi+0cq1pV57E7xwSSPfknQfeINHfF4vtW3ynV+a9YAQGDU7 D1otPmjQPR5HIPyzxLT67A7JCuYdMemzZYzBe1zoMW/xxhV7LY4gE/21FQ/4jOcy FZ5cmiUQELBQJ+iyaEhdEHr14PaNaEcuECopVU30b9Kb6B2hHiX28+6IsPjSGF04 HY/oxCZkB8skeX1Z5EafcYUItCN6852kibEN7Zm+eyJhBX5M1sPXDMujFOHNVV4G KIcnx/AxbVz3kXDRxlOQoRMzAZjwACf/mXWNKAAsSctIwaVBkdwrEolJPmgF1oO8 IizL4A7bPrIG1w82I4M4tDjicqHz5xbBZj61eQaFjtfZo0sV6tBGBUWqOxdftIhq 2Tk6QlXGI32iw57U5/9thKMoVl4k8FkPDmBAGi2la7wG8/fqoY0uU/Q9TNJxngfQ U8AP25N488I6JLaPynS+Z5mNR0bAebBxEf/lrFMfY6fvW1MaNKnVAP1QYLo/58Aj 4dGtyRIHTLpE9uPUrC0KgE/yXYB6N+UVwk7wFaGxfXZLOcpK45FwpVUGkCSwq96Z pFBIYs00VJnovnMp4xmwjZje+MksAzI4ZMWS9G3I1OY8bFjIHoZYwjp8/F/XZGvm QlN/+5N5enQ5R1uFrIC7 =slIO -----END PGP SIGNATURE----- --cf0hFtnykp6aONGL--