[00:50] <xnox> kirkland.... oh not here.
[06:52] <didrocks> infinity: hey, how are you?
[08:34] <infinity> didrocks: Was that a trick question?
[08:35] <didrocks> infinity: can be seen as it, it's a small request regarding rt #63253 :p
[08:35] <didrocks> infinity: so that tvoss can debug Mir tests being stuck on armhf
[08:57] <infinity> didrocks: Looks like he got access to a porter.
[08:57] <didrocks> infinity: yeah, seems to be the case meanwhile. Let's cross fingers he can reproduce the hang on it
[09:01] <infinity> didrocks: Has it been happening on real hardware?
[09:01] <didrocks> infinity: I think the unity-team/daily-build-next are using distro builders, right? so on real hardware
[09:01] <infinity> didrocks: I've been cancelling hung mir builds in virtualized builders, I hadn't noticed it happening on devirt.
[09:02] <didrocks> infinity: oh, unity-team/daily-build-next isn't on real hw? unity-team/daily-build is though, right?
[09:02] <didrocks> (not talking about upstream ppa, I think they are on virtualized builders)
[09:02] <infinity> didrocks: They both might be.  I dunno.  Point me at the archive? :P
[09:02] <infinity> (The upstream PPA is probably where I've been killing builds)
[09:03] <didrocks> infinity: https://launchpad.net/~ubuntu-unity/+archive/daily-build-next
[09:03] <didrocks> (and https://launchpad.net/~ubuntu-unity/+archive/daily-build)
[09:03] <infinity> Ahh ubuntu-unity, not unity-team.
[09:03] <infinity> Way to confuse me. :P
[09:03] <didrocks> infinity: sorry, autotyping :)
[09:04] <cjwatson> stgraber: Seems reasonable enough in principle, though I had to think about some of the details a bit.  A test to ensure that the contents of .marked_good are sane would make me even happier. :-)
[09:04] <didrocks> I can't start anymore any work starting by "u" without writing "nity" now :p
[09:04] <cjwatson> I've been cancelling them in the upstream PPA too.
[09:04] <infinity> So, yeah, that's definitely on real hardware.  And the same hang they're seeing in the upstream builds, AFAIK.
[09:04] <cjwatson> Glad to know somebody's caring.
[09:05] <infinity> But this also means it's trivial to reproduce in a chroot with qemu-user-static, and definitely not hardware (or kernel) related.
[09:05] <didrocks> cjwatson: oh, i do care for 2 weeks already (multiple trials have been done)
[09:05] <didrocks> infinity: I just tried building on the phone TBH and cross pbuilder/sbuild
[09:05] <didrocks> but let's see what tvoss can get
[09:06] <infinity> Speaking of hanging builds... Yay, ruby-god not fixing its testsuite.
[09:09] <infinity> Maybe I'll upload a new version with "killall ruby" or similar in debian/rules after the testsuite runs. :P
[13:42] <stgraber> cjwatson: ok, I'll add tests and push it
[14:42] <bdmurray> could the SRU for bug 1199157 be released early?
[14:42] <ubot2`> Launchpad bug 1199157 in ubuntu-release-upgrader (Ubuntu Raring) "proposed should be disabled on upgrade to development release" [Medium,Fix committed] https://launchpad.net/bugs/1199157
[18:31] <bdmurray> slangasek: could we release the SRU for bug 1199157 early?
[18:31] <ubot2`> Launchpad bug 1199157 in ubuntu-release-upgrader (Ubuntu Raring) "proposed should be disabled on upgrade to development release" [Medium,Fix committed] https://launchpad.net/bugs/1199157
[18:32] <slangasek> bdmurray: I think so, yes
[18:34] <slangasek> (done)
[18:34] <bdmurray> thanks
[19:17] <stgraber> cjwatson: Added a test for .marked_good and pushed the change to nusakan. I'll make sure everything looks tomorrow once we have a new set of dailies
[20:37] <cjwatson> Oh yay, php5 upload, -proposed might clear
[22:54] <xnox> I believe byobu 5.46-0ubuntu1 can be rejected in raring-proposed unapproved queue with a hint "maintainer error, correct target was saucy". I've pinged kirkland and 5.47 version bump got uploaded into saucy