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 HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
