[11:28] <zequence> Could someone please approve above (ubuntustudio-meta). We can't build our ISOs without it
[16:02] <bdmurray> Could somebody fully phase ubuntu-release-upgrader for vivid?
[16:10] <flexiondotorg> bdmurray, Just out of interest, what does that mean?
[16:11] <rbasak> flexiondotorg: https://wiki.ubuntu.com/PhasedUpdates
[16:11] <flexiondotorg> rbasak, Thanks.
[16:11]  * flexiondotorg reads...
[16:11] <bdmurray> flexiondotorg: SRUs go through a phased update process and sometimes there are false positives.
[16:12] <bdmurray> http://www.murraytwins.com/blog/?p=127 that's a better explanation of how things really work
[16:16] <infinity> bdmurray: I have the technology.  I can make it happen.
[16:16] <infinity> bdmurray: When is your cronjob going to run?  I don't want to collide and disappear it.
[16:16] <flexiondotorg> bdmurray, Thanks for the educational materials.
[16:19] <infinity> bdmurray: Oh, it's at 0 right now, so I guess it was halted, and the cronjob won't touch it?
[16:19] <infinity> bdmurray: Confirm/deny? :P
[16:21] <bdmurray> infinity: The cronjob would only touch it if problem d2dd8d went away which it won't.
[16:21] <bdmurray> infinity: and the job runs as ubuntu-archive on snakefruit I think every 8 hours
[16:24] <infinity> bdmurray: Oh, that bin just collects every failure of do-release-upgrade due to dpkg exiting?  Ick.  Does anyone actually look at those to pick out the real bugs?
[16:24] <infinity> bdmurray: Also, phased to 100%.
[16:26] <bdmurray> Yes. No. Thanks!
[16:28] <infinity> bdmurray: Do we trap enough info in those cases to actually examine and *find* the real bugs, assuming someone has the time to do so?
[16:28] <infinity> bdmurray: The only I looked at just had the dpkg exit code, no useful logs, but maybe I wasn't looking in the right place.
[16:29] <bdmurray> infinity: Nope, and that's probably the real issue.
[16:30] <bdmurray> infinity: I'll dig into it a bit.
[16:31] <infinity> bdmurray: Cool.  I suspect the real issue will be a matter of time, but without any debugging info to work from, there's little motivation to even find time to look. :P
[16:32] <bdmurray> It'd also be better if we buckets with real counts to figure out where the actual problem lies.
[19:19] <tdaitx> doko, are you ok removing libecap3 from -proposed so I can ask someone to sponsor libecap2 gcc5 from LP: #1504200? the current squid 3.3 only works with with libecap2 (0.20), it does not work with libecap3 (1.0)
[19:19] <ubot93> Launchpad bug 1504200 in squid3 (Ubuntu) "libecap2 FTBFS due to gcc5 transition" [Undecided,New] https://launchpad.net/bugs/1504200
[19:20] <tdaitx> doko, this way we can at least fix squid 3.3 FTBFS... and I also have an update for it from 3.3.8 to 3.3.14
=== \b is now known as benonsoftware
[20:02] <slangasek> bdmurray: your latest MP seems to have the sssd commit in it
[20:03] <bdmurray> slangasek: Ah, okay. Fixing.
[20:07] <bdmurray> Could we have a wily-updates milestone?
[20:33] <doko> tdaitx, done, should be published in about 45 minutes
[20:37] <tdaitx> doko, thanks!
[21:15] <slangasek> bdmurray: done
[22:33] <bdmurray> slangasek: What was done?
[22:36]  * bdmurray figures out wily-updates was added
[22:36] <slangasek> yes that :)