From owner-freebsd-current@freebsd.org Thu Sep 10 16:43:12 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 5CD9F3DD111; Thu, 10 Sep 2020 16:43:12 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (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 (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BnPp71xvtz4HS2; Thu, 10 Sep 2020 16:43:10 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from skull.home.blih.net (lfbn-idf2-1-288-247.w82-123.abo.wanadoo.fr [82.123.126.247]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 1184539c (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Thu, 10 Sep 2020 16:43:08 +0000 (UTC) Date: Thu, 10 Sep 2020 18:43:08 +0200 From: Emmanuel Vadot To: Glen Barber Cc: freebsd-current@freebsd.org, freebsd-git@freebsd.org Subject: Re: New FreeBSD snapshots available: main (20200903 c122cf32f2a) Message-Id: <20200910184308.68640d4c967cee15d661e55e@bidouilliste.com> In-Reply-To: <20200910163644.GQ61041@FreeBSD.org> References: <20200903150245.GS61041@FreeBSD.org> <20200903173354.33e97d36921d22506f58934b@bidouilliste.com> <20200903160051.GV61041@FreeBSD.org> <20200910182551.e863fb42c3c92223eb0ba09f@bidouilliste.com> <20200910163644.GQ61041@FreeBSD.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4BnPp71xvtz4HS2 X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.53 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mx]; FREEFALL_USER(0.00)[manu]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx:c]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.98)[-0.983]; TO_DN_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[]; NEURAL_HAM_MEDIUM(-1.01)[-1.014]; DKIM_TRACE(0.00)[bidouilliste.com:+]; MID_RHS_MATCH_FROM(0.00)[]; DMARC_POLICY_ALLOW(-0.50)[bidouilliste.com,none]; NEURAL_HAM_SHORT(-0.04)[-0.037]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current,freebsd-git] 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:43:12 -0000 On Thu, 10 Sep 2020 16:36:44 +0000 Glen Barber wrote: > 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: > > > > > On Thu, Sep 03, 2020 at 05:33:54PM +0200, Emmanuel Vadot wrote: > > > > > > > > Hello, > > > > > > > > On Thu, 3 Sep 2020 15:02:45 +0000 > > > > Glen Barber wrote: > > > > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > > > Hash: SHA256 > > > > > > > > > > New FreeBSD development branch installation ISOs and virtual machine > > > > > disk images have been uploaded to the FreeBSD Project mirrors. > > > > > > > > > > NOTE: These are the first snapshots built from the FreeBSD Git sources. > > > > > Also note: The armv6 and armv7 builds failed, and the cause is being > > > > > investigated. > > > > > > > > There is also no embbeded aarch64 image (pine64* rpi3 etc ...), do you > > > > have more info ? > > > > > > > > > > The ports tree failed to mount within the chroot directory. I think > > > I see why, and am testing a fix now. > > > > > > > Looks like there was a problem this week too. > > How can I help ? > > > > 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 > Which port commit and which board ? There haven't been a commit in the u-boot ports or rpi-firmware this a month now so I fails to understand without more info. -- Emmanuel Vadot