From owner-freebsd-amd64@freebsd.org  Mon May  2 14:34:24 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@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 1DEF6B288EF
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Mon,  2 May 2016 14:34: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 0EB8B1F82
 for <freebsd-amd64@FreeBSD.org>; Mon,  2 May 2016 14:34: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 u42EYLKV039275
 for <freebsd-amd64@FreeBSD.org>; Mon, 2 May 2016 14:34:23 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 209147] freebsd-update not working in 10.3-RELEASE
Date: Mon, 02 May 2016 14:34:21 +0000
X-Bugzilla-Reason: CC
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: lewismj@waioeka.com
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-6-Nbx1lDm59Z@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209147-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-209147-6@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-Mailman-Approved-At: Mon, 02 May 2016 14:52:33 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 May 2016 14:34:24 -0000

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

Michael Lewis <lewismj@waioeka.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lewismj@waioeka.com

--- Comment #2 from Michael Lewis <lewismj@waioeka.com> ---
I think the initial fix may have solved one issue, but now there is an issue
with version(s) that is affecting people. After the installing the patch, I
verified that I was on 10.3 p1 :

root@www:~ # freebsd-version
10.3-RELEASE-p1

However, when I re-run fetch:

"
freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 4 mirrors found.
Fetching metadata signature for 10.3-RELEASE from update5.freebsd.org... do=
ne.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 10.3-RELEASE-p0."

It is indicating 10.3 p0=20

See the later comments on this thread,
https://forums.freebsd.org/threads/56060/
Slightly more serious issue for people that have built their own kernels.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=