News for hackers. Stuff that matters.
Re:Update on 1/28 service outage by chatmasta on Friday January 29, 2016 @01:32PM (#10997327)
If this is a problem worth solving, you can absolutely solve it. The easiest would be through the use of a caching proxy and/or load balancing system.

The caching proxy system could be as simple as setting up a squid cache for apt. Multiple projects exist which do this already.

The load balancing system would involve keeping a private mirror of every repository in the dependency graph, and falling back to the mirror when GitHub fails. To automate this, proxy all git requests. If github is up, let the request pass through. If no mirror exists for the repository, create one. If GitHub fails, fall back to the mirror.

Re:Update on 1/28 service outage by yeukhon on Friday January 29, 2016 @02:27PM (#10997815)
> The easiest would be through the use of a caching proxy and/or load balancing system.

Sorring if I sound like an asshole, but before we actually use the word "easiest", can you please share with us how to do all of that. It is not as easy as you claim, to be honest. Not just some /etc/hosts hijack.

Re:Update on 1/28 service outage by brazzledazzle on Friday January 29, 2016 @02:38PM (#10997903)
They didn't say it was easy, just that it was easiest. Ostensibly comparing it to other solutions that they are aware of.
Re:Update on 1/28 service outage by tylorr on Friday January 29, 2016 @02:43PM (#10997933)
For the load balancing system I would assume you would also want to keep the mirrors up to date as well? So for every request if mirror exists and is out of date, update it.
Re:Update on 1/28 service outage by chatmasta on Friday January 29, 2016 @02:45PM (#10997948)
Presumably that would be the responsibility of the mirroring system once a mirror is initiated.