[00:07] <cjohnston> josharenson: I am.. any chance we can chat tomorrow?
[00:11] <josharenson> cjohnston, sure im GMT-8
[00:14] <cjohnston> josharenson: im east coast. just ping me when you come around
[00:16] <josharenson> cjohnston: thanks
[04:09] <Mirv> morning
[07:04] <vila> retoaded: nagios alert on 10.98.191.23 which is not referenced on https://wiki.canonical.com/UbuntuEngineering/CI/Lab (so I have no idea what this host is about), I won't worry about it but may be you will ?
[07:24] <vila> retoaded: hmm, could  10.98.191.23 be one of the VMs for s-jenkins ? It seems a lot of jobs are pending there and all VMs are offline. That seems related to your latest email about the wraith fallouts for naartjie
[08:19] <Mirv> I wonder if anyone has opinion on possible downsides of disabling -Bsymbolic on armhf (or actually any non-x86)? bug #1304709
[08:20] <Mirv> upstream has made the change in 5.3.0 anyhow
[08:23] <Mirv> oh, now looking at the bug report it reminds me seeing cjwatson & co discussing it earlier. so I wonder if mandel's bug could be workarounded with the dee-qt's "-pie -fPIE" too.
[08:23] <Mirv> (the upstream bug report https://bugreports.qt-project.org/browse/QTBUG-36129)
[08:24] <cjwatson> Disabling -Bsymbolic on armhf has potential significant performance effects for process startup, so I think we should try to avoid it if we can
[08:25] <cjwatson> Or rather -Wl,-Bsymbolic-functions, I guess you mean
[08:26] <Mirv> "-Bsymbolic*", the patch bypasses a test that would add them. well in that case I think we'll need a bug to remind us to patch that change _out_ of 5.3.0 when the time comes.
[08:27] <cjwatson> Perhaps worth verifying my intuition about what effect it actually has
[08:28] <cjwatson> But Qt seems like exactly the sort of hot spot that -Bsymbolic-functions is best at
[08:32] <didrocks> sil2100: davmor2: popey: coming?
[08:32] <sil2100> Yes, logging in
[08:32] <didrocks> psivaa: you as well?
[08:33] <psivaa> didrocks: sorry could you give me the link pls?
[08:33] <didrocks> sure
[08:33] <didrocks> https://plus.google.com/hangouts/_/canonical.com/landing-meeting
[08:33] <Mirv> err what happened to my hangout
[08:33] <psivaa> didrocks: thanks
[08:40] <Mirv> so I marked the four in queue packages as tobechecked
[08:43] <sil2100> Aaargh, mail ;/
[08:43] <sil2100> Curse you mailman!
[08:43] <sil2100> didrocks: what's the channel with the bot again?
[08:43] <didrocks> sil2100: #ubuntu-ci-choo-choo
[08:43] <sil2100> ...;p
[08:43] <sil2100> :P
[08:44] <didrocks> Mirv: are you sure the QA team is checking? I think they are not anymore
[08:44] <didrocks> Mirv: mind double checking if they check? :)
[08:44] <davmor2> popey: do you have a 5Ghz network?
[08:44] <Mirv> didrocks: I mean "to be checked" by us, the status of those unapproved items
[08:44] <popey> davmor2: dunno, how will i tell? ☻
[08:44] <popey> (I think I do)
[08:44] <sil2100> Mirv: thanks! ;)
[08:45] <Mirv> so for example I SRUfied now bug #1297297 since it's already in proposed. the other three items in UNAPPROVED would need double-checking from the authors if they are ok with them landing to U instead (ask the packages to be rejected) or if they want them SRUed
[08:45] <davmor2> popey: at some point you would of set 2 id's for the network one as popey and one as popey 5g or they clash :D
[08:46] <popey> i have the same essid for 2.4 and 5
[08:46] <davmor2> popey: interesting mine clashed when I did that
[08:46] <popey> further confounded by the fact that I have two access points
[08:46] <popey> both with the same ESSID, so effectively four networks
[08:47] <popey> tempted to change them to popey_2.4 and popey_5g so it's easier to spot
[08:47] <Mirv> dbarth: your webbrowser-app landing had the bugs already SRUfied, thanks! I just nominated the bugs for trusty as well.
[08:47] <didrocks> Mirv: ah ok ;)
[08:47] <davmor2> popey: can you try and connect strictly to the 5g one and see if osm gives you a location
[08:47] <sil2100> Mirv: let's divide work then
[08:47] <Mirv> sil2100: yeah could you then maybe check the bfiller's and boiko's landings?
[08:48] <sil2100> Mirv: I take bfiller's one
[08:48] <sil2100> Ok
[08:48] <popey> davmor2: ok, will take a while, lemme change network names now ☻
[08:57] <sil2100> Mirv, didrocks: so the landings from bfiller and boiko have either no bugs assigned or not SRUed at all - I'll poke the authors and/or landers if they want to proceed with SRUifying them or rejecting and waiting for U
[08:57] <didrocks> sil2100: thanks!
[08:58] <Mirv> sil2100: thanks!
[09:00] <dbarth> Mirv: thank you
[09:01] <dbarth> yes, we did our homework to go into -updates
[09:02] <popey> davmor2: http://popey.com/~alan/phablet/device-2014-04-23-100233.png
[09:02] <popey> ⍨
[09:03] <popey> its confused, rebotting
[09:23] <mandel> cjwatson,  Mirv I did use -pie and fPIE to fix the issue and it worked like a charm
[09:46] <mandel> didrocks, is there a way I can take the training to help with the ci train in my team, that way we have sergio in the American time zone and me in CET
[09:47] <didrocks> mandel: yeah, we extended the list on demand. But we don't offer anymore training for now. You should coordinate with some other landers to get some hint (it's pretty easy). When you are ready, I can then just add you to the team
[09:47] <mandel> didrocks, awesome, I'll speak with sergio then :)
[09:48] <didrocks> great ;)
[09:48] <didrocks> keep me posted!
[09:54] <didrocks> Saviq: seb128: so, the bot CI Train is now in beta ;) you can join #ubuntu-ci-choo-choo if you are interested
[09:55] <didrocks> you can inspect status, and get notification when it makes sense to you
[10:07] <davmor2> popey: sadtrombone.com
[10:11] <Chipaca> can somebody here give me a hand with three bugs I'm wanting to shepherd through SRU?
[10:12] <Chipaca> I'm at “Ask the Ubuntu bug control team to nominate the bug for the appropriate Ubuntu release(s)/series (e. g. the current LTS and latest stable release).”
[10:12] <Chipaca> I'm on that team, but am unsure how to nominate a bug :)
[10:13] <Chipaca> bugs are: https://bugs.launchpad.net/ubuntu-push/+bug/1297969 https://bugs.launchpad.net/ubuntu-push/+bug/1309237 https://bugs.launchpad.net/ubuntu-push/+bug/1309231
[10:16] <NoNameYet_xnox> Chipaca: done
[10:16] <cjwatson> You need to access it through the /ubuntu/+source/ubuntu-push/ hierarchy rather than /ubuntu-push/
[10:17] <cjwatson> Then you get a "Nominate for series" or "Target to series" link, depending on your privilege level
[10:17] <Chipaca> i get "target"
[10:17] <Chipaca> to milestone
[10:17] <Chipaca> og!
[10:17] <cjwatson> Not that
[10:17] <Chipaca> oh! nominate to series
[10:17] <Chipaca> for*
[10:18] <cjwatson> Right
[10:18] <Chipaca> ok :)
[10:18] <Chipaca> hadn't seen that before :D
[10:18] <Chipaca> s/seen/noticed/
[10:18] <Chipaca> anyway. Thank you, NoNameYet_xnox
[10:18] <cjwatson> But you have to be going through the distribution URL namespace
[10:18] <Chipaca> cjohnston: right. Ta.
[10:18] <Chipaca> and now... i ask to have it landed?
[10:18] <Chipaca> given that next step is "put it into proposed"
[10:19] <NoNameYet_xnox> Chipaca: yeap. all three look good to go into -proposed unapproved queue.
[10:19] <Chipaca> now, i've got a row with all of them fixed all together
[10:19] <NoNameYet_xnox> Chipaca: also subscribe "~ubuntu-sru" to all three.
[10:19] <Chipaca> do i need to do three separate rows/builds/etc?
[10:20] <NoNameYet_xnox> Chipaca: it can go as a single build. it's just it will only be promoted to -updates once all three bugs pass verification.
[10:20] <Chipaca> sweet
[10:21] <Chipaca> sil2100, Mirv, didrocks, could i have a landing (into ... "proposed unapproved"? if that's a thing from your pov) of row 24?
[10:22] <Chipaca> NoNameYet_xnox: this is in universe; is it still ubuntu-sru?
[10:23] <NoNameYet_xnox> Chipaca: yes.
[10:23] <NoNameYet_xnox> Chipaca: all processes are the same for the whole archive.
[10:23] <sil2100> Chipaca: we can try pushing it as an SRU if you want
[10:23] <Chipaca> sil2100: that's what I'm aiming for, yes
[10:24] <Chipaca> sil2100: hence the paperwork on the bugs
[10:25] <sil2100> Chipaca: ok, so I see still 2 bugs requiring description SRUification ;)
[10:25] <Chipaca> sil2100: which ones are they?
[10:26]  * Chipaca looks
[10:26] <sil2100> Chipaca: it's https://bugs.launchpad.net/ubuntu-push/+bug/1309432 and https://bugs.launchpad.net/ubuntu/+source/ubuntu-push/+bug/1308145 it seems
[10:26] <Chipaca> yep
[10:26] <Chipaca> forgot about those less-than-zomg-urgent ones :)
[10:26] <Chipaca> on it
[10:27] <sil2100> Thanks :) !
[10:29] <sil2100> Chipaca: I already nominated the bugs and subscribed sru team
[10:30] <Chipaca> sil2100: ta
[10:31] <sil2100> Chipaca: there's one change in the changelog that doesn't mention a bug number... could you elaborate a bit about that change? Since I need to assess if it can be pushed alongside an SRU
[10:32] <sil2100> Chipaca: I mean the change for: "gave the client the ability to get config from commandline (...)"
[10:32] <sil2100> From Samuele
[10:32] <Chipaca> sil2100: I was a bit lazy, there
[10:32] <Chipaca> the merge was easier that way
[10:32] <Chipaca> sil2100: where should i elaborate?
[10:33] <Chipaca> (there are better reasons than just my laziness)
[10:33] <sil2100> Ah, hm, since we normally only SRU fixes or small modifications - I see the commit is a bit biggish - is it something that's required by the other fixes?
[10:34] <sil2100> I'm simply worried that the SRU team might find this inappropriate or somethin
[10:34] <sil2100> g
[10:36] <Chipaca> sil2100: you know how in all the SRUs i'm having to edit the config file? that change makes it possible to just add a commandline flag instead
[10:36] <Chipaca> sil2100: testing (especially telling other people to test) becomes a lot easier
[10:36] <Chipaca> that was my rationale for it, anyway
[10:37] <Chipaca> sil2100: when you say the commit is big, you mean for that change, or overall?
[10:37] <sil2100> Chipaca: what's the regression potential of that change?
[10:37] <sil2100> Chipaca: I meant that one change - it's big in the sense of 'big as for something that's not related to a bug being fixed for the SRU'
[10:37] <sil2100> ;)
[10:38] <Chipaca> sil2100: if somebody has a corrupt upstart thing that happens to be working now, this would break it
[10:38] <Chipaca> or otherwise has rubbish after the push-client command
[10:38] <Chipaca> that's now looked at and complained about
[10:39] <Chipaca> I could roll it out of the patchset if it's a problem
[10:39] <sil2100> Chipaca: let's consult it with someone from the SRU team
[10:39] <Chipaca> having to explain it underlined how weak a reasoning it was, really :)
[10:40] <sil2100> cjwatson: hi Colin, do you have a moment to help us evaluate an SRU situation?
[10:40] <Chipaca> (i still think it's nice to have and low risk, si yes)
[10:40] <Chipaca> so*
[10:40] <sil2100> Chipaca: yeah, I also would prefer not to remove it unneccesarily
[10:40] <Chipaca> anyway, back to editing bug descriptions
[10:40] <cjwatson> I don't have a problem with the above if it makes it easier to test SRUs
[10:41] <sil2100> o/
[10:41] <sil2100> cjwatson: thanks :)
[10:41] <cjwatson> But expect to have to roll it back if the regression potential turns out to be actual
[10:41] <sil2100> cjwatson: should we create a 'bug' for that one and indicate the bug number in the changelog, or can we simply leave the changelog entry alone?
[10:41] <sil2100> (with no bug assigned for that 'testing enhancer')
[10:42] <Chipaca> the diff itself is https://code.launchpad.net/~pedronis/ubuntu-push/client-takes-cmd-line-flags-as-well/+merge/215617 and its prerequisite, if that's any use in the conversation
[10:42] <cjwatson> It would be helpful to have a bug just in case we discover that it regresses independently from the rest
[10:42] <sil2100> cjwatson: ok, thanks o/
[10:42] <Chipaca> cjwatson: ta. Will file.
[10:43] <sil2100> Chipaca: so, could you create a bug for that commit, mention the regression potential there (according to the SRU guidelines) and attach it to the changelog?
[10:43] <sil2100> Chipaca: I could create the bug for you, but I guess you know best what exactly that commit does
[10:43] <Chipaca> yep
[10:43] <sil2100> Thank you :)!
[10:43] <Chipaca> updated description for https://bugs.launchpad.net/ubuntu-push/+bug/1309432
[10:54] <Chipaca> and updated the description for https://bugs.launchpad.net/ubuntu/+source/ubuntu-push/+bug/1308145
[10:54] <Chipaca> (that was a lot of typing)
[10:54] <Chipaca> (I'm leaving "supurious" because it's my favorite neologism)
[11:03] <sil2100> ;)
[11:04] <sil2100> Chipaca: looking awesome - now just that new bug for that enhancement and we're good to do some publishin'
[11:04] <Chipaca> https://bugs.launchpad.net/ubuntu/+source/ubuntu-push/+bug/1311600
[11:04] <Chipaca> sil2100: ^
[11:04] <sil2100> Chipaca: fast! Thanks, nominating
[11:06] <sil2100> Chipaca: can you append (LP: #1311600) to the changelog of that branch? We'll have to re-build though, but it will be fast as no re-testing will be required
[11:06] <Chipaca> sure, give me a bit
[11:10] <Chipaca> sil2100: build failed, looking for the "ignore" button :)
[11:11] <Chipaca> sil2100: hmm. It doesn't like me.
[11:14] <didrocks> Chipaca: yeah, this is to prevent you shooting on your feet
[11:15] <didrocks> (once you get a successfull build, you don't want to rebuild most of the time and people misclicked)
[11:15]  * Chipaca likes his feet
[11:15] <didrocks> Chipaca: the error message doesn't help you? :)
[11:18] <sil2100> Chipaca: just run the build job with ubuntu-push as the packages to rebuild ;)
[11:18] <sil2100> No other flags should be needed
[11:18] <Chipaca> mucho bettero!
[11:19] <Chipaca> didrocks: the error message told me to run it again with "ignore"
[11:19] <didrocks> Chipaca: yeah, and you rerun with "force rebuild"
[11:19] <Chipaca> https://ci-train.ubuntu.com/job/landing-008-1-build/49/console
[11:19] <didrocks> not "ignore step"
[11:20] <Chipaca> this is true
[11:20] <didrocks> Chipaca: I'm happy to take any better/more clear wording
[11:20] <Chipaca> in my defense, i did that because i read the descriptions on those options, and the ignore sounds like it ignore things if the force doesn't work
[11:21] <Chipaca> oh!
[11:21] <Chipaca> oooh
[11:21] <Chipaca> didrocks: s/ignore if/ignore whether/ and i would've probably understood
[11:21] <didrocks> Chipaca: changing! thanks :)
[11:21] <Chipaca> didrocks: and has, not hasn't, with whether
[11:22] <Chipaca> negaitve logic breaks my brain a bit i'm afraid
[11:22] <didrocks> :)
[11:41] <Chipaca> sil2100: packages built
[11:41] <sil2100> Chipaca: \o/ Lookint at that, thanks!
[11:45] <sil2100> Oh noes!
[11:45] <sil2100> :<
[11:46] <Chipaca> sil2100: what?
[11:46] <sil2100> Chipaca: bad news, we'll have to rebuild again :< The changelog mentions (LP: #216466) as the bug number, which is some other bug (not the one you filled in)
[11:46] <sil2100> Chipaca: it should be (LP: #1311600)
[11:46] <Chipaca> what
[11:46] <Chipaca> where did that come from :-(
[11:46] <sil2100> Chipaca: https://launchpad.net/~ci-train-ppa-service/+archive/landing-008/+sourcepub/4100678/+listing-archive-extra <- :<
[11:47] <Chipaca> i can't even copy and paste
[11:47] <sil2100> Happens to everyone, no worries ;p
[11:47] <Chipaca> i'll go get a mug of coffee and shame, and do it over
[11:47] <Mirv> a random copy paste mangler easter egg would be fun
[11:47] <ogra_> that would require working copy paste, no ?
[11:47] <sil2100> ;p
[11:48] <sil2100> Chipaca: I'm only sad because now you'll have to wait for it to build again!
[11:49] <sil2100> I would always prefer that our landers have a swift landing with good memories of it ;p
[11:49] <Mirv> so there's some motivation for implementing a working copy paste.. with a twist
[11:49] <sil2100> Mirv: please, don't! Or someone will actually implement what you wish for!
[11:49] <sil2100> ;p
[11:51] <Chipaca> ogra_: not if "mangle" means "paste some bytes from /dev/urandom"
[11:51] <ogra_> heh
[12:01] <Chipaca> ogra_: trying to decide whether "shuf -n1 /usr/share/dict/words" or "fortune -os -n 15" would be better paste replacement
[12:02] <ogra_> thats lame, you should pull random words online and call it "cloud integrated pasting"  ;)
[12:04] <sil2100> Chipaca: I see it's basically built, I should be able to publish soon :) Looks good so far
[12:17] <Chipaca> sil2100: \o/
[12:21] <sil2100> Chipaca: published! Let's now make sure the it doesn't get missed by the SRU team :)
[12:21] <Chipaca> sil2100: how do I do that?
[12:21]  * Chipaca opens up international-pizza-delivery.com
[12:21] <sil2100> Chipaca: we'll be poking around, now worries
[12:21]  * Chipaca closes it again, that stuff is expensive
[12:21] <sil2100> Nagging people in your stead ;p
[12:21]  * Chipaca hugs sil2100 
[12:21] <Chipaca> thanks :)
[12:23] <sil2100> Chipaca: yw! Thanks for doing the paperwork :)
[12:27] <Chipaca> i won't lie, i hate the paperwork
[12:27] <Chipaca> at the same time i understand why it's there, so... :-\
[12:55] <popey> davmor2: I can't actually get on 5Ghz here! I have deleted all network manager system-connections and rebooted, and it just keeps asking for the password
[13:07] <davmor2> popey: oh dear
[13:07] <davmor2> popey: works fine here
[13:07] <popey> davmor2: i have connected to a 5G connection at someone else's house with it
[13:07] <popey> but can't get on mine
[13:07] <popey> no idea why
[13:08] <ogra_> popey, tried different channels ?
[13:09] <ogra_> (on the AP side)
[13:14] <popey> ogra_: will fiddle
[13:14] <davmor2> popey: 	Auto (Current channel 36) seems to work fine for me I don't know if that helps any at all
[13:15] <popey> ta
[13:15] <popey> mine is on 36 too
[13:15] <popey> "N Only (5Ghz)"
[13:15] <ogra_> well,  its also a matter of overlapping them with different APs
[13:15] <ogra_> especially if you have different speeds there
[13:15]  * popey switches to "mixed"
[13:18] <popey> popey.mooo.com/screenshots/device-2014-04-23-141802.png
[13:18] <popey> wtf
[13:18] <popey> tried connecting to 5ghz, it failed and dropped back to 2.4
[13:18] <popey> now shows a button next to both
[13:19] <ogra_> lol
[13:19] <ogra_> whats that last one
[13:19] <ogra_> unfriendly neighbors
[13:20] <davmor2> popey: yeah and you think I live in a rough neighbourhood don't get none of that here I'll have you know. (Too thick to change the defaults normally, but shhhhh)
[13:22]  * Saviq wants U :|
[13:23] <josepht> Unholy Uguisu
[13:28] <sil2100> bfiller, boiko: hi guys! I'd like to ask some questions regarding your landings
[13:29] <davmor2> josepht: you mean it not unkind unicorn
[13:29] <boiko> sil2100: sure
[13:29] <sil2100> bfiller, boiko: so, first of all a question regarding the two ones that are published and blocked in UNAPPROVED - they either have no bugs assigned or those bugs are not SRU-ready
[13:30] <sil2100> bfiller, boiko: so the question is:
[13:30] <josepht> davmor2: Uni-horned Unicorn? :)
[13:30] <boiko> sil2100: yeah, well, last week I asked if I should do anything regarding the packaging being unapproved, and I was told to just wait, so that's what I have been doing :D
[13:30] <sil2100> bfiller, boiko: should we try doing the paperwork and pushing those as SRU, or you prefer we reject those and re-publish once U is open?
[13:30] <bfiller> sil2100: how do I make them SRU ready?
[13:31] <bfiller> sil2100: and how long until U is open do we think?
[13:31] <mhr3> sil2100, is there anything more i have to do for line #20?
[13:31] <sil2100> bfiller: each merge/fix should have a LP bug assigned, and that bug should be a bug-fix and be formatted according to the SRU needs (i.e. https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template )
[13:31] <bfiller> sil2100: ok thanks. let me take a look and see if we want to do an sru or not
[13:32] <sil2100> mhr3: no, I guess that landing is safe, it needs to serve its time in -proposed now
[13:32] <sil2100> bfiller: ok! Thanks :) Since the SRU process can take a while itself, so it's usually evaluating and 'guessing' which makes more sense
[13:32] <mhr3> sil2100, very well, thx
[13:32] <davmor2> bfiller: ah just the chap.  You said in a 14.04 update that MMS was supported.  I have an MMS request from my Mom this morning that points to the providers web site to view I had assumed this would go away with the MMS support is that not the case?
[13:33] <bfiller> davmor2: it's not supported yet, it's in the work in progress category
[13:34] <davmor2> bfiller: damn I must of mis-read thanks
[13:34] <bfiller> sil2100: what's the quickest way to get the fixes into the image? that's what I'm most interested in really
[13:35] <bfiller> davmor2: it's coming soon though
[13:35] <ogra_> before or after mark announced U ?
[13:35] <ogra_> :P
[13:36] <ogra_> bfiller, the normal SRU process applies
[13:36] <ogra_> (for getting fixes into the image)
[13:36] <ogra_> oh, that remonds me ...
[13:36] <ogra_> *reminds
[13:36]  * ogra_ promotes 303 to devel
[13:36] <bfiller> ogra_: so we're still spinning trusty images then/
[13:36] <bfiller> ?
[13:37] <ogra_> if they are worth it
[13:37] <bfiller> what's the time estimate for U images?
[13:37] <ogra_> ask mark
[13:38] <ogra_> as lojng as we dont have a name we cant even open the archive
[13:38] <sil2100> Yeah...
[13:38] <sil2100> bfiller: well, it's hard to say  what's the fastest way
[13:39] <ogra_> once the name is there opening the archive (to a usable state) takes a day or two ... then the build tools need adjustment for the new name, then we can start first test images
[13:39] <ogra_> there is a wikipage somewhere
[13:40] <bfiller> so guessing we're at least a week a way
[13:41] <ogra_> https://wiki.ubuntu.com/NewReleaseCycleProcess
[13:41] <ogra_> thats the one i think
[13:42] <ogra_> (note it expects that the name exists 1month before the release)
[13:42] <sil2100> bfiller, boiko: just give me a ping once you decide what you want to do with your landings :)
[13:56] <mandel> sil2100, didrocks small question, when will I be allows to start landing again for udm? do I have to wait until he u name?
[13:56] <ogra_> mandel, where do you want to land ?
[13:56] <mandel> ogra_, touch
[13:56] <ogra_> lol
[13:57] <mandel> ogra_, whatever that is :)
[13:57] <ogra_> so udm doesnt go into server ? :P
[13:57] <mandel> ogra_, or the moon ;)
[13:57] <ogra_> mandel, if you spaniards dont know what to target, how do you expect to win the game tonight ?
[13:58] <mandel> ogra_, and get blamed for heartbleed, no :P
[13:58] <ogra_> mandel,  do mean landing for U ?
[13:58] <ogra_> or for a trusty SRU
[13:59] <mandel> ogra_, U would be easier than a SRU and is just for mms support and browser integration, things we do not have in trusty
[13:59] <ogra_> SRUs can land ...
[13:59] <mandel> ogra_, there is a game going on tonight? /me checks
[13:59] <ogra_> U cant land before an archive exists
[13:59] <ogra_> mandel, ral vs bayern ?
[14:00] <ogra_> *real
[14:00] <mandel> ogra_, oh, that.. I should watch that
[14:00] <mandel> ogra_, I'm more of a rugby man :)
[14:00]  * ogra_ surely will :) 
[14:00] <ogra_> ah
[14:02] <mandel> ogra_, I will just to cheer for the spaniards, you are not allowed to have a better economy && good football, that is the reason we wond the worldcup
[14:02] <ogra_> haha
[14:02] <ogra_> brazil will show i guess :)
[14:04] <bregma> hey sil2100 I see you looking at my line 31: all the bugs are now prepared for SRU, it's ready for a silo assignment when everything is ready on your end
[14:04] <sil2100> bregma: hey! Yes, I saw that, was browsing the bugs like 15 minutes ago
[14:04] <sil2100> I nominated some already
[14:04] <bregma> I just finished editing the last one
[14:06] <sil2100> Awesome!
[14:06] <sil2100> Let me just browse through them quickly and assign a silo
[14:06] <sil2100> We're a bit low on those, but hey, it's not like we're landing anything besides those
[14:28] <sil2100> bregma: silo 14 for you :)
[14:49] <ogra_> didrocks, btw, did you notice that you get the image update together with the update of the three click packages that were added in 303 ...
[14:49] <ogra_> kind of redundant :P
[14:50] <didrocks> ogra_: yeah, it's not the most optimized UI :)
[14:50] <ogra_> lol, you blame the UI ?
[14:51] <ogra_> (just pointing out it is pointless to re-roll images only for click updates ... since you will always get it twice then)
[14:52] <ogra_> oh, just for teh record ... 303 promoted btw
[15:03] <bfiller> sil2100: line 21 sync-monitor: I filed SRU bug here https://bugs.launchpad.net/ubuntu/+source/sync-monitor/+bug/1311719
[15:03] <bfiller> sil2100: would like to get that promoted.
[15:04] <bfiller> sil2100: line 18 can be rejected and pushed to U
[15:04] <sil2100> bfiller: hmmm, ok, I need to consult about the sync-monitor thing, because right now the package that's in UNAPPROVED doesn't have any link to the bug being fixed
[15:05] <sil2100> So it will be hard for the SRU team to track this bug
[15:05] <bfiller> sil2100: I can resubmit if it's easier to reject that one and do it again
[15:05] <sil2100> cjwatson: hi! Sorry to bother again, but what do you think? We have a package in UNAPPROVED that's not linked to any bug - the bug is now prepared, but we're not sure if we should reject this upload and try re-publishing with the bug linked in?
[15:42] <popey> didrocks: I'll miss landing call this evening, have a meeting clash
[15:42] <didrocks> popey: ok, no worry!
[15:45]  * ogra_ guesses there wont be much do discuss anyway ... still 
[15:45] <mhr3> sil2100, silo for 33 pls?
[15:45] <didrocks> mhr3: no need to ping us, we are getting pings
[15:45] <sil2100> mhr3: sadly, no silos...
[15:45] <sil2100> I mean, we have like 1
[15:46] <didrocks> on :#ubuntu-ci-choo-choo :)
[15:46] <mhr3> didrocks, woooo, as in there's a bot? :)
[15:46] <didrocks> mhr3: you can join there!
[15:46] <sil2100> Because of no-U and SRU it's like, geh
[15:46] <didrocks> :)
[15:47] <ogra_> sil2100, i'd call it relaxing
[15:47] <sil2100> Ok, I jump out to the doctor, bbl
[15:47] <ogra_> finally time to do all that overdue paperwork etc :)
[15:48] <ogra_> ... and cleaning the office ...
[15:52] <bfiller> fginther: are the CI jobs supposed to already be producing a click for gallery-app? don't see it anywhere in artifacts
[15:56] <fginther> bfiller, unfortunately, you'll need drill down through a couple of jobs to find it. From gallery-app-ci, you can go to the generic-click-autopilot-trusty-touch job, then the generic-click-builder-trusty-armhf job which will have the click package
[15:57] <bfiller> fginther: ok, thanks. Any plans to surface this in the Launchpad MR page?
[15:58] <fginther> bfiller, I had not thought about that... I'll look into it
[15:58] <bfiller> fginther: cool, possible could just add it to the artifacts zip file that is already created
[16:01] <didrocks> cyphermox: robru: coming?
[16:01] <bfiller> fginther: so I'm here but can't figure out how to drill further: https://jenkins.qa.ubuntu.com/job/generic-click-autopilot-trusty-touch/
[16:04] <fginther> bfiller, the console logs will contain the links to the specific build for each job
[16:05] <fginther> so if you start with https://jenkins.qa.ubuntu.com/job/gallery-app-ci/812/console, you'll see "generic-click-autopilot-trusty-touch #86"
[16:05] <fginther> and then the console log for that will point to "generic-click-builder-trusty-armhf #98"
[17:19] <sil2100> Back
[17:19] <ogra_> Front
[17:31] <rsalveti> utopic unicorn!
[17:31] <ogra_> !!
[17:32] <sil2100> OH!
[17:32] <sil2100> YESSSS \o/
[17:34] <sil2100> The unicorn is ouuunnn!
[17:38] <fginther> sil2100, so now that we're opening a new release, do you know how the 14.04 project branches will be handled? Is this going to be through lp:cupstream2distro-config or is the ci-train going to handle this also?
[17:39] <sil2100> fginther: I would suppose ci-train will handle this as well, but I guess that's a valid question to poke Didier tomorrow morning
[17:39] <sil2100> fginther: I'll try to poke about that in the EU meeting and just inform you once you appear
[17:40] <fginther> sil2100, thanks. for the foreseeable future, we'll still need to maintain the config files in lp:cupstream2distro-config for the -ci jobs, but it would help to know if the former daily-release process will pick anything up
[18:07] <robru> fginther, my understanding is that daily_release is only used for saucy SRUs. there shouldn't be any current branches still using it.
[18:07] <fginther> robru, and trusty SRUs will be handled by the ci-train?
[18:07] <robru> fginther, I assume so.
[18:07] <fginther> robru, that's my assumption as well
[18:08] <robru> fginther, didrocks would have the final say on that, but I can't image we'd want to transition trusty SRUs to the old daily_release stuff.
[18:08]  * robru is secretly hoping that daily_release gets shut off and deleted when saucy EOL's ;-)
[18:09] <fginther> robru, agreed, I'll be sure to poke him tomorrow if sil2100 doesn't get to him first
[18:34] <josharenson> josepht, is this a good time for you?
[18:34] <josepht> josharenson: sure
[18:36] <josharenson> josepht, so I'm writing a performance test suite (well, currently only 1 test), that I would like to integrate into the existing QA dashboard. I have the code from lp:helipad, but was wondering if you could provide some tips on setting up a local instance as I'm running in to a lot of issues.
[18:37] <cjohnston> josharenson: first, don't use lp:helipad
[18:37] <josharenson> cjohnston, ... ok I also have lp:qa-dashboard
[18:37] <josepht> josharenson: what sort of issues are you having setting it up?
[18:37] <cjohnston> josharenson: it's meant to be deployed on precise
[18:39] <josharenson> cjohnston, josepht, I have installed old versions of django and postgres and I can kind of get the server running but obviously there are many errors when trying to interact with the db... how do you recommend I proceed? Is there some sandbox environment available?
[18:40] <cjohnston> josharenson: deploy a precise instance in canonistack and I'll help you setup
[18:42] <josharenson> ... where do I do that?
[18:47] <cjohnston> josharenson: you could also use lxc if you like and that's easier for you
[18:56] <cjwatson> bfiller: yes, please do resubmit that sync-monitor change - we can't do any kind of SRU validation tracking without a bug number
[18:56] <cjwatson> bfiller: I've rejected the existing upload
[18:56] <bfiller> cjwatson: will do
[18:56] <cjwatson> thanks