Re: New FreeBSD snapshots available: main (20200903 c122cf32f2a)

On Thu, Sep 10, 2020 at 06:43:08PM +0200, Emmanuel Vadot wrote:
> On Thu, 10 Sep 2020 16:36:44 +0000
> Glen Barber <gjb_at_freebsd.org> 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 <gjb_at_freebsd.org> 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 <gjb_at_freebsd.org> 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).
> > 
> 
>  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.
> 

The PINEBOOK fetch failed, but after closer inspection, it looks like
a transient "Service not available" error.

But I think the build would have failed in this case if the fetch
succeeded, based on logs from other boards.

Glen