From owner-freebsd-ports@FreeBSD.ORG  Fri Aug 15 14:03:17 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 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5C2D762D
 for <freebsd-ports@freebsd.org>; Fri, 15 Aug 2014 14:03:17 +0000 (UTC)
Received: from mail.tdx.com (mail.tdx.com [62.13.128.18])
 by mx1.freebsd.org (Postfix) with ESMTP id DDD0E2235
 for <freebsd-ports@freebsd.org>; Fri, 15 Aug 2014 14:03:16 +0000 (UTC)
Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251])
 (authenticated bits=0)
 by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s7FE39ch001610
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
 for <freebsd-ports@freebsd.org>; Fri, 15 Aug 2014 15:03:09 +0100 (BST)
Date: Fri, 15 Aug 2014 15:03:10 +0100
From: Karl Pielorz <kpielorz_lst@tdx.co.uk>
To: freebsd-ports@freebsd.org
Subject: Re: Ports, pkg's confusion on upgrades...
Message-ID: <6DDC5F35357B9102A924FB55@Mail-PC.tdx.co.uk>
In-Reply-To: <53EDE679.9050105@wasikowski.net>
References: <52652ABEC925BB93CB8877CD@Mail-PC.tdx.co.uk>
 <53EDE679.9050105@wasikowski.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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: Fri, 15 Aug 2014 14:03:17 -0000


By letting 'pkg upgrade' complete, then running 'pkg info --all -d' I was 
able to find out what package upgrade now requires an additional package 
"to be INSTALLED".

(In our case memcached-1.4.20_2 pkg now requires cyrus-sasl-2.1.26_8 - 
where as it didn't before).

I still can't figure out how to get pkg upgrade to reveal *why* it needs to 
install this, *before* it does it (i.e. only by letting it do it, then 
running 'pkg info --all -d' did it then show memcached having a dependency 
on cyrus - where as the older version of memcached didn't.

-Karl