From owner-freebsd-ports@FreeBSD.ORG Wed Jun 17 11:33:05 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D52D1065673 for ; Wed, 17 Jun 2009 11:33:05 +0000 (UTC) (envelope-from tlott@gamesnet.de) Received: from spirit.gamesnet.de (spirit.gamesnet.de [87.230.101.86]) by mx1.freebsd.org (Postfix) with ESMTP id 563BA8FC16 for ; Wed, 17 Jun 2009 11:33:05 +0000 (UTC) (envelope-from tlott@gamesnet.de) Received: from localhost (localhost [127.0.0.1]) by spirit.gamesnet.de (Postfix) with ESMTP id DA8ED32C70A for ; Wed, 17 Jun 2009 13:32:32 +0200 (CEST) X-Virus-Scanned: amavisd-new at gamesnet.de Received: from spirit.gamesnet.de ([127.0.0.1]) by localhost (spirit.gamesnet.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I5+ZkEl324Dr for ; Wed, 17 Jun 2009 13:32:32 +0200 (CEST) Received: from sub.han.vpn.gamesnet.de (sub.han.vpn.gamesnet.de [192.168.1.101]) by spirit.gamesnet.de (Postfix) with ESMTPSA id 36E1832C5B3 for ; Wed, 17 Jun 2009 13:32:32 +0200 (CEST) Date: Wed, 17 Jun 2009 13:32:31 +0200 From: Tobias lott To: FreeBSD Ports Message-ID: <20090617133231.3883776a@sub.han.vpn.gamesnet.de> In-Reply-To: <4A38B47E.1070906@icyb.net.ua> References: <4A38B47E.1070906@icyb.net.ua> X-Mailer: Claws Mail 3.7.1 (GTK+ 2.14.7; i386-portbld-freebsd7.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: portupgrade/ruby issue? (Stale lock file was found. Removed.) 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, 17 Jun 2009 11:33:06 -0000 On Wed, 17 Jun 2009 12:16:46 +0300 Andriy Gapon wrote: > > After recent massive ports update (I think ruby was touch and > probably portupgrade too) I started getting seemingly sporadic "Stale > lock file was found. Removed." messages. What's interesting is that > those messages are produced on stdout, not stderr. > > Sporadic - because they appear when there are no parallel execution > of any portupgrade tools (or any other package/port related tools). > They appear in situations wheere they never appeared before. > > I see this on two stable/7 systems. > Got the same on five 7-Stable Machines. -- Tobias Lott