[02:12] <bzoltan> robru: do you know any core dev who I can ask to retry these flaky tests? https://requests.ci-train.ubuntu.com/static/britney/ticket-1539/landing-008-yakkety/excuses.html
[02:15] <robru> bzoltan: I dunno who's around at this time, sorry
[02:17] <robru> bzoltan: https://launchpad.net/~ubuntu-core-dev/+members#active
[02:24] <bzoltan> robru: I have no idea either :( we are kind of in the dead timezone until UK wakes up and that is still far away. Somebody from the west coast might be still active..
[02:38] <robru> bzoltan: sil is sleeping a few feet from me and should be functional in about 3 hours
[02:38] <bzoltan> robru: sounds promising :)
[02:41] <robru> lpotter_: your changelog is busted
[02:42] <lpotter_> ffs
[04:18] <lpotter__> do I have to manually do anything for 'dependency wait'?
[04:59] <lpotter__> \0/
[06:02] <sil2100> tvoss_: hey! https://requests.ci-train.ubuntu.com/#/ticket/1534 needs a rebuild
[06:02] <tvoss_> sil2100, thx, kicked
[06:09] <tvoss_> sil2100, not sure what happened here: https://requests.ci-train.ubuntu.com/#/ticket/1534
[06:09] <bzoltan> sil2100: good morning ... I would like to ask you for clicking three recycle icon here -> https://requests.ci-train.ubuntu.com/static/britney/ticket-1539/landing-008-yakkety/excuses.html I am really sorry to bug you with this crap :(  It is shame that we need a core-dev to retry a flaky test...
[06:10] <sil2100> tvoss_: hm, let's give it a moment of time
[06:10] <sil2100> tvoss_: I see stuff is building in the PPA for now
[06:10] <sil2100> bzoltan: on it!
[06:11] <sil2100> bzoltan: no worries, our connection is better so recycling is less painful ;)
[06:11] <bzoltan> sil2100: thank you
[06:11] <sil2100> All pressed
[06:16] <bzoltan> sil2100: do  you mean :) all three or _ALL_
[06:16] <sil2100> bzoltan: hah, all three ;)
[06:16] <bzoltan> sil2100: huhh... thanks
[06:17] <bzoltan> sil2100: that is perfect :)
[06:23] <robru> tvoss_: that's a race condition in the status updater, I'm working on a fix for that right now
[06:23] <tvoss_> robru, ack
[06:23] <robru> lpotter: depends, sometimes 'dependency wait' means 'one package in the silo is waiting for another package in the silo' and will sort itself out, sometimes it means 'ya dun goofed', it requires investigation each time
[06:24] <robru> lpotter: based on your \0/ I'm guessing it sorted itself out
[06:25] <lpotter> yes it did
[07:18] <tvoss_> sil2100, marked https://requests.ci-train.ubuntu.com/#/ticket/1534 as approved again
[07:20] <pstolowski> rvr, morning! i'm rebuilding 2 of the projects in silo 65 because there was some other landing affecting them after you concluded the testing :(. no code changes though (in fact the landing which affected unity-scopes-shell was a no-change rebuild), so I think it be landed without repeating the testing (I'll do a sanity check nevertheless)?
[07:22] <jibel> pstolowski, morning. right, we'll just reinstall the silo to make sure the build didn't break anything then reapprove it
[07:23] <pstolowski> jibel, cool, thanks
[07:26] <sil2100> jibel: hey! So I don't know the current QA policies, we had a QA-approved silo which we had to rebuild due to a landing that landed in the meantime - is it fine that we only get automated tests passing or you need another QA spin on that?
[07:26] <sil2100> jibel: it's the request tvoss mentioned above ^
[07:28] <jibel> sil2100, if it's a no change rebuild, package is installable and automated tests pass, we usually just reapprove it
[07:28] <jibel> same case than silo 65
[07:31] <pstolowski> sil2100, my yesterday's rebuilt & autotesting finished last night, and this morning i found about about another landing affecting ubuntu-system-settings-online-accounts in this silo :/
[07:31] <pstolowski> sil2100, i wodner if it would be possible for bileto to prevent this by some clever warnings
[07:32] <pstolowski> sil2100, first off, to flag every silo which affects same projects. then block/warn/flag whenenver the state of related silo(s) change
[07:33] <mardy> seb128: hi! I think this needs an ubuntu dev to land, and since you were unhappy with the package descriptions, I think this is just for you :-) https://requests.ci-train.ubuntu.com/#/ticket/1532
[07:35] <sil2100> pstolowski: might be a good feature request ;) !
[07:35] <sil2100> jibel: thanks
[07:45] <pstolowski> robru, hey, what do you think? ^^
[07:46] <robru> pstolowski: what do you mean by "state change"? it is already the case when a conflicting silo is published that your silo will change to "destination version missing from changelog" and then when the publish completes and silo is merged to trunk, your status changes to "needs rebuild due to new commits"
[07:47] <seb128> mardy, hey, +1 from me
[07:47] <seb128> mardy, do you need me to publish it?
[07:47] <seb128> mardy, or is there more q.a approval needed?
[07:48] <mardy> seb128: AFAIU, QA has already approved it
[07:48] <mardy> seb128: I see that jibel set the "QA signoff" flag
[07:49] <seb128> mardy, ok, clicked on the publish button
[07:49] <pstolowski> robru, i know of the changelog checks, but this is a bit too late i think? by state changes I mean: when silo A and B affect same projects, and B is set leander approved (ready for QA), silo A shouldn't be allowed to be set lander approved. etc.
[07:49] <mardy> seb128: thanks!
[07:49] <robru> pstolowski: ah good point. please file a bug against lp:bileto
[07:49] <seb128> mardy, yw!
[07:50] <pstolowski> robru, to prevent scenarios such as the one which just happend to silo 65 (and some others before); QA-approved, I hit land and only then I found out about some other landing that happened in the meantime
[07:50] <seb128> mardy, k, publishing worked, thanks for fixing the descriptions!
[07:51] <robru> pstolowski: right
[07:52] <pstolowski> robru, plus, silos affecting same projects could be flagged with a different color all the time in the bileto dashboard, otherwise you have to scan the dashboard all the time
[07:52] <robru> pstolowski: generally one of the longer-term goals is to absorb the QA trello board into bileto, that will give us better control over marshalling the order of tickets in the qa queue. I've also noticed in the past that QA approved two conflicting silos, forcing one to be rebuilt and re-qa'd after publishing the other
[07:52] <pstolowski> robru, k, i'll file a feature request bugf
[07:52] <robru> pstolowski: scan the dashboard? there is a search feature
[07:52] <pstolowski> robru, scan, search... doesn't matter, it needs manual steps
[07:53] <pstolowski> robru, can you remind me what was the project to file the bug against?
[07:54] <robru> pstolowski: lp:bileto
[07:54] <pstolowski> thanks
[07:54] <robru> pstolowski: you're welcome
[07:55] <pstolowski> mardy, hey, Destination version 0.7+16.10.20160610-0ubuntu1 is missing from changelog (ubuntu-system-settings-online-accounts/yakkety) in silo 65, can you take a look?
[07:56] <mardy> pstolowski: let me check...
[07:57] <mardy> pstolowski: oh, another silo landed in the meantime; I'll update my branch
[07:57] <pstolowski> mardy, yeah
[07:57] <mardy> pstolowski: can you also please remove this from the silo? https://code.launchpad.net/~mardy/ubuntu-system-settings-online-accounts/arm64tests-1585942/+merge/296542
[07:58] <pstolowski> mardy, hmm it doesn't say it's merged? did you have it as a part of another change which landed?
[07:58] <mardy> pstolowski: it's in the other silo which landed yesterday
[07:59] <mardy> pstolowski: looks like the bzr merge happens a couple of days later
[07:59]  * mardy doublechecks
[08:00] <mardy> pstolowski: the silo which landed has that branch, so you can remove it from silo 65: https://requests.ci-train.ubuntu.com/#/ticket/1448
[08:00] <pstolowski> mardy, cool,ok
[08:00] <mardy> pstolowski: I think that once the packages leave the proposed pocket, the bzr merge will happen
[08:00] <pstolowski> mardy, yep
[08:04] <jibel> sil2100, 29 reapproved
[08:07] <pstolowski> robru, https://bugs.launchpad.net/bileto/+bug/1593138
[08:20] <robru> pstolowski: thanks
[08:21] <robru> Trevinho: ok, I made the change so that the bzr commit uses the full message, if you rebuild you should see it, let me know if that works for you
[08:22] <sil2100> jibel: thanks!
[09:27] <robru> oh good that's gonna spam IRC every time I do that
[09:29] <sil2100> You're merging a device tarball to trunk?! That's hardcore man, hardcore
[09:41] <mardy> robru: the autotests failed because of some bluez installation issue, completely unrelated; can we force the landing here? http://people.canonical.com/~ubuntu-archive/proposed-migration/yakkety/update_excuses.html#ubuntu-system-settings-online-accounts
[10:02] <robru> mardy: you need to ask #ubuntu-release in the case of proposed migration
[10:03] <mardy> robru: oops, you probably told me already -- I forgot!! Sorry and thanks :-)
[10:03] <robru> mardy: you're welcome
[10:08] <robru> dbarth: congrats on being the first to use the new assign job 😉
[10:34] <jibel> pstolowski, can you reapprove 65?
[10:34] <jibel> so it can land
[10:35] <pstolowski> jibel, i think we still need to wait for ubuntu-system-settings-online-accounts/yakkety landing and the rebuild, no?
[10:35] <robru> pstolowski: jibel indeed it will require another rebuild before qa'ing again
[10:36] <jibel> robru, is there hope for today?
[10:37] <robru> jibel: ah it's stuck here: http://people.canonical.com/~ubuntu-archive/proposed-migration/yakkety/update_excuses.html#ubuntu-system-settings-online-accounts mardy already pinged about that. it does require intervention in order to continue.
[10:38] <mardy> jibel: do you happen to be part of the release team?
[10:38] <jibel> mardy, I am not
[10:38] <jibel> mardy, what do you need?
[10:39] <mardy> jibel: OK, so far I didn't get any answers in #ubuntu-release, I'll try to directly ping someone
[10:39] <mardy> jibel: I need to unblock http://people.canonical.com/~ubuntu-archive/proposed-migration/yakkety/update_excuses.html#ubuntu-system-settings-online-accounts
[10:39] <jibel> mardy, did you try pitti
[10:39] <jibel> ?
[10:40] <jibel> mardy, or laney
[10:40] <robru> mardy: I'm here with slangasek I just asked him, he'll retry the test and investigate
[10:40] <mardy> robru: ah, ok, I pinged cjwatson in #ubuntu-release, but then: cjwatson unping :-)
[10:47] <cjwatson> I really recommend having some other default person to ask about autopkgtests who isn't me
[10:47] <cjwatson> I technically have permissions in at least some cases but don't deal with them much
[11:25] <slangasek> robru: passed on the autopkgtest retry; which FTR any Ubuntu dev can click the button for on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html , does not require a release team member
[11:26] <robru> slangasek: right, thanks. so that'll migrate on the next britney run?
[11:26] <slangasek> release team members are the only ones who can override broken tests or trigger test runs with special options
[11:26] <slangasek> but any Ubuntu dev can retry the test
[11:26] <slangasek> robru: I don't know that it will migrate, I only know that there shouldn't be a test failure as a blocker
[11:27] <robru> slangasek: fair point
[11:27] <robru> pstolowski: jibel: mardy ^^ good news, things are moving forward
[11:28] <mardy> robru, slangasek: thanks!
[11:40] <pstolowski> robru, great. rebuilding
[11:41] <robru> excellent
[12:15] <dbarth> sil2100: i uploaded the ubuntu-html5-launcher branches to silo 058
[12:16] <sil2100> dbarth: thanks! Saw the request :)
[12:53] <rvr> ChrisTownsend: ping
[12:53] <ChrisTownsend> rvr: Hi
[12:53] <rvr> ChrisTownsend: Hi!
[12:53] <rvr> ChrisTownsend: How can I install a package with libertine?
[12:54] <rvr> ChrisTownsend: I'm trying to check "Invalid Libertine Scope results after successfully installing or removing a package"
[12:54] <ChrisTownsend> rvr: I assume you are on a phone/tablet, right?
[12:55] <rvr> ChrisTownsend: Yes, tablet
[12:55] <ChrisTownsend> rvr: Ok, so the Puritine container is RO, so you'll need to create a new container and then install a package in it.  To do that:
[12:56] <ChrisTownsend> rvr: From a non terminal-app shell, such as phablet-shell or ssh, do '$ libertine-container-manager create -i test -n "Test Container"'
[12:57] <ChrisTownsend> rvr: That will take a bit, but once done, then do: '$ libertine-container-manager install-package -i test -p gedit' (or whatever package you want to install)
[12:58] <rvr> Ok
[12:58] <ChrisTownsend> rvr: Be sure to have the XApps scope visible and after the package installs, you should see any icons from that package just show up for that container.
[12:59] <rvr> ChrisTownsend: Yeah, XApps scope is already installed
[13:00] <ChrisTownsend> rvr: Ok, cool
[13:24] <pstolowski> robru, silo 65 lander-approved
[13:25] <robru> pstolowski: cool
[13:26] <rvr> ChrisTownsend: I installed vlc, but it only appeared when I refreshed the scope
[13:26] <rvr> ChrisTownsend: Does it need a new scope version?
[13:26] <rvr> libertine-scope.ubuntu	1.2
[13:44] <ChrisTownsend> rvr: Hmm, I don't think you need a new scope version, but I'll try to see.
[13:45] <rvr> ChrisTownsend: Also installed gedit, and it only showed after pulling to refresh
[13:45] <rvr> ChrisTownsend: And the apps don't start
[13:45] <ChrisTownsend> rvr: Hmm, that is very strange.
[13:45] <rvr> ChrisTownsend: Command line ended with this
[13:45] <rvr> proot error: 'ldconfig.REAL' not found (root = /home/phablet/.cache/libertine-container/test/rootfs, cwd = /home/phablet, $PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games)
[13:45] <rvr> fatal error: see `proot --help`.
[13:46] <ChrisTownsend> rvr: Oh, that is not good, but that explains why it didn't refresh.
[13:46] <rvr> and probably why they don't start
[13:47] <ChrisTownsend> rvr: Were there any issues detected when the container was installed?
[13:47] <rvr> ChrisTownsend: Nope
[13:48] <ChrisTownsend> rvr: Hmm, trying to think what could possibly have happened as that is not normal at all.
[13:48] <rvr> ChrisTownsend: Hmm
[13:48] <ChrisTownsend> rvr: I'm going to try to reproduce.
[13:49] <rvr> ChrisTownsend: I see there were references to that proot error
[13:49] <rvr> Setting up systemd-sysv (219-7ubuntu6) ...
[13:49] <rvr> Refreshing the container's dynamic linker run-time bindings...
[13:49] <rvr> proot error: 'ldconfig.REAL' not found (root = /home/phablet/.cache/libertine-container/test/rootfs, cwd = /home/phablet, $PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games)
[13:49] <rvr> fatal error: see `proot --help`.
[13:49] <rvr> Reading package lists... Done
[13:50] <ChrisTownsend> rvr: I'm scratching my head trying to think why ldconfig.REAL is not in the chroot.  It should be, but that is the problem.
[13:52] <ChrisTownsend> rvr: I'm trying the exact command I gave you on my frieza.
[13:53] <rvr> ~/.cache/libertine-container$ find . -name "ldconfig.REAL
[13:53] <rvr> ./test/rootfs/sbin/ldconfig.REAL
[13:53] <rvr> ChrisTownsend: Maybe /sbin/ is not in the search path
[13:54] <ChrisTownsend> rvr: Yeah..., but it has worked before.
[13:54] <rvr> I see
[13:59] <ChrisTownsend> rvr: It's working fine on my frieza
[14:03] <ChrisTownsend> rvr: Could you do a '$ printenv | grep PATH' and give me the output?
[14:05] <ChrisTownsend> rvr: Or better, '$ echo $PATH'
[14:09] <pstolowski> mardy, a flaky test? https://requests.ci-train.ubuntu.com/static/britney/ticket-979/landing-065-xenial/excuses.html
[14:16] <robru> pstolowski: yeah, that test passed on the last silo, failed in proposed-migration, and succeeded once retried. you need a core dev to click retry on that for you
[14:23] <robru> hold on to your butts
[14:37] <rvr> ChrisTownsend: Hmmm
[14:39] <kenvandine> rvr, we have a settings branch that's adding a rewritten notification panel.  we want to land it so we can ensure the strings get added in plenty of time
[14:40] <kenvandine> rvr, we won't be actually installing the new panel... so the resulting package won't be changed
[14:40] <kenvandine> rvr, can we mark that as NA for QA?
[14:40] <kenvandine> rvr, and of course it'll need QA when we enable the new panel :)
[14:40] <rvr> kenvandine: We can take a quick look just to make sure that everything is ok
[14:41] <rvr> kenvandine: Which branch is it?
[14:41] <kenvandine> ok, i want to push it through quickly so we don't need to rebuild the fingerprint silo to many times
[14:41] <kenvandine> rvr, not quite ready... arthur is doing it right now
[14:42] <rvr> Hmm
[14:42] <ChrisTownsend> rvr: And clues from $PATH?  Your 'Hmmm' left me wanting more;-)
[14:43] <rvr> ChrisTownsend: kenvandine is distracting me ;)
[14:43] <kenvandine> :-p
[14:44] <rvr> ChrisTownsend: phablet@ubuntu-phablet:~$ echo $PATH
[14:44] <rvr> /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
[14:45] <ChrisTownsend> rvr: Ha!
[14:45] <ChrisTownsend> rvr: That $PATH does not look right to me and is the reason proot is failing.
[14:46] <rvr> ChrisTownsend: adb shell returns a root shell, and that's the PATH after "su - phablet"
[14:46] <ChrisTownsend> rvr: Here is my $PATphablet@ubuntu-phablet:~$ echo $PATH
[14:46] <ChrisTownsend> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binH:
[14:46] <ChrisTownsend> rvr: Ahhhh, that's the problem.  Use phablet-shell instead.
[14:47] <rvr> ChrisTownsend: doesn't work on frieza
[14:47] <ChrisTownsend> rvr: Really?  It works for me with no issues.
[14:47] <rvr> because it opens that root shell
[14:47] <rvr> ChrisTownsend: Which image are you using?
[14:48] <ChrisTownsend> rvr: Build 124 plus I did apt-get update to the latest in the overlay.
[14:49] <rvr> ChrisTownsend: Same here :-/
[14:49] <ChrisTownsend> rvr: hrmm
[14:50] <rvr> ChrisTownsend: channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
[14:50] <ChrisTownsend> rvr: Well, I at least understand the problem now.  You could do this to workaround the issue:
[14:50] <ChrisTownsend> export PATH=$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
[14:50] <rvr> export your path
[14:50] <rvr> yeah
[14:51] <ChrisTownsend> rvr: Yeah, same channel for me too.
[14:51] <ChrisTownsend> rvr: Ok, let's try that.
[14:51] <rvr> ChrisTownsend: Ok, removing the old container and creating a new one
[14:51] <ChrisTownsend> rvr: Ok
[15:00] <jibel> pstolowski, re silo 65, ubuntuone-credentials tests fail on xenial/i386 can you recycle them if it's a known flaky test
[15:02] <pstolowski> jibel, yes, i asked pitti to re-try this test but he is not responding; do you know anyone else who has permissions?
[15:02] <mardy> dobey: did you find out the reason for<EMAIL_ADDRESS>?
[15:05] <dobey> mardy: no, i can only assume it's some infrastructure problem causing the python3 process to be killed
[15:05] <dobey> mardy: doesn't seem to be an issue for proposed-migration, only for the PPA autopkgtest runs, afaict
[15:06] <mardy> yep
[15:16] <rvr> ChrisTownsend: No errors now
[15:16] <ChrisTownsend> rvr: Sweet!
[15:16] <rvr> ChrisTownsend: But
[15:17] <rvr> ChrisTownsend: Pull to refresh still needed
[15:17] <ChrisTownsend> rvr: Ugh.  Package installs cleanly?
[15:17] <rvr> ChrisTownsend: Yes
[15:18] <ChrisTownsend> rvr: Hmm, ok, I'll this part now.
[15:19] <rvr> ChrisTownsend: dbus[1805]: apparmor="DENIED" operation="dbus_method_call"  bus="session" path="/com/canonical/URLDispatcher" interface="com.canonical.URLDispatcher" member="DispatchURL" mask="send" name="com.canonical.URLDispatcher" pid=25641 label="libertine-scope.ubuntu_libertine-scope_1.2" peer_pid=1938 peer_label="unconfined"
[15:19] <ChrisTownsend> rvr: How about if you install another package in the same container?
[15:19] <rvr> ChrisTownsend: I have installed vlc, gedit and vim-gtk
[15:20] <rvr> Same result
[15:20] <ChrisTownsend> rvr: Huh?  IS that the Libertine Scope from the Store?
[15:20] <rvr> ChrisTownsend: Yes
[15:21] <bregma> peer_label="unconfined" ...  doesn't that mean it's unconfined?
[15:21] <bregma> I mean, if I had to guess.....
[15:21] <ChrisTownsend> Yeah, it shouldn't be unconfined from the Store.
[15:21] <ChrisTownsend> rvr: But that seems to be some issue with the Scope, not libertine.
[15:23] <rvr> ChrisTownsend: I'm just following the test case in https://bugs.launchpad.net/libertine/+bug/1592115
[15:23] <ChrisTownsend> rvr: Yeah, it works for me, but I'm using a newer Libertine Scope and I installed it by hand.
[15:24] <rvr> ChrisTownsend: Can you send me the click package?
[15:24] <ChrisTownsend> rvr: Sure, I understand, but it's some confinement issue with the Libertine/XApps Scope and not this Libertine landing itself.
[15:25] <ChrisTownsend> rvr: Hmm, actually I'm not using a newer Libertine Scope, but I did install it by hand and not the Store.
[15:28] <pstolowski> cjwatson, hey Colin, can you help with re-trying a flaky test in silo 65 again.. I'm trying to get in touch with pitti but he seems to be away. not sure who else can help
[15:28] <ChrisTownsend> rvr: I'm currently working on a new Libertine Scope landing right now, but I still need to build the click package from it.
[15:28] <rvr> ChrisTownsend: There was a recent change on the Dash for confinement
[15:28] <ChrisTownsend> rvr: That has landed?
[15:29] <cjwatson> pstolowski: any core-dev can; but anyway, sure, which builds exactly?
[15:29] <cjwatson> pstolowski: (quickest is if you give me the +build URLs to retry)
[15:29] <rvr> ChrisTownsend: Hmmm, not sure
[15:29] <rvr> It's silo 65
[15:30] <ChrisTownsend> rvr: Could you try this?
[15:30] <ChrisTownsend> gdbus emit --session --object-path /com/canonical/unity/scopes --signal com.canonical.unity.scopes.InvalidateResults libertine-scope.ubuntu_libertine-scope
[15:31] <rvr> ChrisTownsend: Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
[15:31] <ChrisTownsend> And see if you see the line going back and forth in the XApps scope?
[15:31] <pstolowski> cjwatson, it's a ubuntu-system-settings-online-accounts ; not sure what type of url do you mean?
[15:31] <ChrisTownsend> rvr: Oh, right, the whole su - phablet thing.
[15:31] <rvr> ChrisTownsend: Let me install terminal
[15:32] <ChrisTownsend> rvr: Ok.  Maybe that's the reason too.
[15:32] <pstolowski> rvr, ChrisTownsend no, silo 65 is about to land
[15:32] <ChrisTownsend> rvr: Your user doesn't have access to the session bus so it's denied.
[15:32] <cjwatson> pstolowski: I don't see any ubuntu-system-settings-online-accounts failures on https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-065/+packages.  Are you sure it is still a problem?
[15:32] <pstolowski> cjwatson, https://requests.ci-train.ubuntu.com/static/britney/ticket-979/landing-065-xenial/excuses.html
[15:32] <cjwatson> pstolowski: Ah, I see
[15:33] <rvr> pstolowski: Ack
[15:33] <ChrisTownsend> rvr: Yeah, I'm pretty sure that is the reason come to think of it, the "su - phablet" doesn't set up the environment everything expects.
[15:33] <cjwatson> pstolowski: (always best to give the URL straight away rather than having people try to guess!)
[15:33] <rvr> ChrisTownsend: Right
[15:33] <cjwatson> pstolowski: You mean the ubuntuone-credentials/i386 one?
[15:34] <ChrisTownsend> rvr: I'm still curious why phablet-shell works fine for me and not you.
[15:34] <pstolowski> cjwatson, indeed
[15:34] <cjwatson> pstolowski: retry scheduled
[15:35] <pstolowski> cjwatson, thanks!
[15:36] <pstolowski> cjwatson, btw is there an easy way to identify core devs (other than asking around ;)) ?
[15:36] <cjwatson> pstolowski: https://launchpad.net/~ubuntu-core-dev/+members
[15:36] <pstolowski> nice, ty
[15:37] <ChrisTownsend> rvr: You could also try this:
[15:37] <ChrisTownsend> export `cat /run/user/32011/dbus-session`
[15:43] <rvr> ChrisTownsend: We figured out, I'm flashing with a custom device tarball
[15:44] <ChrisTownsend> rvr: Ah, ok:)
[15:45] <ChrisTownsend> rvr: Maybe by the time you get all of that set up, you'll be able to test the new Libertine Scope that is about to land in your queue as well;-)
[15:52] <rvr> ChrisTownsend: With Terminal, the gdbus signal doesn't return any error
[15:53] <ChrisTownsend> rvr: Ok, you can try to install a package using l-c-m from the terminal-app, but it may or may not work.
[15:53] <rvr> But reflashing
[15:54] <ChrisTownsend> Oh, right
[15:55] <pstolowski> jibel, robru silo 65 passed autopkg tests
[16:12] <pstolowski> jibel, rvr can you sign off silo 65 again?
[16:13] <rvr> pstolowski: Godspeed!
[16:15] <pstolowski> trainguards hey, may i ask for publishing of silo 65?
[16:16] <pstolowski> rvr, thanks!
[16:20] <ChrisTownsend> rvr: BTW, if you are interested in testing the new Libertine Scope landing with the other stuff, it's now ready: https://requests.ci-train.ubuntu.com/#/ticket/1548
[16:56] <pstolowski> kenvandine, hey, can you help & publish silo 65?
[17:03] <kenvandine> pstolowski, looking
[17:03] <rvr> ChrisTownsend: Installed everything, except new scope, and same results :)
[17:09] <pstolowski> kenvandine, thanks!
[17:09] <kenvandine> np
[17:20] <ChrisTownsend> rvr: Same results as in you have to pull down to refresh?
[17:21] <rvr> ChrisTownsend: Yes :-/
[17:21] <ChrisTownsend> rvr: I really don't know what we are missing as it works fine for me and I'm running the same silos.  I'll try installing the Libertine Scope from the Store instead as the last difference.
[17:22] <rvr> ChrisTownsend: I installed the new scope
[17:22] <ChrisTownsend> rvr: You are able to connect with phablet-shell now and not use 'su - phablet'?
[17:22] <rvr> ChrisTownsend: But the new packages aren't installed either
[17:22] <rvr> err
[17:22] <rvr> displayed
[17:23] <rvr> ChrisTownsend: Yes, phablet-shell works now
[17:23] <rvr> There are no errors in dbus.log
[17:23] <ChrisTownsend> rvr: So the denied message is gone now, right?
[17:23] <rvr> ChrisTownsend: Right
[17:24] <ChrisTownsend> rvr: I'm at a loss.
[17:24] <ChrisTownsend> rvr: I'm running that same exact libertine scope click, same silos, and icons show up after installing a package for me.
[17:25] <ChrisTownsend> rvr: Could you try this?  Install a new package or remove one and then run that gdbus command I gave you earlier and see if it refreshes.
[17:26] <rvr> ChrisTownsend: gdbus makes the icons to show up
[17:26] <ChrisTownsend> rvr: That is the same exact call we use in l-c-m
[17:28] <rvr> ChrisTownsend: Hmm... wait, the package wasn't installed
[17:28] <ChrisTownsend> rvr: Could you pastebin the contents of ~/.local/share/libertine/ContainersConfig.json ?  The only way that l-c-m won't update is if the package fails to install cleanly.
[17:28] <ChrisTownsend> rvr: Err, right.
[17:28] <rvr>      1.2+15.04.20160615.1-0ubuntu1 0
[17:28] <rvr>        1100 http://ppa.launchpad.net/ci-train-ppa-service/landing-016/ubuntu/ vivid/main armhf Packages
[17:28] <rvr>  *** 1.0.4+15.04.20160519-0ubuntu1 0
[17:29] <ChrisTownsend> rvr: I think you have to do a dist-upgrade and let it remove libertine-demo and ubuntu-pocket-desktop.
[17:29] <rvr> Los siguientes paquetes se ELIMINARÁN:
[17:29] <rvr>   libertine-demo ubuntu-pocket-desktop
[17:29] <rvr> ChrisTownsend: Right
[17:29] <ChrisTownsend> rvr: This will be fixed soon in the image.
[17:30] <kenvandine> rvr, here's the MR https://code.launchpad.net/~artmello/ubuntu-system-settings/ubuntu-system-settings-new_notifications_panel/+merge/297656
[17:31] <kenvandine> rvr, doesn't build the new panel at all
[17:31] <ChrisTownsend> rvr: Hey, don't distract rvr;-)
[17:32] <ChrisTownsend> Err, I meant that for kenvandine, lol
[17:32] <kenvandine> :)
[17:33] <kenvandine> rvr, it's in silo 29
[17:33] <rvr> lol
[17:34] <rvr> ChrisTownsend: Weee
[17:34] <rvr> ChrisTownsend: Finally
[17:34] <rvr> ChrisTownsend: That was it
[17:34] <ChrisTownsend> rvr: \o/
[17:37] <rvr> kenvandine: That's a lot of code that would be committed untested. If the problem are the strings, you can update manually the pot file. And in any case, why the urgency?
[17:39] <kenvandine> rvr, the pot file is generated during package build, so that's tricky
[17:39] <kenvandine> it'll be tested before any of it is built
[17:42] <kenvandine> rvr, we are hoping to enable it in time for OTA12, but it's blocked on other backends that need to land
[17:44] <rvr> kenvandine: Feature freeze is tomorrow
[17:44] <kenvandine> i know :)
[17:44] <kenvandine> we're hoping the backends we need land
[17:47] <rvr> kenvandine: In my opinion, this should land as any other silo, passing QA.
[17:49] <kenvandine> ok
[17:49] <kenvandine> bfiller, ^^
[17:49] <kenvandine> guess we'll have to hold off
[17:50] <kenvandine> rvr, mostly concerned about having plenty of time for translations
[17:51] <bfiller> rvr: feature freeze next friday, we are just trying to land the strings
[17:51] <bfiller> rvr: it's fine if QA wants to review it, there will be no visible change to the UI as it will be hidden now
[17:51] <bfiller> kenvandine: ^^
[17:51] <rvr> robru: Didn't you create a bileto hook for translations?
[17:51] <kenvandine> right... string freeze tomorrow
[17:52] <kenvandine> rvr, we've done this in the past
[17:54] <rvr> bfiller: My concern is that we are committing code that is not tested and that is not a good practice. I understand that is not currently used, but that's the point: if not used, then we cannot validate.
[17:54] <bfiller> rvr: it has been tested in fact
[17:54] <bfiller> rvr: it has tests and we've tested the ui part
[17:54] <rvr> bfiller: I mean, validated by QA team
[17:55] <rvr> bfiller: The feature freeze is also tomorrow, so if it won't be ready...
[17:56] <bfiller> rvr: no it's not
[17:56] <robru> rvr: yes, see unity 8
[17:56] <kenvandine> string freeze is tomorrow
[17:56] <bfiller> rvr: 24 Jun
[17:57] <rvr> bfiller: See jibel's email
[17:57] <rvr> bfiller: - String/Feature freeze: June 17th (Friday this week)
[17:57] <rvr> robru: How does it work?
[17:58] <robru> rvr: http://bazaar.launchpad.net/~ci-train-bot/unity8/unity8-ubuntu-yakkety-landing-025/view/head:/debian/bileto_pre_release_hook
[17:58] <bfiller> rvr: maybe we have a misunderstanding, I will sync up with jibel
[17:59] <robru> rvr: write that script and bileto will call it and commit results
[18:00] <rvr> bfiller: Ok
[18:00] <rvr> robru: Interesting
[18:00] <rvr> kenvandine: ^
[18:01] <robru> rvr: phone dying,email me with any other questions
[18:01] <kenvandine> rvr, we have the pot file getting updated during package build
[18:01] <robru> kenvandine: that won't commit results though
[18:01] <kenvandine> not to bzr
[18:01] <kenvandine> we don't do that
[18:02] <kenvandine> if we manually update the pot file it'll get stomped next landing
[18:03] <kenvandine> which we like doing
[18:03] <rvr> robru: I'll send you an email to know more
[18:03] <kenvandine> bfiller, feature freeze should really be a week before string freeze... we keep doing this backwards
[18:03] <robru> kenvandine: if you want newest pot every landing bileto can do it so bzr always up to date
[18:03] <kenvandine> many features require string changes
[18:04] <kenvandine> robru, but we don't really care about the pot file in bzr
[18:04] <kenvandine> what we have works great :)
[18:05] <bfiller> kenvandine: I'm looking at UES calendar, 17-June says String freeze and 24-June says Final freeze, nothing about feature freeze
[18:05] <bfiller> will discuss with pat and jibel
[18:05] <bfiller> we might need exceptions
[18:05] <kenvandine> yeah
[18:05] <bfiller> kenvandine: so we better try and land fp reader in a working state tomorrow
[18:07] <rvr> bfiller: jibel told me in our daily standup that other people were surposed to know the feature freeze was tomorrow as well
[18:07] <rvr> suprised
[18:07] <bfiller> rvr: seems we have some miscommunications
[18:07] <rvr> Yup
[18:07] <kenvandine> yeah
[18:08] <rvr> bfiller: AFAIK, Pat is in holidays
[18:09] <dobey> people should have read their e-mail from like 6 weeks ago
[18:09] <dobey> yeesh :P
[18:09] <dobey> bfiller: string freeze is feature freeze
[18:10] <dobey> bfiller: kind of pointless adding features if you can't add strings, eh? :)
[18:10] <bfiller> dobey: whatever dude
[18:10] <bfiller> dont' want to argue it with you right now
[18:10] <dobey> heh, i'm not trying to argue
[18:11] <kenvandine> it's always been  a problem having string freeze before feature freeze... is backwards
[18:11] <kenvandine> looking back at Pat's email, it actually didn't mention feature freeze at all
[18:12] <kenvandine> but when i read it was thinking feature freeze
[18:12] <kenvandine> tvoss, think we can land fingerprint tomorrow?
[18:20] <rvr> kenvandine: A workaround would be to extract the new strings, and put them in a mock qml file or similar
[18:21] <rvr> and remove that file when the real code lands
[18:21] <rvr> I'll have to go now
[18:21] <kenvandine> rvr, well if string freeze and feature freeze are the same, there's no point
[18:21] <kenvandine> thanks rvr
[18:22] <rvr> kenvandine: Right, that's what I was thinking. Idea in case you are granted a FFE.
[18:22] <kenvandine> i hate rushing translators
[18:33] <dobey> well, if you know what the strings will be, before the feature is ready, that can work
[18:33] <dobey> but if you don't, obviously not an option :)
[18:46] <tvoss> kenvandine, think so, I think we can also iterate on rc-proposed
[19:21] <bzoltan> davmor2: I have seen your comment about the UITK silo
[19:21] <bzoltan> davmor2:  i just want to make sure that you do understand what that change is about.
[19:22] <davmor2> bzoltan: yeap I get it so no worries there and it only seems to affect telegram so far as they use no header by default I think
[19:23] <davmor2> but I need to clear off now so I'll pick it up tomorrow morning when the telegram dev is online too
[19:24] <davmor2> bzoltan: hope that makes sense :)
[19:24] <bzoltan> davmor2: We have talked to the telegram devs, and there was a discussion about the topic - https://lists.launchpad.net/ubuntu-phone/msg20703.html
[19:25] <bzoltan> davmor2:  It is not a random, ad-hoc change, but a part of an orchestrated rollut and communication.
[19:25] <bzoltan> davmor2:  we have sent that mail, talked to lots of developers f2f, we have sent patches to apps
[19:27] <bzoltan> davmor2: I have been scanning the whole store for apps using the APL with the old page header. Got all the effected apps under control - https://docs.google.com/document/d/1jo_u29FpC3DM_UTk2GTEZWlBepXNx6zCOOg79j4K2fk/edit#
[19:28] <bzoltan> davmor2:  and this change is a visual alert, so _we_ do see during dogfooding if somebody is using this non compatible mix of these two components.
[19:28] <bzoltan> davmor2: if somebody needs any information about it me, t1mp and zsombi are here to help.
[19:29] <bzoltan> davmor2:  so, design has nothing to do with it... it is not a visual what we will see in real life :)
[19:39] <mterry> jibel, rvr: silo 25 really wants to land before FF.  It's being rebuilt to accomodate a small apparmor fix that landing today, but it's ready for testing
[19:40] <mterry> Could it be put into the QA queue even though it's not "ready"
[19:40] <mterry> ?
[20:47] <dobey> kenvandine, mterry: could one of you smash the retry button on https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-069/+build/10030758 please?
[20:47] <mterry> k
[20:47] <mterry> dobey, done
[20:47] <dobey> mterry: thanks