From owner-freebsd-current@FreeBSD.ORG Sat Jun 20 15:57:41 2015 Return-Path: Delivered-To: current@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6D4D0A91 for ; Sat, 20 Jun 2015 15:57:41 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw11.york.ac.uk (mail-gw11.york.ac.uk [144.32.129.150]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 34DEC1DE for ; Sat, 20 Jun 2015 15:57:40 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from ury.york.ac.uk ([144.32.64.162]:30868) by mail-gw11.york.ac.uk with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1Z6L3S-0003m7-Mm; Sat, 20 Jun 2015 16:51:38 +0100 Date: Sat, 20 Jun 2015 16:51:38 +0100 (BST) From: Gavin Atkinson X-X-Sender: gavin@ury.york.ac.uk To: "Eggert, Lars" cc: "current@freebsd.org" Subject: Re: Difference between pkg 1.5.2 and 1.5.4 In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Sat, 20 Jun 2015 15:57:41 -0000 On Thu, 18 Jun 2015, Eggert, Lars wrote: > Hi, > > I'm netbooting with a read-only rootfs. Up until version 1.5.2 of pkg, that sometimes caused some errors when installing various packages, but the install continued even if some files couldn't be written. > > That seems to have changed with 1.5.4. Specifically, upgrading ca_root_nss from 3.19 to 3.19.1_1 now aborts in archive_read_extract () as shown below. > > This regression makes it difficult to run read-only; any chance this abort can be turned into a warning instead? pkg is maintained externally to FreeBSD, opening a bug report at https://github.com/freebsd/pkg/issues is the best way to get things like this fixed. Thanks, Gavin