[05:19] <Mirv> morning
[05:58] <anpok_> hi
[05:58] <anpok_> we finished testing silo-004 yesterday ..
[05:59] <anpok_> ping trainguards: there is one thing remaining
[05:59] <anpok_> we started with dual landing and switched to wily only landing becaue we have additional source packages..
[05:59] <anpok_> but the landing ppa for silo 004 still has the vivid+overlay packages in it..
[06:00] <anpok_> I hope this does not cause troubles..
[06:00] <anpok_> .. oh and additionally it is still marked as requres QA signoff - not sure if that is needed for a wily landing..
[06:09] <Mirv> anpok_: no it doesn't cause trouble, we can remove the packages not supposed to be there anymore
[06:09] <Mirv> anpok_: and eh, yes, it does not need QA signoff :)
[06:13] <Mirv> anpok_: do you want to make a copy of the vivid packages already built there, or are you ok reuploading/rebuilding them?
[06:21] <anpok_> hm yes .. what do I need to download?
[06:27] <anpok_> Mirv: I started a new row for syncing to vivid+overlay .. can we copy the additional source packages over to that silo then..
[06:27] <anpok_> all but glmark2.. we decided to bump glmark2 in overla
[06:28] <anpok_> so we would use the wily version there..
[06:31] <Mirv> anpok_: ok, just a moment
[06:34] <Mirv> anpok_: ok, all vivid packages from 004 except glmark2 copied to https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-053/+packages - does that look correct?
[06:36] <Mirv> anpok_: I will now remove the vivid packages from 004 and prepare it for the wily publishing
[06:37] <Mirv> anpok_: so I'm running WATCH_ONLY build of 004, don't worry
[06:38] <anpok_> ok
[06:39] <Mirv> anpok_: should I copy the 004's glmark2 wily to 053 for vivid?
[06:42] <anpok_> Mirv: yes
[06:42] <anpok_> the wily one yes
[06:44] <Mirv> anpok_: ok, glmark2 2014.03+git20150611.fa71af2d-0ubuntu2 building for vivid now in 053
[06:45] <Mirv> anpok_: regarding 004, all MP:s would need approval: https://ci-train.ubuntu.com/job/ubuntu-landing-004-2-publish/67/console
[06:45] <Mirv> if you've the permissions to top-approve them, just go through them and do it, but I can't do it
[06:52] <anpok_> Mirv: oh! not all of them .. I will trigger the necessary people
[06:53] <Mirv> anpok_: thanks!
[07:29] <mardy> cihelp, does anyone understand why this build is failing? https://ci-train.ubuntu.com/job/ubuntu-landing-052-1-build/3/console
[07:29] <mardy> looks like it cannot create the source tarball
[07:49] <Mirv> mardy: ping trainguards, not cihelp, if thre's a CI Train problem
[07:52] <Mirv> mardy: my guess would be that you need to add .bzr-builddeb directory to your (first ever) landing (or push such a thing directly to the trunk first)
[07:52] <Mirv> mardy: and the .bzr-builddeb/ would have default.conf like http://bazaar.launchpad.net/~system-settings-touch/ubuntu-system-settings/trunk/view/head:/.bzr-builddeb/default.conf
[07:52] <Mirv> mardy: then try the building again
[07:52] <mardy> Mirv: ah, I'll try that, thanks
[08:03] <sil2100> jibel, davmor2: do we know if there is anyone working on fixing the customization hooks?
[08:05] <jibel> ssweeny and cwayne were discussing a fix yesterday evening. I don't know what the conclusion has been
[08:05] <jibel> if an
[08:05] <jibel> y
[08:18] <sil2100> mzanetti: hey! Where is qml-module-qbluetooth built from?
[08:22] <davmor2> mzanetti: say outer space it will fry his head ;)
[08:23] <sil2100> ;)
[08:23] <sil2100> Today my head is frying anyway, I feel worse than yesterday
[08:25] <mzanetti> sil2100, you mean where to code for it is located?
[08:28] <sil2100> Yes, what source package it's coming from
[08:29] <mzanetti> outer space, yes
[08:29] <mzanetti> sil2100, http://code.qt.io/cgit/qt/qtconnectivity.git/
[08:29] <mzanetti> qtconnectivity5
[08:31] <mzanetti> it also contains QtNfc
[08:32] <mzanetti> not sure how far we are with the kernel enablement there
[08:38] <mardy> trainguards, can you help me solve this build issue? https://ci-train.ubuntu.com/job/ubuntu-landing-052-1-build/lastBuild/console
[08:39] <sil2100> mardy: looks like a geniune failure, looking at the build logs
[08:39] <sil2100> But it seems it  failed building for all arches
[08:39] <sil2100> I see a cmake error there
[08:40] <sil2100> mardy: are you using google mock in your project? Since it seems if you do, you're missing a dependency to google-mock
[08:41] <sil2100> mardy: and cmake is failing to find one of its directories, as it doesn't seem to be installed
[08:43] <mardy> sil2100: I think you are right, but I cannot understand how you got to this conclusion; I don't see anything about google mock in the logs
[08:43] <sil2100> mardy: https://launchpadlibrarian.net/211794576/buildlog_ubuntu-wily-i386.online-accounts-api_0.1%2B15.10.20150716-0ubuntu1_BUILDING.txt.gz <- here for instance
[08:44] <sil2100> mardy: the train only gives you links to build logs of the packages that failed building, so I browsed it through for errors
[08:44] <mardy> sil2100: oh, indeed; I guess I didn't explore the jenkins' interface well enough :-)
[08:44] <sil2100> And saw this:
[08:44] <sil2100> CMake Error at cmake/FindGMock.cmake:6 (add_subdirectory):
[08:44] <sil2100>   add_subdirectory given source "/usr/src/gmock" which is not an existing
[08:44] <sil2100>   directory.
[08:45] <sil2100> :)
[08:45] <mardy> sil2100: thanks a lot, I'll get it fixed
[08:45] <sil2100> Excellent, you're welcome
[09:25] <mzanetti> sil2100, hey, I'm about to train dednick to be a lander, can you grant him permission please
[09:28] <sil2100> mzanetti: sure, on it
[09:29] <sil2100> mzanetti: done
[09:29] <mzanetti> thanks :)
[10:11] <sil2100> ogra_: hey! Can I bother you with https://code.launchpad.net/~sil2100/ubuntu-seeds/ubuntu-touch.wily-qtbluetooth/+merge/264977 for a moment? Once this is approved I'll upload the vivid-packaged version to the overlay
[10:25] <alextu>  #launchpad
[10:57] <psivaa> Laney: I've commented on the wily lvm desktop bug, please take a look. I need to be afk for a bit now, and be happy to answer any questions whey i come back
[11:00] <Laney> psivaa-afk: I think it's likely to be cyphermox rather than me (trying hard not to own this bug), but can you point to where you can see the failure in the logs or give a link/instructions for how to run it outselves?
[11:00] <cyphermox> what's the bug no?
[11:01] <Laney> https://bugs.launchpad.net/ubuntu-test-cases/+bug/1474887
[11:02]  * Laney eyes cyphermox up suspiciously early
[11:02] <cyphermox> doubtful any preseed changes are going to fix a system that already boots
[11:03] <cyphermox> Laney: yeah, couldn't sleep any more... which is weird because I went to bed pretty late after a few hours ingressing
[11:07] <cyphermox> psivaa-afk: my guess is that the test itself is wrong for LVM. It looks for the very first line in the output of mount to start with /dev/mapper, which probably won't be the case
[11:07] <cyphermox> (because the first entry in mount is usually not the mountpoint for /)
[11:13]  * sil2100 off to lunch
[11:16] <cjwatson> FYI, all newly-created amd64/i386 LP builds will now be dispatched to scalingstack (lcy01-*/lgw01-*), even if they're in non-virtualised archives such as silos
[11:17] <cjwatson> Retries will still go to the bare-metal build farm for now, until we're confident enough in things to do the more invasive database surgery
[11:17] <cjwatson> (Retries of builds created prior to this change, that is)
[12:26] <Mirv> sil2100: hmm, I can't free a silo due to an error.. https://ci-train.ubuntu.com/job/ubuntu-landing-035-3-merge-clean/6/console
[12:26] <Mirv> sil2100: actually, it apparently got far enough in https://ci-train.ubuntu.com/job/ubuntu-landing-035-3-merge-clean/5/console already so that it disappeared now from dashboard, even though that too ended in an error
[12:26] <Mirv> weird
[12:27] <sil2100> Mirv: hm, this error usually means the silo was already freed
[12:27] <sil2100> Mirv: you sure it wasn't auto-merged or you didn't run the job twice?
[12:29] <Mirv> sil2100: no, as you can see there it removed packages first in that job nr 5
[12:30] <sil2100> Then maybe the silo was in overall in a busted state.
[12:32] <Mirv> sil2100: probably when the silo is never formally built (build job not run), that happens. I was only manually uploading packages for testing.
[12:34] <sil2100> Ah, no watch_only?
[12:35] <sil2100> ogra_, slangasek: could any of you review/approve this branch? https://code.launchpad.net/~sil2100/ubuntu-seeds/ubuntu-touch.wily-qtbluetooth/+merge/264977
[12:45] <Mirv> anpok_: just two empty commits non-approved anymore, I guess those don't need special permission to top-approve?
[12:46] <Mirv> trying.
[12:47] <Mirv> anpok_: now this is more problems for you though, there are new, non built commits in two of the branches so you need to investigate that: https://ci-train.ubuntu.com/job/ubuntu-landing-004-2-publish/68/console
[12:47] <kyrofa> trainguards: last I heard, I can't actually land anything in the archives via the spreadsheet replacement beta. Is that still the case?
[12:48] <sil2100> kyrofa: hey! Not sure if you can, I think it's still not possible currently, as I think those are using the staging PPAs
[12:48] <Mirv> anpok_: it seems those are only a changelog entry change and comment change by you, so you'll need to decide whether you want to rebuild the packages for those or not
[12:50] <kyrofa> sil2100, alright, thanks for the info! I wanted to make sure before I tried to get a new project silo'd
[12:53] <Mirv> sil2100: actually, I think we cannot even force publishing something if there's a branch that has a newer commit that what was built? ie rebuild needed always?
[12:54] <sil2100> Mirv: I think currently there's no way to force-publish it besides doing a copy-package
[12:54] <sil2100> You need to rebuild or revert the commits from the branch
[12:54] <sil2100> Revert and do a push --overwrite
[12:59] <kyrofa> trainguards: I'm preparing a new project to go through the CI train. Does the debian/changelog version need to be anything special for the train magic to happen?
[13:00] <sil2100> kyrofa: no, the train will try to be smart and change it to something following its format - be sure to just add a changelog entry that's UNRELEASED with the correct upstream version number
[13:00] <sil2100> So, for instance, something like 1.2.3-0ubuntu1 should just work
[13:01] <sil2100> The train should mangle it into something it understands during build
[13:04] <kyrofa> sil2100, alright, very good. Can you please point me to the spreadsheet?
[13:06] <sil2100> https://wiki.ubuntu.com/citrain
[13:06] <sil2100> (it's a redirect)
[13:06] <kyrofa> sil2100, perfect!
[13:08] <jdstrand> john-mcaleely: hey, is bug #1360403 for OTA-5? I saw in bug #1439101 you mentioned OTA-5 will fix a lot of things, but 1360403 actually makes mms work flawlessly for me (t-mobile).
[13:09] <jdstrand> john-mcaleely: I imagine it would fix things for others as well (obviously you would want to talk to abeato-- I'm just mentioning this as a user)
[13:09] <jdstrand> john-mcaleely: (this is already in silo 2 btw)
[13:10] <jdstrand> john-mcaleely: I should be more clear-- rc-proposed (ie all of OTA-5) *plus* silo 2 makes mms work great for me
[13:10] <davmor2> jdstrand: no then ota5 is done, ota 6 will have the fix
[13:11] <jdstrand> that is what I figured. that's too bad (not for me, I will just install silo 2 and be done with it)
[13:12] <davmor2> jdstrand: There are a bunch of underlying fixes that abeato and awe did for ota5 that I think make silo 002 work, but fixed issues with mms for many others.  So I think there will be a few more improvements along the way.
[13:12] <kyrofa> cihelp: Can you verify that autolanding has been disabled for unity-scope-snappy?
[13:13] <jdstrand> sure, I understand that (I've been following this very closely). just saying, ota-5 plus silo 2 is the first time mms has ever worked for me
[13:13] <fginther> kyrofa, yes, it's disabled now
[13:13] <ogra_> pfft ... MMS ... send a postcard ... thats cheaper
[13:14] <jdstrand> and I thought it worth mentioning that it is as close as it is, especially since ota-5 is delayed. it isn't my call, just providing info
[13:14] <kyrofa> fginther, so if I approve MPs nothing will happen without the CI train, correct?
[13:14] <jdstrand> ogra_: heh
[13:14] <ogra_> sil2100, sorry, currently wrangling with a snappy prob ... i'll get to your MP later
[13:14] <abeato> jdstrand, which is your operator?
[13:14] <jdstrand> tmobile
[13:14] <fginther> kyrofa, yes, approved MPs will be ignored by the ci s-jenkins now
[13:15] <ogra_> jdstrand, no joking ... MMS in europe is like 1.20€
[13:15] <kyrofa> fginther, awesome, thank you!
[13:15] <abeato> jdstrand, ok t-mobile us wait for ota-6
[13:15] <fginther> kyrofa, you're welcome
[13:16] <john-mcaleely> jdstrand, sadly, I understand it missed the ota-5 cut
[13:16] <john-mcaleely> so will land in ota-6
[13:16] <davmor2> ogra_: yeah but after the greek affair that's what 3 cents ;)
[13:16] <seb128> ogra_, non-sense, in France most subscriptions include them for free
[13:16] <seb128> like for 5€/month you can get 2 hours call and unlimited sms/mms
[13:16] <jdstrand> hey, like I said. not my call-- I'm extremely pleased to install silo 2 on my device
[13:17] <jdstrand> just thought I'd pass along the info
[13:17] <davmor2> seb128: no pay as you go in the uk include them, I think they are in contract sims though
[13:17] <abeato> jdstrand, note however that many fixes for mms already landed, there was just a small thing needed for t-mobile us, but I think most of the other operators should work now
[13:17] <davmor2> seb128: roughly 60p in the uk up to £1
[13:17] <seb128> davmor2, yeah, most people in france has sim contracts, not pay as you go
[13:17] <seb128> have*
[13:18] <abeato> jdstrand, for instance Free in france
[13:18] <ogra_> seb128, pfft, france ... communists !
[13:18] <ogra_> :D
[13:18] <seb128> :-)
[13:18] <john-mcaleely> they're not in my UK contract
[13:18] <john-mcaleely> which makes testing tedious
[13:19] <ogra_> yeah, same here
[13:19] <davmor2> john-mcaleely: no expensive not tedious ;)
[13:19] <ogra_> i got free SMS
[13:19] <ogra_> but MMS cost a fortune
[13:19] <john-mcaleely> tedious to read the bill :-)
[13:19] <abeato> fortunately in my case the price dropped from 1 eur + VAT to 0.5 a couple of months ago
[13:19] <john-mcaleely> abeato, I guess you're a bulk user :-)
[13:20] <abeato> but anyway I had to spend like 30/40 eur in MMS last month, john-mcaleely knows that :D
[13:20] <john-mcaleely> indeed
[13:20] <abeato> john-mcaleely, probably the only MMS bulk user in Spain these days :)
[13:20] <john-mcaleely> ha
[13:23] <davmor2> abeato: Europe
[13:23] <abeato> davmor2, maybe EMEA ;)
[13:24] <davmor2> abeato: infact, the world bar the USA
[13:24] <abeato> lol
[13:59] <rvr> jdstrand: ping
[14:18] <jdstrand> rvr: hey
[14:18] <rvr> jdstrand: Hi, I'm testing silo 11 and I found some issues with apparmor
[14:18] <rvr> jdstrand: http://paste.ubuntu.com/11887897/
[14:19] <rvr> jdstrand: The popup is stuck loading the login page
[14:19] <rvr> jdstrand: During installation, I downgraded to apparmor-easyprof-ubuntu 1.3.12, the version in the silo PPA.
[14:20] <rvr> The one in the overlay PPA is 1.3.13
[14:21] <jdstrand> rvr: let me circle back to you. got pulled into a meeting right after I said 'hey'
[14:22] <tsdgeos> coolio
[14:22]  * tsdgeos tries
[14:30] <rvr> awe_: ping
[14:32] <awe_> rvr, pong
[14:32] <rvr> awe_: How to test silo 6?
[14:35] <awe_> rvr, I would run your standard network test cases;  if you want to test the specific changes for the APN editor, then you have a choice of either doing so manually using ofono scripts, or using the corresponding system-settings silo for the apn editor
[14:35] <awe_> but you'd need to check with jgdx as to it's current status
[14:36] <awe_> rvr, I think you testing should be primarily focused on ensuring there are no regression
[14:36] <awe_> s
[14:36] <rvr> awe_: Ok
[14:49] <kyrofa> fginther, while autolanding is disabled for unity-scope-snappy, is it still running tests etc. for MPs?
[15:07] <anpok_> Mirv: I rebuilt (004) .. I just realized that the vivid mir package in the former dual landing silo was outdated.. can you copy the wily ubuntu-system-compositor and mir package instead
[15:14] <kyrofa> cihelp: while autolanding is disabled for unity-scope-snappy, is it still running tests etc. for MPs?
[15:14] <josepht> kyrofa: yes, it should be.
[15:17] <kyrofa> josepht, hmm, alright, maybe I'm just being paranoid. It's been over an hour is all
[15:18] <josepht> kyrofa: I'll take a look in a few minutes. Do you have a link to the MP handy?
[15:18] <kyrofa> josepht: https://code.launchpad.net/~kyrofa/unity-scope-snappy/improve_debs/+merge/264640
[15:19] <kyrofa> josepht, I appreciate your eyes :)
[15:22] <jdstrand> rvr: ok, back
[15:22] <jdstrand> rvr: so, 1.3.12 and 1.3.13 are equivalent for what you are testing
[15:22] <rvr> jdstrand: Ok
[15:23] <rvr> jdstrand: So, do you think those denials are harmless?
[15:23] <jdstrand> I do, based on a conversation with mardy before
[15:23] <jdstrand> let me find the bug
[15:25] <jdstrand> rvr: this is https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1468792
[15:25] <jdstrand> let me check something
[15:26] <jdstrand> ah right
[15:26] <jdstrand> rvr: so, what is happening is that we allow this: owner @{HOME}/.cache/online-accounts-ui/id-*-@{APP_PKGNAME}_@{APP_APPNAME}/
[15:27] <jdstrand> rvr: but we intentionally don't allow this: @{HOME}/.cache/online-accounts-ui/
[15:27] <jdstrand> rvr: something needs to create @{HOME}/.cache/online-accounts-ui/ on the apps behalf.
[15:27] <jdstrand> rvr: it is believed that this is another bug:
[15:28] <jdstrand> actually, no
[15:28] <jdstrand> I thought it was related to another one, but I was wrong
[15:29] <jdstrand> rvr: last I heard, with apparmor-easyprof-ubuntu 1.3.12 and higher, all relevant denials are fix and that if there is a problem it is somewhere else
[15:29] <jdstrand> rvr: I'm going to comment in the bug regarding @{HOME}/.cache/online-accounts-ui/
[15:29] <rvr> jdstrand: It is point 1 of that bug
[15:30] <rvr> jdstrand: "1. There is a denial to create this directory if it does not exist already" /home/phablet/.cache/QML/Apps/online-accounts-ui
[15:30] <rvr> Hmm
[15:31] <rvr> name="/home/phablet/.cache/QML/Apps/online-accounts-ui/"
[15:31] <rvr> Yup
[15:32] <kyrofa> josepht, that MP ran! Did you poke it, or did it just take time?
[15:32] <josepht> kyrofa: I poked it
[15:32] <kyrofa> josepht, heh, thanks :)
[15:33] <slangasek> sil2100: qml-module-qtbluetooth, you've analyzed the impact on the size of the phone image and everyone's happy with the result?
[15:33] <josepht> kyrofa: np, it thought it had already looked at rev 32 so it didn't try to run again.
[15:34] <jdstrand> rvr: I'm quite confident the  /home/phablet/.local/share/applications/ is harmless. I'm less so about /home/phablet/.cache/QML/Apps/online-accounts-ui/
[15:35] <jdstrand> rvr: can you do: 'mkdir -p /home/phablet/.cache/QML/Apps/online-accounts-ui/' then ttry again?
[15:35] <rvr> jdstrand: Sure
[15:37] <sil2100> slangasek: I checked that and was fine, but I didn't consult with anyone ;)
[15:38] <rvr> jdstrand: Jul 16 15:37:30 ubuntu-phablet kernel: [   52.552819]type=1400 audit(1437061050.590:131): apparmor="DENIED" operation="mknod" profile="com.ubuntu.developer.rmescandon.asana_account-plugin_1.0.0" name="/home/phablet/.cache/QML/Apps/online-accounts-ui/ef91bab385a7f63fa8bbf22bbf9d1bdf" pid=3546 comm="QQmlThread" requested_mask="c" denied_mask="c" fsuid=32011 ouid=32011
[15:38] <sil2100> I think it was around ~260KB of additional space required
[15:38] <AlbertA> fginther: is it possible to enable listing the mir-clang-ts-wily-amd64-build jobs through a public URL (similar to:  https://jenkins.qa.ubuntu.com/job/mir-clang-wily-amd64-build/)?
[15:40] <jdstrand> rvr: ok-- that indicates two things-- one, the denial is not harmless and two, there is a bug in the silo because /home/phablet/.cache/QML/Apps/online-accounts-ui/ef91bab385a7f63fa8bbf22bbf9d1bdf is not app-specific, and it should be
[15:40] <rvr> jdstrand: Ack
[15:40] <rvr> mardy: ^
[15:42] <rvr> dbarth: ^
[15:42] <dbarth> reading
[15:44] <dbarth> ah, so not harmless after all :/
[15:44] <jdstrand> dbarth: you might see comments 12 and 13 from bug 1468792
[15:45] <slangasek> sil2100: ok.  I'm not sure what the policy should be on adding new interfaces to the phone, this seems like something that should be checked with product management or so?
[15:46] <dbarth> hmm, yet i was able to create the account, whereas rvr could not in his testing
[15:46] <dbarth> rvr: could you double check the package versions that effectively got installed on your test phone?
[15:47] <rvr> dbarth: Hmm
[15:49] <rvr> dbarth: Grrrr... citrain tool didn't install the packages
[15:49] <rvr> dbarth: Rechecking
[15:49] <sil2100> slangasek: I think this was a request from management as well as it's a feature request from higher-up, but I don't know, I'm managing seeds since recently
[15:49] <dbarth> rvr: ah!
[15:49] <rvr> because of the downgrade problem
[15:49] <sil2100> slangasek: I could check with pmcgowan now
[15:50] <sil2100> pmcgowan: hey! mzanetti requested adding qml-module-qtbluetooth to the seeds for bluetooth file transfer support
[15:50] <sil2100> pmcgowan: just want to confirm it's approved by product management
[15:51] <mzanetti> right. I didn't talk to anyone...
[15:51] <mzanetti> I just installed it to my phone, had a little play, it seemed working and so I thought I'd start the discussion
[15:51] <sil2100> Oh, so I misunderstood
[15:51] <mzanetti> but yeah... I still think we should have it
[15:52] <sil2100> Well, still new to this process, in the past I was only getting requests from management
[15:52] <sil2100> pmcgowan: you think this will be fine? It's an additional ~260KB of space (with new dependencies)
[15:52] <pmcgowan> sil2100, is that a standard Qt 5 module
[15:52] <pmcgowan> that seems fine
[15:52] <sil2100> pmcgowan: yes, it's from Qt5
[15:52] <mzanetti> it has been released upstream by now, yes
[15:53] <pmcgowan> ok
[15:53] <mzanetti> when we first put together the seed it was still marked "experimental"
[15:53] <sil2100> slangasek: ^ we have approval, sorry for that, will make sure to confirm every change with the PT
[15:54] <slangasek> sil2100: ok, merged
[15:54] <ogra_> was that the seed change ?
[15:54] <slangasek> sil2100: I guess this needs an ubuntu-touch-meta upload?
[15:54] <slangasek> ogra_: yes
[15:54] <ogra_> ah, thanks
[15:54] <sil2100> slangasek: I have the vivid-overlay version prepared
[15:54]  * ogra_ would have had time now :)
[15:55] <sil2100> slangasek: I can prepare a wily version too, but I never remember if I should prepare it by hand or is there some magic way to build it out of the branch
[15:55] <slangasek> sil2100: ah, this is being changed for vivid too? hmm I'm not sure how that will work
[15:55]  * sil2100 uploads the overlay version in teh meantime
[15:56] <sil2100> slangasek: we always prepare a separate version of the ubuntu-touch-meta and upload
[15:56] <ogra_> slangasek, sil2100, err, wait
[15:56] <slangasek> sil2100: er, you're talking about a vivid-overlay /package/, not a merge?
[15:56] <sil2100> slangasek: yes, package
[15:56] <ogra_> slangasek, sil2100, qml modules need to go into the sdk-libs
[15:56] <ogra_> (and slangasek is right, that would need a framework bump i guess)
[15:56] <slangasek> sil2100: the metapackages are supposed to be autogenerated from the seeds using the ./update command
[15:57] <sil2100> ogra_: oh?
[15:57] <ogra_> slangasek, not for releases releases :)
[15:57] <ogra_> slangasek, there we always need to hack the meta directly
[15:57] <ogra_> because the seeds get locked on release day
[15:57] <slangasek> hmm
[15:57] <ogra_> *released releases
[15:58] <sil2100> If the place for it is in sdk-libs then indeed it's not so easy
[15:58] <ogra_> well, all qml modules live there
[15:58] <rvr> dbarth: Doesn't load either
[15:59] <ogra_> and essentially make up our framework
[15:59] <ogra_> not sure what our policy for vivid is here
[15:59] <ogra_> as an architect :)
[15:59] <dbarth> rvr: ?!
[15:59] <dbarth> rvr: with the same error messages?
[16:00] <ogra_> but i imagine we cant just enhance the framework without any version bumps
[16:00] <sil2100> Ok then, let's hold off getting this change merged/approved
[16:00] <sil2100> It's not critical enough and we need to put a bit more thought into it
[16:00] <ogra_> sil2100, i guess you want tvoss inpout for that one first
[16:00] <ogra_> bumping in wily shouldnt be a prob though
[16:01] <sil2100> Right
[16:02] <davmor2> sil2100: meeting
[16:02] <slangasek> sil2100, ogra_: the merge was committed to the seed branch, but I'll hold off on uploading anything until we have a final decision
[16:03] <pmcgowan> sil2100, ogra_ is right, that becomes part of the sdk
[16:03] <rvr> dbarth: jdstrand: Jul 16 15:51:19 ubuntu-phablet kernel: [   74.711347]type=1400 audit(1437061879.696:123): apparmor="DENIED" operation="exec" profile="com.ubuntu.developer.rmescandon.asana_account-plugin_1.0.0" name="/usr/lib/arm-linux-gnueabihf/oxide-qt/chrome-sandbox" pid=3750 comm="online-accounts" requested_mask="x" denied_mask="x" fsuid=32011 ouid=0
[16:03] <rvr>  
[16:04] <ogra_> slangasek, well, wily is -dev anyway, any chanes there should be ok ... this is just about vivid ... where seeds arent used anyway
[16:04] <pmcgowan> sil2100, ogra_ we did just add a 15.10-dev framework a bit belatedly
[16:04] <pmcgowan> the fw definition is a bit unwieldy
[16:06] <slangasek> ogra_: if it's supposed to go in sdk-libs, that affects the seed for wily also.
[16:06] <jdstrand> rvr: you need the webview policy group
[16:07] <ogra_> slangasek, yes, i'm only talking about wily :)
[16:07] <dbarth> rvr: oh, did you apply comment #3 from the bug report ? that's the key
[16:08] <ogra_> slangasek, vivid doesnt have seeds anymore
[16:08] <dbarth> ie, the package doesn't have the right policy embedded, and it needs an upgrade via:
[16:08] <ogra_> (not functional seeds at least)
[16:08] <dbarth>   cd /var/lib/apparmor/profiles
[16:08] <dbarth>     sudo apparmor_parser -r click_com.ubuntu.developer.rmescandon.asana_account-plugin_1.0.0
[16:09] <rvr> dbarth: Ah
[16:09] <dbarth> rvr: sorry, that was not totally obvious from the spreadsheet comment
[16:11] <jdstrand> dbarth, rvr: comment #3's point '1' is already resolved in apparmor-easyprof-ubuntu 1.3.12 and higher
[16:14] <rvr> dbarth: jdstrand: I executed that, and the popup is still stuck loading the login page
[16:14] <jdstrand> rvr: what dbarth said isn't quite enough
[16:15] <jdstrand> rvr: you need to look at /var/lib/apparmor/clicks/*asana*, then add 'networking' and 'webview' to the policy_groups
[16:15] <jdstrand> rvr: then you need to: sudo rm -f /var/lib/apparmor/profiles/click_*asana* ; sudo aa-clickhook
[16:15] <dbarth> rvr: well, that's the whole of comment #3, ie download the improved profile from mardy, which should go into the next version of the package
[16:16] <jdstrand> dbarth: no
[16:16] <jdstrand> dbarth: stable-phone-overlay has all the fixes that can be applied
[16:16] <jdstrand> dbarth: to apparmor-easyprof-ubuntu
[16:16] <rvr> jdstrand: dbarth: Is the click package wrong?
[16:17] <jdstrand> rvr: if it doesn't contain 'webview', then yes, it is wrong
[16:18] <jdstrand> dbarth: ie, I incorporated mardy's fixes
[16:19] <jdstrand> dbarth: but the silo is not operating correctly in the manner I described in comments #12 and #13
[16:24] <dbarth> jdstrand: which click package version should we use? i refer to the one received by email, not the store upload which is unaccessible for us
[16:25] <rvr> jdstrand: dbarth: Now it loads
[16:25] <dbarth> rvr: what changed?
[16:26] <rvr> dbarth: I added the profile changes that jdstrand described
[16:27] <jdstrand> well, hold on-- you had to do the mkdir still, right?
[16:27] <dbarth> ok
[16:28] <rvr> jdstrand: Yes, let me remove it
[16:30] <jdstrand> dbarth: the asane attached to my email with 'Subject: Re: account-plugins apparmor confinement' on 2015/06/26 has the corrected policy groups
[16:30] <jdstrand> asana*
[16:32] <rvr> jdstrand: It loads, even after removing the directory :-/
[16:33] <jdstrand> :\
[16:33] <jdstrand> rvr: sending you the updated click
[16:34] <rvr> jdstrand: Ack
[16:34] <jdstrand> rvr: I think the test environment is compromised. I advise restarting the tests with the click I provided
[16:34] <rvr> Reflashing
[16:35] <jdstrand> I don't really know what online accounts is doing behind the scenes
[16:35] <dbarth> yup, agreed
[16:35] <dbarth> i can do the same here
[16:35] <jdstrand> I suspect that parts of it completed despite the failure
[16:35] <dbarth> rvr: you on wily, right?
[16:35] <jdstrand> and therefire simply removing the dir didn't reset it
[16:36] <rvr> dbarth: Nope, overlay PPA
[16:36] <rvr> dbarth: ubuntu-touch/rc-proposed/bq-aquaris.en
[16:36] <dbarth> ah ok, switching there then
[17:09] <rvr> jdstrand: dbarth: It loads
[17:09] <rvr> After reinstalling everything
[17:09] <rvr> And using jdstrand's click package
[17:19] <dbarth> rvr: right, i have the same here; worked like a charm (again ;) using my corporate google account to login even
[17:20] <dbarth> though i do get a few denials due to the webview wanting to go over the board, but that's cosmetic, and can be managed in a separate bug
[17:20] <rvr> dbarth: I can also create another account in Ubuntu
[17:20] <rvr> One
[17:27] <rvr> dbarth: jdstrand: Approving the silo
[17:29] <dbarth> rvr: thank you
[17:33] <cwayne> trainguards: hiya, can i get a silo for line 72? it's part of the dconf custom fix
[17:33] <cwayne> sil2100: ^
[17:33] <robru> cwayne: on it
[17:34] <cwayne> robru: <3
[17:34] <robru> cwayne: you didn't specify what series to release to
[17:35] <sil2100> o/
[17:35] <robru> sil2100: goodnight
[17:35] <sil2100> Not yet! Just waving hands to cwayne o/
[17:35] <robru> heh
[17:35] <sil2100> robru, cwayne: can that be dual landed?
[17:36] <cwayne> don't see any reason why not
[17:36] <sil2100> Ok, if that's an MR then it makes sense
[17:36] <cwayne> sil2100: so funny story, seems we had a fix for this in place over a year ago (we didn't realize there was a bug to fix, we were just going to move to a precompiled db)
[17:37] <robru> cwayne: ok silo 35
[17:37] <cwayne> this'll require some fixes to the custom build scripts as well, so we'd need to coordinate its landing sil2100
[17:37] <cwayne> robru: thanks
[17:37] <robru> cwayne: you're welcome
[17:38] <sil2100> cwayne: hm, is this well tested?
[17:38] <sil2100> cwayne: ok, so we'll need a coordinated custom release, right? For OTA-5 we'll only release this fix for arale
[17:38] <cwayne> sil2100: ssweeny just tested it, yeah
[17:39] <sil2100> For vegetahd and krillin we won't do an OTA-5 respin
[17:39] <cwayne> sil2100: ack, ill work on getting a custom tar ready so we can test both together
[17:39] <sil2100> cwayne: excellent, thanks :)
[17:39] <sil2100> davmor2, jibel: ^
[17:39] <robru> kgunn: nah you gotta wait until u-s-s-o-a finishes migrating before rebuilding
[17:40] <kgunn> robru: ah...was just reacting to dashboard
[17:40] <robru> kgunn: yeah it's kind of a race condition, dashboard is set as dirty when the other silo publishes, but rebuilding doesn't work until the other silo merges
[17:41] <robru> kgunn: no, it's exactly a race condition, no kind of about it ;-)
[17:41] <robru> kgunn: fortunately it'll get marked dirty again when the merge happens
[17:41] <kgunn> sure
[17:41] <kgunn> np
[17:46] <psivaa> cyphermox: i've commented on your MP for lvm test fix
[17:46] <cyphermox> ok
[18:16] <jordan> trainguards, line 73 is ready for a silo
[18:16] <dobey> trainguards: if a landing is for vivid without the overlay ppa specified, it will get pushed out to vivid-updates as an SRU, right?
[18:18] <fginther> renatu, The buteo jobs have been running for about a day now, can you confirm they are setup correctly? https://jenkins.qa.ubuntu.com/job/buteo-syncfw-qml-ci/ and https://jenkins.qa.ubuntu.com/job/buteo-sync-plugins-contacts-ci/
[18:21] <renatu> fginther, thanks. Everything looks ok. The "/buteo-sync-plugins-contacts-ci" will fail because some missing deps.
[18:25] <robru> dobey: yep, but it's up to you to make sure you get all the SRU paperwork filed and ping sru people to prod it along, otherwise it just sits in UNAPPROVED for *literally months*
[18:25] <robru> dobey: average lead time on a train SRU is typically 2 months
[18:26] <dobey> robru: ok. i was just making sure that the train handled that sort of thing already. not that i need to do it right now :)
[18:26] <robru> dobey: yep that's been supported since the beginning.
[18:27] <dobey> ok. i'm going to move a couple more projects over to CI train, so just clarifying before i do all the work ;)
[18:28] <robru> jordan: silo 55, note conflicts in silos 3, 4, and 46
[18:29] <kyrofa> trainguards: I don't seem to have permission to modify the CI train spreadsheet. How do I get that?
[18:29] <robru> kyrofa: one sec
[18:30]  * alecu vouches for kyrofa
[18:30] <kyrofa> Got it robru, thank you!
[18:30] <robru> kyrofa: you're welcome
[18:31] <robru> kyrofa: let me know if you have any questions about the spreadsheet. also, don't spend too much time learning about it because it's all changing next week
[18:31] <jordan> robru, ack. These are little four-liner patches in each repo, but I'll confirm that there's not overlap with 3, 4, and 46
[18:31] <robru> jordan: it's more like, after you release this silo, make sure the owners of 3, 4, and 46 know they need to rebuild ;-)
[18:32] <jordan> robru, ack
[18:32] <robru> jordan: or the other way around depending on who publishes first. communication is key
[18:32] <robru> kgunn: safe to rebuild now ^
[18:33] <kgunn> thanks!
[19:39] <robru> kyrofa: ok, silo 11
[19:40] <kyrofa> Thanks robru!
[19:40] <robru> kyrofa: you're welcome
[19:40] <robru> kgunn: do you have a core dev lined up for silo 4? I see Laney is responsible for gtk there but not sure about the rest
[19:41] <kgunn> robru: uh.... :P
[19:41] <kgunn> robru: we have RAOF on our team who is one
[19:41] <robru> kgunn: lots of packaging changes! can you get him to review? https://ci-train.ubuntu.com/job/ubuntu-landing-004-2-publish/69/artifact/
[19:41] <kgunn> he'll be on in about an hour or so
[19:42] <kgunn> robru: ok, after that, is he good to own all the action...or does he need to ping back here ?
[19:42] <robru> kgunn: he can ping me and I can publish the silo.
[19:42] <kgunn> ok..
[19:42] <kgunn> ah crap.... i think he might still be on vacation
[19:50] <kgunn> mterry much thanks!
[19:51] <kgunn> robru: mterry taking a look...
[19:51] <robru> kgunn: mterry great
[19:51]  * mterry waves at robru
[19:51] <robru> mterry: hey buddy, long time
[19:51] <mterry> :)
[19:56] <mterry> Laney, I'm looking at https://ci-train.ubuntu.com/job/ubuntu-landing-004-2-publish/69/artifact/gtk+3.0_packaging_changes.diff and I see that gtk+3.0's debian/control.in didn't get entirely updated -- looks like it got updated in one place, but debian/control got updated in two places.  Right?
[19:57] <mterry> I don't think it's a critical omission
[19:57] <mterry> Laney, but maybe fix it in bzr
[20:01] <mterry> robru, an empty changelog is no good right?  https://ci-train.ubuntu.com/job/ubuntu-landing-004-2-publish/69/artifact/unity-system-compositor_packaging_changes.diff
[20:01] <cyphermox> psivaa: so, should I file a new merge against the other branch or are you including the changes in your branch?
[20:02] <robru> mterry: bah
[20:02] <psivaa> cyphermox: i'd ask you to do an MP against the other branch please
[20:03] <psivaa> cyphermox: that MP has to be approved and merged by ubuntu-server-developers anyway
[20:04] <robru> kgunn: https://ci-train.ubuntu.com/job/ubuntu-landing-004-2-publish/69/artifact/unity-system-compositor_packaging_changes.diff do you have any idea what's going on here? aside from the empty bullet point there's a giant chunk of seemingly duplicated changelog, I have no idea why.
[20:04] <cyphermox> psivaa: https://code.launchpad.net/~mathieu-tl/ubuntu-test-cases/fix_lvm/+merge/265039
[20:04] <cyphermox> I can do the merge myself..
[20:05] <kgunn> robru: no idea
[20:05]  * kgunn looks at mps
[20:05] <robru> kgunn: yeah I guess the MP is busted.
[20:06] <robru> kgunn: I don't know who's idea it was to copy & paste 0.0.5+15.10.20150506.1-0ubuntu1 into a new entry for wily, don't do that
[20:06] <kgunn> robru: i know who the culprits most likely are....will relay the message
[20:06] <psivaa> cyphermox: I have approved it
[20:07] <robru> kgunn: please make the changelog entry like this: http://paste.ubuntu.com/11889568/ then rebuild
[20:08] <kgunn> ack
[20:08] <robru> kgunn: thanks
[20:09] <robru> kgunn: oh and just rebuild that one, not the whole silo ;-)
[20:09] <kgunn> robru: yes of course
[20:09] <robru> great
[20:09] <kgunn> robru: am i that dumb of a manager ? :-P
[20:09] <kgunn> don't answer that
[20:10] <robru> kgunn: I can't remember who but I've seen it happen, just making sure ;-)
[20:10] <kgunn> robru: totally possible with me...thanks for the reminder :)
[20:10] <robru> kgunn: you're welcome!
[20:11] <robru> kyrofa: please have a skim over our packaging guidelines for the train, it may help resolve the build failure you're seeing: https://wiki.ubuntu.com/DailyRelease/InlinePackaging
[20:13] <cwayne> fginther: hi, I can apt-get install stuff in my jenkins job if i need it right?
[20:14] <cwayne> like it's all run in a chroot or something so i wouldn't be polluting anything i mean
[20:14] <robru> kyrofa: particularly the part about split building
[20:15] <kyrofa> robru, oh, is that what it's whining about?
[20:15] <kyrofa> robru, what about the package version?
[20:16] <robru> kyrofa: yeah there's a few packaging niggles I noticed in your branch. split building is a big one, also add '-0ubuntu1' to your changelog version and it should be able to figure the rest out from there.
[20:16] <kyrofa> That's what I had initially and it gave me the native/non-native complaint, so I removed the "-0ubuntu1" to see if that fixed things. It didn't :P
[20:16] <kyrofa> robru, ^^
[20:17] <robru> kyrofa: you should definitely be using -0ubuntu1 in the train.
[20:17] <kyrofa> robru, okay, will do. And a native format?
[20:17] <robru> kyrofa: if you mean dropping quilt, yes.
[20:18] <kyrofa> robru, yeah, 3.0 (native)
[20:19] <robru> kyrofa: yeah read the page, you should drop debian/source entirely
[20:19] <kyrofa> robru, ah yes, right at the top :)
[20:28] <kgunn> robru: just makin' sure i got this right...i added the unrelease entry
[20:28] <kgunn> http://bazaar.launchpad.net/~unity-system-compositor-team/unity-system-compositor/trunk/revision/227
[20:28] <kgunn> but i did not delete
[20:28] <kgunn> http://bazaar.launchpad.net/~unity-system-compositor-team/unity-system-compositor/trunk/revision/222
[20:28] <kgunn> correct ?
[20:28] <kgunn> or should i have deleted that one
[20:28] <robru> kgunn: nope, need you to delete what was added in 222, it's totally redundant and wrong
[20:29] <kgunn> right
[20:29] <kgunn> i get it now
[20:29] <robru> kgunn: if you look a bit further down there's an identical stanza with identical version number.
[20:29] <kgunn> right
[20:29] <kgunn> redundant i see
[20:29] <robru> kgunn: thanks for taking care of that ;-)
[20:30] <kgunn> robru: oh...meant to say, i didn't delete, cause it said entry was from ci train  bot
[20:30] <kgunn> robru: oh...i see what happened
[20:30] <kgunn> anpok did that...but just cnp'd it
[20:30] <robru> kgunn: the original one was from the train bot, but somebody got copy&paste happy there ;-)
[20:30] <kgunn> ah ha
[20:30] <kgunn> yeah
[20:30] <kyrofa> robru, seems to be working now, thank you for the link :)
[20:30] <kgunn> threw me for a minute...but i see the commit on lp
[20:31] <robru> kyrofa: you're welcome!
[20:32] <anpok_> hm?
[20:33] <anpok_> I had issues with building u-s-c jenkinks complained about missing change log entries..
[20:33] <anpok_> and I remeber merging stuff
[20:33] <robru> anpok_: yeah you did it wrong :-P
[20:35] <robru> kgunn: ok that's weird. try making the most recent entry 0.0.5+15.10.20150506.2-0ubuntu1 or something higher. it doesn't scan the full changelog it just does a lexical comparison of the most recent changelog entry with the most recent distro version when it complains there
[21:32] <fginther> cwayne, it depends on exactly how the job is setup. Most use chroots, but there may be a couple that operate outside of that environment. Can you PM me the job(s) in question?
[21:36] <kgunn> robru: ok, tried a couple of times...it's still upset at the changelog...not really sure what's happening here
[21:37] <kgunn> wondering if this is why anpok copied it that wily release in there?
[21:38] <robru> kgunn: I guess so.
[21:39] <robru> kgunn: did you try my suggestion?
[21:39] <robru>  <robru> kgunn: ok that's weird. try making the most recent entry 0.0.5+15.10.20150506.2-0ubuntu1 or something higher. it doesn't scan the full changelog it just does a lexical comparison of the most recent changelog entry with the most recent distro version when it complains there
[21:39] <kgunn> robru: yes
[21:40] <robru> kgunn: then why does the changelog still say '0.0.5-0ubuntu1' when I look at the merge? :-P
[21:40] <kgunn> robru: ohhhh, i thot you meant the one under the unreleased...my bad
[21:40]  * kgunn goes to clean mess
[21:42] <robru> kgunn: yeah, no, when the train says "is missing from the changelog, which has up to" that means that it's compared the most recent changelog entry against the most recent distro version and doesn't like what it saw. changing anything other than the most recent version number in the changelog won't make a difference.
[21:42] <robru> kgunn: sorry that wasn't clear
[21:50] <robru> boiko:  https://ci-train.ubuntu.com/job/ubuntu-landing-008-2-publish/lastSuccessfulBuild/artifact/telepathy-qt5_packaging_changes.diff/*view*/ is this for real? that's a lot of patches you're dropping.
[21:51] <boiko> robru: yep, we upstreamed almost everything
[21:51] <robru> boiko: wow congrats
[21:51] <boiko> :D
[21:51] <boiko> robru: thanks, we actually upstreamed them awhile ago, but we were waiting for an upstream release for quite some time
[21:51] <robru> boiko: ah ok
[21:52] <boiko> robru: in the end both me and salem_ got write access to telepathy-qt and in theory we can do releases now too
[21:52] <robru> boiko: nice!
[22:10] <robru> kgunn: great looks good
[22:11] <kgunn> robru: yep, altho mterry gone for day i think
[22:11] <robru> kgunn: fine by me, we fixed the issue he raised ;-)
[22:12] <kgunn> robru: alright! sounds good...people starting to nag :)
[22:12] <kgunn> heading to the house....bbiab