From owner-freebsd-pkg@FreeBSD.ORG Fri Feb 27 19:20:41 2015 Return-Path: Delivered-To: freebsd-pkg@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 11B77AA3 for ; Fri, 27 Feb 2015 19:20:41 +0000 (UTC) Received: from internal.electricembers.net (internal.electricembers.net [208.90.215.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.electricembers.net", Issuer "DigiCert High Assurance CA-3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE435C73 for ; Fri, 27 Feb 2015 19:20:40 +0000 (UTC) Received: from mail.electricembers.net (npomail1 [208.90.215.73]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ben) by internal.electricembers.net (Postfix) with ESMTPSA id 94A9C27333 for ; Fri, 27 Feb 2015 11:20:39 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 27 Feb 2015 11:20:39 -0800 From: Benjamin Connelly To: freebsd-pkg@freebsd.org Subject: Re: segfault when package locked In-Reply-To: <20150223211909.GE34473@ivaldir.etoilebsd.net> References: <45c872096d431d2df3f66d3546383517@mail.electricembers.net> <20150223211909.GE34473@ivaldir.etoilebsd.net> Message-ID: <7b07bfb13ba43cfeb2142d30ab748315@mail.electricembers.net> X-Sender: ben@electricembers.coop User-Agent: Roundcube Webmail/1.0.2 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2015 19:20:41 -0000 >> If we lock any packages, and then try to run 'pkg upgrade -f' it >> segfaults. We can work around by deleting the package first instead of >> locking it, but it seems like a bug? > > You sounds like a bug, can you give more details? > > The output might be good (do you hit an assert?) > > Best regards, > Bapt Sorry, I'm having trouble recreating the problem. (Maybe it's already been fixed!) If we ever do run into it again, we'll collect all output ;) Ben