From owner-freebsd-current@freebsd.org Thu Sep 10 16:36:47 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 55DE03DCC8F; Thu, 10 Sep 2020 16:36:47 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BnPfl1fFsz4H5R; Thu, 10 Sep 2020 16:36:47 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id BB61EF8C1; Thu, 10 Sep 2020 16:36:46 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Thu, 10 Sep 2020 16:36:44 +0000 From: Glen Barber To: Emmanuel Vadot Cc: freebsd-current@freebsd.org, freebsd-git@freebsd.org Subject: Re: New FreeBSD snapshots available: main (20200903 c122cf32f2a) Message-ID: <20200910163644.GQ61041@FreeBSD.org> References: <20200903150245.GS61041@FreeBSD.org> <20200903173354.33e97d36921d22506f58934b@bidouilliste.com> <20200903160051.GV61041@FreeBSD.org> <20200910182551.e863fb42c3c92223eb0ba09f@bidouilliste.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9D+F+si/X/ZTxnYN" Content-Disposition: inline In-Reply-To: <20200910182551.e863fb42c3c92223eb0ba09f@bidouilliste.com> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1599755807; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=L3SWsANxS86Bbqb0UfULdPRzpxqURhCd2xDeFsPjue0=; b=E1zs4LJhk6rtBZouqF4l9lCwO5+/RBQdppJDyr7s/J6E9L5oCgNH38qEW631hiTlwq5B2C vlEzQM+Pxe8ODBOxwfwbiWyJF8fjJh4M0kL8enwwdtI9YcYvKJ+c9K3Dj3V1yJ1+P5Y8Nt 9b0hoS5NJPgLAgxKq7TiFSrLIKV9rz3knCXMQyIXTyj9cFxjSiswoLkoe2xZH1Y5Jq4gpA 8myht6yDkHhj4oz1qF2mCk4GdyQh3+6jsNmZQNV/NBTY5r45aswuoO4PE0hie5UF8QO0sV Rhj+iRN3Gx5JBbEpMpuSdPmKi2CzDq5q0VR5VXlZ2txohVPfuINeOQ3HdQI0Dg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1599755807; a=rsa-sha256; cv=none; b=ZKDiVs+PiwC43G+4NmaWwgufdXSrsHGMglurAvAQQ6auEzDjsuyLVYbwBDQCQ1PhBStqIW 6Ed+Ia1V/6oWgf1cdewV5STJKBBazYpgpXshQBm0QD700SZ3gtr+aAMTNH6+se3YxVI3Ta JGIxfaKVv9sj953D+BDiaYplvbTT7VUXfDQgJgUtQJm0Fu4RP1BPM0X5qWoiwtmKlikALK aoPMuhGxaVVDU1datzEYRlYC8PAu3uv9Bbfpe5hWlZq75+xP3IfF9Dv+lk35rFYIujvi0Z ASf1YsnAm8/mteHvrskMp7hvXULgZiVdjYlnQzFj6/HDGi9ACk8e8IVhTZCvHg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 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: Thu, 10 Sep 2020 16:36:47 -0000 --9D+F+si/X/ZTxnYN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 10, 2020 at 06:25:51PM +0200, Emmanuel Vadot wrote: > On Thu, 3 Sep 2020 16:00:51 +0000 > Glen Barber wrote: >=20 > > On Thu, Sep 03, 2020 at 05:33:54PM +0200, Emmanuel Vadot wrote: > > >=20 > > > Hello, > > >=20 > > > On Thu, 3 Sep 2020 15:02:45 +0000 > > > Glen Barber wrote: > > >=20 > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > > Hash: SHA256 > > > >=20 > > > > New FreeBSD development branch installation ISOs and virtual machine > > > > disk images have been uploaded to the FreeBSD Project mirrors. > > > >=20 > > > > NOTE: These are the first snapshots built from the FreeBSD Git sour= ces. > > > > Also note: The armv6 and armv7 builds failed, and the cause is being > > > > investigated. > > >=20 > > > There is also no embbeded aarch64 image (pine64* rpi3 etc ...), do y= ou > > > have more info ? > > >=20 > >=20 > > The ports tree failed to mount within the chroot directory. I think > > I see why, and am testing a fix now. > >=20 >=20 > Looks like there was a problem this week too. > How can I help ? >=20 Nothing really. I know what the problem is. The ports tree mounting issue had been fixed, but two things: 1) the u-boot port failed to fetch for at least one of the boards; 2) something got screwed up in the environment, due to path changes and how the git checkout structure is set up. The first is basically a timing issue with a ports commit and distribution of the distfiles. The second I am working on fixing now, which should be Relatively Easy(tm). Glen --9D+F+si/X/ZTxnYN Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAl9aVhwACgkQAxRYpUeP 4pPcsg/8CjqslwSun8rXwysj/YlvCNLozxNQxULppNG4BlbjWKyvaSwJqyzWdlRz w3eyYflvVHcp20fjUFLX4XIPHsE/zT6bj8fyOYukdY4kYjSLbrN4I4SQxLukPyIU kTt3NQcT9m5nvNsgSYXl7JDqYjORutnnChrggVO3czk8JDtUvK2K68PDFXvzRfIQ 6BPODFULztocYOQbRJoxHcbPdoxOrgmDmNbeo10p7ZXcNgbMqKh7exWiH6G+OpSW VIY1Wttb3R51hC4++YkGyRkHW+FKTlHcouM9FMCyPet9EwajOs5CCRqitMqFbjyy i9Dq2USTkHy0+FUx55Uade+vO5GF+HymmVZ7NTVc4Nhs4E3DYRgmAbHn5UIyA9TU ADAoxb9BfLF2sgctd43lhTiPfZX6BOxdCOOz0B1Y0+4cD5fr+Fx0xc5qClO83S11 lDEnQSb+pU3c+jfR23ce3nW+G90aGlb6D9eC30bJ3gNfOIsQVW+47o++arj/Gltf VtlDKWiLS5a6H5TP7y4SuSXdDBgtNHl2GrXv1WMw6ZJUsAh0GWl2BF7FcBS0eA5S xFrG9VeDLQg0DSdDmBAPfePaJ6dgD3aV8patHnDPhfLIeY7iJw67L4SuBM9+qRnZ WYqfSWtRYDvQ2qmbB4JNNQYbHjs1Wjw+QF+J2hSLhspp0hK7aU0= =wver -----END PGP SIGNATURE----- --9D+F+si/X/ZTxnYN--