[01:26] <alecu> damn
[01:36] <slangasek> plars: https://code.launchpad.net/~vorlon/ubuntu-test-cases/better-whoopsie-testing/+merge/229152 for you :)
[05:33] <bzoltan> trainguard is anybody around?
[05:33] <bzoltan> trainguards ^
[06:01] <camako> trainguards, we have found and fixed debian/control problems (see conv. bw robru and kgunn). Would you please clean up any remaining artifacts from silo landing-009 to prevent accidental pickups of binaries from previous builds?
[06:54] <bzoltan> sil2100:  good morning. The UITK is good to go in the silo20. All tests passed except the media player what fails on the CI testbed too. There were flaky tests that failed at some point but gave OK results after re-run http://paste.ubuntu.com/7920791/
[07:05] <tvoss> good morning :)
[07:05] <tvoss> Saviq, around?
[07:07] <tvoss> sil2100, ping
[07:11] <tvoss> ogra_, around?
[07:24] <bzoltan> sil2100:  sorry, I lost the connection. have you seen my line?
[07:25] <thostr_> sil2100: can I get silos for line 28 and 29
[07:31] <sil2100> o/
[07:32] <tvoss> sil2100, what is the new way of running sudo commands when using phablet-shell?
[07:33]  * bzoltan is listening too
[07:38] <sil2100> tvoss: hm, I think I cannot help you, I'm not a phablet-shell user ;)
[07:38] <sil2100> bzoltan: will publish in a moment o/
[07:38] <tvoss> ogra_, ^
[07:38] <ogra_> tvoss, whats not working ?
[07:38] <pete-woods> trainguards: good morning! any chance of a silo for line 29?
[07:38] <bzoltan> sil2100: thanks
[07:39] <sil2100> thostr_: line 28 has unity8 which I guess is already locked, did you coordinate with the other people that have it?
[07:40] <ogra_> tvoss, ah, phablet-shell is solely an interactive shell ... use adb for scripted stuff
[07:40] <tvoss> ogra_, I don't want to script :)
[07:40] <thostr_> sil2100: yes, we talked to saviq. want to build this and give it a test then deciding on the order
[07:40] <sil2100> thostr_: excellent
[07:40] <ogra_> tvoss, then i dont get the issue i fear, whats your problem
[07:41] <sil2100> pete-woods: silo coming right up
[07:41] <bzoltan> ogra_: and how to do sudo in the new "only phablet" adb world?
[07:41] <pete-woods> sil2100: thanks :)
[07:41] <tvoss> ogra_, okay, a reflash fixed things ...
[07:41] <Saviq> thostr_, sil2100, it's safe to release unity8 yeah, we still need a few tweaks in our silo
[07:42] <ogra_> bzoltan, "sudo <command>" ... sudo works as it always did
[07:42] <tvoss> ogra_, not after a manual upgrade, it keeps on asking for the password
[07:42] <bzoltan> ogra_: I mean behind a shell script what is behind the IDE
[07:42] <bzoltan> ogra_:  where the user cannot type password
[07:44] <sil2100> alex-abreu: hi! Not sure if you're still around, but we would need the 2 merges from silo 11 to be approved before publishing
[07:44] <ogra_> bzoltan, over time we should make all functions you need in the IDE available via i.e. dbus for the user ... for the start you can use something like: adb shell "echo $password|sudo -S <command>" .... you will need to ask for the phone password once and store it somewhere safely
[07:44] <Saviq> thostr_, the "default visible fix..." I merged yesterday
[07:45] <thostr_> Saviq: ok, then I'll remove that one from silo
[07:45] <ogra_> tvoss, dont do manual upgrades then :)
[07:45] <ogra_> tvoss, did you ever change the password ?
[07:47] <tvoss> ogra_, nope
[07:49] <ogra_> tvoss, well, i guess the manual update screwed up your /etc/passwd vs /var/lib/extrausers/passwd setup ... check if there is a phablet user in both ... if so, boot to recovery, mount the ubuntu.img and removing it ... would be the only solution i see
[07:50] <ogra_> s/removing/remove/
[07:54] <bzoltan> ogra_: I am not sure if storing passwords and passing plain text passwords to shell script is a secure  solution.
[07:55] <bzoltan> ogra_: anyhow. We use adb and we have few commands that we use the # adb.  Is there a way I can test a new phablet only adb image? I hope the new phablet only adb image will not be just pushed out without taking the SDK in consideration. Disabling root adb will do break the SDK.
[07:55] <ogra_> bzoltan, well, feel free to come up with something better ... long term i think providing a dbus api is fine until thats there we need a solution
[07:56] <bzoltan> ogra_: not changing the adb connctivity before the SDK is adopted to a new modell is something I suggest.
[07:56] <ogra_> bzoltan, see my mail (from 3 weeks ago or so) anout developer mode, there is a deb you can test
[07:57] <ogra_> i know plars tested it in the lab ... he solved the sudo issue by putting an open /etc/sudoers in place though :)
[07:57] <bzoltan> ogra_: OK, I will test. But please do not change before the SDK is fixed for the new way
[07:57] <ogra_> bzoltan, well, before RTM ... this dev mode setup is a management req.
[07:58] <bzoltan> ogra_: obviously, turning the device sudoless is a solution :) but is that what we want for _All_ devices used by app developers?
[07:58] <bzoltan> ogra_:  SDK is a management req too
[07:59] <bzoltan> ogra_: All I am asking is to please do not break the SDK with a change what we have not adopted our tools.
[07:59] <ogra_> bzoltan, i wont forget you, no worries
[08:01] <sil2100> bzoltan: so, looking at the list of flaky tests during UITK... there's a lot of different flaky tests marked, are they running fine after a re-run?
[08:08] <Saviq> thostr_, fyi, added commit message and kicked a build on your silo, it failed before
[08:08] <thostr_> Saviq: thanks
[08:12] <dpm> hi all, could someone trigger the Jenkins autolanding job for https://code.launchpad.net/~dpm/ubuntu-calendar-app/i18n-improvements/+merge/228938 ? I don't quite understand why they didn't run as usual, though
[08:14] <seb128> dpm, we don't have autolanding anymore, we have CI landing manually driven
[08:15] <dpm> hm, then this changed since yesterday for core apps
[08:15] <seb128> dpm, ignore me then
[08:15]  * dpm hugs seb128
[08:16] <seb128> dpm, I though we disabled autolanding for everything in trusty
[08:16] <seb128> but I'm wrong if that was working yesterday
[08:19] <sil2100> seb128: I guess most core click apps have autolanding enabled, as they're not driven by the train
[08:21] <seb128> sil2100, back then we got forced to move everything because we were told that CI didn't want to maintain the old infra to do autolandings
[08:21] <seb128> weird
[08:23] <popey_> core apps clicks aren't in the archive, thats probably the difference
[08:25]  * sil2100 doesn't like the current smoketesting results 
[08:30] <jibel> psivaa, hey, automated tests of precise-alternate 20140731 are failing with
[08:30] <jibel> Jul 31 08:54:29 in-target: The following packages have unmet dependencies:
[08:30] <jibel> Jul 31 08:54:29 in-target:  libgl1-mesa-dri-lts-trusty : Conflicts: libgl1-mesa-dri
[08:30] <jibel> psivaa, can you look at it please?
[08:31] <psivaa> jibel: sure, i'll take a  look at them in a little bit, after the landing meeting
[08:31] <jibel> psivaa, thanks
[08:33] <jibel> psivaa, also LAMP tests are failing on server
[08:55] <popey> sil2100: https://bugs.launchpad.net/music-app/+bug/1350636
[08:55] <sil2100> popey: thanks
[08:56] <popey> sil2100: https://bugs.launchpad.net/reminders-app/+bug/1351041
[08:56] <sil2100> popey: do you also have a bug for the pin-locking by any chance? ;)
[08:58] <psivaa> brendand: sorry, missed it earlier:
[08:58] <psivaa> adb reboot bootloader
[08:58] <psivaa> + ubuntu-device-flash --bootstrap --developer-mode --channel ubuntu-touch/devel-proposed
[08:58] <psivaa> 2014/08/01 01:31:07 Expecting the device to be in the bootloader... waiting
[08:58] <psivaa> Build was aborted
[08:59] <psivaa> so adb reboot bootloader is being called before ubuntu-device-flash
[08:59] <ogra_> but not working it seems
[08:59] <brendand> psivaa, but it's not checking the result
[08:59] <brendand> psivaa, or confirming the device is in the right state
[08:59] <ogra_> well, ubuntu-device-flash checks the result
[09:00] <brendand> ogra_, :)
[09:01] <brendand> actually i was wrong. adb devices does not list it in fastboot mode
[09:02] <ogra_> yeah, it is: fastboot devices
[09:02] <ogra_> or so
[09:02] <psivaa> so adb devices should not list that particular device, right?
[09:02] <ogra_> so call that in a loop with a timer
[09:02] <ogra_> once timed out send another adb reboot bootloader
[09:02] <ogra_> or some such
[09:03] <psivaa> yep, will do that. thanks
[09:06] <bzoltan> sil2100:  how is the UITK publishing?
[09:12] <pete-woods> cihelp: what's the normal process for taking a silo from "ready" to starting the landing? is it my job to ping one of you guys, or should I just be more patient? ;)
[09:15] <psivaa> pete-woods: i think you need 'trainguards' instead of ci-help for this
[09:16] <pete-woods> psivaa: thanks! (still new to the train) I guess that pinged them for me :)
[09:16] <sil2100> bzoltan: will publish it soon, just asked davmor2 to do a quick dogfood run with the silo :) Just to make sure ;)
[09:16] <sil2100> pete-woods: hi! Normally we're pinged by the bot, but I was in a meeting just now so couldn't react
[09:16] <sil2100> :)
[09:17] <pete-woods> sil2100: okay, cool, that's good to know :)
[09:19] <ricmm> sil2100: good morning! I added something to line 38 that needs a silo, to unblock android builds which are broken, any chance I could get a silo? thx
[09:21] <sil2100> ricmm: sure, we're lowish on silos but I guess this is a rather priority landing
[09:22] <bzoltan> sil2100: Cool. If davmor2 would tell me what he is testing and how I could use that in my test plan.
[09:23] <sil2100> ricmm: just make sure to ping camako or kgunn when you land papi, as they need to rebuild then
[09:23] <bzoltan> sil2100: davmor2: is the UITK  in a detention :) ?
[09:23] <bzoltan> davmor2:  when are you going to do the UITK validation and how long it will take?
[09:25] <davmor2> bzoltan: as soon as possible just looking through my email first to see if there is anything important there.  It'll take roughly an hour and it just testing I can do everything with the phone that I could do before
[09:34] <davmor2> sil2100: right nothing more important in my email which silo is it please?
[09:40] <bzoltan1> davmor2: what exactly are you going to test and how?
[09:41] <davmor2> bzoltan1: standard dogfood less some of the adventurous bits.  Basically use the phone as a phone, use it as a device for internet consumption and then try and break it
[09:41] <bzoltan1> sil2100: I sense some trust issue here :) If there is something what a random dogfooding can pop out than my test plan is not good, or the test tools are not reliable. I have run 3 times 4 hours of tests with  hundreds of tests.
[09:43] <bzoltan1> sil2100: davmor2: do you do it for all landings or only for the UITK. Just because it takes awful long time to get the UITK landed after I have run all the tests.
[09:43] <psivaa> jibel: so, the alternate failure of unmet deps is a real bug. isn't it? similar to https://bugs.launchpad.net/ubuntu/+source/xorg-lts-raring/+bug/1191563
[09:44] <bzoltan1> davmor2:  even from now it will take hours before you say OK, and then we need an ack from somebody who checks teh debian changes an dthe hours in the proposed pocket
[09:44] <jibel> psivaa, yes, I think it's a real bug with lts-trusty graphics stack
[09:45] <davmor2> bzoltan1: only an hour ish  and it's only to see if there is something missing from the test the likelihood is everything will be fine
[09:45] <psivaa> jibel: and for precise lamp on server needs a small change in the test code, similar to: http://bazaar.launchpad.net/~ubuntu-server-dev/ubuntu-test-cases/server-tests-raring/revision/95
[09:46] <davmor2> bzoltan1: but because it touches everything kinda like unity8 we like to double check is all
[09:46] <jibel> psivaa, okay, when do you think you'll have time to do the change?
[09:46] <bzoltan1> davmor2: that is exactly why I run _ALL_ available autopilot tests... more than the CI dash shows
[09:46] <psivaa> jibel: i'll make the MP shortly. i think it needs approval from jamespage
[09:47] <jibel> psivaa, great, thanks! can you file another bug for alternate and subscribe me please
[09:47] <psivaa> jibel: ack, will do that too :)
[09:48] <davmor2> bzoltan1: which is why there will almost certainly be no issues that don't already exist, but the tests that are there don't cover everything, so like you can't be sure a call can be heard just that it makes a noise etc
[09:48] <bzoltan1> davmor2:  what are the use cases what tests do not cover?
[09:51] <davmor2> bzoltan1: there are lots, it's more that the tests are fairly basic good paths so don't really check for apps be used incorrectly, there are things like making a call can you actually hear and be heard, System settings app need to intograte with other apps in order to know that the change you made works etc
[09:52] <davmor2> bzoltan1: so changing the keyboard layout you open messaging and ensure that the keyboard layout has changed etc
[09:53] <bzoltan1> davmor2:  but these use cases has nothing to do with the UITK
[09:53] <bzoltan1> davmor2: why to slow down the already very slow releasing process of the UITK?
[09:54] <davmor2> bzoltan1: because I was asked to
[09:54] <bzoltan1> davmor2: that explains :)
[09:54] <pete-woods> sil2100: in-case you haven't got round to it yet, the packaging changes in silo 16 are simply the addition of boost-regex as a build-dep
[09:55] <davmor2> 165 oh holy crap twitter just exploded my messaging indicator
[09:56] <bzoltan1> davmor2: how do you secure that you dogfood on the same image as I was testing (24-8 hours ago) the release candidate?
[09:56] <davmor2> bzoltan1: I test on the current image as that is basically what your landing will be added to
[09:57] <bzoltan1> davmor2:  and if you see any abnormal behavior how do you make sure that it is caused by the UITK and not by something what was landed after I have finished my tests?
[09:57] <davmor2> bzoltan1: by digging, seeing if it exists on the image without your silo added to it etc
[09:58] <davmor2> bzoltan1: but to be honest it's going to take longer if I keep talking to you ;)  Let me get back to you in 60 minutes with good news,  well at least so far so good :)
[09:58] <bzoltan1> davmor2: poor you ... sounds super manual and super slow
[09:59] <bzoltan1> davmor2: :) OK, I let you do your job
[09:59] <davmor2> bzoltan1: it is however what I'm paid for and what I do well
[10:00] <bzoltan1> davmor2: :) All right, ping me if you find something.
[10:04] <davmor2> bzoltan1: I like the new drop down for selecting from a list :)
[10:04] <bzoltan1> davmor2: it is cool is not it :)
[10:06] <psivaa> jibel: https://code.launchpad.net/~ubuntu-server-iso-testing-dev/+junk/server-tests-precise is being a junk branch, i've created another junk with these changes
[10:06] <psivaa> http://bazaar.launchpad.net/~psivaa/+junk/precise-lamp-test-fixes/revision/271
[10:07] <popey> davmor2: you know the "notification sound goes on for ever"? I think its because there's an invisible (or poorly stacked) snap decision. I just tapped in the area where the snap decision would be and it stopped the sound.
[10:13] <sil2100> davmor2: so, is it a +1?
[10:13] <sil2100> ;)
[10:13] <sil2100> My finger itches, I want to press publish for that job
[10:14] <popey> davmor2: run sudoku on latest phone it's wedged at the splash screen
[10:14] <davmor2> sil2100: so far so good still going though about 11:45 my time
[10:15] <davmor2> popey: works here
[10:16]  * popey reboots
[10:16] <davmor2> sil2100: ^ this might be a race that might be causing tests to fail
[10:16] <davmor2> brendand: ^
[10:16] <davmor2> bzoltan1: did you change the height of the header text?
[10:17] <bzoltan1> davmor2: yes
[10:17] <sil2100> Sudoku MUST work! That's like the most used Ubuntu Touch application by me!
[10:18] <bzoltan1> sil2100: +1
[10:18] <popey> sil2100: any idea why https://code.launchpad.net/~dpm/ubuntu-calendar-app/i18n-improvements/+merge/228938 isn't merging?
[10:18] <davmor2> bzoltan1: okay so that explains the headers looking weird then :)
[10:19] <davmor2> sil2100: more import sabdfl uses it ;)
[10:19] <popey> davmor2: after reboot it works this time, will try with lots of webapps open (as I had that before when it failed to start)
[10:19] <bzoltan1> davmor2: in the changelog - * Reduce header height by 0.5 grid units.
[10:19] <sil2100> popey: I see that the mediumtests are still running for this branch... running for over 14 hours!
[10:20] <davmor2> bzoltan1: nice the only issue now is you still get the same size header which makes it look like a lot of wasted space
[10:20] <sil2100> cihelp: ok, from what I see the currently running mediumtest is in some infinite loop
[10:21] <Saviq> sil2100, hey, could you please upload https://code.launchpad.net/~unity-team/kubuntu-packaging/qtdeclarative-fix-1349705/+merge/229183 to silo 7, I'm adding it as a src to the line now
[10:21] <sil2100> cihelp: could anyone abort http://91.189.93.70:8080/job/ubuntu-calendar-app-ci/669/console ? It's blocking everything right now, especially the merge of ubuntu-calendar-app
[10:21] <bzoltan1> davmor2:  these visual bits come from the design team. We are just the carpenters here :)
[10:21] <sil2100> Saviq: sure, let me make a src pacakge
[10:27] <vila> sil2100: done
[10:28] <sil2100> Saviq: ok, reconfigured and package uploaded
[10:28] <sil2100> vila: thanks!
[10:28] <sil2100> vila: I wonder what was causing the test to loop into infinity...
[10:29] <vila> sil2100: I won't say I understand why it happened though :-/
[10:29] <sil2100> popey: so, the autolanding failed for the merge as you can see, the mediumtests went into an infinite loop and had to be aborted
[10:29] <vila> sil2100: where do you see an infinite loop ?
[10:29] <popey> vila: is it possible for someone to trigger the jenkins tests on https://code.launchpad.net/~g-bluehut/ubuntu-terminal-app/whitespacefix/+merge/228807 - new contributor not on the team, so it doesn't happen automatically
[10:30] <vila> popey: can't you ?
[10:30] <sil2100> vila: didn't, as I couldn't get to any logs, but it was running for 14 hours already...
[10:30] <sil2100> vila: so it's not something that can happen without looping into infinity ;)
[10:31] <popey> vila: how?
[10:31] <vila> sil2100: the bottom job seem to be http://91.189.93.70:8080/job/generic-mediumtests-utopic/1241/console and it was stuck at the 'Archiving artifacts' AFICT
[10:31] <popey> there's no link to trigger it
[10:31] <Saviq> sil2100, a local build yields http://pastebin.ubuntu.com/7922748/ though, but it doesn't make much sense, any idea?
[10:31] <vila> popey: gha, misread the link as a jenkins one
[10:32] <psivaa> jibel: https://bugs.launchpad.net/ubuntu/+source/xorg-lts-transitional/+bug/1351262 is the bug for the unmet deps issue with alternate images.
[10:32] <vila> popey: isn't there a whitelist to update somewhere ?
[10:32] <vila> psivaa: do you know ^
[10:32] <vila> ?
[10:35] <psivaa> vila: https://wiki.canonical.com/UbuntuEngineering/CI/Playbook/UpstreamMerger#Specific_merge_proposals_are_not_being_triggered is the part to be done i think
[10:42] <davmor2> bzoltan1, sil2100: okay I've been through most stuff I see nothing more broken than on the current image.  I would however like to go on record as saying that the header text now makes the headers look wrong as it looks off center etc.  But I guess the next job from design will be to reduce it's size so I won't write a bug on it till we know what is happening
[10:42] <psivaa> popey: vila: g-bluehut is added to the allowed users there. so the ci job should trigger soon
[10:44] <popey> thanks
[10:45] <davmor2> popey: oh the apparmor denial for reminders I filed as a separate bug incase they are note related and then link the apparmor issue to the no notes bug in case they were related :)
[10:45] <davmor2> s/note/not
[10:45] <davmor2> I don't think it matter
[10:45] <davmor2> sil2100: land bzoltan1 uitk stuff already ;)
[10:46] <vila> psivaa: you rock !
[10:46] <psivaa> :)
[10:47] <Saviq> sil2100, ohkay... I expect a build failure (due to the switch to default 4.9) of the qtdeclarative package...
[10:47] <Saviq> sil2100, how do we deal with that? I'd propose to force down to 4.8, and do a whole-sale transition of Qt to 4.9 later
[10:49] <sil2100> davmor2: \o/
[10:49] <davmor2> bzoltan1, sil2100 ah wait might of found an issue.
[10:49] <sil2100> Saviq: oh, so it will FTBFS with 4.9?
[10:49] <Saviq> sil2100, http://pastebin.ubuntu.com/7922748/
[10:49] <Saviq> sil2100, just symbols changes, but I wouldn't do a single-package transition to 4.9...
[10:52] <sil2100> Saviq: yeah, so let me for now try and force 4.8 for it still in packaging, it should be enough for a temporary solution
[10:52] <davmor2> bzoltan1, sil2100: no the issue is in the current image with no silo so we are safe and possibly one of the causes for the calendar failures
[10:52] <sil2100> Saviq: Mirv will handle the real thing next week when he's back
[10:52] <sil2100> davmor2: oh?
[10:52] <sil2100> davmor2: what's up?
[10:52] <bzoltan1> davmor2:  dude... are you a cardiologist or what? If not then do not do it again please :D
[10:53] <Saviq> sil2100, yup, will do
[10:53] <davmor2> sil2100: create an appointment click on the time or the date and you should see the date time wheels popup they don't
[10:54] <Saviq> sil2100, same branch do you think or separate MP for correctness?
[10:55] <davmor2> bzoltan1: I did say might of, I then needed to go off and confirm if it was or not :)
[10:56] <sil2100> Saviq: so, let's use this same branch but mention it in the changelog - btw. you forgot to update the changelog earlier as well ;)
[10:56] <sil2100> (in the changelog and commit-log)
[10:57] <Saviq> sil2100, ah oups, always forget that when not using MPs
[10:57] <sil2100> Yeah, happens, but I guess Timo is releasing those directly or as src packages
[11:19]  * sil2100 off to lunch
[11:56] <Saviq> sil2100, it builds with 4.8 now, can you push to the PPA again?
[12:07] <popey> davmor2: or ogra_ if you have a proposed device can you try and reproduce bug 1351057 ?
[12:08] <ogra_> popey, hmm, no issue here ... but i'm not on mako
[12:08] <ogra_> (163)
[12:09] <popey> understood
[12:10] <ogra_> heh, shorts didnt change since i looked at it last
[12:10]  * ogra_ stopped using it when it dropped planet)
[12:13] <davmor2> popey: it's broken if you open it twice
[12:14] <davmor2> ogra_: open shorts twice
[12:14] <ogra_> davmor2, aha !
[12:14] <ogra_> popey, confirmed
[12:14] <popey> aha!
[12:14] <popey> thanks
[12:27] <popey> sil2100: bug 1351057 - shorts broke between 157 and 162...
[12:35] <brendand> sil2100, one of the failures in calendar is reproducible locally. filing a bug
[12:36] <brendand> sil2100, actually i just need to check if it could be apparmor related
[12:36] <sil2100> popey: hm, good to know, let's add that to our issue list
[12:36] <sil2100> brendand: thanks!
[12:58] <Saviq> sil2100, bump, can you please upload qtdeclarative to the PPA again? should build fine now
[13:02] <sil2100> Saviq: ok, doing a bzr pull and generating the source package now
[13:08] <Saviq> sil2100, might need to bump ubuntu8 though
[13:09] <sil2100> Saviq: bump?
[13:10] <Saviq> sil2100, changelog
[13:10] <sil2100> 0ubuntu8 is fine ;)
[13:11] <Saviq> sil2100, ok, thought it got bumped before
[13:11] <sil2100> Saviq: no no, I didn't notice that it didn't have a changelog bump, so the version in the PPA was anyway invalid
[13:13] <jibel> davmor2, popey can you confirm bug 1351308 ? it's a regression, I don't know in which build
[13:15] <davmor2> jibel: works here
[13:17] <jibel> davmor2, yes, but the language in front of "Display Language" is it written Français or English, and after a reboot is every thing in French ?
[13:17]  * jibel tries to convert the world to French lets start by davmor2
[13:18] <davmor2> jibel: I can't talk English I'm not about to start with French :P
[13:18] <popey> jibel: works in #157
[13:19]  * popey tries on proposed phone
[13:20]  * davmor2 confirms jibels bug
[13:21] <jibel> davmor2, thank you
[13:21] <davmor2> it seems to change initially and then flip back and only the language page stay it French
[13:22] <jibel> sil2100, FYI bug 1351308 is a recent regression if you have a list somewhere to keep track of them
[13:25] <Saviq> fginther, hey, the qmluitests job still doesn't seem to have picked up all the xml files...
[13:26] <Saviq> fginther, CardCreatorTest.xml still isn't included in the result
[13:26] <cyphermox> kenvandine: do you know who is working on fixing Silo 6.
[13:26] <cyphermox> ?
[13:26] <kenvandine> me
[13:26] <kenvandine> well, not sure about the build failure for gsettings-qt
[13:26] <cyphermox> Cool :-)
[13:27] <kenvandine> i'm working on the autopilot tests for settings :)
[13:27] <cyphermox> That's what I meant
[13:27] <cyphermox> Who should look at gsettings-qt?
[13:27] <davmor2> popey: the pdf app doesn't work if you open a pdf link in the browser it says no application to open it
[13:28] <kenvandine> seb128, did you see that gsettings-qt is failing for ppc64el?
[13:28] <kenvandine> not sure if it built before, i haven't looked yet
[13:28] <dednick> fginther: hey. ubuntu-settings-components is failing ci. missing xvfb-run is missing (new addition to test procedure). http://s-jenkins.ubuntu-ci:8080/job/ubuntu-settings-components-ci/69/
[13:29] <davmor2> popey: not sure if that is download manage that might need a similar patch as is in for content hub or what
[13:29] <popey> davmor2: thats not surprising
[13:29] <pmcgowan> kenvandine, I think he stepped away, jonas had started looking at it
[13:29] <popey> yes, u-d-m would need patching
[13:29] <kenvandine> pmcgowan, cool
[13:30] <pmcgowan> not sure he got anywhere
[13:31] <davmor2> popey: i'm going to try it by transferring the file across
[13:31] <pmcgowan> kenvandine, here he is now
[13:31] <popey> thats what I did, drag and drop pdf's to ~/Documents
[13:31] <pmcgowan> kenvandine, did it only fail on one arch?
[13:31] <kenvandine> yeah
[13:32] <davmor2> popey: also drag down the transfer indicator do you see anything actually listed there?
[13:33] <popey> no, blanks, know bug
[13:33] <popey> davmor2: bug 1350308
[13:35] <davmor2> popey: ta
[13:35] <popey> np
[13:38] <brendand> sil2100, the test is failing because it's august :)
[13:40] <sil2100> brendand: what, really..? ;p
[13:41] <davmor2> sil2100: can you add jibel's language bug to the blocker list please, if popey is correct it isn't in devel but is in devel-proposed so something broked it  https://launchpad.net/bugs/1351308
[13:41] <sil2100> davmor2: sure
[13:41]  * sil2100 sighs
[13:41] <sil2100> ;)
[13:41] <davmor2> sil2100: p.s. you'll note me and popey didn't break it as you requested :P
[13:42] <brendand> sil2100, yeah. the test doesn't scroll the view so it can only see the first seven months
[13:42] <ogra_> davmor2, oh, you mean bug 1240875 ?
[13:43] <ogra_> :P
[13:43] <davmor2> ogra_: yeah but I only care about jibel he's on my team :P
[13:43] <ogra_> lol
[13:43] <ogra_> the QA cabbal
[13:44] <popey> Zut Alors! Mon téléphone est maintenant en français
[13:45] <davmor2> popey: shhhh that jibel will think his evil plot to make people speak French is working
[13:45] <popey> why is English capitalised by espanol not?
[13:45] <sil2100> ;)
[13:45] <Laney> https://www.google.co.uk/search?client=ubuntu&channel=fs&q=spanish+in+spanish&ie=utf-8&oe=utf-8&gfe_rd=cr&ei=BZrbU_XZIO3H8ge4i4LYBQ
[13:45] <davmor2> popey: because English is the bestest \o/
[13:46] <Laney> ;-)
[13:46] <popey> fancy that
[13:46] <Laney> this is a better link http://www.spanishdict.com/translate/spanish
[13:46] <brendand> sil2100, here's the bug: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1351319
[13:57] <ogra_> sil2100, any images on the horizon ?
[13:59] <sil2100> ogra_: right! I'll kick one now, as UITK seems to be in the archives since a while now
[13:59] <camako> Vanguard, can I get help on silo 9? I'm getting weird packaging errors building qtmir. Is it possible to remove/clean any traces of previous builds of qtmir only, without disturbing other successfully built packages? Or do we have to clean the whole silo?
[13:59] <ogra_> cool
[13:59] <sil2100> brendand: ok, I'll add it to the AP issues in our mail ;)
[14:00] <ogra_> i'd like to have the lxc-android-config changes :)
[14:00] <sil2100> jhodapp: hi! Who's responsible for mediascanner? ;)
[14:00] <davmor2> tvoss: silo 008 seems happy, here and google maps, have both found me so that is a +1 from me :)
[14:00] <tvoss> davmor2, ack and thx
[14:00] <sil2100> jhodapp: do you know?
[14:00] <jhodapp> sil2100, hey, yes
[14:01] <jhodapp> sil2100, Satoris and jamesh
[14:01] <sil2100> jhodapp: thank you o/
[14:01] <jhodapp> np
[14:03] <camako> sil2100, can I get help on silo 9? I'm getting weird packaging errors building qtmir. Is it possible to remove/clean any traces of previous builds of qtmir only, without disturbing other successfully built packages? Or do we have to clean the whole silo?
[14:04] <sil2100> camako: hm, you can just try rebuilding qtmir, CI Train generally starts rebuilds cleanly without reuising the existing tree
[14:06] <camako> sil2100.. I see.. Will try again..
[14:09] <imgbot> [14:45] <seb128> kenvandine, yes, symbols issue it seems, dunno why
[14:57] <bzoltan> rsalveti:  would you please push the rev141 of the QtCreator to the archive (http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtcreator/revision/141) we have a super important fix pending on this change.
[15:09] <bzoltan> seb128:  could you help me with the qtcreator release? I do not think it takes more than a bzr branch, debuild and dput. We need this change in archive (http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtcreator/revision/141) as we have a super important fix pending on this change.
[15:12] <pmcgowan> kenvandine, you sort something out?
[15:13] <kenvandine> pmcgowan, for the autopilot tests yes...
[15:13] <kenvandine> haven't looked at gsettings-qt yet
[15:14] <kenvandine> pmcgowan, i wanted to get the silo rebuilt so we can get some testing while we sort out the build failure on that one arch
[15:14] <pmcgowan> kenvandine, makes sense, remind me why do we need that? seems it hasnt changed in weeks
[15:15] <kenvandine> no idea :)
[15:15] <pmcgowan> jgdx, why do we need gsettings-qt? I dont see any code changes
[15:15] <pmcgowan> let me see what branch it is
[15:15] <kenvandine> oh that
[15:16] <kenvandine> we need that to fix a bug, required for the sim-naming
[15:16] <sergiusens> rsalveti: ^ mind looking at packaging ack?
[15:16] <kenvandine> i thought you asked why we needed that arch :)
[15:16] <seb128> bzoltan, sorry, can't, leaving for china in 45 minutes
[15:16] <pmcgowan> kenvandine, ah ok
[15:17] <bzoltan> seb128: have a good trip :)
[15:17] <seb128> bzoltan, thanks
[15:19] <kenvandine> seb128, weird, the new symbols larsu added are MISSING on ppc64el
[15:19] <kenvandine> i know nothing about that arch, is it common to have symbol issues like this?
[15:20] <jgdx> pmcgowan, there's a completely new schema, com.ubuntu.phone, which holds default for calls/messages as well as sim names.
[15:21] <seb128> kenvandine, not that I know, are the symbols missing or having a different signature?
[15:21] <jgdx> pmcgowan, gsettings-qt cannot currently read the sim names value. The new gsettings-qt can. :)
[15:21] <kenvandine> oh right... signature :/
[15:23] <kenvandine> seb128, no... looks like the signature is the same to me
[15:24] <kenvandine> https://launchpadlibrarian.net/181287698/buildlog_ubuntu-utopic-ppc64el.gsettings-qt_0.1%2B14.10.20140801-0ubuntu1_FAILEDTOBUILD.txt.gz
[15:25] <seb128> kenvandine, weird
[15:36] <pete-woods> trainguards: hi! any chance of a silo for line 39 of the landing sheet?
[15:37] <sil2100> pete-woods: hello! It was not set to ready, so we could not assign :)
[15:37] <pete-woods> sil2100: that's fine, I only just set it to ready :)
[15:38] <sil2100> My spreadsheet is a bit out of date then :) !
[15:38] <pete-woods> ahh!
[15:38] <pete-woods> I set someone else's lime
[15:39] <pete-woods> :$
[15:39] <kenvandine> seb128, am i completely nuts...
[15:39] <kenvandine> it looks like the branch we are trying to land adds some duplicates
[15:39] <sil2100> ;p
[15:39] <imgbot> [15:39] <imgbot> [15:39] <kenvandine> https://code.launchpad.net/~larsu/gsettings-qt/lp1349787/+merge/228841
[15:41] <pete-woods> sil2100: thanks!
[15:41] <sil2100> pete-woods: so, unity-scope-click is already locked by alecu's silo 12
[15:42] <pete-woods> sil2100: yes, you're right, and also another silo for unity-scopes-shell
[15:42] <pete-woods> boo :(
[15:43] <sil2100> pete-woods: you can poke those people and if you coordinate with them, I can assign you with an override ;)
[15:43] <sil2100> But you'll first have to contact them
[15:43] <pete-woods> sure
[15:43] <sil2100> And give me a sign if they're ok with it and coordinating, making sure you rebuild whenever anyone of you releases
[15:48] <davmor2> popey: has your proposed phone pinged you to tell you there is an image yet?
[15:49] <popey> davmor2: no, i beat it to it
[15:49] <davmor2> Chipaca: ^ my phone hasn't pinged me about the last few images should it of done?
[15:50] <popey> my nexus 7 hasn't been pinged
[15:52] <pete-woods> sil2100: can I get a silo just for testing purposes, without the intent to land it immediately?
[15:52] <sil2100> pete-woods: ok, let's just mark it
[15:52] <alecu> pete-woods: I'm testing the click scope right now, will ask for that silo to be landed in a few minutes if all goes ok.
[15:52] <pete-woods> alecu: oh, cool
[15:53] <alecu> pete-woods: what click scope branch do you need to land?
[15:53] <pete-woods> alecu: it's part of the ABI break of unity-scopes-api: https://code.launchpad.net/~unity-api-team/unity-scope-click/scopes-0.6.0/+merge/229245
[15:54] <pete-woods> nothing exciting, but I want to happen sooner rather than later
[15:54] <kenvandine> sil2100, since you're the c++ symbols expert, could you look at the ppc64el symbol issue in silo 6 for me?
[15:55] <pete-woods> :D
[15:55] <sil2100> kenvandine: hah, I'm far from an expert, but let me take a look at it ;p
[15:55] <alecu> pete-woods: please ping me as soon as that lands, so I can merge it back to the click-scope /devel branch
[15:55] <kenvandine> sil2100, thx!
[15:55] <sil2100> ppc64el you say?
[15:55] <pete-woods> alecu: sure, will do
[15:55] <kenvandine> yeah, built on all the other arches
[15:56] <kenvandine> gsettings-qt
[15:56] <sil2100> Ok, I see it, let me dive in
[15:56] <pmcgowan> kenvandine, why didnt the MR build all the arches in jenkins?
[15:56] <kenvandine> pmcgowan, i don't think CI builds for all the same arches as ubuntu
[15:57] <sil2100> Yeah, I don't think there's ppc64el in the CI lab
[15:57] <alecu> sil2100: I've set silo-012 to "testing pass", so pete-woods should no longer need my override.
[15:59] <robru> sil2100, ah, I just saw your new unapproved-merges check for the first time, very nice!
[15:59] <sil2100> robru: glad you like it! I have one modification for that to do, but now I was busy fighting dogfood
[15:59] <bzoltan> robru:  may I get a silo for line41? It will be a quick one... I expect to release it still today
[16:00] <robru> bzoltan, sure
[16:01] <robru> bzoltan, ok, you got silo 20
[16:02] <bzoltan> robru: thank you
[16:02] <robru> bzoltan, you're welcome!
[16:07] <Chipaca> davmor2: it should've, but a bug in go-dbus and a bug in qt-mir conspired against it
[16:09] <popey> these gmail notifications are insane.. I have hundreds of them and can't make them stop, or click anything in the top part of the display
[16:09] <popey> http://popey.mooo.com/screenshots/device-2014-08-01-170939.png <- those
[16:10] <popey> http://popey.mooo.com/screenshots/device-2014-08-01-171024.png 6 months mail notifications
[16:47] <davmor2> popey: on your dev proposed device, tap the power button so it is sleeping, swipe from right to left on the blank screen then wake the phone
[16:48] <davmor2> popey: then play some music in the music app and do the same thing again
[16:49] <davmor2> popey: oh sorry blank it wait for a second or you swipe the app to from right to left
[16:51] <davmor2> is music app still uncontained if so that might be the issue
[16:53] <davmor2> sil2100: ^ just to make you happy
[17:01] <robru> sil2100, oh, what happened in silo 5? did you ping anybody for the core dev ack?
[17:03] <kenvandine> oh sigh...
[17:04] <kenvandine> robru, how do i handle revisions in utopic that aren't in trunk?  manually prepare a branch and propose it too?
[17:04] <kenvandine> it was a no change rebuild a few weeks ago
[17:04] <robru> kenvandine, no change rebuilds you can just FORCE_BUILD and it'll steamroll over them. if there was actually a meaningful change, just push the diff to trunk
[17:04] <kenvandine> ok, i hate losing revisions :)
[17:04] <kenvandine> but the changelog says no change rebuild
[17:05] <robru> kenvandine, yeah, if you really care about preserving that changelog entry, just push it to trunk then.
[17:17] <sil2100> robru: hey! No, not yet - I guess we don't need a poke as it will stay in NEW anyway until the right person reviews it
[17:17] <sil2100> robru: I wanted to check the packaging first but didn't find the time in the end
[17:18] <robru> sil2100, I had reviewed that one already, but more eyes are better for sure
[17:18] <sil2100> Ah, then I guess it's safe to upload :)
[17:18] <robru> sil2100, ok, will do
[18:14] <ToyKeeper> Is it expected that images 165 and 166 no longer allow the user to close any apps?
[18:16] <ToyKeeper> (well, in 165 I could close apps, but the UX flow for it was very strange...  and it only worked when only one app was open)
[18:19] <barry> robru: can you remind me what the right buttons to push are if i've pushed an update to an mp that's already been built.  i want to rebuild from scratch.  build+ignore doesn't seem right, not sure if recon is the right thing either
[18:20] <barry> robru do i need to resubmit mp and then recon?
[18:20] <robru> barry, recon is only necessary if it's a new MP on a new source package.
[18:20] <robru> barry, don't resubmit the mp
[18:21] <barry> robru: ack.  it's just a new revision on the same mp
[18:21] <robru> barry, just build. if it complains about "prevent whole rebuild" or whatever then either put the source package name to rebuild, or pick FORCE_REUILD
[18:22] <barry> robru: ah, thanks.  somehow i thought that was just if you wanted a nochange rebuild
[18:23] <barry> robru: hmm. unhappy.  ^^ that was with FORCE_REBUILD.
[18:23] <robru> barry, yeah, INGORE_STEP tehn
[18:23] <barry> let see!
[18:24] <robru> barry, FORC_BUILD would only do a no-change rebuild if there were no new commits. it always grabs the latest commit
[18:24] <barry> robru: ack
[18:24] <robru> barry, I went through and updated the FAQ and NewbieGuide recently, might be worth rereading.
[18:25] <barry> robru: will do, thanks
[18:25] <robru> meant to merge them but found a big pile of stale info that needed correcting first ;-)
[18:28] <barry> robru: yeah, that doesn't seem right.  it built way too quickly.  i suspect maybe the problem is that the ppa can't be told to rebuild a package it already contains with a new revision keeping the same debian version number
[18:30] <robru> barry, this is because it's a native package. you need to bump the version to trigger a new build. what happened here is that the PPA rejected the upload because it already had that version, and then citrain said "oh look, that version is there and it built successfully!"
[18:30] <robru> barry, basically if you had gone with split packaging this would be fine.
[18:31] <robru> barry, or maybe not native per se, but whatever you did with the version number there. citrain didn't put in the usual +14.10.YYYYMMDD.x because you overrode it to be just 2.3.2
[18:31] <barry> robru: it's actually not a native package in the debian sense (this is just a source-full packaging branch), but i get what you're saying.  it makes sense.  somehow i thought citrain might be doing something magical with ppas :)
[18:32] <robru> barry, nope, they are totally standard PPAs. the magic of citrain is that it autogenerates version numbers, but you disabled that somehow, bad monkey!
[18:32] <barry> oo oo ah ah
[18:34] <robru> barry, looks like you need either 2.3.3 or 2.3.2.1 depending on how big the new commits were... or if you're really married to '2.3.2' then we have to flush you a silo and give you a new one because the PPA just won't accept a new orig tarball with different contents for that version.
[18:40] <robru> barry, hm, you did 0ubuntu2? but how can it have new commits if it uses the same old orig.tar? were the new commits only under debian/*?
[18:40] <barry> robru: 2.3.2-0ubuntu2 does the trick
[18:40] <barry> robru: yep.  typical debuntu package tricks :)
[18:40] <robru> barry, ah ok. I was thinking you had new commits in the actual source
[18:40] <barry> (i.e. upstream is unchanged, only packaging changes in new commit, so only debuntu version number bump needed)
[18:41] <barry> robru: right - if i did that i would have to be an upstream version number bump and new release
[18:41] <barry> robru: basically, i treat system-image just like any other package in the archive, for versioning and release purposes
[18:42] <robru> barry, except for all the other ones managed by citrain ;-)
[18:42] <barry> robru: yeah, except for all those oddities :)
[18:52] <alecu> Thanks queuebot for sorting it out, the previous "is in no known space (and time)." was not encouraging.
[18:52] <alecu> ☺
[18:53] <nik90> lol
[19:18] <ToyKeeper> Were there recently some major changes in the UI for how the user is supposed to close apps?
[19:21] <cyphermox> ToyKeeper: you now do the swipe from the right edge, to show all open apps, and flick up/down like on Android, it seems
[19:21] <ToyKeeper> Hmm, that's not like any Android I've ever used.
[19:22] <ToyKeeper> I think I saw someone doing that at a coffee shop once though.
[19:22] <ToyKeeper> It's good to know that's a feature though, not a bug.
[19:23] <cyphermox> well, I don't know for sure, but I agree the hold-and-press-the-red-X doesn't appear for me either :)
[19:24] <ToyKeeper> The hold-and-press-then-red-X was always a bit hard to do anyway, since one must be extremely still to avoid making it think the action is a swipe of some sort.
[19:24] <ToyKeeper> (which reminds me, I was meaning to file a bug about how hard it is to trigger a press-and-hold action)
[19:25] <ToyKeeper> I've gotten some odd behavior from the new app switch/close UI though, like it shows up in not-3D once in a while.
[19:28] <cyphermox> ahaha I noticed it too just now
[19:37] <bzoltan> robru:  the silo20 is good to go
[19:47] <ToyKeeper> I was pretty confused the first few times I got the not-3D right-edge switcher...  primarily because I only had one app open and it gave me an off-center non-functional screenshot of the app and regular edge functions didn't work.
[19:47] <ToyKeeper> That was in 165 though; in 166 I only saw it with 2+ apps open, which was when I finally figured out what was happening.
[22:00] <alecu> hi trainguards, I can use a silo if it's available for that ^. And I'd like to know if I should just delete row 25 that had a branch that we've decided needs more work during next week.
[23:50] <Chipaca> greetings! any chance of a silo for row #39?