From owner-freebsd-questions@FreeBSD.ORG Thu Jul 18 12:42:33 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 647DA366 for ; Thu, 18 Jul 2013 12:42:33 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) by mx1.freebsd.org (Postfix) with ESMTP id 28C2BB91 for ; Thu, 18 Jul 2013 12:42:32 +0000 (UTC) Received: from steiner.cc.vt.edu (steiner.cc.vt.edu [198.82.163.51]) by lennier.cc.vt.edu (8.13.8/8.13.8) with ESMTP id r6ICXSqq014352 for ; Thu, 18 Jul 2013 08:42:02 -0400 Received: from auth3.smtp.vt.edu (auth3.smtp.vt.edu [198.82.161.152]) by steiner.cc.vt.edu (MOS 4.3.3-GA) with ESMTP id YGU32298; Thu, 18 Jul 2013 08:42:02 -0400 X-Mirapoint-Received-SPF: 198.82.161.152 auth3.smtp.vt.edu 0 none Received: from pmather.tower.lib.vt.edu (pmather.tower.lib.vt.edu [128.173.51.28]) (authenticated bits=0) by auth3.smtp.vt.edu (8.13.8/8.13.8) with ESMTP id r6ICg1FO005145 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 18 Jul 2013 08:42:01 -0400 From: Paul Mather Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Is pkgng supposed to upgrade a dependency of a locked package? Message-Id: <6E003358-F64D-4AA7-9C5B-FAA2918389DC@gromit.dlib.vt.edu> Date: Thu, 18 Jul 2013 08:42:01 -0400 To: freebsd-questions@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) X-Mailer: Apple Mail (2.1508) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 12:42:33 -0000 I am using pkgng 1.1.4_1 on RELENG_9 (r252725), operating on a local = repo I maintain using poudriere 3.0.4. Recently, I wanted to upgrade all packages on a client except two whose = update I want to defer for now as they potentially impact = locally-developed applications. I figured I would use the pkgng "lock" = functionality on those two packages (apache-solr and py27-Jinja2) to = prevent them from being updated. I ran "pkg upgrade" on the client and, = as expected, the locked packages weren't upgraded. However, I was = surprised to see that packages upon which the locked packages depended = were upgraded. Unless I'm misunderstanding something, the man page for = pkg-lock states this should not happen: =3D=3D=3D=3D=3D The impact of locking a package is wider than simply preventing = modifica- tions to the package itself. Any operation implying modification = of the locked package will be blocked. This includes: [[...]] o Deletion, up- or downgrade of any package the locked package = depends upon, either directly or as a consequence of installing or = upgrading some third package. =3D=3D=3D=3D=3D In my case, the following dependencies of apache-solr were updated, even = though apache-solr is locked: java-zoneinfo: 2013.c -> 2013.d; libXi: = 1.7.1_1,1 -> 1.7.2,1; libXrender: 0.9.7_1 -> 0.9.8; and openjdk: 7.21.11 = -> 7.25.15. In the case of the locked py27-Jinja2, these dependencies = were updated: gettext: 0.18.1.1_1 -> 0.18.3; and py27-MarkupSafe: 0.15 = -> 0.18. Dependency information in the two locked packages was updated = to reflect these new, upgraded dependencies. Is this a bug, or am I misreading the man page? Cheers, Paul.=