From owner-freebsd-ports@FreeBSD.ORG Wed Oct 15 14:02:34 2008 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 6C25F1065688 for ; Wed, 15 Oct 2008 14:02:34 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by mx1.freebsd.org (Postfix) with ESMTP id C2CB88FC21 for ; Wed, 15 Oct 2008 14:02:33 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA06.westchester.pa.mail.comcast.net ([76.96.62.51]) by QMTA03.westchester.pa.mail.comcast.net with comcast id T1UM1a00J16LCl05322VG1; Wed, 15 Oct 2008 14:02:29 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA06.westchester.pa.mail.comcast.net with comcast id T22U1a00T2P6wsM3S22V0m; Wed, 15 Oct 2008 14:02:29 +0000 X-Authority-Analysis: v=1.0 c=1 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8 a=2gQC3sJQCF2HVffON7MA:9 a=B32-XwD9f2WaCrALz4wA:7 a=Zjy1sf5k3rWIelFUotgGEygs2GIA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id A1E64C9419; Wed, 15 Oct 2008 07:02:28 -0700 (PDT) Date: Wed, 15 Oct 2008 07:02:28 -0700 From: Jeremy Chadwick To: Jos Chrispijn Message-ID: <20081015140228.GA79394@icarus.home.lan> References: <48F5F3A2.9010505@webrz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48F5F3A2.9010505@webrz.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-ports@freebsd.org Subject: Re: MOVED file 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, 15 Oct 2008 14:02:34 -0000 On Wed, Oct 15, 2008 at 03:44:02PM +0200, Jos Chrispijn wrote: > I recently had some problems with updating my ports because there was a > problem with my MOVED file. > Can you tell me if this is caused by the person that is adding the port > to the update queue? Sometimes the problem can be solved by changing a > single '|' to a '||', but not allways. > The problem is solved now; does this indicate that the port maintainer > checked it and replaced the faulty line/string by the right one? You can use cvsweb to answer this question. See the very bottom of the web page. http://www.freebsd.org/cgi/cvsweb.cgi/ports/ -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |