From owner-freebsd-stable@FreeBSD.ORG Sat Oct 25 14:57:49 2014 Return-Path: Delivered-To: freebsd-stable@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 753BC158 for ; Sat, 25 Oct 2014 14:57:49 +0000 (UTC) Received: from webmail2.jnielsen.net (webmail2.jnielsen.net [50.114.224.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.jnielsen.net", Issuer "freebsdsolutions.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 53559FAB for ; Sat, 25 Oct 2014 14:57:48 +0000 (UTC) Received: from [192.168.2.123] (c-50-160-123-105.hsd1.ut.comcast.net [50.160.123.105]) (authenticated bits=0) by webmail2.jnielsen.net (8.14.9/8.14.9) with ESMTP id s9PEvdqZ043284 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 25 Oct 2014 08:57:44 -0600 (MDT) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail2.jnielsen.net: Host c-50-160-123-105.hsd1.ut.comcast.net [50.160.123.105] claimed to be [192.168.2.123] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: pkgng upgrade -> force upgrade of dependencies From: John Nielsen X-Mailer: iPhone Mail (12B411) In-Reply-To: <5448A373.1070707@ish.com.au> Date: Sat, 25 Oct 2014 08:57:38 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <97F5BECA-C7D0-49EE-AC91-7B87A990307D@jnielsen.net> References: <5448A373.1070707@ish.com.au> To: Aristedes Maniatis Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Oct 2014 14:57:49 -0000 > On Oct 23, 2014, at 12:42 AM, Aristedes Maniatis wrote: >=20 > I've scoured the documentation, but I cannot for the life of me figure how= to do this. Let's say I want to upgrade a package "apache22" without upgrad= ing everything on the system. Now I want to ensure I get enough of the depen= dencies into the upgrade that apache will actually work. So I try this: >=20 > # pkg upgrade apache22-worker-mpm > Installed packages to be UPGRADED: > apache22-worker-mpm: 2.2.27_6 -> 2.2.29_2 >=20 > Hmmm, that doesn't seem right. >=20 > # pkg upgrade | grep openssl > openssl: 1.0.1_15 -> 1.0.1_16 >=20 > # pkg info -d apache22-worker-mpm > apache22-worker-mpm-2.2.27_6: > expat-2.1.0_1 > openssl-1.0.1_15 > perl5-5.16.3_11 > pcre-8.34_2 > apr-1.5.1.1.5.3_4 > libiconv-1.14_3 >=20 > So, a new version of openssl is needed and is linked to the new binary. Bu= t it will not be installed when I upgrade apache. >=20 >=20 > Before I moved to pkgng/poudriere I used to use portmaster. That would mor= e thoroughly examine the dependencies and make sure everything that was inte= r-related (both as parent and child dependencies) was upgraded together. But= it did not force me to upgrade Java when I just wanted to get the new versi= on of bash installed. I'm not certain that it handles dependencies (it ought to), but the document= ed way to upgrade selectively is via "pkg install pkgname ..."