From owner-freebsd-ports@FreeBSD.ORG Wed Jan 10 00:56:09 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0F7B416A40F for ; Wed, 10 Jan 2007 00:56:09 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with SMTP id A425C13C448 for ; Wed, 10 Jan 2007 00:56:08 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 17866 invoked by uid 399); 10 Jan 2007 00:56:08 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 10 Jan 2007 00:56:08 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45A439A2.3070702@FreeBSD.org> Date: Tue, 09 Jan 2007 16:56:02 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Derrick Edwards References: <200701091155.44572.derrick@uniquestrength.net> In-Reply-To: <200701091155.44572.derrick@uniquestrength.net> X-Enigmail-Version: 0.94.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: Portmaster Help X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 00:56:09 -0000 Derrick Edwards wrote: > Hi, > Using portmaster, I get the following error message. Ofcourse, based on the > specific app the first line changes but the second line is consistent. I am > currently getting this error message on several other ports on different > machines. > > tar: etc/authlib/authmysqlrc.dist: Cannot stat: No such file or directory > pkg_create: make_dist: tar command failed with code 256 > > ===>>> Backup package creation failed for courier-authlib-mysql-0.58_2 > ===>>> Aborting update I just committed version 1.12 that has the fix I've been working on for that problem. It allows the user the choice to ignore the error, or abort the update. In many cases (especially for the default backup packaging) ignoring the error is ok. hth, Doug -- This .signature sanitized for your protection