They migrated their servers from EngineYards to Rackspace and are catching up with the migration issues. I guess Apache repo synchronization is one of them.
On Thu, Oct 1, 2009 at 7:00 AM, Antoine Toulme <[email protected]>wrote: > I opened this discussion on Github support to sort it out: > > http://support.github.com/discussions/repos/1568-apache-buildr-mirror-is-out-of-date > > In the mean time, the official git mirror hosted by Apache works great. > > Thanks, > > Antoine > > On Thu, Oct 1, 2009 at 15:40, Daniel Spiewak <[email protected]> wrote: > > > Unfortunately, this sort of thing happens a lot. GitHub is the one who > is > > maintaining the mirror on their servers. They do this by polling the > Apache > > mirrors every half hour or so. However, it seems that their polling has > a > > tendency to get out of date or simply go offline for an extended period > of > > time. As a result, we have these frequent stretches where the GitHub > clone > > of the Apache mirror is outdated. > > > > Daniel > > > > > > On Oct 1, 2009, at 4:38 AM, "Antoine Toulme" <[email protected]> > > wrote: > > > > It looks like the Buildr mirror on github is outdated by 10+ days. > >> Does anyone know why that is happening ? It looks like the apache git > >> repository is ok though. > >> > >> Thanks, > >> > >> Antoine > >> > > >
