From owner-freebsd-pkg@freebsd.org  Tue Oct 13 22:39:21 2015
Return-Path: <owner-freebsd-pkg@freebsd.org>
Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93230A1397F
 for <freebsd-pkg@mailman.ysv.freebsd.org>;
 Tue, 13 Oct 2015 22:39:21 +0000 (UTC)
 (envelope-from ben@electricembers.coop)
Received: from npomail1.electricembers.net (mail.electricembers.net
 [208.90.215.73])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.electricembers.net",
 Issuer "RapidSSL SHA256 CA - G3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 82CEAECD
 for <freebsd-pkg@freebsd.org>; Tue, 13 Oct 2015 22:39:20 +0000 (UTC)
 (envelope-from ben@electricembers.coop)
Received: from private by npomail1.electricembers.net;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=electricembers.coop;
 s=internal; t=1444775478;
 bh=gTgN8N5y+2h1JCljaEFF09xUYzHBA/1YiR8S/bhEQCM=; l=1273;
 h=To:From:Subject:MIME-Version:Content-Type:
 Content-Transfer-Encoding;
 b=Cyg0WNgQZNMs40Pud0yHpzL9OkFmyK/zR5l2+9DX/0zh5DUjMFTmrT1ekcOWaLJ2C
 OGdBdvzbyECKidmahQGemqV+roubFWdbcCCtbu8Q+Ij+BocFxLOIabCjus370yqKa2
 Xo9fxd5HeyHrUM6UfzWWRTjT/kcSRIWcKyGXzOdo=
To: freebsd-pkg@freebsd.org
From: Benjamin Connelly <ben@electricembers.coop>
Subject: locked packages got upgraded anyway
Message-ID: <561D8634.40103@electricembers.coop>
Date: Tue, 13 Oct 2015 15:31:16 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-pkg@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Binary package management and package tools discussion
 <freebsd-pkg.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-pkg>,
 <mailto:freebsd-pkg-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-pkg/>
List-Post: <mailto:freebsd-pkg@freebsd.org>
List-Help: <mailto:freebsd-pkg-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-pkg>,
 <mailto:freebsd-pkg-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2015 22:39:21 -0000

We have a few ports we compile with different compile time options than 
the FreeBSD binary repo, so we keep them locked. Last night when doing 
some patching, we saw those locked packages get updated anyhow. For 
example, pkg said all of these things on one system:

Installed packages to be UPGRADED:
         pkg: 1.5.6 -> 1.6.1

dovecot2-2.2.18 is locked and may not be modified

Installed packages LOCKED:
   Package dovecot2-2.2.18 is locked and may not be upgraded to version 
2.2.19

(dovecot was not listed in the "Installed packages to be UPGRADED:" 
section, but then it was fetched)

Fetching dovecot2-2.2.19.txz: 100%    3 MiB   2.9MB/s    00:01

Installed packages LOCKED:
   Package dovecot2-2.2.18 is locked and may not be upgraded to version 
2.2.19

(it still did not after fetching appear on the list of packages to be 
upgraded, but)

[17/71] Upgrading dovecot2 from 2.2.18 to 2.2.19...
[17/71] Extracting dovecot2-2.2.19: 100%

dovecot-pigeonhole was always on the list of packages to be upgraded, 
and it depends on dovecot2.

Is this a bug, or did we learn a bad habit that's no longer workable, to 
lock the ports we build with different compile time options to keep 'pkg 
upgrade' from touching them.

Benjamin