From owner-freebsd-bugs@FreeBSD.ORG  Wed Feb  4 18:08:56 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id BDD1DBD2
 for <freebsd-bugs@FreeBSD.org>; Wed,  4 Feb 2015 18:08:56 +0000 (UTC)
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 A54BFD3B
 for <freebsd-bugs@FreeBSD.org>; Wed,  4 Feb 2015 18:08:56 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t14I8uFR029776
 for <freebsd-bugs@FreeBSD.org>; Wed, 4 Feb 2015 18:08:56 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 195484] freebsd-update(8) fails to update 9.2-RELEASE to
 10.1-RELEASE
Date: Wed, 04 Feb 2015 18:08:56 +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: 9.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: matt@tnpi.net
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-195484-8-bVMLFG2XkG@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-195484-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-195484-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2015 18:08:56 -0000

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

matt@tnpi.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |matt@tnpi.net

--- Comment #1 from matt@tnpi.net ---
This bug also affects systems upgrading from 9.3-RELEASE -> 10.1-RELEASE. I
experienced this at great inconvenience (servers are a continent away) on three
systems that I upgraded.

Upgrade history: 9.2 -> 9.3 on Aug 13, 2014. 9.1 -> 9.2 on Jan 19, 2014. 9.0 ->
9.1 on Feb 15, 2013. 8.2 -> 9.0 on Aug 7, 2012.

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