From owner-freebsd-questions@FreeBSD.ORG Tue Jul 26 21:10:47 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1805316A41F for ; Tue, 26 Jul 2005 21:10:47 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail25.sea5.speakeasy.net (mail25.sea5.speakeasy.net [69.17.117.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id C031143D46 for ; Tue, 26 Jul 2005 21:10:46 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 29491 invoked from network); 26 Jul 2005 21:10:46 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail25.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 26 Jul 2005 21:10:46 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id F366426; Tue, 26 Jul 2005 17:10:44 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Mike Friedman To: freebsd-questions@freebsd.org References: <20050726103124.S67832@malcolm.berkeley.edu> From: Lowell Gilbert Date: 26 Jul 2005 17:10:44 -0400 In-Reply-To: <20050726103124.S67832@malcolm.berkeley.edu> Message-ID: <44zms9mfxn.fsf@be-well.ilk.org> Lines: 25 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: fastcgi port fixed but not updated? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2005 21:10:47 -0000 Mike Friedman writes: > I've recently discovered a problem report for the mod_fastcgi (2.4.2) > port: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/79774. The > report seems to indicate that the port was fixed shortly after the PR > was sent (May 31), yet I just did a cvsup and the buggy port still > shows up. > > I have made the fix to my copy of the port and it does work, but why > isn't the fixed version available via cvsup? My cvsup log (run just > this morning) shows that the fastcgi Makefile was checked out, yet its > date is still early on May 31, apparently just before the fix was > done, according to the PR. > > Anyone know what might be going on? Since the fastcgi port is called > by the rt-3.4.2 port (which is my real interest), keeping my fixed > version of the former around under a different name is not really a > good option, in case I need to update RT. The bug report claims that the install fails. It works fine for me with the Apache 1.3 port, so I suspect that a more sophisticated fix would be needed; if the path were hardcoded as you suggest, the port would *only* work with Apache2.