From owner-freebsd-bugs@FreeBSD.ORG Thu Feb 28 11:32:12 2008 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4A6F1065674; Thu, 28 Feb 2008 11:32:12 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AEF2F8FC16; Thu, 28 Feb 2008 11:32:11 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47C69BBA.5020108@FreeBSD.org> Date: Thu, 28 Feb 2008 12:32:10 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: yuri@rawbw.com References: <200802280644.m1S6if2J002845@freefall.freebsd.org> <47C65EF7.1060002@rawbw.com> In-Reply-To: <47C65EF7.1060002@rawbw.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: remko@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/121165: pkg_add(1) prints a weird message: PKG_TMPDIR environment variable to a location with at least 0 bytes X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 11:32:12 -0000 Yuri wrote: > remko@FreeBSD.org wrote: >> Synopsis: pkg_add(1) prints a weird message: PKG_TMPDIR environment >> variable to a location with at least 0 bytes >> >> State-Changed-From-To: open->closed >> State-Changed-By: remko >> State-Changed-When: Thu Feb 28 06:44:41 UTC 2008 >> State-Changed-Why: This is not a PR this is a question to begin with. >> You clearly have >> limited space available and pkg_add tells you that it cannot extract the >> file in the temporary directory. find_play_pen probably is a function >> that does the extraction. Why the 0 bytes i dont know, but better -ask- >> around first before submitting these kind of PRs. >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=121165 >> > > I don't understand what is the problem with this PR. > This is clearly a cosmetic problem but still has to be fixed once noticed. > What am I going to ask around? If this is this a problem or not? > After dealing with this for 20 years it's obvious that this is a problem. So you're just asking for the error mesaage to be improved? Kris