Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Aug 2016 21:30:10 +0000
From:      Glen Barber <gjb@FreeBSD.org>
To:        Jan Beich <jbeich@vfemail.net>
Cc:        freebsd-current@FreeBSD.org, FreeBSD Release Engineering Team <re@FreeBSD.org>
Subject:   Re: FreeBSD 11.0-RC1 Now Available
Message-ID:  <20160813213010.GC11079@FreeBSD.org>
In-Reply-To: <20160813204752.GB11079@FreeBSD.org>
References:  <20160813013056.GS11079@FreeBSD.org> <popc-fu6m-wny@vfemail.net> <20160813204752.GB11079@FreeBSD.org>

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

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

On Sat, Aug 13, 2016 at 08:47:52PM +0000, Glen Barber wrote:
> On Sat, Aug 13, 2016 at 07:35:45PM +0200, Jan Beich wrote:
> > Glen Barber <gjb@FreeBSD.org> writes:
> >=20
> > > The first RC build of the 11.0-RELEASE release cycle is now available.
> > >
> > > Installation images are available for:
> > >
> > > o 11.0-RC1 amd64 GENERIC
> > > o 11.0-RC1 i386 GENERIC
> > > o 11.0-RC1 powerpc GENERIC
> > > o 11.0-RC1 powerpc64 GENERIC64
> > > o 11.0-RC1 sparc64 GENERIC
> > > o 11.0-RC1 armv6 BANANAPI
> > > o 11.0-RC1 armv6 BEAGLEBONE
> > > o 11.0-RC1 armv6 CUBIEBOARD
> > > o 11.0-RC1 armv6 CUBIEBOARD2
> > > o 11.0-RC1 armv6 CUBOX-HUMMINGBOARD
> > > o 11.0-RC1 armv6 GUMSTIX
> > > o 11.0-RC1 armv6 RPI-B
> > > o 11.0-RC1 armv6 RPI2
> > > o 11.0-RC1 armv6 PANDABOARD
> > > o 11.0-RC1 armv6 WANDBOARD
> > > o 11.0-RC1 aarch64 GENERIC
> >=20
> > What about granular sets? sparc64 is N/A while amd64 is missing
> > lib32.txz, src.txz, ports.txz, tests.txz. Regressed since 11.0-BETA4.
> > I've waited a day to see if the issue would disappear after mirrors
> > catch up but no joy, even via Tor.
> >=20
> > [...]
>=20
> Thanks for letting us know.  This isn't an re@ issue, it's an admins@
> issue, and we thought this was fixed.  Give me a bit to investigate.
>=20

I forced the mirrors to re-sync from the master.  My initial test (amd64
lib32.txz) seems to have worked.  We need to investigate this further,
as the issues we've seen with this in the past should have been fixed.

Give it about an hour or so to be sure, but I think everything will be
fine this time.

Sorry about that, and thank you again for bringing it to our attention.

Glen


--ZilngB4jitXEoqOO
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXr5FiAAoJEAMUWKVHj+KTbVQP/1hgVNVVTPrCPoHKZUH4e3GF
piJzR+Za2leN+ZKpb567qTqcmlyWOGg2eR57A2udKvtbnF0FdvNWQ3ZJNQK9T6yg
N5+zi++bO/+jPE0rsLe3f8QrROeisTkzF0VtTsyQ8PW8NS0WUBBiAnqbpIU4GLXu
Fc32jEn6DD/A9JmkrdGgInr4E2rYayvlWz9m89TPRr90dJ6cBEs/Jl6O0Ly5JoM4
p1NbdDMsnqtYnd5KIQAGKEH1yvQKnGIaoUMQdRqSV0cjL08X0pcJpthlTg/b5wsb
U/qI/khrpdSQ4EaFSTo8PaQmKHAYbBWPHURhd5c1lesdvEz2Gz3f85S4wZAf1zXS
GyV1pk2wGSEgx7dZ4DzvAIjGZpz8eBvaUwO5ojKorAbLWl8o83v2pGyJ37qzzLbT
jnmTj7emC55PSJRanji43gZT9qAP2jAd9YfnvNA8FnsopeSpPxdRKhGGQ+//EUGC
4rVH0rNHi5JXNA+OkSV/q4Emp0h5HPa2IxZUAUnKsyaant73PfNShyAw3kxKO55h
Z6pBUpqhlkxOlcrwwYec+Nz7vhMxG3XhKApk8aV4IBVPgRwuShKWA6G/D10Gdb3x
fYaFejf6asOQnroRGfEtIGBc6noGhP7aNMGSnKCgII2emyb6He1ArQe5C6roLFOp
mTz63GEHWUfM5GON7pa+
=FzTG
-----END PGP SIGNATURE-----

--ZilngB4jitXEoqOO--



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