[07:06] <didrocks> @cihelp: I can't connect to desktop-team@q-jenkins.ubuntu-ci (asking me for a password). I want to deploy latest lp:cupstream2distro, who can do it?
[07:28] <vila> didrocks: 'You are missing 41 revisions:' , pfew, serious update, are you confident enough that I can pres enter after 'bzr pull -v' ?
[07:29] <didrocks> vila: yeah, tests are running
[07:29] <didrocks> vila: only the latest rev is really impacting this ocde
[07:29] <didrocks> code*
[07:29] <vila> didrocks: and just in case some vanguard doesn't know it yet, this is documented at https://wiki.canonical.com/UbuntuEngineering/CI/Playbook/q-jenkins#Deploy_cu2d_code
[07:29] <didrocks> ah great ;)
[07:29] <vila> didrocks: huh ? 'tests are running' and it's ok to deploy ?
[07:29] <didrocks> vila: running as "running successfully", sorry :)
[07:30] <vila> ha
[07:30] <vila> didrocks: done
[07:30] <didrocks> vila: if after that you have time: any idea why we can't access to desktop-team anymore btw?
[07:30] <didrocks> vila: thanks!
[07:30] <didrocks> or maybe someone can just create a jenkins job allowing us to deploy
[07:31] <vila> didrocks: err I thought that was a fallout from removing [root] access to ci hosts and that you knew that for.. weeks ?
[07:32] <vila> didrocks: and yes, creating a jenkins job sounds like the way to go, it doesn't make a lot of sense (to me) to require a hard sync between 2 humans for such a task
[07:32] <vila> didrocks: let's discuss that with ev
[07:33] <didrocks> vila: desktop-team never had root access to q-jenkins IIRC
[07:33] <cyphermox> didrocks: want to do the pre-NEW for usensord and goget-ubuntu-touch?
[07:33] <didrocks> I'm ok with not having access, just need the jenkins job soon then :)
[07:33] <vila> didrocks: sure, but it's kind of the same motivation (AIUI). That's why I say we need to clarify that with ev
[07:34] <didrocks> cyphermox: I've done them, see my answers on the landing spreadsheet (last lines)
[07:34] <didrocks> cyphermox: still some work needed :)
[07:34] <cyphermox> alright.
[07:34] <didrocks> vila: yeah, would have been great to have the warning (if I didn't miss it) though ;)
[07:34] <cyphermox> tbh I didn't check it again in the past hour
[07:34] <didrocks> cyphermox: yeah, it's really really fresh from less than 30 minutes ;)
[07:35] <didrocks> cyphermox: however, always remember to check if there is a copyright file in the source btw while doing bootstrapping
[07:35] <cyphermox> yeah, i was hacking at bluez and sponsoring chad's gnome-bluetooth update
[07:35] <didrocks> cyphermox: it's something upstream is used to oversee :)
[07:35] <cyphermox> well, if the copyright is in the files it's not a huge deal..
[07:36] <didrocks> it's ok for other licenses, not for *GPL
[07:36] <vila> didrocks: well, I raised the issue on 2013/11/22 according to asana ;)
[07:36] <cyphermox> you get to check all the files individually anyway if you review this thoroughly, just in case a LICENSE file doesn't match what the files actually say
[07:36] <didrocks> vila: sure I was in the destinaries? :)
[07:36] <cyphermox> oh, right
[07:36] <didrocks> cyphermox: right, what the archive admin are doing
[07:37] <cyphermox> yeah
[07:37] <didrocks> cyphermox: licensecheck -r * --copyright
[07:37] <didrocks> in case you don't know that command
[07:37] <didrocks> really useful, catch 90% :)
[07:37] <cyphermox> I forgot about that crap about adding the copying file because you need to physically ship the whole thing with it
[07:37] <cyphermox> I know
[07:37] <cyphermox> I check it and then look at the files manually too to be sure
[07:38] <cyphermox> licensecheck misses some stuff
[07:38] <cyphermox> less for GPL, but other weird licenses or setups... e.g in cordova
[07:38] <didrocks> oh right, for those…
[07:38] <didrocks> anyway, just a head's up it's a common mistake :)
[07:39] <cyphermox> yeah
[07:39] <vila> didrocks: you weren't, just mentioning that the issue existed back then and the discussion started
[07:39] <vila> didrocks: so it's not new ;)
[07:39] <didrocks> vila: ah… so, that explains why I wasn't aware "weeks" ago :)
[07:43] <vila> didrocks: you were aware,2013-12-13 10:26:54 +0100 <didrocks>	vila: I'll need you to deploy the latest cu2d
[07:45] <didrocks> vila: don't turn into another way something that doesn't mean that…
[07:45] <didrocks> vila: it was that fact that I thought you cp ~destkop-team/cupstream2distro ~jenkins/cupstream2distro
[07:45] <didrocks> and not ln -s it
[07:45] <didrocks> we discussed it over hangout
[07:46] <vila> didrocks: Indeed, that's why I say the issue is known, nothing has changed since then
[07:46] <didrocks> vila: ? you told me it was just a ln -s in the end
[07:47] <didrocks> vila: so no, I even didn't try to ssh desktop-team@ at the time
[07:47] <didrocks> and I wasn't aware/warned about this
[07:48] <vila> didrocks: let's re-start from scratch,
[07:49] <vila> didrocks: I filed the issue in asana when I realized ci was asked to deploy cu2d, which is when you lost the ability to do it yourself (or wanted to transfer that responsibility, the details are unclear)
[07:50] <vila> didrocks: whether you didn't understood the details at the time is also unknown to me
[07:50] <vila> didrocks: but the point is: AFAIK, only access rights have changed, the layout on dick never changed
[07:50] <vila> err, disk ;)
[07:50] <didrocks> vila: we discussed over IRC and I thought it was because you cp the code, not ln -s it
[07:50] <didrocks> anyway, as told, I don't care about access, as long as you debug it
[07:51] <didrocks> but clearer communication from the CI team would be needed to warn about it
[07:51] <didrocks> and now, we need a job to deploy ;)
[07:51] <sil2100> Morning!
[07:52] <didrocks> hey sil2100!
[07:52] <vila> didrocks: no 'ln -s' was involved ever, there was nothing to communicate about :)
[07:53] <didrocks> vila: removing access rights was to communicate about
[07:53] <vila> didrocks: the existing symlink was not changed, the issue was $JENKINS_HOME
[07:53] <didrocks> vila: but seems you don't want to recognize it's an issue, I'm afraid about future communication channel though :/
[07:53] <didrocks> anyway, let's move on
[07:54] <vila> didrocks: yeah, let's move on, but *you* should recognize that "you don't want to recognize it's an issue" is non-sense when *I* tell you that I filed an issue
[07:54] <didrocks> vila: seems childish to me, anyway…
[07:55] <didrocks> filed to somewhere I don't have access or pinged about != communicating to the other the access write will be changed
[08:02] <vila> didrocks: I take blame gladly when it's deserved. In this specific case, access changes to the ci hosts has been communicated. You've been well aware of the issues related to moving q-jenkins during the 1ss move and were involved in requesting cu2d code and jobs deployments to the ci team instead of handling them yourself. I fail to see why you don't want to ack that. I've asked back then that the issue was addressed, it still hasn
[08:02] <vila> 't. We did get some required bits documented though. But the issue remains as reported: it makes little sense to me to require the ci team to push a button when the landing team says it's the right time to do so. I've been advocating that the landing team stays in charge.
[08:03] <vila> didrocks: see https://app.asana.com/0/8309126707866/8799306105026
[08:04] <didrocks> vila: that's what is wrong, I'm asking you for the past 30 minutes *when* I was communicated about those credentials removal. When you moved to 1ss, we still had this access at first
[08:05] <didrocks> vila: the task you are showing is Mirv talking, not me
[08:05] <didrocks> vila: so, I'm just asking for when those things happen, an email, something to communicate (and again, if I missed that email, I'm happy to be corrected and my bad)
[08:07] <didrocks> and again, the discussion you pasted in December, I still had access to desktop-team@ (or at least, I believe) and was just thinking you discussed that you cp -a ~desktop-team@q-jenkins.ubuntu-ci ~jenkins@q-jenkins.ubuntu-ci and that's what we discussed over hangouts
[08:07] <didrocks> nothing related to "can't access to desktop-team@"
[08:08] <didrocks> (thanks for adding me as a follower for this task)
[08:09] <vila> good, we're making progress, I still don't know if/when access changes (and I'm blaming no one !), I only focused on something in the process that seemed wrong: the landing team should be able to decide when cu2d code and jobs are deployed. This has changed and I raised the issue as I thought it was wrong.
[08:10] <vila> Since we seem to share the same goal, let's focus on getting it solved instead of blaming each other ;)
[08:10] <didrocks> vila: I wasn't blaming you at all, just ensuring that we have better communication when such operations happen
[08:10] <didrocks> vila: on the second point, agreed, I think we should be in control of the deployment
[08:11] <vila> didrocks: ok, that's where the misunderstanding started then, since you did request some deployments since last November, I thought you knew you couldn't do it yourself anymore
[08:11] <vila> didrocks: and didn't even try to check if that was the case or not
[08:11] <didrocks> vila: Mirv did ask in November, and I cleared out why I asked on December ;)
[08:12] <didrocks> so good ;)
[08:12]  * didrocks adds a job for this btw on citrain meanwhile
[08:12] <vila> didrocks: and I think fginther did create a jenkins job to deploy cu2d jobs (I may be wrong...)
[08:13] <vila> yeah, documented on https://wiki.canonical.com/UbuntuEngineering/CI/Playbook/q-jenkins#Deploy_cu2d_jobs , we're getting therre ;)
[08:14] <didrocks> vila: seems I can run it even
[08:14] <didrocks> so great ;)
[08:19] <jibel> vila, didrocks didn't this 'access' issue started when access control switch from local accounts to centralized ldap a week or so before Christmas holidays?
[08:20] <didrocks> jibel: ah, that would make even more sense and match the timeline, was that communicated and I missed that email (as I was on holidays, I maybe lost the email about that change in the flood of christmas emails)?
[08:20] <jibel> vila, I lost all access to management accounts that are not in ldap when this switch occured
[08:20] <didrocks> ev: FYI ^
[08:37] <popey> didrocks: will miss the landing call as I need to take a cat to the vet
[08:37] <popey> only appointment I could get
[08:37] <didrocks> popey: no worry, we'll give all the work to you then :)
[08:38] <popey> \o/
[08:38] <didrocks> popey: you should call for the hangout on ubuntu touch app ;)
[08:46] <popey> Not sure what's more painful. Trying to use G+ on Ubuntu Touch, or trying to get a mad cat into a box.
[08:47] <didrocks> it was surely easier when it was smaller :)
[08:49] <popey> heh
[09:00] <popey> didrocks: #121 is fine, spreadsheet updated
[09:01] <didrocks> popey: thanks!
[09:10] <sil2100> didrocks: in-between stuff, could you approve https://code.launchpad.net/~sil2100/cupstream2distro-config/mediascanner_v2_enable/+merge/201142 ?
[09:10] <popey> morning sil2100, happy new year
[09:11] <sil2100> popey: hello and happy new year to you too!
[09:11] <didrocks> sil2100: that was what I wanted to talk about to you:
[09:11] <didrocks> $ bzr branch lp:mediascanner-v2
[09:11] <didrocks> bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/+branch/mediascanner-v2/".
[09:11] <didrocks> so, the branch is in mediascanner/v2 something
[09:11] <didrocks> and so source package name != project name, right?
[09:12] <sil2100> Ah, right, that will cause problems, they didn't want to create a new LP project not to bloat LP, but I guess it's needed
[09:13] <didrocks> sil2100: yeah
[09:31] <didrocks> sil2100: coming?
[09:31] <sil2100> Yes yes! Trying to hangout
[09:32] <didrocks> Saviq: do you mind having a try on r121 to look at the unity8 crashes on mako?
[09:32] <didrocks> maybe those will be better :)
[09:33] <ev> vila, didrocks: I think two things are getting confused here. One is that we moved to userdirldap for authentication, to replace the mess of different sets of manually created accounts on different systems. The other is that we removed root access from non-CI accounts and removed the ubuntu account (we should have, at least). This is to make us more
[09:33] <ev> responsible (and blamable) for running the infrastructure, rather than expecting other teams to pull the levers. Larry sent mails about both of these.
[09:33] <ev> I think a Jenkins job that automagically did the deployments would be a good idea.
[10:23] <vila> ev: late notice, but yeah, "Jenkins job that automagically did the deployments" is what I suggest in the asana ticket
[10:34] <ev> vila: cool, I'll have a look. I was flooded with tasks this morning, so it's a bit slow going getting to email and asana
[10:35] <ev> psivaa: can I give a task to you to verify that 12.04.4 is ready for the OSP2 team? I can forward you the email with the full details
[10:36] <ev> infinity is sleeping still, but they need to know by EOD in Taipei
[10:37] <vila> ev: no worries
[10:37] <psivaa> ev: sure, i'll still need to see the details :)
[10:38] <ev> cool, forwarding
[10:38] <psivaa> ev: thanks
[10:39] <ev> sent
[10:48] <Saviq> ev, hey, do you have an idea what might be happening here https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/1930/ ?
[10:48] <Saviq> ev, suddenly tonight unity8 started SEGV'ing on every single test
[10:50] <cjwatson> psivaa: don't worry about it, I've replied directly
[10:51] <psivaa> cjwatson: ok, thanks.
[10:54] <ev> Saviq: tracking at https://app.asana.com/0/8736198969650/9504356304887
[10:55] <Saviq> ev, thanks, first I've seen asana, though...
[10:59] <ev> Saviq: we use a project in asana to track the work by the vanguard
[10:59] <ev> thought it might be helpful for you to see updates to that task
[10:59] <Saviq> ev, sure, thanks
[11:51] <sil2100> didrocks: could you re-take a look at https://code.launchpad.net/~sil2100/cupstream2distro-config/mediascanner_v2_enable/+merge/201142 once you have a free moment? The project name has been set, changed and prepared
[11:58] <didrocks> sil2100: was it preNEWed?
[12:00] <sil2100> didrocks: not yet, but we can do this after this is merged in - I did a pre-preNEW review myself, if we have this in we can at least have it building and then make it easier for people to test and check
[12:01] <didrocks> sil2100: approved it then
[12:01] <sil2100> didrocks: thank you!
[12:01] <sil2100> didrocks: I'll proceed with the preNEW now etc. etc.
[12:12] <didrocks> yw!
[12:49] <Laney> would it be possible for me to get access to retry autopkgtests?
[13:01] <sil2100> didrocks: are you very busy? It seems seb is rather busy today with other work, maybe you could preNEW lp:mediascanner2 ? No problem if you are busy as well, I can poke further then ;)
[13:02] <didrocks> sil2100: quite busy, but I guess nobody else is available :)
[13:11] <didrocks> sil2100: reviewed, +1. Really nothing to mention, good work!
[13:12] <didrocks> seb128: FYI ^
[13:13] <sil2100> \o/
[13:13] <sil2100> Thank yoU!
[13:17] <seb128> didrocks, thanks
[13:24] <sil2100> didrocks: hm, is it normal that I can't access q-jenkins through ssh anymore?
[13:24] <didrocks> sil2100: I discovered that this morning as well, so apparently, it is, you need to ask someone to pull the cu2d-config I guess
[13:24] <Laney> see my request ^ someone ;-)
[13:24] <sil2100> didrocks: ACK
[13:24] <Laney> or I can apply britney hints
[13:25] <sil2100> Laney: sadly, I don't know anything about that - didrocks ^ ? ;)
[13:25] <didrocks> I don't either
[13:25] <didrocks> Laney: you need to ping cihelp
[13:25] <Laney> okay, guess you just did, thanks
[13:25] <cjohnston> Laney: if you check the topic, there is a vanguard.. please use the vanguard
[13:26] <sil2100> josepht: hi! Do you know if anyone could pull the latest cu2d-config on q-jenkins? I added a new project which I need to appear on jenkins
[13:27] <Laney> cjohnston: ok
[13:27] <Laney> josepht: Do you know if it's possible for me to get jenkins access to retry autopkgtests?
[13:27] <josepht> sil2100: I'll find someone to do this soon and let you know
[13:28] <sil2100> josepht: thanks!
[13:29] <josepht> Laney: I'll find out and let you know
[13:30] <Laney> ty
[13:48] <dobey> didrocks: hi. is cu2d deployed already with that change? i saw you had to ask for it, and lp says that comment was 6 hours ago :)
[13:48] <didrocks> dobey: yeah, it's done ;)
[13:49] <sil2100> dobey: hello! I have a new change that needs redeploying if anything ;)
[13:51] <dobey> hi sil2100
[13:51] <dobey> didrocks: cool
[13:53] <josepht> sil2100: is this what you are expecting to see? http://q-jenkins.ubuntu-ci:8080/job/cu2d-media-head-1.1prepare-mediascanner2/
[13:54] <didrocks> sil2100: while I was on snakefruit, I bzr pulled btw
[13:54] <sil2100> josepht: yes! I see it in jenkins now, thanks :)
[13:54] <josepht> sil2100: np
[13:54] <didrocks> for the whitelist
[13:54] <sil2100> didrocks: thanks! So we're ready for a release then \o/
[13:54] <sil2100> Let me build everything
[13:54] <dobey> who's around that i can bug to ask for some daily release ppa builds?
[13:54] <didrocks> sil2100: hum
[13:54] <didrocks> sil2100: not on q-jenkins though
[13:54] <didrocks> sil2100: not sure if this was done :p
[13:55] <sil2100> didrocks: I guess it was! I think josepht did it just now?
[13:55] <didrocks> ok, if the job bzr pull the config as well
[13:55] <didrocks> (I think it's only needed when we add a stack anyway, I don't remember)
[13:55] <didrocks> for q-jenkins
[13:55] <fginther> morning
[13:57] <josepht> good morning fginther
[13:57] <didrocks> hey fginther
[13:57] <sil2100> fginther: morning!
[13:58] <fginther> wow, such a welcoming channel
[13:58] <josepht> fginther: everybody needs something :)
[13:58] <sil2100> ...;)
[14:19] <josepht> Laney: can you register an account here: http://d-jenkins.ubuntu-ci:8080/ you'll need VPN access with DNS configured.
[14:22] <didrocks> davmor2: oh, forgot to ask you, can you run some tests on image 121? it's a candidate for promotion :)
[14:23] <davmor2> didrocks: hmmmmmmm hang on
[14:25] <davmor2> didrocks: yeap I'll make a start in about 10 minutes
[14:25] <didrocks> davmor2: thanks, no hurry!
[14:30] <dobey> cihelp: who can i ping to request some daily-release PPA builds?
[14:30] <cjohnston> dobey: please use the vanguard in the topic
[14:30] <josepht> dobey: I'll find someone
[14:30] <dobey> thanks josepht
[14:31] <Laney> josepht: done; I'm laney
[14:35] <dobey> kenvandine: ^^ i guess i get to bug you again :)
[14:36] <dobey> kenvandine: can you trigger the daily build job for ubuntu-purchase-service again (or click stack if it's the whole stack thing)? thanks
[14:37] <josepht> Laney: okay, I've added permissions to your user.  I'm assuming you know when and when not to kick-off retries. :)
[14:38] <Laney> josepht: thanks
[14:38] <josepht> Laney: np
[14:38] <Laney> I'll try and be good ... we used to have this ability before
[14:40] <kenvandine> dobey, kicked
[14:43] <dobey> kenvandine: thanks
[14:43] <davmor2> popey: wow you must really be wishing this year away if you think it is the 10/09/2014 ;)
[14:43] <popey> hah
[14:46] <sil2100> kenvandine: hello! Happy new year! Can you take a look? https://code.launchpad.net/~sil2100/cupstream2distro-config/new_extras_media/+merge/201196
[14:47] <kenvandine> happy new year sil2100
[14:53] <sil2100> LP is awefully slow in generating diffs today
[14:57] <dobey> kenvandine: the things all built. yay!
[14:58] <fginther> didrocks, what was the issue with credentials and deploy cu2d? https://code.launchpad.net/~dobey/cupstream2distro/native-versions/+merge/200736/comments/467801
[14:58] <didrocks> fginther: can't connect to desktop-team@q-jenkins anymore (and we weren't warned about the creds removal)
[14:59] <didrocks> fginther: as we have the job for deploying, it's fine, we won't be able to help though debugging if needed
[14:59] <fginther> didrocks, thanks, I wanted to understand what issue was
[14:59] <didrocks> no worry ;)
[15:00] <kenvandine> sil2100, yeah, i'm still waiting for a diff
[15:00] <sil2100> kenvandine: I think it will be faster just to look here: http://bazaar.launchpad.net/~sil2100/cupstream2distro-config/new_extras_media/revision/996
[15:01] <kenvandine> ack
[15:02] <cjwatson> sil2100: Looks like the celery instance that's supposed to deal with this was left stopped by mistake after an upgrade.  I've asked ops to restart it
[15:03]  * didrocks out for a run
[15:09] <cjwatson> sil2100,kenvandine: it's back up now; I suspect it has something of a backlog but it should get there
[15:09] <kenvandine> cjwatson, thanks
[15:13] <didrocks> sil2100: do you mind checking latest properties-cpp that is in the ppa as well?
[15:13] <didrocks> sil2100: if good, I'll resync it after a quick check
[15:17] <cjwatson> sil2100: hmm, it's still saying "Updating diff", but the diff is up to date
[15:18] <cjwatson> sil2100: so, um, I don't know, if it's important ask #launchpad-ops internal, hopefully you can disregard it as noise :)
[15:28] <sil2100> didrocks: ok, will do that in a minute
[15:29] <sil2100> cjwatson: I'll look into that, since last time I had like 5-10 minute delays, but now it's taking far longer
[15:29] <cjwatson> sil2100: well, before you ask anyone to investigate, see what it's like on something pushed after the celery instances were restarted 20 minutes ago
[15:29] <xnox> when does #122 kicks off?
[15:30] <xnox> or shall i do another run now?
[16:50] <didrocks> xnox: anything that needs to be kicked off right now?
[16:50] <didrocks> davmor2: not sure if you meant in your email that you have seen regression or not (doesn't seem so)
[16:52] <davmor2> didrocks: no regressions they are old bugs
[16:56] <didrocks> davmor2: thanks for cleaning that up
[16:57] <didrocks> sil2100: did you publish it?
[17:01] <sil2100> didrocks: going to the meeting! One moment!
[17:01] <ogra_> same here
[17:02] <didrocks> kenvandine: coming?
[17:02] <didrocks> that was quick ;)
[17:03] <kenvandine> ha
[17:03] <kenvandine> i was already joining ;)
[17:04] <xnox> didrocks: i don't think so, i thought it was cronned.
[17:06] <didrocks> xnox: cronned once a day
[17:07] <xnox> didrocks: ack, thanks.
[17:11] <cjwatson> didrocks: twice a day, as requested near end of last year
[17:11] <cjwatson> didrocks: oh, somebody put it back to once a day, OK ...
[17:11]  * cjwatson actually reads crontab -l
[17:11] <ogra_> cjwatson, yep, i did on monday
[17:11] <cjwatson> ok
[17:11] <ogra_> oh, i forgot to commit that
[17:11] <ogra_> sorry
[17:13] <cjwatson> not sure I committed the move to twice a day *shrug*
[17:13] <ogra_> heh
[17:25] <didrocks> sil2100: both NEWed, please update the spreadsheet :)
[17:27] <sil2100> didrocks: \o/
[17:27] <didrocks> sil2100: I'll let you track and update the spreadsheet :)
[18:17] <ogra_> [18:18] <sil2100> \o/
[18:18] <sil2100> Thanks!
[18:27] <kenvandine> fginther, can you look at a failure for me?  is this failing because of ssh host key failure?
[18:27] <kenvandine> https://code.launchpad.net/~ricmm/unity-mir/sidestage-reenable/+merge/198489
[18:27] <kenvandine> whoops
[18:27] <kenvandine> https://jenkins.qa.ubuntu.com/job/bamf-trusty-amd64-autolanding/8/console
[18:27] <kenvandine> fginther, ^^
[18:47] <sergiusens> robru, cyphermox kenvandine hey the convention for go sourcepackages is to add golang-
[18:47] <sergiusens> wrt https://code.launchpad.net/~robru/goget-ubuntu-touch/fix-prepare/+merge/201240
[18:47] <kenvandine> sergiusens, the problem is we need the project name to match the source package name
[18:47] <kenvandine> so the alternative is to rename the project
[18:48] <sergiusens> ack; conflicting conventions :-/
[18:50] <fginther> kenvandine, I reapproved the MP, the problem was fixed a short while ago
[18:52] <kenvandine> fginther, thx
[18:55] <robru> sergiusens, if you really insist on having golang- prefix in the source package name, you need to copy lp:goget-ubuntu-touch to lp:golang-goget-ubuntu-touch. it's entirely possible to do, I just chose to rename the source package because it seemed like less work at the time.
[18:55] <robru> sergiusens, let me know how you want to proceed with that.
[18:55] <sergiusens> robru, it's ok I guess; we'll just diverge
[18:56] <robru> sergiusens, thanks
[18:56] <sergiusens> that policy would break with the golang policy (non packaged); so the source package name change is fine
[19:04] <bfiller> fginther: is jenkins messed up for mako tests? both these MR's failing these two: https://code.launchpad.net/~bfiller/camera-app/click-support/+merge/200889 and https://code.launchpad.net/~bfiller/gallery-app/click-support/+merge/201238
[19:07] <cjohnston> bfiller: the first one is probably due to the crashes
[19:07] <fginther> bfiller, both MPs have unity and app crashes
[19:11] <fginther> bfiller, there is open bug related to some crashes found earlier this week, it may be related: https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1262982
[19:12] <fginther> bfiller, I'll also run a test of trunk for both gallery-app and camera-app
[19:12] <bfiller> fginther: ok thanks
[19:15] <elopio> ci-help: I'm having problems using the on-screen keyboard on mako.
[19:15] <elopio> maybe one of you has clues or pointers about what happens
[19:15] <elopio> I'm getting this error: 'Unable to find maliit-server dbus object. Has it been started with introspection enabled?'
[19:17] <bfiller> elopio: is maliit-server process running?
[19:25] <cjohnston> elopio: looks like bfiller is trying to help, but that sounds like an issue for #ubuntu-touch
[19:26] <cjohnston> I'd also guess that you have a crash
[19:34] <elopio> bfiller: sorry, I got distracted in other channel.
[19:34] <elopio> I think maliit is running before I start the test.
[19:34] <elopio> afterwards it is not. I'll check for crashes.
[19:35] <bfiller> elopio: if you're trying to run OSK tests with autopilot it needs to be started in testability mode
[19:35] <bfiller> elopio: think you need to edit it's upstart conf file to add that, or first do stop maliit-server then maliit-server -testability
[19:38]  * elopio tries.
[19:46] <elopio> bfiller: maliit-server doesn't recognize the -testability arg.
[19:47] <bfiller> elopio: it spits out warnings but it does support it
[19:48] <bfiller> elopio: maybe it's --testability, I can't remember. ask veebers when he comes online
[19:49] <elopio> bfiller: I'm looking at this: https://bugs.launchpad.net/touch-preview-images/+bug/1201195
[19:49] <fginther> bfiller, camera-app and gallery-app both passed when built from trunk:  https://jenkins.qa.ubuntu.com/job/camera-app-ci/156/, https://jenkins.qa.ubuntu.com/job/gallery-app-ci/629/
[19:50] <elopio> from that, I get that it's -testability, and it should print something about testability driver loaded.
[19:50] <elopio> I can ask veebers on monday.
[20:22] <dobey> kenvandine: how much longer are you going to be around today?
[20:43] <kenvandine> dobey, until 5ish
[20:46] <dobey> kenvandine: can you do another daily ppa build of click stack? once it's built can we get the resulting ubuntu-purchase-service into ubuntu universe?
[20:47] <dobey> (was waiting for one more branch to merge, but it's merged now)
[20:47] <kenvandine> i'll kick off a build
[20:47] <kenvandine> dobey, add it to the landing asks for getting published
[20:48] <dobey> that spreadsheet thing still?
[20:48] <kenvandine> dobey, yup... that's the process
[20:49] <dobey> ok
[20:51] <dobey> i thought that was only after it had actually be uploaded to universe, for wholly new packages
[20:52] <kenvandine> we've still been tracking new stuff on there
[20:53] <dobey> ok
[20:53] <dobey> i'll ask for it to be added to the list of things to ask for ;)