From owner-freebsd-bugs@freebsd.org  Thu May  5 01:26:57 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 ED917B2CD6C
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu,  5 May 2016 01:26:57 +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 DE3EE186A
 for <freebsd-bugs@FreeBSD.org>; Thu,  5 May 2016 01:26:57 +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 u451Qvst050112
 for <freebsd-bugs@FreeBSD.org>; Thu, 5 May 2016 01:26:57 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 01:26:58 +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: adamw@FreeBSD.org
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-209147-8-iQ4oKZ2c6i@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 01:26:58 -0000

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

Adam Weinberger <adamw@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adamw@FreeBSD.org

--- Comment #6 from Adam Weinberger <adamw@FreeBSD.org> ---
(In reply to Masachika ISHIZUKA from comment #5)

Jason, Masachika is correct. The update servers are serving p2 for i386, but
have been stuck at p0 ever since 10.3-RELEASE.

You can verify this with

    for arch in i386 amd64; do \
    URLBASE=3D"http://update.freebsd.org/10.3-RELEASE/$arch"; \
    fetch -qo- $URLBASE/latest.ssl \
        | openssl rsautl -pubin -inkey \
            =3D( fetch -qo- $URLBASE/pub.ssl ) -verify; \
    done

freebsd-update|i386|10.3-RELEASE|2|9292852427c7151fbe106b93c4e67be5fcfafc00=
9c4e17ca0cbfca037c8a6b97|1525132800

freebsd-update|amd64|10.3-RELEASE|0|8797efb5915e47a0a9bbcd69e1389d010a8041f=
8f1ca2c0dcfc0c4e4eca3fa8c|1525132800

So, for whatever reason, the i386 updates are being built and published, but
the amd64 updates haven't been yet.

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