[09:44] <ogra_> infinity, did you disable the system-image import job on nusakan in your hunt for the arm64 snappy issue ?
[09:44]  * ogra_ tries to find out why it was disabled 
[09:48] <infinity> ogra_: I don't know anything about any part of that sentence.
[09:48] <ogra_> lol, ok
[09:48] <ogra_> then i guess it was slangasek
[09:48] <infinity> ogra_: Unless by "the arm64 snappy issue", you mean the firewall issue.
[09:48] <infinity> ogra_: But I was just hunting firewalls, slangasek might have dropped the crontab bits.
[09:48] <ogra_> yeah, your conversation in the backlog starts with slangasek trying to enable arm64 builds
[09:49] <ogra_> i could imagine he switched off the importer for that ... then ran into the keyserver issue and forgot to switch it back on ...
[09:49] <infinity> Possibly.
[09:50] <infinity> He's on VAC this week, but if you yell loud enough, he might hear you.
[09:50] <ogra_> would really be nice to announce it here if he switches it off ..
[09:50] <ogra_> (we have some unwritten rule that we do this among all others that are able to disable it :) )
[09:51] <ogra_> aha, seems my manual run just finished
[09:51] <infinity> ogra_: I tend to announce when I'm disabling things.  Usually.  But that could mean either that he didn't announce or that he didn't turn it off. :P
[09:51] <ogra_> right
[09:55]  * ogra_ switched the importer back on now ... seems to have run fine
[11:25] <doko> infinity, can you overwrite/disable the taskcoach autopkg test?
[11:28] <infinity> doko: It did actually regress on Oct 26, would be nice to figure out what's up with that.
[11:28] <doko> infinity, tell that the debian maintainer, they disabled the autopkg test now
[11:29] <doko> just kept it for the last upload to see how it behaves in vivid
[11:32] <infinity> doko: Diffing the logs, it looks like the difference is that the successful one pulls in wx*2.8, and the failed one pulls in wx*3.0
[11:32] <infinity> doko: Half done transition, I guess?
[11:33] <doko> infinity, no, I tried reverting back to 2.8, didn't work either
[11:33] <infinity> doko: No, I mean the test deps pull in 3.0
[11:33] <infinity> doko: When the deps pulled in 2.8, it worked fine.
[11:34] <infinity> doko: So, maybe taskcoach needs to move to 3.0, now that other bits seem to have moved on.
[11:35] <doko> infinity, please don't speculate. if you are interested, please have a look at the sources
[11:37] <infinity> doko: Oh, I missed that you merged a new version a few days ago that uses 3.0.  Hrm.
[11:39] <infinity> doko: My speculation made more sense without that context.
[11:41] <doko> infinity, https://jenkins.qa.ubuntu.com/job/vivid-adt-zodb/ another one, always failing
[11:41] <doko> jibel, ^^^
[12:00] <flexiondotorg> I'd like to help an FFe get through. Who here can I discuss it with?
[12:38] <infinity> flexiondotorg: Which FFe?
[12:41] <flexiondotorg> infinity, https://bugs.launchpad.net/ubuntu-mate/+bug/1434412
[12:42] <flexiondotorg> Marcos has already got Folder Color in the 15.04 archive. Folder Color debuted in the 15.04 archive.
[12:42] <flexiondotorg> Ubuntu MATE is including it.
[12:43] <infinity> flexiondotorg: Does this affect anyone other than MATE?
[12:43] <flexiondotorg> Marcos has discovered he needed to change Folder Color to interact with icon themes correctly.
[12:43] <flexiondotorg> infinity, Nope. Not yet.
[12:43] <infinity> flexiondotorg: Then go for it.  Quickly.  Beta on Thursday. :P
[12:43] <flexiondotorg> infinity, How should I proceed?
[12:43] <flexiondotorg> Does someone need to approve the FFe?
[12:43] <infinity> flexiondotorg: I just did.
[12:44] <flexiondotorg> infinity, OK. Now what? Debdiff?
[12:44] <infinity> flexiondotorg: Uploads, ideally.
[12:44] <flexiondotorg> infinity, So I can ask the MOTU to do that?
[12:44] <infinity> flexiondotorg: *nod*
[12:44] <doko> tumbleweed, do you still track the python-cffi FFe?
[12:45] <flexiondotorg> infinity, Perfect. Thanks very much.
[13:38] <jamespage> please can the oslo-log uploaded to vivid NEW last month be rejected; I have a more Debian future-friendly version to replace it with.
[13:42] <infinity> jamespage: Done.
[13:42] <jamespage> infinity, thankyou
[13:43] <jamespage> zul, ^^
[13:43] <jamespage> uploading the revised one now
[13:43] <zul> jamespage:  ack
[13:49] <jamespage> that sync is under bug 1434526
[13:51] <jamespage> I also need a willing AA to deal with another oslo package required for OpenStack kilo-3 (oslo-policy)
[13:51] <jamespage> another refactoring into a shared common library
[13:51] <jamespage> (condition of the release team ack)
[13:51] <flexiondotorg> infinity, ubiquity-slideshow-ubuntu recently merge some Ubuntu MATE changes. Changes I really need to test in the next Beta.
[13:52] <flexiondotorg> infinity, Please can you direct me towards someone who could build a new ubiquity-slideshow-ubuntu package?
[13:52] <infinity> flexiondotorg: I'd ask cyphermox nicely, if I were you.
[13:52] <flexiondotorg> infinity, Thanks.
[14:05] <cyphermox> let me get this done nao
[14:08] <flexiondotorg> cyphermox, Thank you very much! :)
[15:08] <doko> hrm, what keeps gcc-4.8 in main?
[15:10] <cjwatson> http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.vivid/rdepends/ALL/gcc-4.8 -> gcj-4.8-jdk in supported-development-common seed, gcj-4.8-source in development seed
[15:10] <cjwatson> I see libstdc++-4.8-pic in the former and gcc-4.8-source in the latter too
[15:11] <doko> argh ...
[15:11] <doko> ok, didn't think about the seeds
[16:03] <doko> infinity, please can we get python-defaults into the release pocket?
[16:03] <infinity> doko: Yes.
[16:03] <Mirv> could the mesa 10.1.3-0ubuntu0.4 be released to trusty, it keeps on hitting people trying to install SDK on Ubuntu 14.04.2?
[16:04] <Mirv> the mlankhorst's proposed upload is now 11 days old
[16:05] <infinity> Mirv: Looking.
[16:06] <infinity> Mirv: Done.
[16:06] <Mirv> thank you!
[16:07] <Mirv> bzoltan_: ^ the SDK installability issue on 14.04.2 being resolved now(ish)
[16:33] <flexiondotorg> cyphermox, I see version 94. Thank you.
[16:34] <mlankhorst> goodie :)
[17:08] <rbasak> infinity: mysql-5.6 is pretty broken right now. I'll be uploading a fix shortly. "I will be freezing the archive later today" means that's OK, right?
[17:09] <infinity> rbasak: Yeahp.
[17:09] <infinity> rbasak: As the email noted, I intend to sleep before I freeze anything.
[17:09] <rbasak> Thanks
[18:43] <slangasek> ogra_: sorry - yes, I had disabled the cronjob because I was starting to clean up some of the phone channels, then I was down all weekend with a fever so didn't get it reenabled
[18:43] <ogra_> slangasek, can you try to remember to leave a note in the channel ?
[18:44] <slangasek> I can try
[18:44] <slangasek> :)
[18:55] <rsalveti> slangasek: or at least in the cron job :-)
[18:55] <rsalveti> hope you're feeling better today
[19:06] <sil2100> slangasek: hey! Shouldn't you be away resting btw.? ;)
[19:11] <balloons> infinity, when can we see a milestone for final beta?
[19:11] <infinity> balloons: When I do the builds $later.
[19:11] <infinity> Though, if someone wants to create the empty milestone now, I won't mind.
[19:11] <infinity> stgraber: ^ :)
[19:12] <infinity> stgraber: (One of these days, you need to show me if there's some QnD way to do that and I'm bugging you for no good reason)
[19:12] <stgraber> infinity: it's about 5 click in a web UI :)
[19:12] <infinity> stgraber: Today isn't that day, cause I need sleep between now and spinning images.
[19:12] <infinity> stgraber: FIVE?!
[19:12] <infinity> stgraber: Yeah, screw that.  Too many clicks.
[19:12] <stgraber> well, not exactly the most user friendly web UI :)
[19:13] <balloons> infinity, lol.. Just wondering on timing so I can tell folks to attack some images :-)
[19:13] <stgraber> infinity: did you turn off cron already? otherwise all daily builds will show up in the milestone
[19:13] <infinity> stgraber: It's pretty hostile, but at least it's not Jenkins?
[19:13] <infinity> stgraber: I didn't.  I will. :P
[19:13] <stgraber> oh yeah, it's beautiful and user friendly compared to Jenkins
[19:14] <infinity> stgraber: Alright, cron disabled.
[19:15] <stgraber> milestone ready
[19:15] <infinity> balloons: Images will be many hours out still, I'm waiting on a new kernel, need to force some things to migrate, do a d-i upload, and I need a nap before all that happens.
[19:16] <infinity> balloons: If there are people bored and wanting to test things, bugs reported against the last daily would still be worth knowing about.  Nothing particularly magical about the next image.
[19:17] <balloons> infinity, yes tis true. thanks for the heads up
[23:54] <slangasek> anyone else seeing debconf failures under update-manager in vivid?
[23:55] <slangasek> nothing that uses debconf in postinst is configuring successfully for me
[23:55] <slangasek> (and this is a recent regression, no more than a week or two since the last successful update)
[23:59] <slangasek> last successful update on 2015-03-18, which brought in a qt update and probably nothing that talked to debconf.  first failing update on 2015-03-20, which pulled in a lot of new packages, including glib2.0 which but nothing that would obviously account for debconf breakage