From owner-freebsd-current@FreeBSD.ORG Tue Nov 4 06:51:20 2014 Return-Path: Delivered-To: current@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 51FB7D2E for ; Tue, 4 Nov 2014 06:51:20 +0000 (UTC) Received: from luigi.brtsvcs.net (luigi.brtsvcs.net [204.109.60.246]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2BA0FAB8 for ; Tue, 4 Nov 2014 06:51:19 +0000 (UTC) Received: from chombo.houseloki.net (unknown [IPv6:2601:7:400:640:21c:c0ff:fe7f:96ee]) by luigi.brtsvcs.net (Postfix) with ESMTPSA id CDAFE2D4F9B; Mon, 3 Nov 2014 22:51:11 -0800 (PST) Received: from [IPv6:2601:7:2580:674:baca:3aff:fe83:bd29] (unknown [IPv6:2601:7:2580:674:baca:3aff:fe83:bd29]) by chombo.houseloki.net (Postfix) with ESMTPSA id E06B5BDA; Mon, 3 Nov 2014 22:51:09 -0800 (PST) Message-ID: <54587759.4050206@bluerosetech.com> Date: Mon, 03 Nov 2014 22:51:05 -0800 From: Darren Pilgrim Reply-To: "current@freebsd.org" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Kevin Oberman Subject: Re: pkg 1.4 freeze please test test test! References: <20141028231933.GG26796@ivaldir.etoilebsd.net> <20141101161332.b9c8fc19bf9fc54f73bc5c00@gmail.com> <20141101224549.GG15967@ivaldir.etoilebsd.net> <20141102102455.30d42f85ff81e079788eae06@gmail.com> <5457F64F.6090408@selasky.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 06:51:20 -0000 On 11/3/2014 9:50 PM, Kevin Oberman wrote: > I simply do periodic(8) weekly runs of "pkg version -vRl\<" to catch any > port that has not been updated due to being locked. On option to only > report locked packages would simplify this and looks to me like it would be > pretty easy to add, but unless you have a lot of locked packages, it's not > a problem. I just do `pkg info -ka | egrep 'yes$'`.