Update: the production repositories are back and expected to remain up. JIRA, Confluence, and build services are currently expected to be up by some time tomorrow.
We'll continue to work on transitioning to the new infrastructure quickly. On Tue, Dec 18, 2012 at 09:51:49AM -0500, Michael K. Johnson wrote: > The infrastructure changes that have been posted in the news section > of the web site, on the planet, on G+, and discussed on IRC somehow > never made it to this list, for which I apologize. > > We are in the process of deploying a new cluster of systems for both > developer services and public repositories for Foresight and other > related Conary repositories. We're making good progress though more > slowly than we had anticipated. > > Yesterday, a network outage removed access to the existing build > cluster which includes the foresight-commits repository. Early > this morning, that outage extended to the production repositories > failing to respond to queries properly. Therefore, at this time, > system updates are not possible. Admins are investigating both of > these problems. > > At this point, we're intending to just bring up new developer services > as we can on the new cluster, and to set up production repositories > on the new cluster as soon as practicable. Other services will follow > shortly. > > Thanks for your patience. > _______________________________________________ > Foresight-devel mailing list > Foresight-devel@lists.rpath.org > http://lists.rpath.org/mailman/listinfo/foresight-devel _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
