[00:03] <cjwatson> infinity: ^- could you do the honours?
[00:03] <cjwatson> infinity: (When you get a chance.  That does the lts-saucy bit.)
[00:26] <robru> cjwatson, infinity : poke about hud being blocked in -proposed. I don't understand the excuses page there, need some help / guidance
[00:29] <stgraber> robru: the build regressed on 3 architectures
[00:29] <robru> stgraber, well i doubt we care about the two ppc variants, but I'm unsure about arm64 (unsure how to fix it)
[00:30] <stgraber> robru: well, all of them used to build, so britney won't let the package migrated until they build again (or are properly dropped)
[00:31] <robru> stgraber, ok, thanks. i'm not very familiar with hud so I guess I'll punt this back to upstream
[00:31] <stgraber> technically they're not failing to build, they're missing a build-depend: unity-voice-service
[00:32] <cjwatson> Right, you don't have to build on all architectures if you never did, but you don't get to regress.
[00:33] <cjwatson> Hm, what's going on here
[00:33] <stgraber> hmm, apparently unity-voice-service exists now
[00:33] <cjwatson> OK, this isn't your or upstream's problem, it's just a component mismatch
[00:33] <robru> cjwatson, oh, can you fix it?
[00:33] <stgraber> ah yeah, just spotted it, I guess hud is in main, unity-voice is in universe
[00:33] <cjwatson> robru: looking
[00:33] <robru> cjwatson, thanks
[00:33] <cjwatson> just checking the MIR status and such
[00:34] <cjwatson> looks fine, promoting
[00:34] <robru> cjwatson, excellent, thanks
[00:34] <cjwatson> hud should auto-retry in an hour or two
[00:35] <stgraber> I'm just confused as to how the other architectures managed to build, did unity-voice-service somehow got demoted at the middle of the build?
[00:35] <cjwatson> publisher cycle plus hourly recheck-all-depwaits
[00:35] <cjwatson> stgraber: PPA
[00:35] <cjwatson> unity-voice would've been in the unity PPA and PPAs don't do components
[00:35] <stgraber> cjwatson: oh, yeah, forgot about that, naively assumed this was a good old standard upload :)
[00:35] <cjwatson> but they also don't do arm64/powerpc/ppc64el
[00:35] <cjwatson> (or at least this one doesn't)
[00:36] <robru> stgraber, yeah, i don't have upload rights, so if you ever hear from me in this channel it's bout something I pushed through the unity ppa with jenkins ;-)
[05:30] <ScottK> PPAs can be made to check components.  Seems like this would be a good candidate for it.
[07:37] <robru> cjwatson, hmmm, seems hud is still blocked. excuses page hasn't changed.
[08:55] <apw> robru, the builds look to have retried and now further wait on gsettings-qt which is in universe also
[09:03] <apw> robru, and it also has a dep on libdee-qt5-dev (source dee-qt) which is also in universe
[09:04] <apw> robru, which will make it fail once the first one is fixed
[10:37] <cjwatson> robru: Right, there are missing MIRs for dee-qt and gsettings-qt.  I can't promote those without MIRs.
[10:38] <Laney> ScottK: True
[10:40] <Laney> didrocks: ^ do you know if there's a reason the daily release PPA(s) doesn't build with that option?
[10:42] <didrocks> Laney: which option, only main? we have main and universe content in the ppa. People are normally running check-mir when they ack packaging changes
[10:42] <cjwatson> perhaps it would be worth finding out why that didn't happen in this case
[10:42] <didrocks> cjwatson: human error?
[10:43] <didrocks> I'll rehash the advice
[10:45] <cjwatson> fair enough except everyone else who commits human error tends to be asked by touch people to investigate :P
[10:46] <Laney> I guess people would be reluctant to promote to satisfy build-depends in a PPA
[10:46] <cjwatson> Maybe, we'd need to extend component-mismatches to support it, probably
[10:46] <didrocks> cjwatson: so, you want that I checked the logs and find the guilty guy? I thought you didn't like blame war
[10:49] <cjwatson> No, I don't; there's a difference between being able to give targeted advice to the right person (as opposed to general advice to everyone), and blaming them
[10:50] <cjwatson> "Hey - we noticed this problem.  Could you remember to use check-mir next time, which could help avoid this?"  or something
[10:50] <cjwatson> I'd also be fine with touch people not asking other people to trace through root causes so much, but it should be symmetric ;-)
[10:50] <didrocks> cjwatson: well, this is what I meant by rehashing the advice :)
[10:51] <cjwatson> OK, if you mean rehashing it to the person who forgot rather than by broadcast, sure
[10:52] <cjwatson> Anyway, hopefully no great harm done, it'll just stall hud until it's fixed
[10:53] <cjwatson> I see my breakage from yesterday is back to green now
[10:53] <didrocks> yeah, nice work! we are thinking about promoting the current image btw
[11:20] <Laney> slangasek: Did you get anywhere with finding a checklist person for A2?
[12:44] <xnox> didrocks: there is a tickbox of "build packages with all components, vs build with the same components as in the ubuntu archive" such that e.g. hud would be build with main only in the ppa, but universe stuff would be build with universe enabled.
[12:45] <didrocks> xnox: oh really? let me look
[12:46] <xnox> didrocks: sounds like that option needs enabling across all PPAs that eventually land in the archive, e.g. all non-virtualised ppas.
[12:46] <cjwatson> are you sure that the "universe stuff" wouldn't actually be considered as main within the PPA?
[12:46] <xnox> cjwatson: since the ppa itself publishes into main only? right....
[12:46] <cjwatson> or indeed that it wouldn't cause problems for builds of packages not yet in Ubuntu in that PPA, which are intended for universe?
[12:46] <didrocks> yeah, so if you have a build-dep published in the ppa, that can be a trouble
[12:46] <cjwatson> I'm just not sure that the cure wouldn't be worse than the disease here
[12:47] <xnox> cjwatson: didrocks: yeah, if the depwait in the ppa, no ppa options would help, as was the case here with hud =)
[12:47] <xnox> =(
[15:57] <slangasek> Laney: I did not get anywhere because I failed at asking
[15:57] <slangasek> ScottK, Riddell: are either of you interested in driving alpha 2 this time around?
[15:57] <sergiusens> didrocks, can you review goget-ubuntu-touch on the new queue for me please?
[15:57] <ScottK> No time.  Sorry.
[15:58] <didrocks> sergiusens: not really today. Is that in the new queue, not dailies?
[15:59] <sergiusens> didrocks, -queuebot/#ubuntu-release- New source: golang-goget-ubuntu-touch (trusty-proposed/primary) [0.1-0ubuntu1]
[15:59] <Riddell> slangasek: what's the dates?
[15:59] <slangasek> Riddell: Jan 23: https://wiki.ubuntu.com/TrustyTahr/ReleaseTaskSignup
[15:59] <didrocks> sergiusens: hum, I think it should be in the daily release process. Mind moving it to it?
[15:59] <didrocks> sergiusens: that enables us to preNEW and so on :)
[15:59] <sergiusens> didrocks, I would want it added to daily release (together with usensord), the upstream merger part is just now only capable of doing it's thing
[16:00] <didrocks> sergiusens: anyway, I will review it, but not before tomorrow
[16:00] <Riddell> slangasek: yeah I could do that, I'll add my name
[16:00] <slangasek> Riddell: cheers :)
[16:00] <Laney> Riddell: merci
[16:32] <sergiusens> didrocks, ty
[16:32] <didrocks> yw!
[19:21] <cjwatson> Riddell: ^- Did you mean to upload that PPA version to Ubuntu proper?
[19:23] <Riddell> doh
[19:23] <Riddell> nope, well caught
[19:23]  * Riddell rejects
[19:24] <Riddell> time to call it a day if I'm doing that
[22:42] <bladernr_> anyone around?  Can someone confirm that for Trusty, the final beta on Mar 27 is the likely release version assuming no major bugs?
[22:43] <bladernr_> IOW, the final beta released then should not see any real changes other than critical bug fixes discovered between final beta freeze and final freeze
[22:43] <knome> that's the *goal*, but nobody can promise that
[22:44] <bladernr_> yeah, I know it's always fluid, but at I just wanted to be sure i was correct in thinking that is how it "should" work in a perfect world
[22:44] <bladernr_> thanks knome
[22:44] <knome> yes, ideally that