From owner-freebsd-questions@FreeBSD.ORG Mon Apr 19 17:10:40 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9187F106566C for ; Mon, 19 Apr 2010 17:10:40 +0000 (UTC) (envelope-from joe@netmusician.org) Received: from mail.netmusician.org (dorian.netmusician.org [66.244.95.101]) by mx1.freebsd.org (Postfix) with ESMTP id 5D1078FC08 for ; Mon, 19 Apr 2010 17:10:40 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by mail.netmusician.org (Postfix) with ESMTP id AA335B912 for ; Mon, 19 Apr 2010 13:10:38 -0400 (EDT) X-Virus-Scanned: amavisd-new at netmusician.org Received: from mail.netmusician.org ([127.0.0.1]) by localhost (dorian.netmusician.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Uyq3pnTwNPuV for ; Mon, 19 Apr 2010 13:10:38 -0400 (EDT) Received: from Shakti.local (c-67-176-145-181.hsd1.in.comcast.net [67.176.145.181]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.netmusician.org (Postfix) with ESMTPSA id C5D2EB90C for ; Mon, 19 Apr 2010 13:10:37 -0400 (EDT) Message-ID: <4BCC8E8C.80406@netmusician.org> Date: Mon, 19 Apr 2010 13:10:36 -0400 From: Joe Auty User-Agent: Postbox 1.1.4 (Macintosh/20100408) MIME-Version: 1.0 To: freebsd-questions@freebsd.org X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Questions about port revision numbers, portsnap, csup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2010 17:10:40 -0000 Hello, I've identified my pecl-APC install as being broken after upgrading to PHP 5.3.2. According to the commit history listed here: http://www.freshports.org/www/pecl-APC/ there is a fix out. However, doing a portsnap fetch update does not seem to fetch this latest revision to this port, after doing my portsnap it shows no updates are available for the port although I'm pretty certain that I last portsnapped before April 12. I'm assuming that portsnap only grabs a new version of the portrevision number has been bumped? My questions: 1) If I were to csup my ports tree to force a fetch of this update, would this break portsnap? 2) Is there a way to look at the commit history of the ports I have installed in /usr/ports so that I can verify whether or not I have the revision with this particular fix? Thus far I've been relying on freshports.org and trusting that doing a portsnap will always fetch the latest stuff visible on freshports.org, but now I'm not so sure... 3) Shouldn't the portrevision number be bumped whenever there is an update? I always assumed that the _x suffixes indicated a portrevision bump. Why was it not bumped for this pecl-APC fix? Human error? Is there any other way I can force the download of this port, or is csup my best bet? -- Joe Auty, NetMusician NetMusician helps musicians, bands and artists create beautiful, professional, custom designed, career-essential websites that are easy to maintain and to integrate with popular social networks. www.netmusician.org joe@netmusician.org