avsm changed the topic of #mirage to: mirage 2 released! party on!
thomasga has quit [Quit: Leaving.]
nojb has quit [Quit: nojb]
jonludlam has quit [Ping timeout: 250 seconds]
MrScout_ has joined #mirage
MrScout_ has quit [Ping timeout: 245 seconds]
brson has joined #mirage
so has quit [Remote host closed the connection]
nojb has joined #mirage
brson has quit [Ping timeout: 245 seconds]
avsm has joined #mirage
thomasga has joined #mirage
thomasga has quit [Client Quit]
nojb has quit [Quit: nojb]
avsm has quit [Quit: Leaving.]
mort___ has joined #mirage
yiannis_t has quit [Ping timeout: 276 seconds]
yiannis_t has joined #mirage
mort___ has quit [Quit: Leaving.]
andreas1 has joined #mirage
mort___ has joined #mirage
avsm has joined #mirage
andreas1 has quit [Quit: Leaving.]
andreas has joined #mirage
andreas1 has joined #mirage
andreas has quit [Ping timeout: 264 seconds]
<dsheets>
grrr travis is basically unusable today
<dsheets>
but neither github nor travis acknowledge that they have some sort of link failure between them
<dsheets>
what a productivity drain
<dsheets>
we gotta get rid of this asap
andreas1 has quit [Ping timeout: 256 seconds]
<avsm>
dsheets: yeah, status.github.com "it's all 100%!"
<dsheets>
well it could be on Travis's end because they fail to pull down PPA data, too
<dsheets>
avsm,
<avsm>
something's up with Ubuntu PPA mirrors I think
<dsheets>
why would that also cause package archives to fail?
<dsheets>
or do you think there are multiple issues?
<avsm>
yeah there's a dodgy travis http proxy, and dodgy PPA
<avsm>
but mostly bitrot, as Travis seems to be encouraging people to move to containers
<avsm>
which dont work for us :(
<avsm>
since you have to whitelist any packages from apt
<avsm>
the age of travis is indeed a little limited
<dsheets>
heaven forbid someone tries to build a test infrastructure on top of theirs and requires dynamic builds...
<avsm>
well, it is free, to be fair. we've probably done >20000 builds on it to date
<dsheets>
it's between getting github 1.0 out or working on test schedules
<avsm>
not bad going
<avsm>
am merging all the github prs atm
<dsheets>
sure, but this is a little mistaken, too -- we've been writing automation against their service and advertising it to our community so... that's their business model
<dsheets>
if we could keep building on them and integrating more tightly, we might and send them whatever commercial users decide to adopt the open source stuff
<dsheets>
at least, that's how i perceive their strategy
<avsm>
yeah, although I'm not sure how to do that. I'd be quite willing to spend money on Travis infrastructure, but they don't have a scheme
<avsm>
Last time I asked, that's what they said
<avsm>
ooh, 2FA support in GitHub PRs! nice
<dsheets>
2fa for token gen
<dsheets>
what do you mean no scheme? for private install or saas?