Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 5EBB663287E for ; Fri, 11 Jun 2010 14:12:39 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 26544-03 for ; Fri, 11 Jun 2010 17:12:31 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.anarazel.de (mail.anarazel.de [217.115.131.40]) by mail.postgresql.org (Postfix) with ESMTP id 26F3163249C for ; Fri, 11 Jun 2010 14:12:30 -0300 (ADT) Received: from alap2.localnet (p579FAB46.dip.t-dialin.net [87.159.171.70]) by mail.anarazel.de (Postfix) with ESMTPSA id 5023C448004; Fri, 11 Jun 2010 19:12:28 +0200 (CEST) From: Andres Freund To: pgsql-hackers@postgresql.org Subject: Re: Error with GIT Repository Date: Fri, 11 Jun 2010 19:12:26 +0200 User-Agent: KMail/1.13.3 (Linux/2.6.35-rc2-andres-00054-g84f7586; KDE/4.4.85; x86_64; ; ) Cc: Magnus Hagander , Stephen Frost , Andrew Dunstan , Stephen Frost , "Luxenberg, Scott I." References: <9477.1267142614@sss.pgh.pa.us> <20100610162029.GI21875@tamriel.snowman.net> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201006111912.26423.andres@anarazel.de> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.79 tagged_above=-5 required=5 tests=BAYES_50=0.8, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201006/684 X-Sequence-Number: 164314 On Thursday 10 June 2010 19:30:00 Magnus Hagander wrote: > On Thu, Jun 10, 2010 at 18:20, Stephen Frost wrote: > > * Andrew Dunstan (andrew@dunslane.net) wrote: > >> I don't see why not. Buildfarm members are going to have to reset their > >> repos when we finally cut over in a few months. Luckily, this is a > >> fairly painless operation - blow away the repo and change the config > >> file and the script will resync as if nothing had happened. > > > > Should we stop bothering to offer http://git.postgresql.org then..? Or > > No, we should not. > > Especially if someone has a clue how to do it. The last time I fixed > it by runnin repack, but that didn't work this time. I have no clue > why it's asking for a file that doesn't exist. Does the repo run 'update-server-info' in some hook? Andres