Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 30 Jan 2021 16:08:49 +0000
From:      Glen Barber <gjb@freebsd.org>
To:        Emmanuel Vadot <manu@bidouilliste.com>
Cc:        src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org
Subject:   Re: git: 7ae27c2d6c4f - main - newvers.sh: set to ALPHA1 as part of the 13.0 cycle
Message-ID:  <20210130160849.GV77557@FreeBSD.org>
In-Reply-To: <20210130143606.8076a6b3f566d6aaf67d0fec@bidouilliste.com>
References:  <202101140002.10E0211m024446@gitrepo.freebsd.org> <20210129160639.bfdabc0df278ec8ee100d8e2@bidouilliste.com> <20210129160708.GR77557@FreeBSD.org> <20210129172829.a5508a3f415baf47acd2fe8c@bidouilliste.com> <20210129164025.GS77557@FreeBSD.org> <20210129210814.e2dba591fe1d309268673a29@bidouilliste.com> <20210129201845.GU77557@FreeBSD.org> <20210130143606.8076a6b3f566d6aaf67d0fec@bidouilliste.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--MiMBASdxvnz+XAiL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jan 30, 2021 at 02:36:06PM +0100, Emmanuel Vadot wrote:
> On Fri, 29 Jan 2021 20:18:45 +0000
> Glen Barber <gjb@freebsd.org> wrote:
>=20
> > On Fri, Jan 29, 2021 at 09:08:14PM +0100, Emmanuel Vadot wrote:
> > > On Fri, 29 Jan 2021 16:40:25 +0000
> > > Glen Barber <gjb@freebsd.org> wrote:
> > >=20
> > > > On Fri, Jan 29, 2021 at 05:28:29PM +0100, Emmanuel Vadot wrote:
> > > > > On Fri, 29 Jan 2021 16:07:08 +0000
> > > > > Glen Barber <gjb@freebsd.org> wrote:
> > > > >=20
> > > > > > On Fri, Jan 29, 2021 at 04:06:39PM +0100, Emmanuel Vadot wrote:
> > > > > > >=20
> > > > > > >  Hi Glen,
> > > > > > >=20
> > > > > > > On Thu, 14 Jan 2021 00:02:01 GMT
> > > > > > > Glen Barber <gjb@FreeBSD.org> wrote:
> > > > > > >=20
> > > > > > > > The branch main has been updated by gjb:
> > > > > > > >=20
> > > > > > > > URL: https://cgit.FreeBSD.org/src/commit/?id=3D7ae27c2d6c4f=
e4f21e1219bb5d8a37cfc932337b
> > > > > > > >=20
> > > > > > > > commit 7ae27c2d6c4fe4f21e1219bb5d8a37cfc932337b
> > > > > > > > Author:     Glen Barber <gjb@FreeBSD.org>
> > > > > > > > AuthorDate: 2021-01-14 00:01:30 +0000
> > > > > > > > Commit:     Glen Barber <gjb@FreeBSD.org>
> > > > > > > > CommitDate: 2021-01-14 00:01:30 +0000
> > > > > > > >=20
> > > > > > > >     newvers.sh: set to ALPHA1 as part of the 13.0 cycle
> > > > > > > >    =20
> > > > > > > >     Sponsored by:   Rubicon Communications, LLC (netgate.co=
m)
> > > > > > > > ---
> > > > > > > >  sys/conf/newvers.sh | 2 +-
> > > > > > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > > > > >=20
> > > > > > > > diff --git a/sys/conf/newvers.sh b/sys/conf/newvers.sh
> > > > > > > > index b8667844210b..2a0ace45f2f6 100644
> > > > > > > > --- a/sys/conf/newvers.sh
> > > > > > > > +++ b/sys/conf/newvers.sh
> > > > > > > > @@ -54,7 +54,7 @@
> > > > > > > > =20
> > > > > > > >  TYPE=3D"FreeBSD"
> > > > > > > >  REVISION=3D"13.0"
> > > > > > > > -BRANCH=3D"CURRENT"
> > > > > > > > +BRANCH=3D"ALPHA1"
> > > > > > > >  if [ -n "${BRANCH_OVERRIDE}" ]; then
> > > > > > > >  	BRANCH=3D${BRANCH_OVERRIDE}
> > > > > > > >  fi
> > > > > > >=20
> > > > > > >  So since ALPHA1 we do not have new GCP images.
> > > > > > >  Is that intended ?
> > > > > > >=20
> > > > > >=20
> > > > > > I see 13.0-ALPHA3 GCE images:
> > > > > >=20
> > > > > > NAME                       PROJECT                FAMILY       =
 DEPRECATED  STATUS
> > > > > > freebsd-13-0-alpha3-amd64  freebsd-org-cloud-dev  freebsd-13-0 =
             READY
> > > > >=20
> > > > >  Ah sorry, no idea how I missed it.
> > > > >  Anyhow when I try to use it in cirrus-ci I have :
> > > > > Failed to start an instance: INVALID_ARGUMENT: Not Found
> > > > >=20
> > > > >  Tested with the full name freebsd-13-0-alpha3-amd64 and the smal=
l name
> > > > > freebsd-13-0. Any tips on that ?
> > > > >=20
> > > >=20
> > > > Hmm, I am not sure.  I do not see any errors (i.e., from installing
> > > > ports or the like) in the log.
> > > >=20
> > > > > > >  Also there is no 14.0 snapshot while there was some new 11/1=
2 images
> > > > > > > and no 13-ALPHA3 too it seems.
> > > > > >=20
> > > > > > Right.  We likely will not have 14-CURRENT builds until releng/=
13.0 is
> > > > > > branched.  13.0-ALPHA3 was built a day later so it is ready for=
 Friday,
> > > > > > the same as is done for BETA* and RC* builds.
> > > > >=20
> > > > >  Ok, I indeed see some alpha3 images on the ftp but I don't see a=
ny for
> > > > > armv7 or aarch64, was there any problems ?
> > > > >=20
> > > >=20
> > > > Yes, all arm builds failed because of a problem in the ports tree.
> > > >=20
> > > > -------------------------- begin quoted text ----------------------=
-----
> > > > Installing gettext-tools-0.21...
> > > > =3D=3D=3D>   p5-Locale-gettext-1.07 depends on executable: msgfmt -=
 found
> > > > =3D=3D=3D>   Returning to build of p5-Locale-gettext-1.07
> > > > =3D=3D=3D>   p5-Locale-gettext-1.07 depends on package: perl5>=3D5.=
32.r0<5.33 - found
> > > > =3D=3D=3D>   p5-Locale-gettext-1.07 depends on shared library: libi=
ntl.so - found (/usr/local/lib/libintl.so)
> > > > =3D=3D=3D>  Configuring for p5-Locale-gettext-1.07
> > > > env: /usr/local/bin/perl5.32.1: No such file or directory
> > > > *** Error code 127
> > > > --------------------------- end quoted text -----------------------=
-----
> > > >=20
> > > > Glen
> > > >=20
> > >=20
> > >  Mhm ok, is there a place where we can see those errors or at least be
> > > aware of them ?
> > >=20
> >=20
> > Not exactly.  I am happy to make the logs public on an as-needed basis,
> > but they contain environment information that potentially contains
> > sensitive data (i.e., API keys and such).  When there is a specific
> > cause to a failure, I do ping those involved in the cause (i.e., a port
> > build failure, or a userland/kernel failure).
> >=20
> > In this case, the error is uninteresting.  The failure is exactly as
> > what is included above.  The odd thing though, is
> > /usr/local/bin/perl5.32.0 is installed in the chroot(8), not
> > /usr/local/bin/perl5.32.1, but I have not yet had luck tracking down
> > exactly why.
> >=20
> > Glen
> >=20
>=20
>  Could it be a latest vs quarterly problem ?

No, the ports are built from the ports tree.

>  head have 5.32.1 and 2021Q1 was only updated on 25th of January to
> this version.

This is where I am confused, to be honest.  The older binary is
installed, but the ports version of the checkout has 5.32.1.

>  When was the build started ?
>=20

00:00 UTC Friday.

>  Also could we have some retry when such failure happens ? (this is
> especially important in those alpha/beta/rc phase).
>=20

Well, in this case, a retry would not help.  I am still investigating
how the older version of perl5.32 got installed in the first place.
This has not happened before.

Glen


--MiMBASdxvnz+XAiL
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAmAVhI0ACgkQAxRYpUeP
4pNsDw//dEKUVdI0vqoPbb9nLUS3hU1RRujCCY8M8k+g+P9JHxm/TG21uGTBPWf5
ybKwQjIPALT5x+mlgBmmbFifevTONbGU/Jwptkc1Q8C2dRgSbJEX5Gx8HNL13/WZ
ckDN4kRW81BZMXWoo2P+KmEpTyeJA+pZ9CXrSAFaKVmxpw/HJV/nWv2leLSF/DuO
ceeSubgTRT9g+lJfuIJKTaUYs57X/OrkhFbQlrntwePyfKnKXArzuXX95WmMti5x
IzB1xEzWsB1UGy3DzGlUpTCpW8rBYgk/m8Jx/Fu7frKXp44UZH5qQXo/ahn9OTJq
jiXT6S/cHri/og6NxJ0uNQ5DKZG08+heCeuEyttjcekJh25CatomBnyjQfQvTA7M
9SIxpHHo357g6R95Mu5Un4a0QIjaccHdBPoMrQjjARNY+anmVw55LXVChAAMowME
dPWN0V11rYX0aICfEICetmlmhaO5n6FoIvzvUsR5OZTsa+G7XIOmWSYfgHy18tP6
TuhwEYWWUKgS6jmSn3+dQ+eV+VbPc7BrTcEvlKtZSB+axocKDJDul0En4z1AAa2N
GcVcL+W77nkRXwt4qEX/LO/q+Dq+hFODFvhFM98IhcI87JsV6AO9OTm0ZJXbGdcu
VdGNNlEbNlUzugHZ+lTrZS0mj07H+J4M0hOmiZCdQknJYM6zDqk=
=8Zdp
-----END PGP SIGNATURE-----

--MiMBASdxvnz+XAiL--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210130160849.GV77557>