From owner-freebsd-questions@FreeBSD.ORG  Wed Oct 22 01:14:30 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CEF74C2C
 for <freebsd-questions@freebsd.org>; Wed, 22 Oct 2014 01:14:30 +0000 (UTC)
Received: from pandora.au.calorieking.net (114.179.70.115.static.exetel.com.au
 [115.70.179.114])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 72B6AAA9
 for <freebsd-questions@freebsd.org>; Wed, 22 Oct 2014 01:14:29 +0000 (UTC)
Received: from pandora.au.calorieking.net (localhost [127.0.0.1])
 by pandora.au.calorieking.net (Postfix) with ESMTP id 32F456
 for <freebsd-questions@freebsd.org>; Wed, 22 Oct 2014 09:07:53 +0800 (WST)
X-Virus-Scanned: amavisd-new at calorieking.com
Received: from pandora.au.calorieking.net ([127.0.0.1])
 by pandora.au.calorieking.net (mail.au.calorieking.net [127.0.0.1])
 (amavisd-new, port 10024)
 with ESMTP id 8s1fyBA8kAWt for <freebsd-questions@freebsd.org>;
 Wed, 22 Oct 2014 09:07:52 +0800 (WST)
Received: from egeria.internal (egeria.internal [192.168.2.111])
 by pandora.au.calorieking.net (Postfix) with ESMTPSA id DA4C94
 for <freebsd-questions@freebsd.org>; Wed, 22 Oct 2014 09:07:52 +0800 (WST)
Message-ID: <54470368.5050708@calorieking.com>
Date: Wed, 22 Oct 2014 09:07:52 +0800
From: Gregory Orange <gregory.orange@calorieking.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: freebsd-questions@freebsd.org
Subject: Re: freebsd-update - upgrade from 9.1-RELEASE to 9.3-RELEASE -
 requries all ports rebuilt?
References: <517BECC5D916EAC560741895@Mail-PC.tdx.co.uk>
 <alpine.BSF.2.11.1410211651070.4966@wonkity.com>
In-Reply-To: <alpine.BSF.2.11.1410211651070.4966@wonkity.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Oct 2014 01:14:30 -0000

On 22/10/14 06:52, Warren Block wrote:> On Tue, 21 Oct 2014, Karl 
Pielorz wrote:
 >> I just walked a system from 9.1-RELEASE to 9.3-RELEASE using
 >> 'freebsd-update -r 9.3-RELEASE upgrade'
 >>
 > Normally, it should not be necessary to rebuild ports for a minor
 > version upgrade.  I don't use freebsd-update, but it might be suggesting
 > the safest way to do it, not necessarily that ports will not work
 > afterward.

Upon advice that we could probably ignore the warning, we've had no 
trouble after upgrading 8.3-RELEASE to 8.4-RELEASE. We've slowly rebuilt 
ports anyway, but that's more because of newer versions available than 
because of this warning.