From owner-freebsd-stable@freebsd.org  Mon Oct  9 15:36:51 2017
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0379E335AF
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Mon,  9 Oct 2017 15:36:51 +0000 (UTC) (envelope-from gjb@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "freefall.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 57F857E64F;
 Mon,  9 Oct 2017 15:36:51 +0000 (UTC) (envelope-from gjb@FreeBSD.org)
Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by freefall.freebsd.org (Postfix) with ESMTPS id C0FA51F564;
 Mon,  9 Oct 2017 15:36:08 +0000 (UTC) (envelope-from gjb@FreeBSD.org)
Date: Mon, 9 Oct 2017 15:36:06 +0000
From: Glen Barber <gjb@FreeBSD.org>
To: Matthew Seaman <matthew@FreeBSD.org>
Cc: freebsd-stable@freebsd.org
Subject: Re: 10.4 release - is the binary update corrupt?
Message-ID: <20171009153606.GU49395@FreeBSD.org>
References: <B3C507A4-2955-465C-A355-C38B22569843@truespeed.com>
 <201710081227.35629.dr.klepp@gmx.at>
 <17d76f7d-4b9a-6a3e-ffae-ee3c2ffd27b0@FreeBSD.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature"; boundary="e9fMjeYs+GPci+mg"
Content-Disposition: inline
In-Reply-To: <17d76f7d-4b9a-6a3e-ffae-ee3c2ffd27b0@FreeBSD.org>
User-Agent: Mutt/1.8.2 (2017-04-18)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Oct 2017 15:36:51 -0000


--e9fMjeYs+GPci+mg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sun, Oct 08, 2017 at 12:04:25PM +0100, Matthew Seaman wrote:
> If you consistently get broken patch files from whichever of the update
> servers you get directed to, that probably means that update server
> needs some TLC.  Please do report that to clusteradm@...

s/clusteradm@/secteam@/

Glen


--e9fMjeYs+GPci+mg
Content-Type: application/pgp-signature; name="signature.asc"

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

iQIzBAEBCAAdFiEEVVuz/A7vpH93hEhKuWzd6q+LXtAFAlnbl2YACgkQuWzd6q+L
XtDubRAAkDl42U5JOMR05R0niYKrdK0ki0ZQST8Z/JIwSNu7g+cDdEqL5hLcTK0/
Rv1vyxThgz/TR9x3OwT5PtQKazWLgMUBK0HW4oKWffxKRpNeS3pfAwtbVEgMhoFU
jeUNXxi0MPV1v2UfOHkLQ27C11IC6NMWztps39sWi+ZOijDUCluL1W1qrNDCxJGJ
Xn4nQsTdsD1jlnKCMGeKmgiZFhPK2DJRNlgC+ZU8CspxSyg1vfhFVgbHuhYyIHG4
18HD+k7xMoWMMt5vcrjnkmoh1oL/pS4CteNclw5VtNJO8Bs9UhnwKRzhnisa8d1w
BuO2den0Mz+Ks9yNbdrBU/ZXMHGrZtkJ/AD7uMlZFAZ/Qnu7GVoQdMTp9kIsGdLg
KbCvsxs6ks1UbH0ClK615M4MOVht33gI3joeOKmxdNlRaF7TvlASvLv/e0X+S7x7
ZVpsaUrNHJY4wOVD707nY+i09nV4vph+e75dUDE7DJU1i55TGRtuXHL60gfnngyR
W1C1s9hRIK8nPH9/mccSYQLA0J5/cF2Kq+oFltKFA+mchsK2vSppwyJ1SyZC0d7O
fAWw/xgwJ/ZPUC7kWWFsyIjKJgrktkhbn51V/9tC6SCvUhGmtKp2GeStV9XeGcAp
0y+Tbpiby2+YeXjh122bfWbHj62RsN96Cs5wqnEqeJAcJ1wmE5g=
=mPDk
-----END PGP SIGNATURE-----

--e9fMjeYs+GPci+mg--