From owner-freebsd-ports@FreeBSD.ORG Thu Jun 10 01:36:20 2010 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 64FBD1065672 for ; Thu, 10 Jun 2010 01:36:20 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from sunner.semmy.ru (sunner.semmy.ru [195.54.209.159]) by mx1.freebsd.org (Postfix) with ESMTP id 214408FC1B for ; Thu, 10 Jun 2010 01:36:19 +0000 (UTC) Received: from [109.173.73.7] (helo=[172.16.100.23]) by sunner.semmy.ru with esmtpa (Exim 4.71 (FreeBSD)) (envelope-from ) id 1OMWgr-000FfA-BF; Thu, 10 Jun 2010 05:36:17 +0400 Message-ID: <4C104191.3060408@FreeBSD.org> Date: Thu, 10 Jun 2010 05:36:17 +0400 From: Sergey Matveychuk User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4 MIME-Version: 1.0 To: Paul Schmehl References: <4E3C5EC96AEE55AE692F0276@utd65257.utdallas.edu> In-Reply-To: <4E3C5EC96AEE55AE692F0276@utd65257.utdallas.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports Subject: Re: Can someone explain this? (portupgrade of textproc/p5-Perl-Critic 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: Thu, 10 Jun 2010 01:36:20 -0000 09.06.2010 19:54, Paul Schmehl wrote: > First it checks for prereqs and finds them all. Then it checks for > prereqs and says they're missing. Then it generates three stops due to > errors, and at the end it says the upgrade was successful??? WTF??? > > And it *is not* installed. I'm still working to get all the prereqs > installed, even though they already were. What exactly is the problem > with this port? > Unfortunately sometimes portupgrade can't detect some failures (failures for portupgrade is any output to stderr). As I can remember it has happened after one of ruby updates. I could not find a reason for this behaviour. -- Semy.