From owner-freebsd-stable@freebsd.org Sun Oct 9 22:56:11 2016 Return-Path: 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 C1DCEC0B414 for ; Sun, 9 Oct 2016 22:56:11 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [IPv6:2001:418:3fd::f7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7DC05E61 for ; Sun, 9 Oct 2016 22:56:11 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [10.100.0.31] (haymarket.m5p.com [10.100.0.31]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id u99Mu30S079727; Sun, 9 Oct 2016 18:56:08 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Subject: Re: Failing to upgrade from 10.1-RELEASE to 10.3-STABLE To: Kurt Jaeger References: <5942b107-349b-4a97-7f26-e24ea09079bb@m5p.com> <20161009195746.GC4560@home.opsec.eu> Cc: FreeBSD Stable Mailing List From: George Mitchell Message-ID: Date: Sun, 9 Oct 2016 18:56:03 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161009195746.GC4560@home.opsec.eu> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [10.100.0.247]); Sun, 09 Oct 2016 18:56:09 -0400 (EDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Oct 2016 22:56:11 -0000 On 10/09/16 15:57, Kurt Jaeger wrote: > Hi! > >> What am I doing wrong? (I get the same failure attempting to upgrade >> to 10.1-RELEASE and 10.2-RELEASE.) -- George > > Ah, one thing: > > Please do update to the latest 10.1-REL patch level, first. > After upgrading to the latest 10.1-RELEASE: I can update to 10.3-RELEASE, and that will probably do for now. Should it have worked to update from 10.1-RELEASE to 10.3-STABLE directly? If I decide to upgrade from 10.3-RELEASE to 10.3-STABLE later on, should I expect that to work? -- George