From owner-freebsd-bugs@freebsd.org  Thu May  5 22:01:24 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 55AA5B2F842
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu,  5 May 2016 22:01:24 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 46A251289
 for <freebsd-bugs@FreeBSD.org>; Thu,  5 May 2016 22:01:24 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u45M1GM3021543
 for <freebsd-bugs@FreeBSD.org>; Thu, 5 May 2016 22:01:24 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 209147] freebsd-update not working in 10.3-RELEASE
Date: Thu, 05 May 2016 22:01:16 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: portmaster@bsdforge.com
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-209147-8-N9BSj9oNqk@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209147-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-209147-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 May 2016 22:01:24 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209147

--- Comment #12 from Chris Hutchinson <portmaster@bsdforge.com> ---
(In reply to Adam Weinberger from comment #11)
> (In reply to gkontos from comment #10)
>=20
> Yes. Folks, you can stop pasting in your error message, everyone gets the
> same error.
>=20
> See
> https://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D45930+0+current/freebsd-
> security for confirmation.
>=20
> There is clearly a problem with amd64 updates not being built. The soluti=
on
> will come from a combination of the security team and the server admin te=
am.
> I guarantee you both teams are aware of the problem.

Yet those in the know, felt they couldn't afford to squander the 120 seconds
required to inform the FreeBSD Community -- those whom use, and depend on
FreeBSD. About their concerns -- especially in light of the recent SA?

It's been better than 2 days, after all. :(

--=20
You are receiving this mail because:
You are the assignee for the bug.=