[04:22] <cjwatson> xnox: I fixed a syntax error in python3.4_all_dev.ben that was breaking the transition tracker (unmatched parenthesis).  Just removing the unmatched paren produced something nonsensical, so I guessed a bit at what it actually was supposed to be from the most recent commit; please review
[04:23] <xnox> cjwatson: looking. but it is actually doko__ who is growing number of underscores in his nick, and requesting that tracker.
[04:24] <cjwatson> xnox: fine, but you were the committer :-)
[04:27] <xnox> =))) touch-it-last strikes again...
[04:35] <cjwatson> if you're doing it on behalf of somebody else then you can always mention their name in the commit message, or use --author, or whatever
[09:58] <mlankhorst> poke, can someone accept all lts packages in NEW?
[10:11] <xnox> doko__: excellent =) now who is going to port unity & nux to glew 1.10? =)
[10:18] <mlankhorst> https://launchpad.net/ubuntu/precise/+queue?queue_state=0
[15:17] <doko> xnox, sorry, didn't know the reason why it was kept back :-/
[15:18] <xnox> doko: nevermind, i did the first round upload & nux/unity turned out to be trivial to fix =)
[15:18] <xnox> doko: as soon as arm64 catches up.... i'll look into finishing it off.
[15:19] <xnox> glew (42%) done as per transition tracker.
[16:15] <infinity> rtg: ^-- Guessing we want that for 12.04.4?
[16:16] <rtg> infinity, nah, its for v3.10+ kernels, e.g., the Trusty backport
[16:16] <apw> rtg, saucy is 3.11
[16:16] <infinity> rtg: Last I checked, saucy was 3.10+
[16:17] <rtg> oh, dyslexia reigns supreme this morning
[16:18] <rtg> infinity, lemme make really sure. I'll get back to you in  a bit.
[16:18]  * infinity goes to find some back to work breakfast.
[16:19] <infinity> rtg: Sure.  If we want it for 3.11, get someone to smoketest that the new files appear kinda sane and work with lts-saucy somehow, and we'll jam it through.
[16:50] <rtg> infinity, ok, I've determined that the iwlwifi 7K and 3K firmware updates will definitely affect the Saucy LTS kernel. The Brocade bits should have no impact on v3.11
[17:26] <zul> how does syncs get processed btw?
[17:36] <infinity> zul: That question needs more context to know what you're actually asking.
[17:37] <zul> infinity:  sorry i was talking about libvirt-python from debian
[17:42] <xnox> zul: like so ^ =)
[17:42] <zul> xnox:  yeah thanks
[17:43] <infinity> zul: To be fair, it all would have happened automatically, if you waited for an autosync.  But yeah, if you sync something NEW explicitly, we need to process it like any other NEW package, except that we don't bother reviewing it if it's obviously a straight Debian sync.
[17:46] <zul> infinity:  coolio
[18:25] <utlemming> has the 13.04 EOL been announced yet?
[18:26] <utlemming> All I've seen is that it is sometime in January, but no date.
[18:32] <infinity> utlemming: D'oh.  I should have sent out an announce during the break, probably.  I'll get to that later today.
[18:35] <mlankhorst> infinity: hey can you accept mesa binaries?
[18:35] <mlankhorst> mesa-lts-saucy in precise
[18:36] <infinity> mlankhorst: I'll look at all the LTS userspace stuff this afternoon if no one beats me to it.  Just dealing with kernels right now.
[18:39] <mlankhorst> infinity: just accept the binaries, after that xorg-server can build and you can tell everything that's left to build :-)
[18:42] <infinity> mlankhorst: Fiiiine.  Just had to make sure it was all destined for main first, etc.