From owner-freebsd-isp@FreeBSD.ORG Thu Aug 10 20:49:42 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 040B616A4E2 for ; Thu, 10 Aug 2006 20:49:42 +0000 (UTC) (envelope-from mark@gaiahost.coop) Received: from biodiesel.gaiahost.coop (biodiesel.gaiahost.coop [64.95.78.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA2E243D45 for ; Thu, 10 Aug 2006 20:49:41 +0000 (GMT) (envelope-from mark@gaiahost.coop) Received: from gaiahost.coop (host-64-65-195-19.spr.choiceone.net [::ffff:64.65.195.19]) (AUTH: LOGIN mark@hubcapconsulting.com) by biodiesel.gaiahost.coop with esmtp; Thu, 10 Aug 2006 16:49:39 -0400 id 000BC1DD.44DB9BE3.00005DF9 Received: by gaiahost.coop (sSMTP sendmail emulation); Thu, 10 Aug 2006 16:49:43 -0400 Date: Thu, 10 Aug 2006 16:49:43 -0400 From: Mark Bucciarelli To: freebsd-isp@freebsd.org Message-ID: <20060810204943.GG2164@rabbit> Mail-Followup-To: freebsd-isp@freebsd.org References: <20060810132435.GB2636@rabbit> <44DB9955.10102@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <44DB9955.10102@FreeBSD.org> User-Agent: Mutt/1.4.2.1i Subject: Re: Ports/source dance X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2006 20:49:42 -0000 On Thu, Aug 10, 2006 at 01:38:45PM -0700, Doug Barton wrote: > Mark Bucciarelli wrote: > > > > I guess the broader question is how to handle security upgrades > > when the port isn't ready. > > First off, you posted to the wrong list, you should have posted this to > freebsd-ports@, ideally _after_ you contact the maintainer for the port > (which can be found in the port's Makefile). There's a scary security alert from yesterday out and no port update so I judged it to be isp-related. I looked for ports-security list but didn't see one. > To answer your question more usefully, the Porter's Handbook > (on the FreeBSD web site) has a lot of good information about > how to create and maintain ports. If you are lucky, the > following will work for you for a quick and dirty update till > the maintainer (or you) have a chance to do a more thorough job > of it. If you're not lucky and need help, please follow up with > the maintainer, and the freebsd-ports list if needed. > > cp -Rp /usr/ports//rubygem-rail ~/ cd ~/rubygem-rail vi > Makefile Update version information to the desired version make > makesum Use some out of band method to try and determine that > the files you downloaded are the right ones make Heh. I looked at the patch for the upgrade from 1.0.0. to 1.1.2 and there were 14 seperate files changed across seven (IIRC) ports. I think I'll wait--turns out the versions I have running are not affected. Although if the maintainter doesn't get back to me in a week or so I may tackle it. Thanks, m