From owner-freebsd-ports@FreeBSD.ORG Fri Mar 9 09:27:18 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id 1A77F106564A for ; Fri, 9 Mar 2012 09:27:18 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id A087714EA67; Fri, 9 Mar 2012 09:27:17 +0000 (UTC) Message-ID: <4F59CCF5.4040102@FreeBSD.org> Date: Fri, 09 Mar 2012 01:27:17 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120224 Thunderbird/10.0.2 MIME-Version: 1.0 To: Mel Flynn References: <4F57E8DF.3070706@acsalaska.net> In-Reply-To: <4F57E8DF.3070706@acsalaska.net> X-Enigmail-Version: 1.3.5 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, Michael Heitmeier Subject: Re: Squeezeboxserver loops endlessly 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: Fri, 09 Mar 2012 09:27:18 -0000 On 03/07/2012 15:01, Mel Flynn wrote: > Hi, > > On 3/7/2012 22:48, Michael Heitmeier wrote: > >> I just cvsupped ports so I'm wondering is that a problem on my side or is >> the port broken? > >> ===>>> Port directory: /usr/ports/www/p5-libwww >> >> ===>>> Launching 'make checksum' for www/p5-libwww in background >> ===>>> Gathering dependency list for www/p5-libwww from ports >> >> ===>>> The dependency for net/p5-Net-HTTP >> seems to be handled by p5-libwww-5.837 > > This one of two cases I know of that portmaster is trying to be smarter > then it should. > It notices a conflict and tries to redirect the dependency to the > conflicting port. In many cases this is the correct thing to do, but not > in this case, because one of the ports depends on the other. This problem was caused by the way that the maintainer did the update, and perpetuated by the maintainer refusing to fix it. > Deleting > both p5-libwww-5.837 and p5-Net-HTTP-* and then re-running portmaster > should fix things for you. Yes. -- This .signature sanitized for your protection