[02:05] <imgbot> [03:35] <imgbot> [03:35] <imgbot> [04:51] <Mirv> that's all for now I think. upstart wasn't marked as ready yet, but assigned a silo anyhow
[07:19] <brendand> ogra_, champions!
[07:27] <Mirv> :)
[07:38] <bzoltan> Mirv: ogra_: rsalveti: Here is the first MR for the SDK meta package -> https://code.launchpad.net/~bzoltan/ubuntu/utopic/ubuntu-touch-meta/add_packages/+merge/226635
[07:41] <sil2100> I wonder if we'll have ogra_ around today ;) Who knows if he's still not celebrating?
[07:52] <camako> Hello... Just added a silo request for landing the welcome screen fix.
[07:52] <sil2100> o/
[07:52] <sil2100> mvo_: can you assign? ^
[07:53] <camako> thx!
[07:53] <mvo_> sure
[07:53] <sil2100> camako: thanks for the fix!
[07:54] <camako> mvo_, oh hold on for a sec... I need to check something..
[07:54] <camako> sil2100 sure...
[07:54] <mvo_> ok
[07:54] <mvo_> camako: just say when
[07:55] <camako> mvo_, sure
[08:00] <camako> mvo_, probably be an hour or two... still waiting on an MP to land on a branch...
[08:00] <camako> sorry... shoulda checked first
[08:01] <Mirv> xnox: I assigned your upstart a silo too, but I'd like to check if it's ok since it's not set to "Ready?" "Yes" yet?
[08:02] <psivaa> sil2100: fyi, i'm running the missing tests for 129 now
[08:03] <ogra_> brendand, \o/
[08:03] <ogra_> sil2100, i'm not such a big party guy :) but inded stayed up late :)
[08:03]  * ogra_ is still quite tired
[08:04] <ogra_> bzoltan, commented on th MP
[08:04] <mvo_> ogra_: not a party guy?!?
[08:04] <ogra_> :D
[08:04]  * mvo_ remembers differently
[08:04] <ogra_> well, i was watching at home with my GF ... we partied just a bit :)
[08:07] <bzoltan> ogra_: http://pastebin.ubuntu.com/7792430/
[08:08] <sil2100> psivaa: ok, thanks! I saw we're missing some test-suites there
[08:10] <psivaa> sil2100: yea, one device misbehaved
[08:12] <ogra_> sil2100, someone was complaining on the ML that his networking didnt work ... and there was a urfkill upload  .... at the same time the failures started, i wonder if there is a connection
[08:22] <sil2100> I'm looking at the changelog
[08:25] <bzoltan> ogra_: and here comes the other MR for the same package -> https://code.launchpad.net/~bzoltan/ubuntu/utopic/ubuntu-touch-meta/remove_friends_from_sdk_libs/+merge/226641
[08:26] <ogra_> bzoltan, giving me the list of deps wont help :) please chack they are not doing anything harmful (like making all input devices 0666 from a postinst script or some such ... )
[08:26] <Mirv> bzoltan: what about btw qtwebkit and qtscript, should they be removed at some point?
[08:26] <ogra_> *check
[08:26] <bzoltan> Mirv:  sure, why not
[08:28] <ogra_> sil2100, FYI i had quite a few UI crashes over the weekend (on the promoted image)
[08:28] <bzoltan> ogra_: these packages are required to be installed on the app developer's machine. Right now they have to do it manually or hope that all these packages are pulled by an other package installed already on the system. So these are not new dependencies.
[08:28] <ogra_> bzoltan, i dont care about dependencies ...
[08:29] <ogra_> bzoltan, i know that autpilot on the phones makes input devices insecure for example ... that is something you dont want on a developer machine ... please make sure this cant happen we cant make all dev desktops vulnerable
[08:30] <bzoltan> ogra_: I do not know a lot about many things... but I expect that each package in the main/universe are safe to install. The SDK pulls in many-many packages. I have not reviewed each and do not review each update of all those packages.
[08:30] <ogra_> (there is a difference between having developers install this by hand or pulling it in by default ... the latter needs a deeper audition)
[08:32] <bzoltan> ogra_: it is waaaay beyond my competence to review the hundreds of packages what the SDK pulls. I check this autopilot-desktop, but I really did expect that the releasing engineer or the landing team does check the packages before they are added to the archive.
[08:34] <ogra_> it is beyond your competence to diff content of /dev before and after installing that package ?
[08:36] <bzoltan> ogra_:  that one I can do ... but doing a full blown security audit on one of the biggest asset we develop is kind of beyond :) I am just paranoid ...
[08:38] <ogra_> yeah, i just want to be sure we done install something superharmfull :)
[08:38] <bzoltan> ogra_:  there was no diff between the contents of the /dev/ before and after installing the autopilot-desktop
[08:41] <bzoltan> ogra_: same here, but I really do expect the people who land the autopilot packages do that check.
[08:41] <ogra_> well, if the expectation is their packages are only installed during testing ...
[08:42] <ogra_> the autopilot-touch one surely assumes that
[08:42] <ogra_> (at least parts of it do)
[08:44] <bzoltan> ogra_:  With the sdk we distribute tests for the template/example apps, so the test tools are expected to be present.
[08:48] <xnox> Mirv: thanks.
[08:56] <xnox> Mirv: cihelp: can landing-005 be "de-allocated" it's no longer needed. Plymouth was uploaded direct into archive and stuck in new queue. and I will be uploading binNMU for casper&mountall direct as well.
[08:56] <bzoltan> ogra_: as cjwatson suggested -> The correct MR is here -> https://code.launchpad.net/~bzoltan/ubuntu-seeds/add_sdk_packages/+merge/226642
[08:58] <cjwatson> xnox: done
[08:58] <xnox> cjwatson: thanks.
[08:59] <cjwatson> sil2100: do we just delete the spreadsheet row in this kind of situation, or what?
[08:59] <cjwatson> (after the silo finishes cleaning)
[09:00] <sil2100> cjwatson: let me take a look, one moment
[09:00] <sil2100> cjwatson: ok, so we have two approaches - we can either just remove it, or mark it as 'Rejected' in the Status field
[09:00] <cjwatson> xnox: have you tested the new plymouth on the phone?
[09:00] <sil2100> But in this case I would just delete it
[09:01] <cjwatson> sil2100: what happens to subsequent rows that move up?
[09:01] <sil2100> cjwatson: CI Train spreadsheet handles those correctly, all associations are made per-UID not per-line
[09:01] <sil2100> So all should be ok
[09:01] <cjwatson> ok, good to learn
[09:03] <cjwatson> deleted ... er, hope that won't confuse things with silo 5 still cleaning, brain not switched on
[09:03] <cjwatson> ah, it's cleaned
[09:04] <ogra_> bzoltan, i would just have tranferred that manually ... but yeah, thanks
[09:46] <ogra_> psivaa, hmm ... what is "daily" (on img 129)
[09:46] <sil2100> camako: how's the work on the branch going? :)
[09:46]  * mvo_ is off for lunch
[09:46] <ogra_> psivaa, (5th from the bottom on http://ci.ubuntu.com/smokeng/utopic/touch/mako/129:20140714:20140712/9040/)
[09:46] <psivaa> ogra_: ohh.. let me take a lool
[09:47] <ogra_> sure, take a lol :)
[09:47] <camako> sil2100, just waiting for the fix to be merged into the 0.4 branch...
[09:47] <camako> work itself is done
[09:54] <popey> Mirv: could you pleae upload http://s-jenkins.ubuntu-ci:8080/job/music-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.music_1.3.522_all.click to the store when you get a moment, thank you.
[09:55] <psivaa> ogra_: i took care of it.. hope that reflects in the dashboard
[09:56] <psivaa> and yea, i cant type, talk or even think properly today.. too much sunlight yesterday :D
[09:59] <psivaa> sil2100: brendand: the tests completed. weather_app has one new failure
[10:00] <brendand> psivaa, yeah - i reran it and couldn't reproduce it
[10:07] <sil2100> psivaa: thanks, I guess it might be a single case, can happen sometimes it seems
[10:13] <psivaa> sil2100: brendand: ack, we'll see if it comes up with the next image
[10:18] <ogra_> psivaa, yeah, seems gone
[10:24] <popey> psivaa: brendand who can add reminders-app to the QA dashboard?
[10:25] <ogra_> popey, i thought plars was on that
[10:25] <ogra_> but seems it got forgotten or so
[10:29] <om26er> sil2100, Hi!
[10:33] <popey> -> lunch
[10:33] <bzoltan> ogra_: about the qtdeclarative5-friends0.2
[10:33] <ogra_> bzoltan, well, as cjwatson said, you should talk to slangasek ... iirc he was working on that
[10:33] <bzoltan> ogra_:  I have just made an MR to throw an error when a developer want to package an app what is using the Friends API
[10:34] <ogra_> ah
[10:35] <ogra_> i thought the plan was to keep the API and only drop the app
[10:35] <ogra_> (but i'm likely the worng person ... steve works on that and knows more)
[10:35] <bzoltan> ogra_: I see the trunk ubuntu-touch.utopic has some change related to that. I think we should stop seeding the qtdeclarative5-friends0.2
[10:35] <bzoltan> ogra_: I understood that we will keep friends-service on the phone as long as we support the 14.04 framework, but it should not be allowed by the SDK when targeting 14.10
[10:36] <cjwatson> That's what removing it from sdk-libs should have done
[10:38] <cjwatson> (OK, perhaps with matching changes to the SDK itself)
[10:39] <sil2100> om26er: hello!
[10:39] <sil2100> om26er: good to have you around :)
[10:39] <om26er> sil2100, hah, I was about to tell you that ;-)
[10:40] <om26er> i'll be covering for davmor2 this week.
[10:40] <cjwatson> But I don't see any further seed changes that are needed at this point
[10:41] <sil2100> om26er: we're still waiting for one fix to land first, i.e. for the hang-up issues in Mir
[10:41] <sil2100> om26er: once this lands, we'll build a new image and we'll try looking it up dogfooding-wise
[10:44] <sil2100> om26er: before that happens, maybe camako could use some help with the Mir silo - once it's ready :)
[10:44] <sil2100> With testing it
[10:44] <om26er> sil2100, ok
[10:45] <psivaa> popey: i take reminders-app is not a click package one?
[10:45] <popey> psivaa: it is a click package and is now on the image by default
[10:45] <popey> psivaa: http://people.canonical.com/~ogra/touch-image-stats/124.changes arrived in that image
[10:46] <psivaa> popey: ack, i'd check how to enable those tests
[10:46] <Mirv> popey: music app updated
[10:46] <popey> Mirv: ythanks
[10:46] <popey> -y
[10:47] <Mirv> ywelcome
[10:47] <popey> psivaa: is that "I would" or "I will"?
[10:47] <psivaa> popey: consider I will :)
[10:47] <popey> thanks
[10:48] <psivaa> wasn't intentionally ambiguous :)
[10:52] <popey> ☻
[11:09] <bzoltan> cjwatson:   has that change land landed already? On my utopic the ubuntu-sdk-libs still depends on qtdeclarative5-friends0.2
[11:11] <cjwatson> bzoltan: The metapackage hasn't been refreshed (I assume slangasek will be doing that next; he was doing a lot of this late on Friday evening, I think), but the seeds look correct.
[11:11] <cjwatson> But we shouldn't be going around doing parallel not-quite-matching metapackage changes for things that have already been fixed in the seeds.
[11:12] <cjwatson> (Well, in general.  I was considering doing a partial backport of a seed change to ubuntustudio-meta this week, but that's specifically to unblock a weird and complex transition ...)
[11:13] <bzoltan> cjwatson: OK, I will wait  for slangasek with the deprecation of the Friends API.
[11:17] <mvo_> mandel: could you please check silo-011 ? I can't publish currently as it says "2014-07-14 10:23:51,641 ERROR Some projects (mediascanner2, location-service, platform-api) that were in the silo configuration list were not built. Prepare either prepare the latest missing projects or use the ignore missing projects flag which will release the lock on them.". I assume you just need to rebuild the silo
[11:17] <mandel> mvo_, es, it is in my radar building atm
[11:18] <mvo_> mandel: excellent, thank you!
[11:18] <mandel> mvo_, no problem :)
[11:44] <xnox> !cihelp how does one upload "additional source packages land" in a given assigned silo?
[11:44] <xnox> cihelp how does one upload "additional source packages land" in a given assigned silo?
[11:45] <sil2100> It's better to ask trainguards here ;) We don't get pings per cihelp
[11:45] <cjwatson> xnox: dput.  If you don't have permission, then either give us a source package, or put it in a PPA somewhere and we can do a copy-and-rebuild.
[11:45] <sil2100> xnox: so... you have to dput those yourself to the silo ppa
[11:46] <sil2100> The group with permissions to do so is managed by asac, but maybe we should ask him to include ubuntu-core-devs into that group
[11:46] <cjwatson> It results in rather a lot of mail
[11:46] <xnox> ok, i'm not in the team. And it ftbfs on virtualiased ppas. I'll put _sources somewhere on people.
[11:47] <cjwatson> I suspect it isn't worth further polishing silo upload permissions since that's all going to be replaced by the airline anyway ...
[11:47] <asac> your call... tell me if i should do something
[11:47] <asac> slangasek is also admin in case i am not around
[11:47] <sil2100> I would simply add the core dev group as part of this group, it's just one click and might make things easier for everyone
[11:48] <cjwatson> sil2100: Did we decide on landing team shifts for this week?
[11:48] <xnox> yeah, airline should be easy in that respect.
[11:48] <sil2100> cjwatson: yes, it's mvo_'s shift today :)
[11:48] <sil2100> Tomorrow mine and on Wednesday is yours
[11:48] <cjwatson> OK
[11:49] <cjwatson> Ah yes, I see the wiki page is updated now
[12:07] <plars> ogra_: there's an MP for it from last week, but there's a bit of disagreement about the results
[12:07] <popey> this mir lockup is very frustrating
[12:07] <plars> ogra_: I'm planning to take a look again today
[12:07] <ogra_> plars, ah ... tell psivaa then :)
[12:07] <plars> psivaa: &
[12:07] <plars> err
[12:07] <ogra_> popey, yeah
[12:07] <plars> psivaa: ^
[12:08] <ogra_> popey, there is a landing from kgunn it seems ...
[12:08] <popey> k
[12:09] <psivaa> plars: ahh ack. appears we need to install some deps from the first look. dint yet figure out what
[12:09] <camako> popey, ogra_, been waiting for the last few hours for the fix to automerge...
[12:09] <ogra_> ah, crap
[12:10] <ogra_> sil2100, is there any chance we can speed that up ^^^ ?
[12:10] <sil2100> hmm
[12:10] <camako> perhaps I should manually merge??
[12:10] <sil2100> The automerger is not part of CI Train, so I don't know - can't we anyway get the merge into the silo and build in the meantime?
[12:11] <sil2100> Since the merge from CI Train only happens on the very end anyway
[12:11] <camako> I cannot MP lp:mir/0.4 to lp:mir if the commit is not in 0.4
[12:11] <camako> I guess I can but..
[12:12] <sil2100> Ah, ok, since I saw a different MP in the MP list
[12:12] <sil2100> https://code.launchpad.net/~vanvugt/mir/fix-1339700-both-0.4/+merge/226629 <- this doesn't look like a merge of lp:mir/0.4 to lp:mir on first look
[12:12] <camako> right, that's not the right one.. row marked as "not ready" so pls ignore
[12:13] <camako> just a placeholder for myself
[12:13] <sil2100> Ah, ok
[12:13] <sil2100> Someone like fginther would have to look at what's up with that auto-merge
[12:14] <sil2100> cihelp: is there anyone around currently that could give us a status update how far a merge is in automerging?
[12:49] <davmor3> popey: can you try logging into here maps app and let me know if you can please
[12:51] <davmor3> popey: just trying to figure out if it is the app/browser or the crappy connection
[12:52] <popey> davmor3: hey
[12:52] <popey> davmor3: will have to sign up, i dont think i have an account
[12:53] <camako> sil2100, mvo_... spread sheet entry updated... requesting silo now...
[12:53] <davmor3> I could do that I just couldn't login after
[12:54] <popey> davmor3: i can't even sign in my desktop!
[12:54] <ogra_> popey, davmor3, i think mandel knows more about that (not sure if also about the app, but definitely about "here" stuff)
[12:55] <popey> davmor3: broken here, on desktop
[12:56] <davmor3> Thanks as long as I know I'll go back to relaxing and not saving searches :)
[12:56] <popey> heh
[13:00] <fginther> sil2100, what MP are you wanting to check?
[13:00] <sil2100> fginther: hi! I think we're good now, right camako ?
[13:00] <camako> fginther, yes we are good...
[13:00] <camako> sil2100^
[13:00] <fginther> sil2100, camako, ack
[13:04] <camako> fginther, though not urgent any more, be nice to know why this didn't get automerged (didn't get Jenkins run on it, either) :
[13:04] <camako> https://code.launchpad.net/~vanvugt/mir/fix-1339700-both-0.4/+merge/226629
[13:05] <sil2100> mvo_: ^
[13:05] <sil2100> mvo_: did you assign a silo?
[13:06] <mandel> ogra_, is not within my reach, I'm improving the location service, that should improve it
[13:06] <sil2100> Ok, I'll assign it..
[13:06] <ogra_> mandel, ah, not the app ... k
[13:06] <ogra_> (i thought so actually)
[13:12] <mvo_> sil2100: in a meeting right now, I think I assigned it, but will check in a sec
[13:12] <fginther> camako, there are no jenkins jobs or configuration for lp:mir/0.4. What's the purpose of this series?
[13:17] <camako> fginther, Curious... This is for Mir. We put Mir on a series/branch like this one... The second number is bumped every time there is an ABI break. And we release to our trunk from what ever branch we are on.... So 0.3.0, 0.4.0 (ABI break), 0.4.1 (no ABI break)....and so on
[13:17] <sil2100> mvo_: no worries, I assigned it
[13:20] <sil2100> grrrr
[13:20]  * sil2100 irritated about some things
[13:20] <fginther> camako, so how does your development work? Once you create 0.4.0 (or 0.4.1, etc.) do you then line up a series of MPs to land into that one?
[13:21] <fginther> camako, and then when it's ready, propose a merge of lp:mir/0.4.0 to lp:mir?
[13:21] <camako> fginther, correct
[13:22] <fginther> camako, how does lp:~mir-team/mir/development-branch fit into this?
[13:22] <camako> fginther, the MPs are from our devel to 0.*.*
[13:23] <camako> fginther, basically we check into devel... then we move it to a series 0.x... then we MP from there to trunk
[13:23] <camako> fginther what 0.x branch/series is determined by the ABI breakage
[13:25] <mvo_> sil2100: I'm back so if you haven't look at it already I can do so now
[13:25] <fginther> camako, ok, so once 0.4.0 is merged to trunk, is it 'closed'? and the next work happens on 0.4.1 or 0.5.0?
[13:26] <sil2100> mvo_: as mentioned, I assigned it :)
[13:26] <mvo_> t
[13:26] <mvo_> ta
[13:26] <camako> fginther, "next" is determined by ABI break.. It could be 0.4.1 if nothing has been broken since 0.4.0 or it could go to 0.5.0 if we have broken the ABI
[13:26] <fginther> camako, jenkins has to know what lp branches to monitor for MPs. So when the series changes from 0.4.0 to 0.4.1, the job configurations need to be created for that new branch
[13:27]  * camako didn't know that
[13:27] <xnox> cihelp - please copy source only: upstart_1.13-0ubuntu1.dsc from ppa:canonical-foundations/upstart-daily into Silo 003 and mark PPA for building.
[13:27] <xnox> $ ./copy-package -n -d ubuntu -s utopic --ppa canonical-foundations --ppa-name upstart-daily --to-ppa ci-train-ppa-service --to-ppa-name landing-003 upstart
[13:27] <camako> fginther, this process is new and a bit immature... still needs polishing...
[13:27] <mvo_> xnox: I will take care of this - its best to ping trainguard btw, we all highlight on it
[13:27] <camako> fginther, is the config done by us (the mir team) or do we have to let you guys know?
[13:28] <fginther> camako, no worries, I'm just trying to understand it better to come up with a way to handle this with the jenkins jobs
[13:28] <xnox> mvo_: had no idea. Why topic says "Vanguard: cihelp" then? or what's the difference between trainguard vs vanguard?
[13:28] <brendand> fginther, do you know if it's in any way possible to get the jenkins coverage plugin to link through to the actual source code?
[13:28] <brendand> fginther, most projects i've seen so far don't have that
[13:28] <mvo_> xnox: its because I'm too lame to set the topic correct :/
[13:29] <xnox> mvo_: also FAQ doesn't say how to request additional source inclusion at all. Would be helpful to document it there, as to how to properly request such things =)))))
[13:29] <robotfuel> ev: https://errors.ubuntu.com/ broken and not returning any data, someone said you were the person to notify.
[13:29] <xnox> mvo_: ah =)))))
[13:29] <cjwatson> xnox: I think that's the vanguard for other CI things, not the CI train
[13:29] <xnox> cjwatson: oh. i see.
[13:29] <cjwatson> xnox: "CI Train Sheriff" is the one you want for the latter
[13:29] <fginther> camako, it's easy enough to propose an MP to update a jenkins configurations from lp:mir/0.4.0 to lp:mir/0.next.next. I can show you how this is done
[13:29] <ogra_> xnox, yeah, you want the sherriff ... not the deputy ;)
[13:29] <ogra_> -r
[13:29] <cjwatson> Because metaphors are never knowingly undermixed around here, apparently
[13:30] <ev> robotfuel: GAHH. On it.
[13:32] <sil2100> xnox: well, this is a CI channel, so the Vanguard is for CI stuff - for CI Train stuff there's CI Train Sheriff
[13:32] <sil2100> xnox: as the topic says ;)
[13:32] <ev> robotfuel: webops is on it
[13:33] <camako> fginther, pls do
[13:34] <fginther> brendand, I don't know how that is done, have you talked to alesage?
[13:34] <brendand> fginther, not yet, but i will
[13:38] <ChrisTownsend> trainguards: Hi, could someone please start a rebuild of silo-014?
[13:39] <sil2100> ChrisTownsend: sure
[13:39] <sil2100> mvo_: doing this ^
[13:40] <mvo_> sil2100: oh, ok. I just clicked on "build"
[13:40] <sil2100> Oh
[13:40] <sil2100> THen please do ;)
[13:40] <ChrisTownsend> sil2100: mvo_:  Thanks!
[13:40] <sil2100> Thanks!
[13:40] <mvo_> sil2100: if you could do the upstart package copy/upload in silo-003, that would be great, I got a permission denied error
[13:40] <sil2100> mvo_: hm, let me try
[13:46] <sil2100> mvo_, xnox: I uploaded the package to the PPA, now we need to wait for it to build and then run watch-only
[13:47] <xnox> looks good, thank you all =)
[13:48] <mvo_> sil2100: thanks! I will wait for the build then. is it possible that I get added to the people with upload permission (ie ~ci-train-ppa-service)?
[13:48] <sil2100> mvo_: as I mentioned, this team is managed by asac and slangasek ;) Only they can add people - I would opt for adding the whole ubuntu-core-dev team though
[13:49] <asac> all trainguards should be in
[13:49] <asac> I will add mvo for now
[13:49] <mvo_> thanks
[13:49] <sil2100> Since it make sense for core devs to be able to upload, as any core dev can anyway do landings as they wish
[13:49] <asac> done
[13:50] <asac> yes, core-dev was the plan to do, but read above that cjwatson had concerns about emails getting sent to all core-devs abvoe
[13:50] <asac> discuss with cjwatson and slangasek ... slangasek is admin so whate3ver you agree he can just do
[14:02] <stgraber> the potential e-mail flood could be avoided by setting a mailing-list as the contact address for the team, though indeed, may not be worth doing as we'll replace everything soon enough anyway
[14:11]  * sil2100 is angry at LP API
[14:15] <cjwatson> sil2100: What's wrong?
[14:16] <cjwatson> stgraber: ~ubuntu-core-dev has had a mailing list set as its contact address for years, but a good deal of junk still gets through for teams it belongs to.
[14:17] <cjwatson> Maybe that's a bug somewhere ...
[14:21] <Laney> 006 is conflict-able, yes?
[14:21] <ChrisTownsend> mvo_: Hi, I'm watching the status of silo-014 in the dashboard and it hasn't updated at all as of yet.  I'm not familiar with how long things take for this, so should the status have been updated by now or am I being impatient?
[14:24] <mvo_> ChrisTownsend: packages are build and ready for testing afaict, what status are you currently expecting?
[14:25] <mvo_> ChrisTownsend: the normal workflow is to test them now and once that is done I can publish - or am I missing something here?
[14:25] <mvo_> ChrisTownsend: oh, I do
[14:25] <mvo_> ChrisTownsend: hold on a sec
[14:26] <ChrisTownsend> mvo_: Ok
[14:26] <ChrisTownsend> mvo_: I'm needing a rebuild
[14:28] <popey> plars: you about? is "reminders on the qa dashboard" on your plate?
[14:28] <alesage> charles is getting a ppc unit test failure and wants to investigate further cihelp, I recall that there are boxes somewhere for this kind of thing?
[14:29] <mvo_> ChrisTownsend: I triggered it now with different parameters (the previous one apparently did not had enough --force options).
[14:29] <cjwatson> alesage: https://wiki.canonical.com/InformationInfrastructure/ISO/BuildInfrastructure/PorterBoxes
[14:29] <cjwatson> charles: ^-
[14:29] <ChrisTownsend> mvo_: Ok, thanks
[14:29]  * charles clicks
[14:30] <alesage> cjwatson, thanks
[14:30] <cjwatson> charles: once you have access (ask #is if not) you can use "schroot -c utopic-powerpc", and if necessary you'll have limited "sudo apt-get install" capability in there
[14:31] <cjwatson> Right now it's a big shared chroot rather than anything cleverer, though usually that's not a problem
[14:31] <popey> plars: bug 1307542
[14:35] <plars> popey: right, just need to sort out a few things with the merge on our side
[14:36] <plars> popey: I could put it in right now, but I suspect we're missing something because I'm told the tests all pass, but most fail when I try them
[14:43] <popey> plars: ok, we need to fix broken tests then, balloons ^
[14:44] <balloons> I would need to see plars's output.. they should work
[14:44] <plars> popey: well, like I said, it could be that we're just missing some dependency or something. I pinged leo about it earlier
[14:44] <plars> balloons: take a look at http://q-jenkins.ubuntu-ci:8080/job/plars-smoke-daily-test/4/#showFailuresLink
[14:45] <balloons> plars, I see the problem right off the top. This has to be run as python3
[14:45] <Laney> stgraber: queuebot seems a bit quiet
[14:45] <ogra_> it is hung over ... it is a germany fan ;)
[14:46] <plars> balloons: oh, I thought phablet-test-run was running them all with python3 already
[14:46] <balloons> plars, it has a bug in it causing things to run py2 when they shouldn't. maybe you are hitting it?
[14:47] <stgraber> Laney: restarted
[14:47] <Laney> danke
[14:47] <balloons> either way, make sure it runs as py3 and things should go better
[14:50] <plars> balloons: isn't that something controlled by the test, not me?
[14:50] <balloons> plars, no you can run it with autopilot or autopilot3
[14:51] <plars> balloons: we are running it with phablet-test-run
[14:56] <balloons> plars, ok, well sparing taking about how you are running it, it needs to run with autopilot3 ;-)
[14:56] <balloons> I believe on the dashboard the tooling is different and phablet-test-run is not invovled
[14:56] <plars> balloons: I know, I'm just saying that I don't have any control over that unless we put in some weird hack for working around this in reminders
[14:57] <plars> balloons: we have been running all autopilot tests with phablet-test-run for a very long time now, because that's how everyone else is supposedly running it
[14:57] <balloons> plars, you don't have any control over what exactly? are you concerned this won't run properly on the dashboard?
[14:57] <plars> balloons: which dashboard are you talking about?
[14:57] <balloons> ci.ubuntu.com
[14:57] <balloons> let me check something
[14:57] <plars> balloons: ci.ubuntu.com is just a dashboard to display the results, the tests themselves are run with phablet-test-run, which is supposed to select the correct autopilot
[14:57] <plars> balloons: for some reason, it's selecting the wrong one it seems
[14:58] <balloons> plars, really phablet-test-run is used? that's surprising to me
[14:58] <plars> looking at it now, but I'm about to have to go to a meeting. I suspect this is something wrong with reminders-app tests since the others behave
[14:58] <plars> balloons: that has been the case for quite a while
[14:58] <balloons> mm.. plars I thought maybe the debian/control file used py2, it doesn't
[14:59] <plars> balloons: looks like the change to use phablet-test run was since january or so
[14:59] <balloons> plars, mm, looks like one of the issue may have been fixed: https://bugs.launchpad.net/ubuntu/+source/phablet-tools/+bug/1327325
[14:59] <plars> balloons: I'll play with it some more after this call
[14:59] <plars> balloons: that would do it
[14:59] <balloons> plars, phablet-test-run is just weird in how it determines py2 and py3.. I don't like it
[15:00] <plars> balloons: there's a warning about ubuntuuitoolkit
[15:00] <plars> The ubuntuuitoolkit.emulators module is deprecated. Import the autopilot helpers from the top-level ubuntuuitoolkit module.
[15:00] <plars> I'm surprised other tests are not affected by this
[15:00] <balloons> plars, yes, that's ok
[15:01] <plars> balloons: but from the title of the bug, it makes it sound as if that could be the source of the problem
[15:01] <balloons> several apps have the same warning and will need to be migrated.. but support still exists
[15:01] <balloons> plars, yes I'm assuming it or something like it is the source issue
[15:01] <balloons> I've run into it in the past.
[15:02] <balloons> let's chat after meetings ;-)
[15:03] <pmcgowan> kenvandine, the next build failed the same way on gallery
[15:03] <kenvandine> :/
[15:05] <pmcgowan> sil2100, can you help us figure out why build failed as unstable like http://s-jenkins.ubuntu-ci:8080/job/generic-mediumtests-utopic/1624/console
[15:05] <pmcgowan> sil2100, 1625 fails in a similar way
[15:05] <pmcgowan> for a diff project
[15:06] <kenvandine> sil2100, same problem i was seeing when the network was failing on the devices
[15:07] <Laney> I doubt it
[15:07] <Laney> click on autopilot-testrunner-otto-utopic-XXX
[15:07] <Laney> and then you see the real failure
[15:10] <kenvandine> Laney, but that job is successful
[15:11] <Laney> where?
[15:11] <kenvandine> https://code.launchpad.net/~saviq/ubuntu-system-settings/fix-wizard-sim/+merge/226555
[15:11] <kenvandine> that's the MP
[15:11] <pmcgowan> kenvandine, its failing on the about page, I wonder if phone number broke the test
[15:12] <pmcgowan> kenvandine, like when there is no sim or something
[15:12] <kenvandine> pmcgowan, where do you see that failure?
[15:12] <pmcgowan> kenvandine, http://s-jenkins.ubuntu-ci:8080/job/autopilot-testrunner-otto-utopic/1360/
[15:12] <pmcgowan> shows 2 failures
[15:12] <Laney> kenvandine: I followed a trail from the MP and got to https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/2161/
[15:12] <Laney> which is the same
[15:12] <sil2100> hmmm
[15:13] <Laney> It's a real bug I think, was looking at it earlier but didn't reproduce
[15:14] <Laney> see recent scrollback in #ubuntu-desktop for example
[15:14] <Laney> I asked pitti for insight but didn't get a reply ;-)
[15:15] <Laney> (we first noticed late on friday)
[15:15] <Laney> (could be related to py3 AP test porting)
[15:16] <Saviq> mvo_, sil2100, can I get a silo for line 31 please?
[15:16] <Laney> (one way to verify that would be to propose an MP with that branch reverted and look at the testing on that)
[15:16] <sil2100> Saviq: mvo_'s on it :)
[15:16] <Saviq> ok thanks
[15:17] <kenvandine> i doubt this has anything to do with adding the number
[15:18] <sil2100> kenvandine: I'll try to look in a moment, but as I am not really well oriented in the CI infrastructure there, I guess someone from cihelp might be a better match
[15:18] <Laney> although that branch itself had successful CI
[15:18] <Laney> so ...
[15:18] <kenvandine> yeah, it did
[15:19] <kenvandine> i guess we need to bisect it
[15:19] <Laney> doesn't happen locally
[15:19] <Laney> so, not fun
[15:19] <kenvandine> but it looks like something with the updates stuff
[15:19] <Laney> it's when trying to get a handle for dbusmock's system bus
[15:19] <Laney> you get a Connection refused
[15:19] <kenvandine> yeah
[15:20] <Laney> that's why I figured pitti would know
[15:21] <pmcgowan> kenvandine, I think perhaps the error is misleading, the failing line is lookign for what used to be the first info item
[15:24] <pmcgowan> kenvandine, perhaps I am wrong...
[15:24] <Laney> lemme push a branch to get it checked by CI
[15:32] <slangasek> bzoltan, cjwatson: I haven't changed the metapackages yet for friends; mhall119 wanted me to wait so it could be announced on developer.ubuntu.com
[15:34] <mhall119> slangasek: in my team call right now I'll bring it up
[15:34] <slangasek> mhall119: cheers :)
[15:35] <kenvandine> Laney, are you going to remove the subscriberNumber from about and test that?
[15:35]  * kenvandine really doesn't think that's related
[15:35] <Laney> first I'm reverting the py3 tests branch
[15:35] <kenvandine> ah
[15:35] <Laney> then we can try other ones
[15:35] <slangasek> xnox: what was the "additional source package" for the landing in question? upstart?
[15:36] <slangasek> aha, it was
[15:37] <Laney> kenvandine: https://code.launchpad.net/~system-settings-touch/ubuntu-system-settings/test-reverts/+merge/226691 use this one for testing if you like after I've gone EOD
[15:38] <kenvandine> Laney, thx
[15:38] <kenvandine> both of the failures seem related to dbus SystemBus connections
[15:39] <Laney> yeh
[15:47] <sil2100> camako, kgunn: how's testing silo 17 going?
[15:47] <sil2100> Any possibility of us landing that soon?
[15:47] <camako> sil2100, without my ppa, I'm only getting background.. Is this a known issue?
[15:47] <kgunn> sil2100: is something wrong with the latest devel-proposed ?
[15:48] <ogra_> kgunn, disablet the welcome wizard
[15:48] <ogra_> its is broken
[15:48] <sil2100> kgunn, camako: I heard something with the wizard beign broken, so this can be it
[15:48] <sil2100> There's a critical landing for that
[15:48] <sil2100> (silo 18)
[15:48] <camako> ogra_, how?
[15:49] <kgunn> camako: touch /home/phablet/.config/ubuntu-system-settings/wizard-has-run
[15:49] <ogra_> there is a phablet-config option iirc
[15:49] <sil2100> Yeah
[15:49] <camako> thanks
[15:49] <mhall119> slangasek: got a minute to talk about this change?
[15:49] <slangasek> mhall119: sure
[15:50] <mhall119> so the friends API was part of ubuntu-sdk-14.04 and up to ubuntu-sdk-14.10-dev2
[15:50] <slangasek> yes
[15:50] <mhall119> are we moving to -dev3 now?
[15:50] <slangasek> that would be the logical step
[15:50] <slangasek> cjwatson: who manages the revisions of the frameworks?  I've seen you and jdstrand involved in this previously
[15:51] <cjwatson> slangasek: lool has dealt with the last couple, I think
[15:51] <mhall119> and will those old frameworks be removed from future device images?
[15:51] <slangasek> ok
[15:51] <cjwatson> slangasek: it normally requires involvement from the security team
[15:51] <slangasek> mhall119: post-14.10, they should be
[15:51] <cjwatson> slangasek: it used to require a click patch, but (for -dev bumps) no longer does
[15:51] <ogra_> cjwatson, and the store and .. and ...
[15:51] <cjwatson> ogra_: right
[15:51] <slangasek> hmm
[15:52] <slangasek> I don't suppose the process is written down anywhere?
[15:52] <ogra_> sadly not
[15:52] <slangasek> it's never too late
[15:52] <cjwatson> https://wiki.ubuntu.com/Click/Frameworks has bits of it but not as a checklist
[15:52] <slangasek> :)
[15:52] <cjwatson> that's where it should go
[15:52] <ogra_> and we run into one ofr the missing "and"'s every time
[15:53] <cjwatson> It's not clear to me what will prevent the use of the friends API.  click-reviewers-tools?
[15:53] <slangasek> https://wiki.ubuntu.com/Click/Frameworks/UpdateProcess#preview
[15:53] <slangasek> someone can fill this in ;)
[15:53] <slangasek> or put it on https://wiki.ubuntu.com/Click/Frameworks if that's preferred
[15:54] <slangasek> cjwatson: if it's not part of the SDK, won't it be prevented locally?
[15:54] <cjwatson> (I suppose rather, it's not clear to me what permitted it before)
[15:54] <cjwatson> slangasek: I don't know exactly how QML interface use is enforced)
[15:54] <slangasek> ok
[15:55] <mhall119> cjwatson: I assume that it'll stop working once the libs providing it are removed
[15:55] <mhall119> though "stop working" might mean "crash"
[15:55] <cjwatson> mhall119: But they aren't being removed from the image, because that would preclude continuing to provide the -dev2 interface
[15:55] <mhall119> ideally the images that have dropped the lib won't have the older framework files on it, so it shouldn't be installable
[15:55] <cjwatson> mhall119: That's not my point
[15:56] <slangasek> mhall119: the question is, what ensures that an app uploaded with -dev3 doesn't reference it
[15:56] <mhall119> oh, they're not being removed?
[15:56] <cjwatson> Exactly that
[15:56] <cjwatson> They can't be removed yet, otherwise 14.04 apps using it break
[15:56] <slangasek> mhall119: yes, as I said above the removal from the image is post-14.10
[15:57] <slangasek> in practice only two apps in the store are affected and these are handled out-of-band already by popey; nevertheless we need to follow our own deprecation best practices, which it seems are currently still a bit fuzzy :)
[15:57] <cjwatson> My best guess is either the SDK or the review tools, but i really don't know
[15:57] <cjwatson> jdstrand or lool might
[15:57] <pmcgowan> review tools, SDK build chroot,  no way at runtime I think
[15:57] <cjwatson> No, the chroot doesn't help
[15:57] <cjwatson> Not for QML stuff
[15:57] <pmcgowan> true
[15:57] <mhall119> I think the review tools might already give a warning on using the friends namespace or policy
[15:57] <mhall119> popey: ^^ can you verify that?
[15:58] <cjwatson> friends wasn't in the chroot to begin with
[15:58] <mhall119> cjwatson: the app or the API?
[15:58] <cjwatson> either
[15:58] <slangasek> cjwatson: oh? then what does sdk-libs map to?
[15:58] <cjwatson> but I meant the API
[15:58] <jdstrand> bzoltan2: just submitted an mp for the review tools for friends
[15:58] <cjwatson> slangasek: sdk-libs *should* be what the chroot uses, but right now it's hardcoded due to multiarch trouble
[15:58] <jdstrand> s/://
[15:58] <cjwatson> so sdk-libs is sort of aspirational
[15:58] <bzoltan2> jdstrand: thank you
[15:59] <cjwatson> I tried to get to the point of the chroot installing ubuntu-sdk-libs:armhf in trusty, but failed
[15:59] <cjwatson> Haven't yet tried again in utopic
[15:59] <cjwatson> It'll probably be easier once friends is gone, as that was actually one of the blockers
[15:59] <slangasek> cjwatson: aha
[16:00] <cjwatson> regardless, still doesn't help here as we only use the chroot for native apps, it's not (afaik) used to enforce QML use
[16:00] <cjwatson> sounds like jdstrand's MP should do the trick
[16:01] <jdstrand> it is actually bzoltan2's, but yes
[16:01] <mhall119> ok, so I need to writeup the announcement for what's being done, so to make sure I'm clear we're going to stop allowing apps to use the Friends API immediately, in the SDK and the store, but we won't be removing the actual API or the old frameworks that included it until after 14.10's release (not RTM<, but actual release in October)?
[16:01] <cjwatson> ah right yeah
[16:01] <slangasek> mhall119: yes
[16:01] <bzoltan2> jdstrand: I have pushed a single character fix to the MP
[16:02]  * jdstrand nods
[16:02] <mhall119> and then starting with 15.04 builds we'll drop those old frameworks? ubuntu-sdk-14.10 won't include friends, so we can still have that in 15.04
[16:03] <popey> mhall119: pass, not seen that
[16:04] <bzoltan2> nik90_:  I fixed that typo in the MR https://code.launchpad.net/~bzoltan/click-reviewers-tools/deprecated_friends/+merge/226650
[16:04] <slangasek> mhall119: correct
[16:05] <mhall119> kenvandine: content-hub is going to provide the ability to share links and text to Facebook/Twitter, is that correct?
[16:05] <kenvandine> someday
[16:05] <kenvandine> mhall119, it can share photos with facebook now
[16:05] <ogra_> and G+!
[16:05] <camako> sil2100, testing was completed successfully.
[16:05] <kenvandine> ogra_, yell at google about that :)
[16:05] <mhall119> it already can for links too right? It's just facebook doesn't accept them yet?
[16:06] <kenvandine> mhall119, the hub can yes
[16:06] <ogra_> kenvandine, can't yell that loud
[16:06] <kenvandine> the facebook webapp needs to handle them
[16:06] <mhall119> ok
[16:07] <mhall119> jdstrand: slangasek: and just so I'm clear, is the Friends API being deprecated for security reasons, maintenance reasons, or both?
[16:09] <slangasek> mhall119: I would say both, but maybe jdstrand disagrees on the "security" part.  But if not security, then at least correctness of the model.
[16:10] <jdstrand> security isn't an issue. the friends policy group is currently reserved
[16:10] <jdstrand> I'm happy to remove it though
[16:11] <mhall119> ok
[16:12] <robru> jdstrand, slangasek, mhall119: well, security not an issue on the phone, but on the desktop friends exposes an unsecured posting API such that any dbus-aware app can impersonate you on any of your connected social media networks. so it's a security nightmare if you're installing debs
[16:14] <plars> barry: xnox: is everything working for python3 now so that the phablet-test-run check can be removed and just run every autopilot test with python3?
[16:15] <barry> plars: i don't think all the core app ap test ports to py3 have landed
[16:15] <plars> barry: xnox: apparently https://bugs.launchpad.net/ubuntu/+source/phablet-tools/+bug/1327325 is messing with some of the tests, which got me wondering if phablet-test-run can just skip that check now
[16:15] <plars> ok :(
[16:15] <barry> plars: but hey, a forcing function can be a good idea :)
[16:15] <plars> heh, that's one way to get there I guess :)
[16:15] <xnox> plars: things shouldn't print or execute stuff on import.... =)
[16:16]  * balloons listens
[16:16] <barry> plars: maybe the only way :/
[16:16] <xnox> plars: why do they do that? =)
[16:16] <plars> xnox: with reminders app, you get a warning it looks like:
[16:16] <plars> The ubuntuuitoolkit.emulators module is deprecated. Import the autopilot helpers from the top-level ubuntuuitoolkit module.
[16:16] <xnox> ...
[16:16] <xnox> plars: well that's a bug in reminders, now isn't it?
[16:16] <mhall119> robru: is it being removed from the desktop as well then?
[16:17]  * ogra_ thinks he has seen that message in many other tests too
[16:17] <plars> xnox: I would think so, but I think quite a few others might be affected as well
[16:17] <robru> mhall119, I hope so! My goal was to just nuke it from orbit. slangasek?
[16:17] <balloons> well it's just a warning about deprecation
[16:18] <barry> xnox: better to use a DeprecationWarning, which can be silenced (not sure if this particular case is or isn't)
[16:18] <ogra_> plars, webbrowser and terminal have the same message in console log
[16:18] <slangasek> robru: I have no opinion on the desktop side, ask the desktop team ;)
[16:18] <robru> ugh
[16:18] <ogra_> plars, but that doesnt seem to cause any issues
[16:18] <slangasek> robru: regardless, removal from the desktop doesn't require any of the same deprecation overhead... it just needs the desktop team to take a decision
[16:19] <slangasek> but "default apps on the desktop" are definitely the desktop team's bailiwick
[16:19] <robru> slangasek, back when we MIR'd friends, I don't think we ever actually completed the seeding of friends
[16:20] <slangasek> robru: it certainly is seeded
[16:20] <cjwatson> only in -desktop-next, right?
[16:20] <slangasek> no
[16:20] <slangasek> $ apt-cache show friends | grep Task
[16:20] <slangasek> Task: ubuntu-desktop, ubuntu-usb, edubuntu-desktop, edubuntu-usb, ubuntu-sdk-libs
[16:20] <cjwatson> oh, was looking at the wrong package
[16:21] <cjwatson> friends-app != friends :P
[16:21] <robru> cjwatson, slangasek: friends is where the security hole is. and friends-app doesn't function without it
[16:22] <balloons> so plars my guess then is other apps are running via py2 as well then, given the fact that warning forces it to use py2
[16:22] <cjwatson> it's not explicitly seeded - comes in via unity Recommends: unity-lens-friends Depends: libfriends0 Depends: friends-dispatcher etc.
[16:22] <robru> cjwatson, yeah we should drop that. I just grepped the seed and didn't see it
[16:22] <mhr3> robru, ehm, any idea what happened with line #16?
[16:22] <plars> balloons: but running it alone, I don't seem to have python2, so I guess we are just getting lucky and something else is installing python2
[16:23] <plars> balloons: we probably shouldn't count on that
[16:23] <mhr3> robru, i'm pretty sure i landed that last week
[16:23] <xnox> barry: what warning type is it? and can I silence it while doing the py3/py2 check?
[16:23] <mhr3> robru, i have no idea why is it in a silo again
[16:23] <balloons> plars, we don't want to use python2 ;-) And indeed it's not depending on python2. However the toolkit is, and that's what is pulling the python2 stuff in
[16:23] <balloons> there's a bug open for that :-)
[16:24] <robru> mhr3, indeed those mps both are merged. no idea how that got that way
[16:24] <robru> mhr3, i'll free it
[16:24] <plars> balloons: is that the one you pointed me to earlier, or a different one?
[16:24] <mhr3> robru, thx
[16:24] <balloons> plars, https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1339191
[16:25] <xnox> balloons: hm. it must to support unported apps.
[16:25] <balloons> xnox, that bug is asking for a split package if needed
[16:26] <xnox> barry: so ubuntuuitoolkit does "logger.warning("text")" can i subconvert that somehow?
[16:26] <xnox> balloons: that is no good.
[16:26] <xnox> balloons: because clicks.
[16:26] <xnox> balloons: we explicetely requested for all emulators to be bilingual.
[16:26] <balloons> plars, for reminders specifically I will try and update things so the warning goes away
[16:27] <xnox> balloons: and stay so, until everything is ported and python2 removed from testing infrastructure.
[16:27] <balloons> xnox, hmm.. it gets annoying pulling py2 stuff
[16:27] <balloons> xnox, well, see this is in the context of changing how we run tests..
[16:27] <xnox> balloons: plars: barry: do we know what's still unported?
[16:27] <balloons> the brave new world of autopkg
[16:27] <balloons> ideally we won't be shipping python or autopilot on the images
[16:28] <balloons> xnox, dialer app.. I'm not sure of what else
[16:29] <balloons> xnox, so if the requirement for being bilingual is because we don't do test depends correctly, I would say that's no longer an argument.
[16:30] <barry> xnox: i'm not 100% sure, but i have a bunch of branches that haven't been merged, mostly because there have been some flaky tests along the way
[16:31] <xnox> balloons: unported tests is the requirement for keeping /just/ the emulators bilinging. porting uported tests is still an argument =)
[16:31] <barry> xnox: unmerged branches (some may have landed via other means) include dialer-app, address-book-app, mediaplayer-app: https://code.launchpad.net/~barry
[16:32] <balloons> xnox, it shouldn't be a requirement once the runner is changed is what I'm saying. Have you see the work on autopkg to run clicks? and the manifest changes to specify dependencies?
[16:34] <xnox> balloons: sure. but existing unported apps, are using legacy runner, and legacy python2, and needs legacy ubuntu-ui-toolkit to have python2 compatible emulators.
[16:34] <xnox> balloons: splitting ubuntu-ui-toolkit into python2, and creating python3-ubuntu-ui-toolkit is waste of time into legacy stuff....
[16:35] <xnox> balloons: instead the higest priority is to merge barrys last remaining 3 packages, and drop python2 support all together everywhere, and worry about python3 only in the new runner with simplified dependencies and stacks.
[16:35] <xnox> balloons: and even bigger priority at the moment is that /current/ runner is using python2 against tests that have been ported to python3.
[16:36] <xnox> plars: barry: figured one-liner to silence the warning, will make proposal against phablet tools to fix this.
[16:36] <robru> sil2100, what's going on in silo 0? it's said "Landed. Cleaning Silo" for days now... can I clear that out?
[16:37] <xnox> plars: what example app/package/click should I use to test that it does "import .emulator" and isn't run with python3?
[16:37] <sil2100> robru: ah, sorry, let me finish that up ;) CI Train got a bit confused, need to commit some latest stuff for that
[16:37] <sil2100> robru: I'll deal with that in a moment
[16:37] <sil2100> No worries, and sorry about that ;p
[16:37] <balloons> xnox, fair enough.. in the end, py2 needs to go away. I am also concerned we are running many things with py2 because of how the runner is interacting
[16:37] <robru> sil2100, ok thanks. I just ask because it screws up the spreadsheet's ability to count how many free silos we have
[16:37] <sil2100> Ah, don't tell me it also takes into consideration silo 000?
[16:38] <robru> sil2100, yeah apparently it just goes 20-assigned and silo 000 counts under assigned.
[16:38] <robru> sil2100, my silo dashboard knows not to count it at least
[16:38] <plars> xnox: reminders sounds reasonable
[16:38] <plars> xnox: that's where it was failing before
[16:38] <plars> oh
[16:38] <balloons> xnox, clock has the warning
[16:39] <plars> xnox: wait, you need one that actually needs python2? I have no idea which ones actually need it
[16:39] <balloons> really most core apps have it
[16:39] <plars> xnox: that was my original question, I thought all were converted now
[16:39] <balloons> none of them need py2 ofc
[16:39] <plars> balloons: barry was saying that he thinks some of the core apps still need it
[16:39] <xnox> plars: no, not all converted. I need the one that is ported to python3, upon import generates "you shouldn't use ubuntuuitoolkit.emulators", and thus fallbacks to python2
[16:40] <sil2100> Laney: how's testing silo 18 going? ;)
[16:40] <xnox> plars: i will unbreak that, and make it run with python3 from now on, using phablet-test-run.
[16:40] <plars> xnox: ah, ok. In that case reminders is one for sure
[16:40] <xnox> plars: tah.
[16:40] <Laney> sil2100: hoping someone else will help out, looks okay to me
[16:40] <sil2100> kenvandine: ^
[16:41] <Laney> maybe brendand ?
[16:41] <sil2100> Oh, or om26er !
[16:41] <sil2100> om26er: do you have a moment for some testing now?
[16:41] <om26er> sil2100, yes
[16:42] <om26er> sil2100, what needs to be tested
[16:42] <sil2100> om26er: could you help out Laney with testing silo 18? It's a very important fix for the welcome wizard brokeness, which is critical
[16:42] <brendand> Laney, om26er is the right man
[16:42] <Laney> kay
[16:44] <om26er> Laney, Hi! what exactly do I need to test
[16:44] <Laney> om26er: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1341007 - just check you can go through the welcome wizard
[16:44] <om26er> that was quick
[16:44] <mterry> robru, can I have a medium-term silo assigned for line 28?
[16:44] <Laney> I think that there's a different mode for no sim (mterry confirm/deny please) so please check with and without sim
[16:45] <mterry> Laney, there is a different page displayed after the language page, yes
[16:45] <Laney> ta
[16:45] <Laney> I'll probably be gone before the testing is finished so please anyone just publish or not depending on om26er
[16:45] <om26er> Laney, mterry how do I force it to show wizard ? today when I flashed my phone I was welcomed with a background and empty toolbar. I rebooted and that wizard never appeared
[16:46] <robru> mterry, you got silo 4
[16:46] <Laney> om26er: delete ~/.config/ubuntu-system-settings/wizard-has-run and restart
[16:46] <mterry> robru, thank you!
[16:46] <robru> mterry, you're welcome!
[16:47] <mterry> Laney, om26er: or do phablet-config welcome-wizard --enable
[16:47] <Laney> oh, nice hax
[16:47] <xnox> balloons: plars: clicks are correctly handled.
[16:47] <plars> xnox: great!
[16:48] <xnox> balloons: plars: and since reminders is shipping python3 module only, in the test environment it is also handled correctly.
[16:48] <xnox> balloons: plars: how/when do you see python2 getting trigger?
[16:49] <plars> xnox: when using phablet-test-run to run the reminders app test
[16:50] <xnox> plars: can you give me full steps? since reminders app is a deb, running phablet-test-run, for me clearly gives that python3 is used.
[16:50] <plars> err
[16:50] <plars> I thought reminders was click installed
[16:50] <xnox> plars: running $ ps on my machine it has -> python3 listed.
[16:50] <xnox> plars: hm, there is a deb in the archive with correct debs. and it's not a pre-installed click that i have on my default image.
[16:51] <plars> xnox: which image are you on? it's on mine
[16:51] <plars> com.ubuntu.reminders    0.5.172
[16:52] <xnox> horum. no idea what image i'm on then. let me grab that one and push it to the image et.al.
[16:52] <xnox> plars: doh, published today, no i have an image from last week =)
[16:52] <plars> ah
[16:52] <balloons> :-)
[16:52] <plars> yeah, grab the latest proposed
[16:52] <xnox> plars: i actually use my phone.
[16:52] <mhall119> slangasek: jdstrand: I've published the announcement and will remove the API docs from the 14.10 section now, you are free to remove it from the images
[16:52] <slangasek> mhall119: cheers!
[16:53] <plars> xnox: but it's so much more exciting to depend on something running trunk :)
[16:55] <mterry> robru, I can't build with unapproved branches anymore?  :(
[16:56] <robru> mterry, you can, you just have to check the flag for that in the build job
[16:56] <mterry> robru, ah great
[16:56] <mterry> thx
[16:56] <robru> mterry, you're welcome.
[16:56] <mterry> That must be new?
[16:57] <robru> kenvandine, are you testing http://people.canonical.com/~platform/citrain_dashboard/#?q=landing-018 ?
[16:57] <sil2100> mterry: yep, recently added ;) As there were problems with people actually landing stuff not accepted anywhere
[16:58] <sil2100> robru: om26er is helping with testing that
[16:58] <robru> ah
[16:58] <sil2100> (at least he was to help!)
[16:58] <sil2100> ;)
[16:58] <sil2100> om26er: how's it going?
[16:58] <robru> mterry, also be aware of your system settings conflict with silo 18, you may need to rebuild
[16:58] <kenvandine> robru, i wasn't :)
[16:58] <kenvandine> but i can if needed
[16:58] <robru> kenvandine, oh i heard a rumour that you were...
[16:58] <kenvandine> i reviewed and tested the branch
[16:58] <pmcgowan> Laney, did you fix something to make the CI run on that wizard MR?
[16:59] <sil2100> robru: btw. really like the new looks of the CI Train Dashboard ;)
[16:59] <xnox> plars: https://code.launchpad.net/~xnox/phablet-tools/no-uitk-deprecation/
[16:59] <robru> sil2100, thank you! Yeah I tried really hard to make it have a cleaner look ;-)
[16:59] <xnox> plars: with ./phablet-test-run from that branch everything is tip-top
[16:59] <xnox> plars: scheduling to land now.
[16:59] <Laney> pmcgowan: which one?
[16:59] <plars> xnox: thanks!
[16:59] <mterry> robru, ok, will look thx
[16:59] <sil2100> robru: now it's much cleaner and somehow, how to say that... ubuntish ;)
[16:59] <pmcgowan> Laney, the one you are testing now
[16:59] <Laney> pmcgowan: no fixes in particular
[17:00] <Laney> We've got another mp gonig on in parallel to try and fix that
[17:00] <Laney> well, first to identify what is wrong
[17:00] <robru> sil2100, glad you like it!
[17:00] <sil2100> Good job in overall!
[17:00] <robru> thanks
[17:00] <balloons> plars, so what does this mean now for getting reminders into the image? we need phablet-tools to release/
[17:00] <balloons> ?
[17:00] <pmcgowan> Laney, seems to have worked here https://code.launchpad.net/~saviq/ubuntu-system-settings/fix-wizard-sim/+merge/226555 or am I missing something
[17:01] <Laney> hmm nope, didn't see that, must have been the run that kenvandine triggered
[17:01] <Laney> maybe something else got fixed?!
[17:02] <kenvandine> weird
[17:02] <kenvandine> it passed though :)
[17:02] <Laney> mysterious fixes, always reassuring :P
[17:02] <om26er> sil2100, it works, now testing without sim
[17:02] <plars> balloons: I just updated the MP, I think we can go ahead and land it. If it happens to run before the phablet-test-run branch lands, then it could fail though
[17:02] <sil2100> \o/
[17:02] <sil2100> Laney, robru, kenvandine: so you'll be able to land in a moment ^ :)
[17:03] <Laney> sil2100: cool
[17:03] <Laney> sil2100: I'm going now however, sure someone else can pres butan though
[17:03] <sil2100> robru: when that lands, make sure both mir and ubuntu-system-settings migrate to release and have an image kicked
[17:03] <sil2100> Laney: sure thing, thanks!
[17:04] <balloons> plars, awesome news, thanks!
[17:04] <plars> balloons: actually, I can even double check by trying it with the phablet-tools with the fix. I'll do that now just as an extra sanity test
[17:04] <xnox> plars: we had a fix since 2014-06-06 for that by fginther, but it wasn't merged nor landed.....
[17:04] <xnox> balloons: ^
[17:04]  * xnox dputs that into the archive.
[17:04] <balloons> xnox, yes, I mentioned it to plars in the beginning who mentioned it to you, heh
[17:04] <balloons> we went into the weeds too much I think
[17:05] <plars> balloons: a fix for what?
[17:05]  * balloons notes xnox has dput powers
[17:05] <xnox> plars: https://code.launchpad.net/~fginther/phablet-tools/fix-ptr-python3-import-check/+merge/222391
[17:05] <plars> I don't think I saw that you mentioned that
[17:05] <xnox> plars: python3 vs python2 misdetection.
[17:05] <plars> hah, no I didn't see that one
[17:05] <balloons> plars, when I mentioned the bug, I mentioned it the fix wasn't landed
[17:05] <plars> balloons: I saw the bug, but not the MP I guess
[17:05] <balloons> or maybe I didn't
[17:05] <slangasek> lool: ping
[17:05] <balloons> ahh
[17:05] <balloons> sorry, I'll take the blame for then :-)
[17:07] <robru> sil2100, sure thing
[17:07] <slangasek> ogra_, cjwatson: https://wiki.ubuntu.com/Click/Frameworks/UpdateProcess#preview as a first stab at documenting the deprecation process
[17:08] <slangasek> of course, this current activity neatly contradicts https://wiki.ubuntu.com/Click/Frameworks#How_long_are_frameworks_supported.3F , heh
[17:11] <robru> slangasek, yeah, if we can not support friends-service "ideally forever" I'll be very happy
[17:11] <slangasek> technically we would only have to support the API, not the service ;)
[17:12] <robru> slangasek, you mean create a stub that returns nothing? I'll happily do that ;-)
[17:12] <slangasek> robru: well, if "returns nothing" is semantically valid under the current API, yes ;)
[17:14] <robru> slangasek, yeah, I mean like, exposes the API but never actually makes any attempt to contact any social network, every API call is just a nop, etc.
[17:15] <slangasek> yeah
[17:15] <slangasek> that would be entirely valid, and then we wouldn't have to drop the 14.04 framework
[17:16] <slangasek> robru: how much work would that be?  I'm not sure it's worth putting a /lot/ of effort into
[17:16] <om26er> sil2100, its good to go, seems there is nothing related to run autopilot tests
[17:17] <robru> slangasek, probably actually not much. just make a few small changes in friends-dispatcher to not invoke any of the social network plugins, but still expose the dbus api. update the tests to recognize that everything just comes back empty... I could probably do that in a couple hours if you want.
[17:18] <robru> om26er, you talking about silo 18?
[17:18] <slangasek> robru: ok, I think that's worthwhile then
[17:18] <robru> sweet
[17:18] <om26er> robru, yes
[17:18] <slangasek> popey: ^^ are your friends-using apps ready to go, if robru neuters the api?
[17:19] <slangasek> jdstrand: ^^ if we keep the friends api around but make it a no-op, does that impact your apparmor changes at all?
[17:21] <sil2100> robru: o/ releaaaseeee
[17:21] <sil2100> SHIIIP IIIT
[17:23] <jdstrand> slangasek: no
[17:23] <jdstrand> slangasek: I'm going to remove the friends policy group for 1.2 and leave it for 1.1 and 1.0
[17:24] <jdstrand> a no op should just mean that if a 14.04 app on 14.10 uses it, then it'll just work since no additional permissions are needed
[17:30] <slangasek> jdstrand: ok :)
[17:35] <sil2100> o/
[17:39] <slangasek> robru: are you on point for the rebuild for this latest blocker landing (wizard not working)?
[17:39]  * Chipaca glares at ogra_ 
[17:40] <popey> slangasek: go for it, one has submitted a fix, the other is aware
[17:40] <robru> slangasek, yeah I'm just waiting for system settings to migrate then I'll poke somebody to kick an image build
[17:40] <slangasek> popey: ok, great
[17:40] <slangasek> robru: sounds like you're all clear to neuter the friends API then
[17:41] <robru> slangasek, sweeet
[17:41] <slangasek> robru: ok - that was the intent of my question, to see if you still needed help for kicking off the image builds :)
[17:41] <robru> slangasek, oh yeah, I can't do it myself.
[17:41] <slangasek> robru: ok; feel free to ping me when the time comes
[17:42] <mterry> robru, does building a silo's packages go one-by-one now?  only unity8 is building in the PPA, and jenkins seems to be waiting before uploading the next package to the PPA
[17:43] <robru> mterry, not sure, if that changed it'd be sil2100's doing, I didn't change that behavior
[17:43] <mterry> k
[17:43] <robru> mterry, as recently as friday I witnessed it doing all merges first, then doing all uploads, then the PPA builds go in parallel
[17:44] <mterry> I'll wait and see what happens once unity8 is done building
[17:45] <robru> mterry, according to the build log it did all the merges: https://ci-train.ubuntu.com/job/landing-004-1-build/134/consoleFull (grep for 'Trying to merge'). my guess would be your system-settings upload was rejected
[17:46] <mterry> robru, hmm https://ci-train.ubuntu.com/job/landing-004-1-build/134/console just shows a spinner.  Where do I see that upload error message?
[17:46] <robru> mterry, which is probably caused by the other silo having already uploaded an orig.tar with different contents for the same version. try a version bump and rebuild system settings (or wait a bit, since system settings is publishing and you'll need to rebuild in an hour anyway)
[17:46] <mterry> robru, that makes sense, sure
[17:47] <robru> mterry, the upload error message gets emailed to a mailing list that I'm not on, so I'm just assuming based on past experiences.
[17:50] <slangasek> cjwatson: so I went back and looked at lool's upload history to figure out that the framework revisions are apparently handled via ubuntu-touch-meta... I'm adding frameworks/ubuntu-sdk-14.10-qml-dev3.framework, but is this really all that's required?
[17:50] <slangasek> I guess the SDK then also needs updated to generate dependencies against -dev3 instead of -dev2
[17:50] <slangasek> seems too simple though :)
[17:50] <cjwatson> framework in ubuntu-touch-meta, preceded by security declaration in click-apparmor or whatever it is
[17:51] <slangasek> ah
[17:51] <cjwatson> and the store needs to be taught that it can accept uploads for this, which probably includes the click review tools
[17:51] <cjwatson> robru: mm, I should follow up on the discussions I'd had with Didier and William about improving that; I think I know what to do in citrain
[17:52] <robru> cjwatson, improving what?
[17:52] <cjwatson> The first step was to make the address in the changelog not be ps-jenkins, since that doesn't actually confer any benefit
[17:52] <cjwatson> who gets mailed about upload errors from citrain
[17:52] <robru> oh right
[17:53] <robru> cjwatson, can citrain spoof who the uploader is so launchpad sends the email to the right place?
[17:53] <cjwatson> if ps-jenkins is a robot preparing an upload according to my instructions, that doesn't mean that ps-jenkins belongs in the changelog
[17:53] <cjwatson> and that would give LP more information
[17:54] <cjwatson> I'm not sure that will be sufficient, but it's the sensible first step
[17:54] <robru> cjwatson, well the changelog attributes the committers, and the the bot gets credit just for the upload.
[17:54] <cjwatson> yeah, that's nonsense
[17:54] <cjwatson> from LP's point of view
[17:55] <cjwatson> it's just a bot acting on human instructions; it doesn't deserve credit any more than my editor does :)
[17:55] <robru> heh
[17:55] <cjwatson> and the [ Person ] bits of the changelog are useless to LP
[17:55] <cjwatson> I already agreed with Didier and William that we should change this, so just need to do it
[17:56] <cjwatson> might have a look on my next sheriff shift
[17:56] <robru> cjwatson, ok cool, happy to cooperate if you need me to review a branch against lp:cupstream2distro or something
[17:56] <cjwatson> ta, will let you know
[17:56] <robru> cjwatson, thanks
[17:56] <cjwatson> I think LP will still notify just the signer, as-is, but I can look into that
[17:56] <slangasek> cjwatson: according to jdstrand's comments above, the click-apparmor change seems to be to drop the friends policy group from the existing 1.2 (== ubuntu-sdk-14.10), so I think click-apparmor doesn't need to be uploaded first in this case
[17:56] <cjwatson> slangasek: ok
[17:57] <slangasek> since it doesn't appear to define separate -devX
[17:57]  * cjwatson -> dinner
[18:07] <jdstrand> click-apparmor shouldn't need any changes
[18:07] <jdstrand> it doesn't care about -dev, it only deals with the base framework
[18:08] <jdstrand> slangasek: ^
[18:13] <slangasek> jdstrand: right, that's what I gathered from the contents, thanks for confirming
[18:16] <robru> slangasek, https://code.launchpad.net/~robru/friends/neuter/+merge/226724 that should pretty well do it. so if that merge were to be released in ubuntu, we'd still have an api-complete friends-service and friends-dispatcher, except when you call the dbus api, nothing happens. so an app that depending on friends would still be able to import and call it, but it would just silently fail to send or receive any messages.
[18:16] <robru> kenvandine, can you help me test this? ^ ;-)
[18:19] <alecu> hi trainguards! I need to add one MP to landing-009, and in the process I'll take over the silo; anything special I should be doing besides filling the spreadsheet with the new MP and testplan?
[18:19] <alecu> and my name on the lander cell?
[18:20] <kenvandine> robru, in a bit, sure
[18:20] <Saviq> uh oh robru looks like something broke in the vm (ro file system) https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-utopic/433/console
[18:21] <robru> alecu, is the new MP part of the existing set of packages in there, or are you adding a new package?
[18:21] <robru> alecu, yes put your name in the lander cell
[18:21] <robru> Saviq, fun
[18:22] <alecu> robru: it's a new package. Was unity8, now, it's unity8+unity-scope-click
[18:22] <robru> alecu, ok, in that case just fill out the spreadsheet and then you need me to reconfigure. if it was all the same package, you can do the reconfigure yourself.
[18:23] <robru> fginther, any idea about saviq's failure ^^ ? I can't seem to log in to even retry that...
[18:25] <robru> alecu, let me know when the spreadsheet is up to date
[18:25] <fginther> robru, Saviq, the VM fs died a short while ago and we're still trying to clean up.
[18:25] <xnox> plars: OUCH! /o\ just saw your email
[18:26] <fginther> Saviq, the last two unity-phablet-qmluitests-utopic will need to be retried
[18:27] <plars> xnox: oh, the cobbler thing?
[18:28] <alecu> robru: it's up to date now, and ready to be reconfigured, thanks.
[18:28] <xnox> plars: yeah.
[18:28] <plars> xnox: yeah, it's a lovely failure mode, I can't install what you asked for, so I'm just going to silently give you something else
[18:28] <robru> alecu, which row was it?
[18:28] <alecu> robru: 25
[18:28] <plars> xnox: we think that cobbler install is just very borked, someone's working on it now
[18:29] <Saviq> fginther, thanks for the update
[18:29] <xnox> plars: sounds, better than most British restaurants. Usually, the waiter comes back 40 minutes later saying "oh we don't have the main you ordered, would you like to order something else?"
[18:29] <plars> xnox: *hopefully* that's really at the root of all our problems
[18:29] <plars> xnox: hah
[18:29] <robru> mterry, ok, please rebuild system settings now
[18:29] <mterry> robru, ah thanks for the heads up
[18:30] <robru> mterry, you're welcome
[18:30] <plars> xnox: this would be more like ordering steak, and having the waiter bring you a mud cake shaped into the form of a steak 40 min. later
[18:32] <xnox> plars: well, not mud cake, but steak made from oatmeal is what I usually get when i accidentally walk into a vegetarian restaurant.
[18:33] <plars> ew
[18:42] <alecu> Saviq: so, I've requested only unity-scope-click to be rebuilt. Will the unity8 debs be included in the same ppa? Where do I find out when they have been built?
[18:42] <Saviq> alecu, the build job will wait for boht
[18:42] <Saviq> both
[18:42] <Saviq> alecu, and yes, they're in the same PPA
[18:42] <alecu> great.
[18:44] <robru> alecu, queuebot will ping you in this channel when the build is complete. also you can watch the build log: https://ci-train.ubuntu.com/job/landing-009-1-build/109/console
[18:44] <kenvandine> robru, ok, so what needs testing?
[18:44] <kenvandine> robru, apps that use the API should just do nothing right?
[18:44] <robru> kenvandine, yep
[18:45] <robru> kenvandine, started a silo: http://people.canonical.com/~platform/citrain_dashboard/#?q=landing-013
[18:45] <robru> kenvandine, I guess basically, just install that silo (once it's done building) and then run friends-app and make sure it runs without crashing, but no messages get loaded
[18:45] <kenvandine> ok
[18:48] <robru> slangasek, hey what ever happened in silo 8? do you need any more help with that?
[18:51] <slangasek> robru: waiting for exploratory testing; tvoss and davmor2 driving this AIUI
[18:51] <robru> slangasek, alright thanks
[19:14] <robru> slangasek, you around to kick an image build? system settings finally migrated
[19:14] <slangasek> robru: yep
[19:14] <robru> slangasek, thanks!
[19:17] <kenvandine> robru, it runs without crashing, but i tried to post with it and it just spins
[19:17] <kenvandine> doesn't blow up though
[19:17] <kenvandine> i guess it's the async call waiting
[19:17] <robru> yeah the post should be unsuccessful
[19:18] <kenvandine> not getting through
[19:18] <kenvandine> and nothing new in my feed
[19:18] <robru> kenvandine, oh right, I just return instead of calling the callback
[19:19] <rsalveti> robru: are we building a new image before cron today?
[19:20] <robru> rsalveti, yep slangasek just kicked one now
[19:20] <rsalveti> oh, great then
[19:20] <rsalveti> just saw that a bunch of important fixes landed
[19:20] <robru> rsalveti, yep ;-)
[19:22] <robru> kenvandine, ok, I changed it to call the success callback so it doesn't just spin forever. rebuilding now
[19:23] <kenvandine> thx
[19:25] <imgbot> [19:27] <cjwatson> ogra_: Nitpick: could imgbot say "trainguards" rather than "trainguard", since the former is the string that AFAIK we've been told to highlight on?
[20:11] <robru> cjwatson, any idea why http://ppa.launchpad.net/ci-train-ppa-service/landing-013/ubuntu/dists/ no longer has a 'devel' directory? that was handy...
[20:19] <robru> kenvandine, tested the new thing, looks good. friends-app runs fine, no messages show up, posting messages happens instantly but go nowhere. think I should publish?
[20:20] <kenvandine> robru, testing
[20:23] <kenvandine> robru, posting still just spins for me
[20:24] <robru> kenvandine, testing on device? I didn't see any spinner
[20:24] <kenvandine> robru, and a reply just crashed...
[20:24] <robru> but but
[20:25] <robru> how can it crash? it just returns successful immediately!
[20:25] <kenvandine> displatcher logged something about signatures
[20:25] <kenvandine> oh, i think the callback expects an arg
[20:25] <kenvandine> upload i think returns the url returned from facebook
[20:25] <robru> kenvandine, can the arg be a string? I'll put a little deprecation warning int here
[20:26] <kenvandine> i seem to recall them all taking a string
[20:26] <robru> kenvandine, ok if I put a string in there will it crash if it isn't a URL? can the string be 'Warning: friends is now deprecated' or do I have to contort it into 'http://example.com/friends-is-now-deprecated' or something?
[20:27] <kenvandine> shouldn't need to be a url
[20:27] <robru> ok
[20:27] <kenvandine> i think the reply and send functions return the message id
[20:27] <kenvandine> or something
[20:28] <cjwatson> robru: I believe that's a known bug introduced by recent changes to Apache configuration on ppa.launchpad.net
[20:29] <cjwatson> I saw an Asana task for that the other day
[20:29] <robru> cjwatson, so should I update my citrain script to point at utopic or will devel come back?
[20:30] <kenvandine> robru, looks like all the async functions pass a result string to the callback
[20:30] <kenvandine> so just stick a string in those :)
[20:30] <robru> kenvandine, ok, just pushed a fix, will rebuilt
[20:30] <kenvandine> cool
[20:32] <alecu> trainguards: I need a silo for this MP, should I just add it to the spreadsheet? https://code.launchpad.net/~ted/pay-service/verify-after-purchase/+merge/226728
[20:33] <robru> alecu, yep
[20:34] <cjwatson> robru: I think it should come back, but let me check
[20:35] <cjwatson> wgrant: ^- You seem to have marked the FollowSymLinks task for ppa.lp.net as done this morning, but robru reports that http://ppa.launchpad.net/ci-train-ppa-service/landing-013/ubuntu/dists/ doesn't list "devel", and http://ppa.launchpad.net/ci-train-ppa-service/landing-013/ubuntu/dists/devel/ returns 403
[20:35] <cjwatson> So I think there's still something wrong there
[20:38] <robru> alecu, ok you got silo 5
[20:42] <bschaefer> sooo unity8 is still broken on the desktop?
[20:45] <alecu> robru: thanks!
[20:45] <robru> alecu, you're welcome!
[21:00] <robru> kenvandine, ugh, just updated, of course *now* I'm getting spinner forever.
[21:00] <imgbot> [21:00] <imgbot> [21:00] <robru> kenvandine, maybe spinner forever is a good thing, will indicate to users that it's not usable ;-)
[21:00] <robru> still no idea why it's doing that, I'm calling the success callback
[21:01] <robru> kenvandine, maybe a race condition or something? friends-app displaying the spinner after the callback already gets called to hide the spinner?
[21:02] <robru> kenvandine, at least it isn't posting the message.
[21:02] <robru> kenvandine, so I think this is fine since friends-app is also being de-seeded.
[21:05] <kenvandine> robru, the silo is still rebuilding
[21:05] <robru> kenvandine, heh, armhf finished before the rest of the silo did so I started testing sooner ;-) (also done now)
[21:05] <kenvandine> ok
[21:07] <kenvandine> robru, reply works right, but post isn't
[21:08] <kenvandine> seems ok though, it doesn't crash and doesn't do anything bad
[21:08] <robru> kenvandine, yeah I'm fine with this
[21:08]  * kenvandine needs to head out though
[21:08] <kenvandine> bbl
[21:08] <robru> kenvandine, k, i'm gonna publish. cya
[21:13] <robru> slangasek, hey what's going on with the friends-app de-seed? it's still on the phone in image 130
[21:14] <slangasek> robru: possibly a race with germinate?  ubuntu-touch-meta 1.165 is in utopic now and should unseed it, to be sure
[21:15] <robru> slangasek, ah, image 130 just has 1.163. ok thanks
[21:26] <robru> brb
[22:31] <robru> Blam.
[22:31] <robru> I hope image #131 doesn't get depressed, because it's not going to have any friends! http://instantrimshot.com/
[22:54] <popey> robru: http://tumbleweed.popey.com/
[22:56] <robru> popey, where did you find that picture of my home town?
[23:02] <popey> heh