From owner-freebsd-pkg@FreeBSD.ORG Tue Apr 15 01:54:18 2014 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8E8A32D7; Tue, 15 Apr 2014 01:54:18 +0000 (UTC) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E24081748; Tue, 15 Apr 2014 01:54:17 +0000 (UTC) Received: by mail-lb0-f179.google.com with SMTP id p9so6273314lbv.38 for ; Mon, 14 Apr 2014 18:54:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=AwsJu5aULFv3RfZIu5jO9Oh5EugkMcB+ZZBXJj/b0V0=; b=auMdcEUmrkB+AmpxjB2Dt7bd1FDgTHe8XXB+9tcHbkDCCOEquJQ2k63ssi1Nhmd/GY ESzPoPVjfiX+mHa1UJXgw34bmlAQP4ATtTIuSOwEbKe82iQvyeWO427XCaX8Kn0buk7s 193YzSYWzDE1vgvkJV4Sek8uJaGdCMxg5O0uApJTdiKmoGB/REo6J8jwfM7j7wV6wVXH IfaQM0tZh++b9jD3nWN63bGGSYAh7ShCyguahrml8CkinWGsu4KcXTqGJLiU3SqX21G2 7nqxHA+nyxBXJVO+qQ5L79qSWwuvLgiGN2wb088NTyUdg/h9WEJyJlSrgdBwUDZe+mYS //7w== MIME-Version: 1.0 X-Received: by 10.152.184.66 with SMTP id es2mr32293641lac.22.1397526855666; Mon, 14 Apr 2014 18:54:15 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.169.68 with HTTP; Mon, 14 Apr 2014 18:54:15 -0700 (PDT) In-Reply-To: <1397525950.1293.4.camel@powernoodle.corp.yahoo.com> References: <1397525950.1293.4.camel@powernoodle.corp.yahoo.com> Date: Mon, 14 Apr 2014 18:54:15 -0700 X-Google-Sender-Auth: FCPHJg0ILYNYXItZUnixGJv8aRU Message-ID: Subject: Re: Read-only nullfs mounts should become read-write? From: Craig Rodrigues To: Sean Bruno Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-pkg@freebsd.org X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.17 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: Tue, 15 Apr 2014 01:54:18 -0000 On Mon, Apr 14, 2014 at 6:39 PM, Sean Bruno wrote: > > > Maybe set PORTSDIR= in make.conf or whatever to point at where your > ports are? I think I ran into this too. > > e.g. > make.conf: > PORTSDIR=/usr/local/poudriere/ports/default I don't think PORTSDIR is necessary. I have the following in the following files /etc/poudriere.d/ports/p/method contains: git and /etc/poudriere.d/ports/p/method contains: /usr/home/rodrigc/freenas/freenas//FreeBSD/ports That's where my ports tree is, and it is being accessed properly. It is just that something is trying to write to a read-only mount. > Maybe spam the entire build log from poudriere somewhere we can look at > too. I put the build logs here: http://people.freebsd.org/~rodrigc/d/logs/ Here is one example failure due to a read-only mount: http://people.freebsd.org/~rodrigc/d/logs/bulk/j-p/2014-04-15_01h52m30s/logs/errors/m4-1.4.17,1.log -- Craig