=== zequence_ is now known as zequence
[08:06] <elfy> good morning channel - can anyone tell me when the iso tracker will get updated so I can let people know the url for beta final ? thanks
[08:07] <infinity> elfy: Sometime tomorrow (well, tomorrow for me)...
[08:08] <elfy> I hope you're west of me then :p
[08:09] <infinity> elfy: Western Canadia.  I suppose it's technically "later today", but it's all tomorrow until I've slept. :P
[08:09] <elfy> infinity: indeed :)
[08:09] <elfy> thanks
[08:40] <doko> Mirv, is it intended that that "CI Train PPA Service Team" PPA's build on powerpc?
[08:41] <Mirv> doko: unless something has changed, yes. didrocks ^
[08:41] <Mirv> so that there is no builds needed after copying to archives
[08:41] <didrocks> doko: it does, right
[08:41] <doko> hmm, ok
[10:40] <doko> pitti, jibel: please overwrite the ubuntuone-client autopkg test, blocks the zope.interface migration
[10:40] <pitti> doko: I can't, that needs to be done by ~ubuntu-release
[10:41] <pitti> Laney: ^ mind adding a nudge?
[10:54] <doko> pitti: is there a tag for failing autopkg tests?
[10:55] <pitti> doko: there's some ~u-r bzr branch which has these hints
[10:55] <doko> pitti: no just wanted to add a tag for a bug report I just filed
[10:56] <pitti> doko: ah; I'm using http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=autopkgtest;users=autopkgtest-devel@lists.alioth.debian.org for Debian
[10:56] <pitti> doko: for ubuntu, "qa-daily-testing" and "autopkgtest" will do
[10:59] <Laney> pitti: ok, can you file a bug about it?
[10:59] <pitti> Laney: ack
[11:01] <doko> Laney, pitti: lp: #1296656
[11:01] <ubot2> Launchpad bug 1296656 in ubuntuone-client (Ubuntu Trusty) "ubuntuone-client autopkg tests fail in trusty" [High,Confirmed] https://launchpad.net/bugs/1296656
[11:01] <Laney> nice, ty
[11:01] <pitti> ah, thanks; /me cancels the report he is filng
[11:03] <doko> and now reference this issue in update_excuses.html ...
[11:22] <doko> pitti, cjwatson: are update-excuses currently not updated?
[11:22] <pitti> indeed, apparently it's stuck
[11:24] <cjwatson> It's just very very very slow
[11:24] <cjwatson> The x264 update is blowing its mind
[11:27] <cjwatson> I could kill it, but I think it might be better to let it carry on and get the output
[11:32] <cjwatson> Since most of what the last run complained about seems to be fixed
[11:33] <pitti> cjwatson: ah, thanks for the heads-up
[11:34] <cjwatson> And then fix things as fast as we can so that we get past this transition
[11:46] <apw> cjwatson, by my "eye" measurement she is on the last couple of AYEEIs
[11:47] <cjwatson> I'll take your word for it :)
[11:48] <cjwatson> There've been more this time than last, though, so hard to say
[11:49] <apw> well she finished them for x264 sadly she now is unhappy about vlc
[12:42] <cjwatson> Good grief, it's still going
[12:49] <doko> all the "binNMUs" for x264 did succeed, at least all the ones I uploaded
[12:50] <cjwatson> Ah, it's into the copies now
[12:50] <cjwatson> Still lots of uninstallables here, let's see what excuses looks like when it finishes
[12:50] <Riddell> beta freeze happening today?
[12:51] <Riddell> infinity: ↑
[12:51] <elfy> Riddell: sometime later today he said earlier to me
[12:51] <Riddell> okay dokay
[12:59] <cjwatson> Ah, libav was waiting for autopkgtests
[12:59] <cjwatson> Hm, still is, wrongly
[13:00] <cjwatson> I'm going to kill this run and go through all the issues
[13:09] <cjwatson> At least libav is a valid candidate now, so that should help
[13:49] <cjwatson> phew, that managed to migrate x264
[13:50] <cjwatson> I've stopped p-m for a while so that it doesn't do anything else until the next publisher run has happened, otherwise the next run will take ages (probably much longer than the publisher)
=== caribou_ is now known as caribou
[14:04] <doko> why did it take that much time to calculate the x264 update? these just about 10-15 binNMU's ...
[14:14] <cjwatson> doko: lots and lots of uninstallables when not everything was migrated together
[14:14] <cjwatson> that sort of thing hits pathological cases
[14:15] <cjwatson> I don't know the internals of britney well enough to be able to do much about it
[14:15] <cjwatson> there's some deep magic there
[15:02] <cjwatson> p-m should be back to normal now
[15:04] <jamespage> release team question: how does feature freeze cover seed changes? if I want to add something to the server-ship seed do I need a release team ack?
[15:40] <doko> Laney, stgraber, please overwrite the pytables autopkg test, blocking python3-defaults. filed lp: #1296798
[15:40] <ubot2> Launchpad bug 1296798 in pytables (Ubuntu Trusty) "pytables autopkg tests failing (never did succeed in trusty)" [High,Confirmed] https://launchpad.net/bugs/1296798
=== rcj` is now known as rcj
[16:37] <jibel> doko, done
[16:37] <Laney> oh sorry, I saw this and then forgot
[16:43] <infinity> Hrm, is the mysql-5.5 autopkgtest really still running, or is britney confused?
[16:44] <infinity> jibel / pitti: ^
[16:44] <Laney> Jenkins thinks it's still running, AFAICS
[16:44] <pitti> infinity: it's still running
[16:44] <Laney> It shows that if you click "private"
[16:44] <infinity> Kay.  Long test.
[16:44] <jibel> last time I checked it was still running
[16:44] <infinity> Laney: Yeah, I never bothered to get the right bits set up to see the private instance.
[16:44] <pitti> 7:30 hours ago *sigh*
[16:44] <infinity> Mostly as a protest vote against HAVING private infra that impacts community process.
[16:44] <pitti> it looks like it's  hanging
[16:44] <infinity> Also, lazy.
[16:45] <jibel> infinity, still running, Ill kill it
[16:45] <pitti> and also it seems it disabled autopkgtests's timeout
[16:45] <infinity> pitti: Hung on both amd64 and i386, or just one?
[16:45] <pitti> infinity: aside from that, the flood got drained surprisingly well (with a few retries)
[16:45] <Laney> Yah. It's the only way to retry tests though, so I keep it set up.
[16:45] <pitti> infinity: on both
[16:46] <pitti> and it hung on the same test apparently on both arches
[16:46] <infinity> pitti: Kay.  Can't really be a product of my glibc upload, then, so I'll just XFAIL it in britney.
[16:47]  * pitti doesn't follow that conclusion, but we'll just retry it and see if it looks any different then
[16:47] <pitti> back then the machines were still clogged
[16:47] <infinity> pitti: My upload didn't change anything for the amd64 build.  I'd be suspicious if it was hanging only on i386.
[16:47] <pitti> ah
=== maclin__ is now known as maclin
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
[20:02] <stgraber> queuebot was moved to another box and from precise to trusty so let me know if it's acting up in any usual way
[20:03] <stgraber> (I had to fight with the LP credentials quite a bit, not entirely sure those actually work, we'll see when the next package hits the queue)
[20:07] <jdstrand> unless someone is looking at oxide-qt right now, I will do it
[21:03] <utlemming> stgraber: it looks like the SRU for walinuxagent went into the wrong proposed pocket...any chance you could move it?
[21:03] <utlemming> stgraber: it got dropped to precise-proposed/univerise instead of precise-proposed
[21:04] <utlemming> stgraber: and it didn't get built
=== ajmitch_ is now known as ajmitch
=== infinity changed the topic of #ubuntu-release to: Released: Trusty Beta 1 | Archive: Beta Freeze | Trusty Tahr Release Coordination.  Please don't upload things during freezes where you shouldn't, or be prepared to apologise to the release team | we accept payment in cash, check or beer | melior malum quod cognoscis
[23:54] <jtaylor> hi, can pytables be forced into trusty? the adt tests never succeeded and seem to be specific to the adt environment, the tests work fine on my machine