github ghc.git broken on libraries/binary

Shayne Fletcher shayne.fletcher at
Thu Mar 14 21:50:40 UTC 2019

Hi Ben,

On Thu, Mar 14, 2019 at 5:05 PM Ben Gamari <ben at> wrote:

> Shayne Fletcher via ghc-devs <ghc-devs at> writes:
> > I'm between a rock and a hard place here. I appreciate gitlab hosts the
> > official upstream (and at work use it extensively). We do however also
> > maintain a fork of the github mirror on github (rightly or wrongly) and
> its
> > existence and correctness is critical to some of our workflows.
> Hi Shayne,
> I have been working to resolve the issue. Unfortunately, the process has
> been complicated by the fact that GitHub has flagged our mirror account
> as a bot and the credentials of an older mirror account have been lost
> to history. I am engaging with GitHub to resolve this but this has taken
> longer than expected. I will leave updates on the tracking ticket [1] as
> the situation develops.
> In the meantime I have manually updated these GitHub mirror
> repositories. I will try to do this on a daily basis until the situation
> is resolved.
> > So, beyond this issue today which I assume to be temporary, going
> > forward can I assume no guarantees about its reliability and do I have
> > to advocate rejigging those aforementioned workflows so that github is
> > out of the picture?
> >
> In general the mirror is maintained and we have no intention of dropping
> it. However, in the last week other responsibilities, coupled with the
> latency of working with GitHub support, has meant that bringing it back
> online has taken longer than I would have preferred. Sorry for the
> inconvenience.

Not at all Ben. All totally understandable and I hope you know how much I
(we) appreciate how much you are doing for us! If I gave a different
impression in my original post, please be assured, that wasn't intentional

> However, do keep in mind that even when working normally the GitHub
> mirror has a synchronization period of 20 minutes; if your systems
> depend upon having a consistent picture of the GHC repositories then
> you might consider using the official upstream.

We can totally live with the synchronization lag in this instance. In
summary, I'm happy to leave things be with the understanding that stability
to will naturally improve and we just need to demonstrate some patience
while things get ironed out!

Thanks for taking time out to catch me up!

> Cheers,
> - Ben
> [1]
> iQEzBAEBCAAdFiEEmwpsh4C13+CdDZRjcVB86Evun78FAlyKwfcACgkQcVB86Evu
> n78CJQf/V19WmieWw6fs+rCSFEtfZvsQW+wFtDewqrpBgvW5hIC3Br3s032DCEUA
> nc8N3EteX9GExwNO7KkzCb/6vosmm9O7r+s3MQdY3CB69K0Yg3uXwfUXjttoneXB
> l65fIonx5pcgvVFsa2QLIyOmYUq3lpZg0MEQjtLBZBnWa2H4WylRyU3hIdmMQZui
> Ttt0TcJ4pWNGf3DgXU1EPD7FLdTkjlX2lptxh+r3uRzrqgGTSGCplOFJVk6ER8xA
> WqQho8lGz1DAuU2noezQZLDGR7dbhk7ZFUT2ycubNBi5UdSicoSW5H1zXZ+9vaJK
> 7vx1i3crhurIrjEcteKTLsmZBr4oWg==
> =gqDF

Shayne Fletcher
Language Engineer
c: +1 917 699 7763
e: shayne.fletcher at
Digital Asset Holdings, LLC
4 World Trade Center                                                        150
Greenwich Street, 47th Floor
New York, NY 10007, USA
<,+47th+Floor%C2%A0+%C2%A0+%C2%A0+%C2%A0+%C2%A0+New+York,+NY+10007,+USA&entry=gmail&source=g> <>

This message, and any attachments, is for the intended recipient(s) only, 
may contain information that is privileged, confidential and/or proprietary 
and subject to important terms and conditions available at 
<>. If you are not the 
intended recipient, please delete this message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the ghc-devs mailing list