/srv/irclogs.ubuntu.com/2016/06/16/#ubuntu-ci-eng.txt

=== _salem is now known as salem_
=== chihchun_afk is now known as chihchun
bzoltanrobru: 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.html02:12
robrubzoltan: I dunno who's around at this time, sorry02:15
robrubzoltan: https://launchpad.net/~ubuntu-core-dev/+members#active02:17
=== chihchun is now known as chihchun_afk
bzoltanrobru: 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:24
=== chihchun_afk is now known as chihchun
robrubzoltan: sil is sleeping a few feet from me and should be functional in about 3 hours02:38
bzoltanrobru: sounds promising :)02:38
robrulpotter_: your changelog is busted02:41
lpotter_ffs02:42
=== chihchun is now known as chihchun_afk
lpotter__do I have to manually do anything for 'dependency wait'?04:18
=== salem_ is now known as _salem
=== chihchun_afk is now known as chihchun
lpotter__\0/04:59
=== lpotter__ is now known as lpotter
sil2100tvoss_: hey! https://requests.ci-train.ubuntu.com/#/ticket/1534 needs a rebuild06:02
tvoss_sil2100, thx, kicked06:02
=== _salem is now known as salem_
tvoss_sil2100, not sure what happened here: https://requests.ci-train.ubuntu.com/#/ticket/153406:09
bzoltansil2100: 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:09
sil2100tvoss_: hm, let's give it a moment of time06:10
sil2100tvoss_: I see stuff is building in the PPA for now06:10
sil2100bzoltan: on it!06:10
sil2100bzoltan: no worries, our connection is better so recycling is less painful ;)06:11
bzoltansil2100: thank you06:11
sil2100All pressed06:11
bzoltansil2100: do  you mean :) all three or _ALL_06:16
sil2100bzoltan: hah, all three ;)06:16
bzoltansil2100: huhh... thanks06:16
bzoltansil2100: that is perfect :)06:17
robrutvoss_: that's a race condition in the status updater, I'm working on a fix for that right now06:23
tvoss_robru, ack06:23
robrulpotter: 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 time06:23
robrulpotter: based on your \0/ I'm guessing it sorted itself out06:24
lpotteryes it did06:25
tvoss_sil2100, marked https://requests.ci-train.ubuntu.com/#/ticket/1534 as approved again07:18
pstolowskirvr, 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:20
jibelpstolowski, morning. right, we'll just reinstall the silo to make sure the build didn't break anything then reapprove it07:22
pstolowskijibel, cool, thanks07:23
=== faenil_ is now known as faenil
sil2100jibel: 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
sil2100jibel: it's the request tvoss mentioned above ^07:26
jibelsil2100, if it's a no change rebuild, package is installable and automated tests pass, we usually just reapprove it07:28
jibelsame case than silo 6507:28
pstolowskisil2100, 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
pstolowskisil2100, i wodner if it would be possible for bileto to prevent this by some clever warnings07:31
pstolowskisil2100, first off, to flag every silo which affects same projects. then block/warn/flag whenenver the state of related silo(s) change07:32
mardyseb128: 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/153207:33
sil2100pstolowski: might be a good feature request ;) !07:35
sil2100jibel: thanks07:35
pstolowskirobru, hey, what do you think? ^^07:45
robrupstolowski: 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:46
seb128mardy, hey, +1 from me07:47
seb128mardy, do you need me to publish it?07:47
seb128mardy, or is there more q.a approval needed?07:47
mardyseb128: AFAIU, QA has already approved it07:48
mardyseb128: I see that jibel set the "QA signoff" flag07:48
seb128mardy, ok, clicked on the publish button07:49
pstolowskirobru, 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
mardyseb128: thanks!07:49
robrupstolowski: ah good point. please file a bug against lp:bileto07:49
seb128mardy, yw!07:49
pstolowskirobru, 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 meantime07:50
seb128mardy, k, publishing worked, thanks for fixing the descriptions!07:50
robrupstolowski: right07:51
pstolowskirobru, 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 time07:52
robrupstolowski: 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 other07:52
pstolowskirobru, k, i'll file a feature request bugf07:52
robrupstolowski: scan the dashboard? there is a search feature07:52
pstolowskirobru, scan, search... doesn't matter, it needs manual steps07:52
pstolowskirobru, can you remind me what was the project to file the bug against?07:53
robrupstolowski: lp:bileto07:54
pstolowskithanks07:54
robrupstolowski: you're welcome07:54
pstolowskimardy, 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:55
mardypstolowski: let me check...07:56
mardypstolowski: oh, another silo landed in the meantime; I'll update my branch07:57
pstolowskimardy, yeah07:57
mardypstolowski: can you also please remove this from the silo? https://code.launchpad.net/~mardy/ubuntu-system-settings-online-accounts/arm64tests-1585942/+merge/29654207:57
pstolowskimardy, hmm it doesn't say it's merged? did you have it as a part of another change which landed?07:58
mardypstolowski: it's in the other silo which landed yesterday07:58
mardypstolowski: looks like the bzr merge happens a couple of days later07:59
* mardy doublechecks07:59
mardypstolowski: the silo which landed has that branch, so you can remove it from silo 65: https://requests.ci-train.ubuntu.com/#/ticket/144808:00
pstolowskimardy, cool,ok08:00
mardypstolowski: I think that once the packages leave the proposed pocket, the bzr merge will happen08:00
pstolowskimardy, yep08:00
jibelsil2100, 29 reapproved08:04
=== faenil is now known as faenil_
pstolowskirobru, https://bugs.launchpad.net/bileto/+bug/159313808:07
ubot5Launchpad bug 1593138 in Bileto "Flag/block/serialize silos affecting same project" [Undecided,New]08:07
robrupstolowski: thanks08:20
robruTrevinho: 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 you08:21
sil2100jibel: thanks!08:22
=== faenil_ is now known as faenil
robruoh good that's gonna spam IRC every time I do that09:27
sil2100You're merging a device tarball to trunk?! That's hardcore man, hardcore09:29
mardyrobru: 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-accounts09:41
robrumardy: you need to ask #ubuntu-release in the case of proposed migration10:02
mardyrobru: oops, you probably told me already -- I forgot!! Sorry and thanks :-)10:03
robrumardy: you're welcome10:03
=== chihchun is now known as chihchun_afk
robrudbarth: congrats on being the first to use the new assign job 😉10:08
=== salem_ is now known as _salem
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
jibelpstolowski, can you reapprove 65?10:34
jibelso it can land10:34
pstolowskijibel, i think we still need to wait for ubuntu-system-settings-online-accounts/yakkety landing and the rebuild, no?10:35
robrupstolowski: jibel indeed it will require another rebuild before qa'ing again10:35
jibelrobru, is there hope for today?10:36
robrujibel: 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:37
mardyjibel: do you happen to be part of the release team?10:38
jibelmardy, I am not10:38
jibelmardy, what do you need?10:38
mardyjibel: OK, so far I didn't get any answers in #ubuntu-release, I'll try to directly ping someone10:39
mardyjibel: I need to unblock http://people.canonical.com/~ubuntu-archive/proposed-migration/yakkety/update_excuses.html#ubuntu-system-settings-online-accounts10:39
jibelmardy, did you try pitti10:39
jibel?10:39
jibelmardy, or laney10:40
robrumardy: I'm here with slangasek I just asked him, he'll retry the test and investigate10:40
mardyrobru: ah, ok, I pinged cjwatson in #ubuntu-release, but then: cjwatson unping :-)10:40
cjwatsonI really recommend having some other default person to ask about autopkgtests who isn't me10:47
cjwatsonI technically have permissions in at least some cases but don't deal with them much10:47
=== _salem is now known as salem_
=== dpm_ is now known as dpm
slangasekrobru: 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 member11:25
robruslangasek: right, thanks. so that'll migrate on the next britney run?11:26
slangasekrelease team members are the only ones who can override broken tests or trigger test runs with special options11:26
slangasekbut any Ubuntu dev can retry the test11:26
slangasekrobru: I don't know that it will migrate, I only know that there shouldn't be a test failure as a blocker11:26
robruslangasek: fair point11:27
robrupstolowski: jibel: mardy ^^ good news, things are moving forward11:27
mardyrobru, slangasek: thanks!11:28
pstolowskirobru, great. rebuilding11:40
robruexcellent11:41
=== salem_ is now known as _salem
dbarthsil2100: i uploaded the ubuntu-html5-launcher branches to silo 05812:15
sil2100dbarth: thanks! Saw the request :)12:16
rvrChrisTownsend: ping12:53
ChrisTownsendrvr: Hi12:53
rvrChrisTownsend: Hi!12:53
rvrChrisTownsend: How can I install a package with libertine?12:53
rvrChrisTownsend: I'm trying to check "Invalid Libertine Scope results after successfully installing or removing a package"12:54
ChrisTownsendrvr: I assume you are on a phone/tablet, right?12:54
rvrChrisTownsend: Yes, tablet12:55
ChrisTownsendrvr: 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:55
ChrisTownsendrvr: From a non terminal-app shell, such as phablet-shell or ssh, do '$ libertine-container-manager create -i test -n "Test Container"'12:56
ChrisTownsendrvr: 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:57
rvrOk12:58
ChrisTownsendrvr: 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:58
rvrChrisTownsend: Yeah, XApps scope is already installed12:59
ChrisTownsendrvr: Ok, cool13:00
pstolowskirobru, silo 65 lander-approved13:24
robrupstolowski: cool13:25
rvrChrisTownsend: I installed vlc, but it only appeared when I refreshed the scope13:26
rvrChrisTownsend: Does it need a new scope version?13:26
rvrlibertine-scope.ubuntu1.213:26
ChrisTownsendrvr: Hmm, I don't think you need a new scope version, but I'll try to see.13:44
rvrChrisTownsend: Also installed gedit, and it only showed after pulling to refresh13:45
rvrChrisTownsend: And the apps don't start13:45
ChrisTownsendrvr: Hmm, that is very strange.13:45
rvrChrisTownsend: Command line ended with this13:45
rvrproot 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
rvrfatal error: see `proot --help`.13:45
ChrisTownsendrvr: Oh, that is not good, but that explains why it didn't refresh.13:46
rvrand probably why they don't start13:46
ChrisTownsendrvr: Were there any issues detected when the container was installed?13:47
rvrChrisTownsend: Nope13:47
ChrisTownsendrvr: Hmm, trying to think what could possibly have happened as that is not normal at all.13:48
rvrChrisTownsend: Hmm13:48
ChrisTownsendrvr: I'm going to try to reproduce.13:48
rvrChrisTownsend: I see there were references to that proot error13:49
rvrSetting up systemd-sysv (219-7ubuntu6) ...13:49
rvrRefreshing the container's dynamic linker run-time bindings...13:49
rvrproot 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
rvrfatal error: see `proot --help`.13:49
rvrReading package lists... Done13:49
ChrisTownsendrvr: 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:50
ChrisTownsendrvr: I'm trying the exact command I gave you on my frieza.13:52
rvr~/.cache/libertine-container$ find . -name "ldconfig.REAL13:53
rvr./test/rootfs/sbin/ldconfig.REAL13:53
rvrChrisTownsend: Maybe /sbin/ is not in the search path13:53
ChrisTownsendrvr: Yeah..., but it has worked before.13:54
rvrI see13:54
ChrisTownsendrvr: It's working fine on my frieza13:59
ChrisTownsendrvr: Could you do a '$ printenv | grep PATH' and give me the output?14:03
ChrisTownsendrvr: Or better, '$ echo $PATH'14:05
pstolowskimardy, a flaky test? https://requests.ci-train.ubuntu.com/static/britney/ticket-979/landing-065-xenial/excuses.html14:09
robrupstolowski: 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 you14:16
robruhold on to your butts14:23
rvrChrisTownsend: Hmmm14:37
=== olli__ is now known as olli
kenvandinervr, 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 time14:39
kenvandinervr, we won't be actually installing the new panel... so the resulting package won't be changed14:40
kenvandinervr, can we mark that as NA for QA?14:40
kenvandinervr, and of course it'll need QA when we enable the new panel :)14:40
rvrkenvandine: We can take a quick look just to make sure that everything is ok14:40
rvrkenvandine: Which branch is it?14:41
kenvandineok, i want to push it through quickly so we don't need to rebuild the fingerprint silo to many times14:41
kenvandinervr, not quite ready... arthur is doing it right now14:41
rvrHmm14:42
ChrisTownsendrvr: And clues from $PATH?  Your 'Hmmm' left me wanting more;-)14:42
rvrChrisTownsend: kenvandine is distracting me ;)14:43
kenvandine:-p14:43
rvrChrisTownsend: phablet@ubuntu-phablet:~$ echo $PATH14:44
rvr/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games14:44
ChrisTownsendrvr: Ha!14:45
ChrisTownsendrvr: That $PATH does not look right to me and is the reason proot is failing.14:45
rvrChrisTownsend: adb shell returns a root shell, and that's the PATH after "su - phablet"14:46
ChrisTownsendrvr: Here is my $PATphablet@ubuntu-phablet:~$ echo $PATH14:46
ChrisTownsend/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binH:14:46
ChrisTownsendrvr: Ahhhh, that's the problem.  Use phablet-shell instead.14:46
rvrChrisTownsend: doesn't work on frieza14:47
ChrisTownsendrvr: Really?  It works for me with no issues.14:47
rvrbecause it opens that root shell14:47
rvrChrisTownsend: Which image are you using?14:47
ChrisTownsendrvr: Build 124 plus I did apt-get update to the latest in the overlay.14:48
rvrChrisTownsend: Same here :-/14:49
ChrisTownsendrvr: hrmm14:49
rvrChrisTownsend: channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en14:50
ChrisTownsendrvr: Well, I at least understand the problem now.  You could do this to workaround the issue:14:50
ChrisTownsendexport PATH=$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin14:50
rvrexport your path14:50
rvryeah14:50
ChrisTownsendrvr: Yeah, same channel for me too.14:51
ChrisTownsendrvr: Ok, let's try that.14:51
rvrChrisTownsend: Ok, removing the old container and creating a new one14:51
ChrisTownsendrvr: Ok14:51
jibelpstolowski, re silo 65, ubuntuone-credentials tests fail on xenial/i386 can you recycle them if it's a known flaky test15:00
pstolowskijibel, yes, i asked pitti to re-try this test but he is not responding; do you know anyone else who has permissions?15:02
mardydobey: did you find out the reason for https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ci-train-ppa-service-landing-065/xenial/i386/u/ubuntuone-credentials/20160616_135441@/log.gz ?15:02
dobeymardy: no, i can only assume it's some infrastructure problem causing the python3 process to be killed15:05
dobeymardy: doesn't seem to be an issue for proposed-migration, only for the PPA autopkgtest runs, afaict15:05
mardyyep15:06
rvrChrisTownsend: No errors now15:16
ChrisTownsendrvr: Sweet!15:16
rvrChrisTownsend: But15:16
rvrChrisTownsend: Pull to refresh still needed15:17
ChrisTownsendrvr: Ugh.  Package installs cleanly?15:17
rvrChrisTownsend: Yes15:17
ChrisTownsendrvr: Hmm, ok, I'll this part now.15:18
rvrChrisTownsend: 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
ChrisTownsendrvr: How about if you install another package in the same container?15:19
rvrChrisTownsend: I have installed vlc, gedit and vim-gtk15:19
rvrSame result15:20
ChrisTownsendrvr: Huh?  IS that the Libertine Scope from the Store?15:20
rvrChrisTownsend: Yes15:20
bregmapeer_label="unconfined" ...  doesn't that mean it's unconfined?15:21
bregmaI mean, if I had to guess.....15:21
ChrisTownsendYeah, it shouldn't be unconfined from the Store.15:21
ChrisTownsendrvr: But that seems to be some issue with the Scope, not libertine.15:21
rvrChrisTownsend: I'm just following the test case in https://bugs.launchpad.net/libertine/+bug/159211515:23
ubot5Launchpad bug 1592115 in libertine (Ubuntu) "Invalidate libertine-scope results when adding/removing packages" [Medium,Triaged]15:23
ChrisTownsendrvr: Yeah, it works for me, but I'm using a newer Libertine Scope and I installed it by hand.15:23
rvrChrisTownsend: Can you send me the click package?15:24
ChrisTownsendrvr: Sure, I understand, but it's some confinement issue with the Libertine/XApps Scope and not this Libertine landing itself.15:24
ChrisTownsendrvr: Hmm, actually I'm not using a newer Libertine Scope, but I did install it by hand and not the Store.15:25
pstolowskicjwatson, 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 help15:28
ChrisTownsendrvr: 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
rvrChrisTownsend: There was a recent change on the Dash for confinement15:28
ChrisTownsendrvr: That has landed?15:28
cjwatsonpstolowski: any core-dev can; but anyway, sure, which builds exactly?15:29
cjwatsonpstolowski: (quickest is if you give me the +build URLs to retry)15:29
rvrChrisTownsend: Hmmm, not sure15:29
rvrIt's silo 6515:29
ChrisTownsendrvr: Could you try this?15:30
ChrisTownsendgdbus emit --session --object-path /com/canonical/unity/scopes --signal com.canonical.unity.scopes.InvalidateResults libertine-scope.ubuntu_libertine-scope15:30
rvrChrisTownsend: Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY15:31
ChrisTownsendAnd see if you see the line going back and forth in the XApps scope?15:31
pstolowskicjwatson, it's a ubuntu-system-settings-online-accounts ; not sure what type of url do you mean?15:31
ChrisTownsendrvr: Oh, right, the whole su - phablet thing.15:31
rvrChrisTownsend: Let me install terminal15:31
ChrisTownsendrvr: Ok.  Maybe that's the reason too.15:32
pstolowskirvr, ChrisTownsend no, silo 65 is about to land15:32
ChrisTownsendrvr: Your user doesn't have access to the session bus so it's denied.15:32
cjwatsonpstolowski: 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
pstolowskicjwatson, https://requests.ci-train.ubuntu.com/static/britney/ticket-979/landing-065-xenial/excuses.html15:32
cjwatsonpstolowski: Ah, I see15:32
rvrpstolowski: Ack15:33
ChrisTownsendrvr: 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
cjwatsonpstolowski: (always best to give the URL straight away rather than having people try to guess!)15:33
rvrChrisTownsend: Right15:33
cjwatsonpstolowski: You mean the ubuntuone-credentials/i386 one?15:33
ChrisTownsendrvr: I'm still curious why phablet-shell works fine for me and not you.15:34
pstolowskicjwatson, indeed15:34
cjwatsonpstolowski: retry scheduled15:34
pstolowskicjwatson, thanks!15:35
pstolowskicjwatson, btw is there an easy way to identify core devs (other than asking around ;)) ?15:36
cjwatsonpstolowski: https://launchpad.net/~ubuntu-core-dev/+members15:36
pstolowskinice, ty15:36
ChrisTownsendrvr: You could also try this:15:37
ChrisTownsendexport `cat /run/user/32011/dbus-session`15:37
rvrChrisTownsend: We figured out, I'm flashing with a custom device tarball15:43
ChrisTownsendrvr: Ah, ok:)15:44
ChrisTownsendrvr: 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:45
rvrChrisTownsend: With Terminal, the gdbus signal doesn't return any error15:52
ChrisTownsendrvr: 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
rvrBut reflashing15:53
ChrisTownsendOh, right15:54
pstolowskijibel, robru silo 65 passed autopkg tests15:55
pstolowskijibel, rvr can you sign off silo 65 again?16:12
rvrpstolowski: Godspeed!16:13
pstolowskitrainguards hey, may i ask for publishing of silo 65?16:15
pstolowskirvr, thanks!16:16
=== dpm is now known as dpm-afk
ChrisTownsendrvr: 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/154816:20
=== dpm-afk is now known as dpm
pstolowskikenvandine, hey, can you help & publish silo 65?16:56
kenvandinepstolowski, looking17:03
rvrChrisTownsend: Installed everything, except new scope, and same results :)17:03
pstolowskikenvandine, thanks!17:09
kenvandinenp17:09
ChrisTownsendrvr: Same results as in you have to pull down to refresh?17:20
rvrChrisTownsend: Yes :-/17:21
ChrisTownsendrvr: 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:21
rvrChrisTownsend: I installed the new scope17:22
ChrisTownsendrvr: You are able to connect with phablet-shell now and not use 'su - phablet'?17:22
rvrChrisTownsend: But the new packages aren't installed either17:22
rvrerr17:22
rvrdisplayed17:22
rvrChrisTownsend: Yes, phablet-shell works now17:23
rvrThere are no errors in dbus.log17:23
ChrisTownsendrvr: So the denied message is gone now, right?17:23
rvrChrisTownsend: Right17:23
ChrisTownsendrvr: I'm at a loss.17:24
ChrisTownsendrvr: I'm running that same exact libertine scope click, same silos, and icons show up after installing a package for me.17:24
ChrisTownsendrvr: 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:25
rvrChrisTownsend: gdbus makes the icons to show up17:26
ChrisTownsendrvr: That is the same exact call we use in l-c-m17:26
rvrChrisTownsend: Hmm... wait, the package wasn't installed17:28
ChrisTownsendrvr: 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
ChrisTownsendrvr: Err, right.17:28
rvr     1.2+15.04.20160615.1-0ubuntu1 017:28
rvr       1100 http://ppa.launchpad.net/ci-train-ppa-service/landing-016/ubuntu/ vivid/main armhf Packages17:28
rvr *** 1.0.4+15.04.20160519-0ubuntu1 017:28
ChrisTownsendrvr: I think you have to do a dist-upgrade and let it remove libertine-demo and ubuntu-pocket-desktop.17:29
rvrLos siguientes paquetes se ELIMINARÁN:17:29
rvr  libertine-demo ubuntu-pocket-desktop17:29
rvrChrisTownsend: Right17:29
ChrisTownsendrvr: This will be fixed soon in the image.17:29
kenvandinervr, here's the MR https://code.launchpad.net/~artmello/ubuntu-system-settings/ubuntu-system-settings-new_notifications_panel/+merge/29765617:30
kenvandinervr, doesn't build the new panel at all17:31
ChrisTownsendrvr: Hey, don't distract rvr;-)17:31
ChrisTownsendErr, I meant that for kenvandine, lol17:32
kenvandine:)17:32
kenvandinervr, it's in silo 2917:33
rvrlol17:33
rvrChrisTownsend: Weee17:34
rvrChrisTownsend: Finally17:34
rvrChrisTownsend: That was it17:34
ChrisTownsendrvr: \o/17:34
rvrkenvandine: 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:37
kenvandinervr, the pot file is generated during package build, so that's tricky17:39
kenvandineit'll be tested before any of it is built17:39
kenvandinervr, we are hoping to enable it in time for OTA12, but it's blocked on other backends that need to land17:42
rvrkenvandine: Feature freeze is tomorrow17:44
kenvandinei know :)17:44
kenvandinewe're hoping the backends we need land17:44
rvrkenvandine: In my opinion, this should land as any other silo, passing QA.17:47
kenvandineok17:49
kenvandinebfiller, ^^17:49
kenvandineguess we'll have to hold off17:49
kenvandinervr, mostly concerned about having plenty of time for translations17:50
bfillerrvr: feature freeze next friday, we are just trying to land the strings17:51
bfillerrvr: it's fine if QA wants to review it, there will be no visible change to the UI as it will be hidden now17:51
bfillerkenvandine: ^^17:51
rvrrobru: Didn't you create a bileto hook for translations?17:51
kenvandineright... string freeze tomorrow17:51
kenvandinervr, we've done this in the past17:52
rvrbfiller: 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
bfillerrvr: it has been tested in fact17:54
bfillerrvr: it has tests and we've tested the ui part17:54
rvrbfiller: I mean, validated by QA team17:54
rvrbfiller: The feature freeze is also tomorrow, so if it won't be ready...17:55
bfillerrvr: no it's not17:56
robrurvr: yes, see unity 817:56
kenvandinestring freeze is tomorrow17:56
bfillerrvr: 24 Jun17:56
rvrbfiller: See jibel's email17:57
rvrbfiller: - String/Feature freeze: June 17th (Friday this week)17:57
rvrrobru: How does it work?17:57
robrurvr: http://bazaar.launchpad.net/~ci-train-bot/unity8/unity8-ubuntu-yakkety-landing-025/view/head:/debian/bileto_pre_release_hook17:58
bfillerrvr: maybe we have a misunderstanding, I will sync up with jibel17:58
robrurvr: write that script and bileto will call it and commit results17:59
rvrbfiller: Ok18:00
rvrrobru: Interesting18:00
rvrkenvandine: ^18:00
robrurvr: phone dying,email me with any other questions18:01
kenvandinervr, we have the pot file getting updated during package build18:01
robrukenvandine: that won't commit results though18:01
kenvandinenot to bzr18:01
kenvandinewe don't do that18:01
kenvandineif we manually update the pot file it'll get stomped next landing18:02
kenvandinewhich we like doing18:03
rvrrobru: I'll send you an email to know more18:03
kenvandinebfiller, feature freeze should really be a week before string freeze... we keep doing this backwards18:03
robrukenvandine: if you want newest pot every landing bileto can do it so bzr always up to date18:03
kenvandinemany features require string changes18:03
kenvandinerobru, but we don't really care about the pot file in bzr18:04
kenvandinewhat we have works great :)18:04
bfillerkenvandine: I'm looking at UES calendar, 17-June says String freeze and 24-June says Final freeze, nothing about feature freeze18:05
bfillerwill discuss with pat and jibel18:05
bfillerwe might need exceptions18:05
kenvandineyeah18:05
bfillerkenvandine: so we better try and land fp reader in a working state tomorrow18:05
rvrbfiller: jibel told me in our daily standup that other people were surposed to know the feature freeze was tomorrow as well18:07
rvrsuprised18:07
bfillerrvr: seems we have some miscommunications18:07
rvrYup18:07
kenvandineyeah18:07
rvrbfiller: AFAIK, Pat is in holidays18:08
dobeypeople should have read their e-mail from like 6 weeks ago18:09
dobeyyeesh :P18:09
dobeybfiller: string freeze is feature freeze18:09
dobeybfiller: kind of pointless adding features if you can't add strings, eh? :)18:10
bfillerdobey: whatever dude18:10
bfillerdont' want to argue it with you right now18:10
dobeyheh, i'm not trying to argue18:10
kenvandineit's always been  a problem having string freeze before feature freeze... is backwards18:11
kenvandinelooking back at Pat's email, it actually didn't mention feature freeze at all18:11
kenvandinebut when i read it was thinking feature freeze18:12
kenvandinetvoss, think we can land fingerprint tomorrow?18:12
rvrkenvandine: A workaround would be to extract the new strings, and put them in a mock qml file or similar18:20
rvrand remove that file when the real code lands18:21
rvrI'll have to go now18:21
kenvandinervr, well if string freeze and feature freeze are the same, there's no point18:21
kenvandinethanks rvr18:21
rvrkenvandine: Right, that's what I was thinking. Idea in case you are granted a FFE.18:22
kenvandinei hate rushing translators18:22
dobeywell, if you know what the strings will be, before the feature is ready, that can work18:33
dobeybut if you don't, obviously not an option :)18:33
tvosskenvandine, think so, I think we can also iterate on rc-proposed18:46
bzoltandavmor2: I have seen your comment about the UITK silo19:21
bzoltandavmor2:  i just want to make sure that you do understand what that change is about.19:21
davmor2bzoltan: 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 think19:22
davmor2but I need to clear off now so I'll pick it up tomorrow morning when the telegram dev is online too19:23
davmor2bzoltan: hope that makes sense :)19:24
bzoltandavmor2: We have talked to the telegram devs, and there was a discussion about the topic - https://lists.launchpad.net/ubuntu-phone/msg20703.html19:24
bzoltandavmor2:  It is not a random, ad-hoc change, but a part of an orchestrated rollut and communication.19:25
bzoltandavmor2:  we have sent that mail, talked to lots of developers f2f, we have sent patches to apps19:25
bzoltandavmor2: 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:27
bzoltandavmor2:  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
bzoltandavmor2: if somebody needs any information about it me, t1mp and zsombi are here to help.19:28
bzoltandavmor2:  so, design has nothing to do with it... it is not a visual what we will see in real life :)19:29
mterryjibel, 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 testing19:39
mterryCould it be put into the QA queue even though it's not "ready"19:40
mterry?19:40
dobeykenvandine, 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
mterryk20:47
mterrydobey, done20:47
dobeymterry: thanks20:47

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!