MIME-Version: 1.0
In-Reply-To: 
 <CABUevEyh4tWHYTNcCFf_Pwm9WNBTz8ftcCh_1P=z3YiYn4J5jw@mail.gmail.com>
References: <20130304020324.GE16142@tamriel.snowman.net>
	<2480.1362363162@sss.pgh.pa.us>
	<20130304023335.GH16142@tamriel.snowman.net>
	<CABUevEwfw24iF9-czueLSmdFQwck012qfVmLXcoKbG37xG56jQ@mail.gmail.com>
	<CABUevEzM2F8qAxVds9Me-41L5BqeEGO4DuosCQhC0C6v05HPUw@mail.gmail.com>
	<20130304125013.GB3943@awork2.anarazel.de>
	<20130304143349.GX9507@alvh.no-ip.org>
	<20130304143852.GH3943@awork2.anarazel.de>
	<20130304145842.GZ9507@alvh.no-ip.org>
	<20130304150344.GK3943@awork2.anarazel.de>
	<20130304151127.GB9507@alvh.no-ip.org>
	<5564.1362410250@sss.pgh.pa.us>
	<CABUevEyh4tWHYTNcCFf_Pwm9WNBTz8ftcCh_1P=z3YiYn4J5jw@mail.gmail.com>
Date: Mon, 4 Mar 2013 16:31:15 +0100
Message-ID: 
 <CABUevEzGmbk+EbpYDZjd+c+VsY2iqe0scntsS3bPuJYuC7OYnA@mail.gmail.com>
Subject: Re: gitweb is no longer a real-time view
From: Magnus Hagander <magnus@hagander.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
	Andres Freund <andres@2ndquadrant.com>,
	Kevin Grittner <kgrittn@mail.com>, Peter Eisentraut <peter_e@gmx.net>,
	PostgreSQL WWW <pgsql-www@postgresql.org>,
	Stephen Frost <sfrost@snowman.net>
Content-Type: text/plain; charset=ISO-8859-1
Precedence: bulk
Sender: pgsql-www-owner@postgresql.org

On Mon, Mar 4, 2013 at 4:22 PM, Magnus Hagander <magnus@hagander.net> wrote:
> On Mon, Mar 4, 2013 at 4:17 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>>> I guess there clearly weren't enough protections in the gitmaster server
>>> to prevent me from causing major breakage (hopefully there are now),
>>
>> Are there?  I concur with your recommendation that we should lock
>> this down *before* we set about repairing the master repo's contents.
>
> There are. I put them in, and I'm currently working on repairing the
> repo contents.

Ok, both repos *should* now be where they are supposed to be, per this
discussion.

AFAICT, pushing now works fine between primary and anonymous.

And yes, the cache purging appears to be broken *as well*. The reason
for that one seems to be that I forgot to update the port number for
cache invalidation when I moved it into production. Oops. That should
start working on the next commit that someone does.

But git:// access to anonymous and ssh:// access to master should both
work, and contain the complete and correct repositorires.

-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


-- 
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www