X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id 71D6E11F6009; Wed, 12 Apr 2006 19:25:12 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: -2.373 X-Spam-Level: X-Spam-Status: No, score=-2.373 required=5 tests=[AWL=0.226, BAYES_00=-2.599] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id c71Y67TjKB7U; Wed, 12 Apr 2006 19:25:07 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from davinci.ethosmedia.com (server227.ethosmedia.com [209.128.84.227]) by postgresql.org (Postfix) with ESMTP id 40C8A11F6C41; Wed, 12 Apr 2006 19:25:03 -0300 (ADT) X-EthosMedia-Virus-Scanned: no infections found Received: from [64.81.245.111] (account josh@agliodbs.com HELO [192.168.1.27]) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 9253803; Wed, 12 Apr 2006 15:28:06 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: pgsql-www@postgresql.org Subject: Re: pgfoundry and gborg Date: Wed, 12 Apr 2006 15:23:39 -0700 User-Agent: KMail/1.8 Cc: "Marc G. Fournier" , Bruce Momjian References: <200604121745.k3CHj2h26333@candle.pha.pa.us> <20060412185719.V1096@ganymede.hub.org> <20060412185910.O1096@ganymede.hub.org> In-Reply-To: <20060412185910.O1096@ganymede.hub.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604121523.39911.josh@agliodbs.com> X-Archive-Number: 200604/44 X-Sequence-Number: 9820 Marc, > Appendum: but, we don't know how easy getting pgfoundry moved to the new > server is going to be yet ... we've done the file/ports stuff, but, as > far as I know, we haven't done any testing of the result (ie. run it > live and check for any issues) ... if you want to move it to the new > server first, let's concentrate on that and then worry about > gborg->pgfoundry ... No, the new server isn't ready yet so we can do things in any order -- there's issues with Apache and with one drive which I and Sean are working on. The idea, though, is to have everything on pgfoundry on the new faster server by June 1. -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco