From owner-freebsd-ports@freebsd.org Wed Jun 14 18:30:12 2017 Return-Path: Delivered-To: freebsd-ports@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 05DE6BF120A for ; Wed, 14 Jun 2017 18:30:12 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (108-84-10-9.lightspeed.austtx.sbcglobal.net [108.84.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darth.immure.com", Issuer "darth.immure.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BE48A74082 for ; Wed, 14 Jun 2017 18:30:11 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (localhost [127.0.0.1]) by rancor.immure.com (8.15.2/8.15.2) with ESMTPS id v5EIU3Le005633 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 14 Jun 2017 13:30:03 -0500 (CDT) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.15.2/8.15.2/Submit) id v5EIU3of005632 for freebsd-ports@freebsd.org; Wed, 14 Jun 2017 13:30:03 -0500 (CDT) (envelope-from bob) Date: Wed, 14 Jun 2017 13:30:03 -0500 From: Bob Willcox To: ports list Subject: pkg delete of firefox fails: firefox-51.0.1_1,1 is locked and may not be modified Message-ID: <20170614183003.GA5608@rancor.immure.com> Reply-To: Bob Willcox MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jun 2017 18:30:12 -0000 I'm trying to update firefox on my system but can't update it or even delete it. I get this result on pkg delete (for example): root@tavion:1 /usr/ports/www/firefox> pkg delete firefox firefox-51.0.1_1,1 is locked and may not be modified Checking integrity... done (0 conflicting) Package(s) not found! Now, I suspect that I am the one responsible for 'locking' it a few months back when I didn't want to inavertantly update it. Unfortunately I can't recall what I might have done to lock it (memory isn't what it used to be). Can someone shed some light on where/what this lock may be? Thanks, Bob -- Bob Willcox | Lawsuit, n.: A machine which you go into as a pig and bob@immure.com | come out as a sausage. Austin, TX | -- Ambrose Bierce