[10:23] <tjaalton> halp, need someone to approve mesa & mesa-lts-quantal
[10:24] <mlankhorst> HALPPP PLXX
[10:27] <infinity> On it.
[10:28] <tjaalton> :)
[10:28] <tjaalton> thanks
[10:28] <tjaalton> I'll do the same for raring
[10:29] <infinity> mesa-lts-quantal's changelog history seems to have gotten mangled.
[10:29] <tjaalton> we don't care about that
[10:29] <tjaalton> it's scripted
[10:30] <tjaalton> the changelog should have everything via the quantal "upstream"
[10:30] <tjaalton> the latest one just adds ~preciseN
[10:30] <mlankhorst> sec
[10:31] <tjaalton> of course this is the first time I'm on this, so could have messed things
[10:31] <mlankhorst> you did mess up
[10:31] <mlankhorst> :P
[10:31] <tjaalton> damn
[10:31] <tjaalton> how?
[10:31] <mlankhorst> tjaalton: https://launchpadlibrarian.net/144071101/mesa-lts-quantal_9.0.3-0ubuntu0.3~precise1_9.0.3-0ubuntu0.4~precise1.diff.gz
[10:32] <mlankhorst> that's why lts-pkg-rename takes an argument to the old stack dir
[10:32] <tjaalton> oh
[10:32] <mlankhorst> but just fix it up manually
[10:32] <tjaalton> so you did have those
[10:32] <tjaalton> *keep
[10:33] <mlankhorst> yeah, just the ones in release, the ubuntu0.3 one never left NEW so I don't care about it
[10:33] <mlankhorst> but you wiped the original LP bug entry
[10:34] <tjaalton> the diff doesn't show 0.3
[10:34] <tjaalton> oh I see
[10:34] <mlankhorst> still shows up in the changes file though, so meh..
[10:34] <tjaalton> I'll merge that too then
[10:34] <infinity> What do you mean "0.3 never left NEW"?
[10:34] <tjaalton> infinity: ok I'll fix it up
[10:34] <infinity> It's in -proposed.
[10:34] <tjaalton> it's in NEW
[10:34] <infinity> Oh, it's in binary NEW, sure.
[10:34] <infinity> I can fix that. :P
[10:35] <mlankhorst> hehehe
[10:35] <tjaalton> you could fix xserver-xorg-video-intel-lts-quantal still being there :)
[10:35] <mlankhorst> yeah I hate this stuff
[10:35] <tjaalton> I'll fix the changelog and reupload, feel free to reject the current one
[10:35] <mlankhorst> dual-level changelogs suck
[10:35] <tjaalton> right, two steps to bug the archive admins
[10:35] <tjaalton> that too
[10:37] <mlankhorst> infinity: xxv-intel-lts-raring is in unapproved, can you accept it too?
[10:45] <infinity> mesa-lts-raring also seems to have a vaguely confused changelog, but maybe that one's unavoidable, I dunno.
[10:47] <mlankhorst> sadly no way out
[10:48] <mlankhorst> it had to close the original bug too
[10:50] <tjaalton> ok new version uploaded
[10:55] <tjaalton> meh, mesa 9.1.4 needs an sru bug
[11:51] <doko> cjwatson, removed all the binaries built with gdc-v1 on powerpc. except for plplot, which ftbfs for qt reasons currently
[11:52] <doko> and cleaned up the lib*-ruby binaries
[11:52] <cjwatson> armhf too?
[11:54] <doko> there were none
[11:54] <doko> that was gcc-4.4 based
[12:20] <xnox> infinity: https://launchpad.net/ubuntu/+source/gnuradio/3.6.5.1-1ubuntu1/+build/4766558 is dead, can that build be done on the fast one? (sagari?!)
[12:23] <infinity> xnox: I don't imagine speed will help it much, but it could be tried.
[12:23] <cjwatson> doko: There are certainly some out-of-dates on armhf from the set of packages we were talking about.
[12:37] <infinity> xnox: Retried on sagari.  Good luck.  Maybe I should bump the timeout back up a bit.  That said, a build that produces no output for 60m isn't ideal.
[12:39] <xnox> infinity: it only took 27minutes to build on amd64....
[12:40]  * xnox likes the build score of 99999999
[17:13] <jbicha> who should I ask politely to review mozjs17 in new?
[19:14] <Laney> hmm
[19:14] <Laney> Could it be that proposed-migration is forgetting about failed tests?
[19:14] <Laney> I just uploaded glib2.0 and some rdep autopkgtests definitely did fail - colord and firefox are two examples. They were on excuses as FAILED but now they're not there.
[19:17] <ScottK> Did someone override the results?
[19:20] <Laney> firefox is, yeah, but not colord as far as I can see
[19:20] <Laney> wait, I can't remember which way around the force-footests are
[19:21] <ScottK> Did you see the new way to do it (-release)
[19:21] <Laney> I only know force-badtest force-skiptest
[19:21] <ScottK> Thos.
[19:21]  * Laney nods
[19:21] <ScottK> Those even
[19:22] <ScottK> badtest means skip that test for all cases since the test is bad.
[19:22] <Laney> OK, so firefox is skipped then
[19:22] <ScottK> skiptest means don't trigger tests for this package, skip them because we want it in -release ASAP.
[19:22] <Laney> but still colord.
[19:22] <ScottK> Dunno
[19:23] <ScottK> Maybe it's bug.  Not sure how cjwatson tested it.
[19:24] <Laney> Not gonna complain if it lets it migrate. ;-)
[19:34] <jibel> Laney, "forgotten failed" is a bug. I have a fix that will be pushed tomorrow morning.
[19:35] <ScottK> Laney: Quick, upload today.
[20:47] <slangasek> Laney: forgetting failed tests> yes, cjwatson mentioned something about that today
[20:48] <slangasek> right, jibel said already
[20:48] <Laney> slangasek: yeah, jibel just confirmed
[20:48] <Laney> :-)