From owner-freebsd-ports@FreeBSD.ORG  Sat Oct 11 13:54:55 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@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 D304CF44
 for <freebsd-ports@freebsd.org>; Sat, 11 Oct 2014 13:54:55 +0000 (UTC)
Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201])
 by mx1.freebsd.org (Postfix) with ESMTP id BC5C1A9B
 for <freebsd-ports@freebsd.org>; Sat, 11 Oct 2014 13:54:55 +0000 (UTC)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from isux.com (firewall.isux.com [213.165.190.213])
 by hades.sorbs.net
 (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013))
 with ESMTPSA id <0NDA00D2E9IEUT00@hades.sorbs.net> for
 freebsd-ports@freebsd.org; Sat, 11 Oct 2014 06:59:03 -0700 (PDT)
Message-id: <543936AC.7030102@sorbs.net>
Date: Sat, 11 Oct 2014 15:54:52 +0200
From: Michelle Sullivan <michelle@sorbs.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24)
 Gecko/20100301 SeaMonkey/1.1.19
To: freebsd-ports@dan.me.uk
Subject: Re: PKG not quite ready for prime time
References: <sl4g3adpms8lkd2rr38n3666et8eptsp9i@4ax.com>
 <543817AA.8080305@gmx.de> <he6g3apojoln19fd9d8gr2rs0koq3a6940@4ax.com>
 <54381E16.9070609@FreeBSD.org> <1a8g3athvnun67c4kljhjtsjjlc30116j1@4ax.com>
 <543837CF.9070607@FreeBSD.org> <e79i3ale313b5iqvuql3ns08m86hmtonoa@4ax.com>
 <543931DB.7070205@sorbs.net> <54393381.1000204@dan.me.uk>
In-reply-to: <54393381.1000204@dan.me.uk>
Cc: freebsd-ports@freebsd.org
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Oct 2014 13:54:55 -0000

Daniel Austin via freebsd-ports wrote:
> Hi,
>
> On 11/10/2014 14:34, Michelle Sullivan wrote:
>> scratch65535@att.net wrote:
>>>> You are missing this:
>>>> https://www.freebsd.org/security/advisories/FreeBSD-EN-14:03.pkg.asc
>>>>
>>>> freebsd-update can provide it.
>>>>
>>>
>>> Thank you for the pointer.
>>>
>>> What puzzles me is why the problem wasn't fixed for o/s versions
>>> prior to 10.0 since it was being made mandatory for those
>>> versions.   That doesn't seem like good practice.
>>>
>> We have a winner! <3\
>
> I've upgraded countless machines from 9.x to 10.x using freebsd-update
> and have never come across this issue.  (have done a few 8.x to 10.x
> via 9.x and been fine too - but not many of these)
>
> What upgrade path did you use, what version did you come from, and
> what version did you go to?

Not talking about changing versions - talking about machines that are
forced to use pkg that are not 10.x and the freebsd-update tool was used
to patch the box at the same major version.

Michelle

-- 
Michelle Sullivan
http://www.mhix.org/