[02:05] <imgbot> [06:51] <Mirv> alexabreu: it seems the rtm-013 was rebuilt before the trunk was properly updated, thus it's not publishable and needs another rebuild + testing instead
[07:48] <popey> Mirv: will probably miss the landing meeting as I have an appointment at school.
[07:52] <Mirv> popey: ok
[08:44] <ogra_> rvr, how did it fail ?
[08:50] <ToyKeeper> ogra_, sergiusens, robru: Could you take a look at http://pad.lv/1427559 to review a phablet-tools fix needed for automated sanity testing?
[08:51] <ToyKeeper> (patch already linked)
[08:52] <ogra_> ToyKeeper, any reason you can not use the existing -n option ?
[08:53] <ogra_> (we use it in the lab)
[08:53] <ToyKeeper> For one, it requires patching every tool which uses phablet-network...
[08:54] <ToyKeeper> (which expect phablet-network to "just work" with no options or input)
[08:55] <ogra_> well, couldn't you just add a default for that file instead then ?
[08:56] <ToyKeeper> I suppose it could use an environment variable or dotfile to point toward a NM config file, and eliminate a few lines to parse the other file...
[08:57] <ToyKeeper> (and use that instead of '-n', when available)
[09:00] <ogra_> ToyKeeper, http://paste.ubuntu.com/10512922/
[09:00] <ogra_> err
[09:00] <ogra_> http://paste.ubuntu.com/10512925/
[09:01] <ogra_> the second one is the right way around :)
[09:04] <ToyKeeper> ogra_: Are you suggesting it as a patch, or suggesting that each affected person modify /usr/bin/phablet-network?  I'm trying to avoid the need to modify files installed by apt-get.
[09:05] <ogra_> huh ? i suggeted to change your MP :) ... but there are bugs ... one sec
[09:05] <jibel> ogra_, what you propose makes no difference with current behaviour because you always have to provide a network file as argument to -n and the default will never be used
[09:05] <ogra_> ToyKeeper, http://paste.ubuntu.com/10512940/ this one should work
[09:05] <ogra_> jibel, yes, fixed
[09:06] <ToyKeeper> Okay, I'm fine with a different method/patch...  so long as it will "just work" with no changes to files from the distro or tools which rely on phablet-network.  (so, behavior specified by env var or checking for a special file)
[09:07] <ogra_> ToyKeeper, yeah, no prob with changing the coe ... i just found your change a bit huge for the task :) test my change, if it works for your usecase we can land it
[09:07] <ogra_> *code
[09:14]  * popey returns
[09:16] <jibel> ToyKeeper, maybe using the network file provided on the command line, then ~/.phablet-network, then the system configuration then fail would do what you want. It won't change phablet-network's behaviour for current users, no change to the argument, no env to specify, and minimal changes to phablet-network and fixes the problem for automated tests running on machines without NM or without a Wifi
[09:16] <jibel> connection.
[09:17] <ToyKeeper> jibel: Yup, that's what I was just doing.  :)
[09:18]  * jibel re-reads your patch :)
[09:19] <ToyKeeper> I mean, what I was just redoing; no point having two slightly different formats for the wifi auth file.
[09:21] <ogra_> jibel, that is what my patch does ...
[09:22] <ogra_> well, in a different order ... if ~/.phablet-network exists it gets used, else it uses NMs default file unless there is -n
[09:22] <ogra_> http://paste.ubuntu.com/10512940/
[09:25] <ToyKeeper> ogra_: Thanks.  Mostly, I wanted to make sure the idea was okay, and that someone on the project was aware of the patch.  :)
[09:26] <ogra_> thanks for bringing it up :)
[09:26] <ToyKeeper> ogra_: New patch is uploaded, much simpler than the first, and does as jibel described.
[09:27] <ogra_> one small nitpick, can you put the actual filename in the usage line too ?
[09:27] <ogra_> (or uses NM-format wifi config from $DEFAULT_NETWORK_FILE which defaults to ...)
[09:27] <ToyKeeper> ogra_: It *is* in the usage line.  Did you try running it?
[09:28] <ogra_> i dont see usage pointing to ~/.phablet-network in your code
[09:29] <ogra_> only to the var ... it should tell you that there is a default value for the var
[09:29] <ToyKeeper> The variables get expanded when it prints the help string.
[09:29]  * ogra_ slaps forehead
[09:29] <ogra_> sorry ...
[09:29] <ogra_> i need more coffee :)
[09:30] <ogra_> ToyKeeper, approved
[09:33] <ToyKeeper> I can't say I'm fully awake either...
[09:36] <ogra_> :)
[10:41] <rvr> ogra_: ping
[10:41] <ogra_> rvr, hey, so what failed exactly ?
[10:41] <rvr> ogra_: push/pull
[10:41] <rvr> ogra_: They work when the screen is locked
[10:42] <ogra_> hmm, did you reboot after installing the package ?
[10:42] <rvr> Yes
[10:42] <rvr> But let me recheck again
[10:44] <rvr> After reboot
[10:44] <rvr> $ adb push diff.diff /home/phablet
[10:44] <rvr> 645 KB/s (26568 bytes in 0.040s)
[10:44] <ogra_> hmm, did you ever install that phone with --developer-mode ?
[10:45] <ogra_> check if there is a dev-mode override file in place, it is called /userdata/.adb_onlock
[10:45] <ogra_> that would disable the lock screen check altogether
[10:48] <rvr> ogra_: Let me see
[10:49] <rvr> ogra_: Yes, the file exists
[10:49] <ogra_> remove it and reboot
[10:49] <ogra_> so we know at lest the behavior is correct with the file in place :)
[10:49] <rvr> :D
[10:50] <ogra_> i should have added that to the test plan, sorry
[10:51] <rvr> $ adb push diff.diff /home/phablet
[10:51] <rvr> error: closed
[10:51] <ogra_> perfect :)
[10:51] <rvr> Perfect
[10:51] <ogra_> (sadly the error message is hardcoded on the PC side ... i would have liked something like "error: screen locked" )
[10:52] <rvr> The other tests passed, I'm approving the silo
[10:52] <ogra_> thanks :)
[11:08] <bzoltan_> Mirv: we have started the final Vivid landing ... I hope it will make it
[11:08] <sil2100> bzoltan_: hey! The final big release of UITK to vivid - does that have any features?
[11:08]  * sil2100 assigned a silos
[11:08] <sil2100> *silo even
[11:08] <sil2100> bzoltan_: but if it's feature-packed, then we'll probably have to file an FFe for it
[11:09] <sil2100> FFe's are the cool thing this cycle
[11:09] <bzoltan_> sil2100:  at this phase all new UITK festures address long pending bugs
[11:12] <bzoltan_> sil2100:  it is a big one, packed with 13 bugfixes. Who's call is to make an FFe or not?
[11:13] <sil2100> It's usually the release team deciding, as if we publish it'll require their approval - if they find that it requires an FFe, it needs to be filled in, but it's always best to try knowing that beforehand
[11:14] <sil2100> Let's ask the release team, sometimes they give us FFe's quite easily for typical touch/next components
[11:14] <sil2100> bzoltan_: is the UITK used anywhere in the desktop, besides Desktop Next?
[11:15] <bzoltan_> sil2100: our own QtCrator does, but not the version this landing has.
[11:15] <bzoltan_> sil2100:  no other application depends on it
[11:17] <Mirv> bzoltan_: good luck!
[11:23] <bzoltan_> Mirv: sil2100: i have added the gles branch too. Would you please reconf teh silo?
[11:24] <sil2100> bzoltan_: sure ,on it
[12:00] <Mirv> bzoltan_: you'll need to bzr rm debian/patches in your -gles branch, since the real fix is in staging now and conflicts
[12:05] <bzoltan_> Mirv:  OK, thanks
[12:05] <davmor2> ogra_, sil2100: so it appears there is a custom-tarball option in ubuntu-device-flash it just doesn't work
[12:05]  * sil2100 off to lunch
[12:05] <ogra_> davmor2, time for a bug then
[12:06] <davmor2> ogra_: indeed
[12:46] <jibel> davmor2, I filed bug 1427667
[12:47] <davmor2> jibel: nice
[13:32] <alexabreu> Mirv, ack (for silo 13)
[14:02] <ogra_> imgbot, status 119 vivid
[14:03] <imgbot> Status: succeeded, Started: 2015-03-03 02:02:09 UTC, Finished: 2015-03-03 02:56:07 UTC
[14:03] <imgbot> Build URL: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-touch/+build/21663
[14:03] <imgbot> Changelog: http://people.canonical.com/~ogra/touch-image-stats/119.changes
[14:27] <ogra_> sil2100, rsalveti, once the livecd-rootfs upload i just did lands in the archive, i want to do a re-build (need the log info)
[14:28] <ogra_> for vivid that is
[14:30] <rsalveti> sure
[14:35] <kenvandine> dbarth, what's the status of rtm silo 10?
[14:36] <kenvandine> dbarth, i'd like to prepare another landing for settings soon
[14:46] <popey> balloons: what's happening with https://code.launchpad.net/~nskaggs/ubuntu-calendar-app/fix-infloop-ap-trunk/+merge/251122 ?
[14:47] <popey> balloons: It appears to be blocking https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/LiveEventModification/+merge/247711
[14:47] <popey> (which I am gettng increasingly worried about)
[14:51]  * balloons erases his original comment
[14:52] <balloons> popey, specific to that merge, I created it to help kunal's merge and fixup the tests. I filed several more bugs as well around calendar as you know. It seems trunk is not stable
[14:53] <sil2100> ogra_: sure thing
[14:54] <balloons> popey, I was also going to mention calendar seems to have struggled in the past, but we've done work to make it well tested and working. It seems to break down over time
[14:55] <balloons> I can only assume the previous tests were not completely stable and they are changing code and not tests as time goes on
[14:55] <Mirv> sil2100: 5.4.1 not all sun and flowers, so no early signoff testing this week at least. no other problems seen yet but there's a problem with the keyboard for unknown reason.
[14:56] <Mirv> sil2100: if there are any big issues, it would mean I'd land it to vivid after the fork, not before...
[14:56] <ogra_> if that publisher will ever move ...
[14:56] <sil2100> Mirv: ouch, you mean the OSK doesn't work properly?
[14:56] <balloons> popey, the weird part is how trunk manages to get broken tests in it. This whole 'run it again' when jenkins doesn't pass it is how that happens.
[14:57] <popey> balloons: I landed a few merges a couple of weeks back and had to retry a few times
[14:57] <Mirv> sil2100: you could say so... a crash bug #1427710 - tsdgeos might have time to look at it at some point. but it better have a good explanation (plausible, there is always some room for something not noticed) or otherwise Qt 5.4.1 starts to sound too risky.
[14:57] <popey> balloons: this one just refuses to pass
[14:58] <Mirv> sil2100: during the meeting I hadn't yet tried to _type_ anything, just playing media and swiping along :)
[14:58] <balloons> popey, right.. I've re-run things as well, but doing that rather than fixing the issue does lead to messes like this
[14:58] <sil2100> hah ;)
[14:58] <popey> balloons: is there someone who can help us clean these up?
[14:59] <tsdgeos> Mirv: sil2100: need to talk to Saviq later to see if i can sneak some time into this
[15:00] <balloons> popey, I mention that they have struggled because I've seen things removed / commented out in the tests when I went to correct the loop issue in my mp
[15:00] <Mirv> sil2100: meanwhile, we do have FFe granted...
[15:00] <sil2100> Mirv: oh!
[15:00] <popey> balloons: we need a way forward, because right now we're stuck and nothing is landing
[15:00] <balloons> popey, yes, I noticed Carla actually has been submitting calendar mp's before I even asked her or Daniel to look
[15:03] <balloons> popey, this is marked critical, so in theory it should be first on the list for folks: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1426183
[15:04] <popey> :(
[15:05] <balloons> aww, now I feel sad
[15:06] <popey> welcome to my world
[15:26] <dbarth> kenvandine: you could take the branch if you want; i'd still like to get dobey's approval on that one though
[15:26] <dbarth> brb
[15:26] <dobey> what's up?
[15:27] <kenvandine> dbarth, i'll leave it to you, i mostly wanted to know when you thought it would get an ack... so i can plan when i can do my landing or if i should try to get in front of you in line
[15:27] <kenvandine> dobey, rtm silo 10
[15:27] <dobey> well the branch is already approved
[15:28] <dobey> there is some other issue in rtm that makes it sort of not work right though
[15:28] <kenvandine> i'm asking about the silo
[15:28] <dobey> or well, i'm not sure if it's another issue in rtm, or a feature
[15:29] <dobey> the code is correct though
[15:47] <dbarth> dobey: so the hook that cleans up the account acl is fine to land ?
[15:48] <dobey> wait, what?
[15:49] <dobey> no, i don't think we should land that
[15:50] <dobey> why is that in there?
[15:52] <dobey> that code doesn't exist in vivid, so i don't think we should land it in rtm. and we don't fully understand what is happening on boot in rtm, so landing a "fix" without understanding the issue seems wrong to me.
[15:55] <imgbot> [15:58] <dobey> mardy: won't this hook fail anyway, because it's unconfined and unconfined isn't in the acl, so it can't actually do queryInfo() on the identity?
[16:20] <dobey> well i need to get lunch
[16:26] <ogra_> jibel, could you try image 120 (once it is done) wrt /var/log ownership ... according to the buld log it is definitely syslog owned now
[16:27] <jibel> ogra_, what is 120? 130 is in devel-proposed for krillin
[16:27] <ogra_> jibel, ah, the both goes after mako versions :)
[16:27] <ogra_> *bot
[16:27] <jibel> ok
[16:28] <ogra_> jibel, the image that is just building ... should be done soon
[16:28] <jibel> I'll try whatever is in proposed
[16:47] <Saviq> trainguards, can you please remove qtmir{,-gles} from vivid silo 19
[16:48] <sil2100> Saviq: sure, from the PPA you mean?
[16:48] <Saviq> sil2100, yes, because the build job lied to me again :P
[16:48]  * Saviq tries to find the bug
[16:48] <sil2100> Oh, so it seems it still doesn't remove packages when reconfiguring ;/
[16:49] <Saviq> yeah
[16:51] <sil2100> Saviq: should be gone from the PPA now
[16:51] <Saviq> om26er, ↑
[16:51] <Saviq> sil2100, thanks
[16:52] <om26er> Saviq, great, thanks
[17:17] <bzoltan_> sil2100:  my krillin dived into a reboot loop and even the recovery mode does not bring it out
[17:18] <bzoltan_> ogra_: ^
[17:18] <bzoltan_> or anybody :(
[17:20] <imgbot> [17:20] <imgbot> [17:20] <sil2100> bzoltan_: huh?
[17:20] <sil2100> bzoltan_: how? What did you do to get it in this state?
[17:22] <bzoltan_> sil2100:  the AP tests of the dialer app ... it does it all the time
[17:22] <bzoltan_> sil2100:  but this time I can not do anything with it
[17:23] <sil2100> ogra_: ^ do you know what can be done in this case?
[17:23] <ogra_> nope
[17:23] <ogra_> well, first of all file a bug against that ap test
[17:23] <ogra_> then try to get into fastboot mode and flash the open recovery.img
[17:23] <ogra_> from there you should be able to do u-d-f
[17:23] <bzoltan_> ogra_: sil2100: anything what could bring back this device to a working state?
[17:24] <bzoltan_> ogra_:  how to flash the open recovery.img?
[17:25] <ogra_> bzoltan_, by following the instructions from the mailing list
[17:25] <bzoltan_> ogra_:  with what subject?
[17:25]  * bzoltan_ gets hundreds of mails on many ML
[17:25] <ogra_> something about adb and recovery
[17:27] <bzoltan_> ogra_:  I am not much closer...
[17:30] <ogra_> popey, ok, all links restored for rtm
[17:31] <popey> yay
[17:31] <popey> thanks
[17:35] <bzoltan_> ogra_:  sil2100: and where to get the recovery.img from?
[17:35] <ogra_> bzoltan_, click the link in the mail
[17:35] <ogra_> it has all instructions
[17:49] <jibel> ogra_, on 131 /var/log is owned by root:syslog
[17:49] <ogra_> \o/
[17:50] <jibel> what changed?
[17:50] <ogra_> the code used "chgrp syslog /var/log"
[17:50] <ogra_> not sure why that didnt work
[17:50] <ogra_> i switched it to"chown root:systlog /var/log"
[17:50] <ogra_> (without the typo :P )
[17:51] <ogra_> so we should be fine now ...
[17:51] <ogra_> what scares me a bit is that there could potentially be other dirs we dont cover like this
[17:51] <ogra_> syslog is just sticking out because we all look at it all the time
[17:55] <jibel> indeed that was my concern with this bug
[17:55] <ogra_> right, but not much we can do except keepin our eyes open
[17:57] <bzoltan_> ogra_:  I did not find "the" mail .. I have 11k mails in that folder and I did not find the one with instructions on how to flash the recovery.img
[17:58] <ogra_> bzoltan_, i get between 600-800 mails per day, dont try to get into a pissing contest with me :P
[17:58] <popey> bzoltan_: "adb no longer available in recovery on krillin/vivid (and rtm too)"
[17:58] <popey> that's the subject
[17:59] <bzoltan_> ogra_:  you win me by far great master :) but that does not help my device
[17:59] <ogra_> bzoltan_, well, what popey said
[17:59]  * popey wins at making the google mail bots search his mail
[17:59] <ogra_> lol, i wont give them access to my imap server :)
[18:00] <bzoltan_> ogra_:  how tricky .. it was on the phablet ML
[18:00] <popey> ya
[18:00] <ogra_> (i'm pretty sure i would have found it in minutes if i had the time for searching)
[18:03] <davmor2> bzoltan_, ogra_: Can I join in the pissing contest I get around 800-1200 emails a day when I take a week off it takes 3 weeks to get fully caught up again. And even I know about the adb not working any more mail.  Also I have several folders around the 20-30000 email mark and 3 over 50,000 and I haven't been here as long as ogra_ so I assume his folders are bigger still :D
[18:04] <ogra_> my whole /var/mail/ogra on the server contains around 5mio mails
[18:04] <ogra_> dating back to before i started at canonical
[18:04] <bzoltan_> davmor2: ogra_: with 3years I am junior here ... but still I am surprised that ML archive here is considered as documentation storage :)
[18:04] <davmor2> ogra_: yeah but your old dude ;)
[18:05]  * ogra_ shakes his cane
[18:05] <ogra_> get off my lawn !
[18:05] <davmor2> can't you see the sign
[18:05] <ogra_> :D
[18:06] <ogra_> bzoltan_, well, it helped me a lot to have it over the last decade
[18:06] <ogra_> and evolution is reasonable fast at searching piles of mail
[18:06] <ogra_> even at that size
[18:06] <davmor2> ogra_: claws is blistering quick
[18:07] <bzoltan_> ogra_:  searching in mails my client is fast too.. once I figure out the right folder :)
[18:07] <davmor2> bzoltan_: just search them all ;)
[18:07]  * bzoltan_ checks the oldes mail ... yes it came in 96
[18:08] <dobey> searching in /dev/null is the fastest evar
[18:08] <ogra_> dobey, yeah, but the results are so unsatisfying
[18:08] <dobey> s/un// :)
[18:08] <ogra_> haha
[18:09] <dobey> the oldest mail in my inbox is from "?"
[18:09] <dobey> yay spam
[18:09] <ogra_> lol
[18:12] <dobey> oldest actual mail i have is i think ~1997ish
[18:12] <Laney> man I wasn't even born then
[18:12] <bzoltan_> mine is from a mailing list
[18:13] <davmor2> bzoltan_, ogra_: my first mail on my home server is 2006 and in gmail is 2004 -ish
[18:14] <davmor2> Laney: bigRon at our lug can tell you about the days they invented the interwebz ;)
[18:16] <bzoltan_> davmor2:  I am confused with my records... I wrote a mail server and client in 92 for novel netware 3.1 without nowing about the existence of internet/email do those mails count?
[18:16]  * bzoltan_ gets sensitive about the golden past
[18:42] <davmor2> bzoltan_: hahaha
[18:51] <bzoltan_> ogra_:  fastboot - u-d-f - reboot cycle again ...
[20:26] <bzoltan_> does anybody know what the hack I do wrog here https://ci-train.ubuntu.com/job/ubuntu-landing-003-1-build/147/console ?
[21:06] <robru> bzoltan_: yeah, -gles isn't configured in the silo
[21:28] <bzoltan_> robru: do we need tro reconf?
[21:29] <robru> bzoltan_: yeah, seems so. one sec
[21:30] <robru> bzoltan_: ok try now
[23:30] <robru> tedg
[23:31] <robru> nuddy
[23:31] <robru> buddy
[23:31] <robru> lol
[23:31] <tedg> robru, I'm getting ready to head out, is that a purposeful ping? :-)
[23:31] <robru> tedg: yes. you apparently didn't manage your silo conflicts very well
[23:31] <tedg> ?
[23:31] <robru> tedg: there it is ^
[23:32] <robru> tedg: you had url-dispatcher in silo 4 and 8
[23:32] <tedg> Hmm... I don't have an RTM silo.
[23:32] <robru> tedg: you published 8 and then didn't rebuild 4.
[23:32] <robru> tedg: but you do? http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=tedg
[23:32] <tedg> robru, That branch landed, someone must have reallocated the silo after I deallocated it.
[23:33] <tedg> Perhaps a race condition
[23:33] <tedg> (human)
[23:33] <tedg> Let me kill it.
[23:33] <robru> tedg: weird, it was built by bfiller: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-004-1-build/104/console
[23:34] <robru> tedg: ok well if you're sure it's wrong, you can kill it. also the mp is merged, so that's curious.
[23:34] <tedg> I marked it as not ready anymore.
[23:34] <robru> tedg: thanks
[23:34] <tedg> robru, The MP was in silo8, it landed with the webbrowser changes.
[23:35] <tedg> I originally had a silo for the MP so that the browser folks could test, but then they just worked on vivid since it was there already.
[23:35] <tedg> Anyway. Useless history :-)
[23:35] <tedg> robru, Thanks for mentioning it, cleaned it up :-)
[23:35] <tedg> 'night folks.
[23:35] <robru> tedg: night