[00:24] <robru> yay
[01:04] <kenvandine> robru, btw... i kicked the tires a little on your new tool, sorry i didn't really have any feedback :)
[01:04] <kenvandine> i was just excited to see the end of the spreadsheet in sight i couldn't think straight :)
[01:04] <robru> kenvandine: i saw that, thanks. I've managed to find enough holes in my own so far ;-)
[01:05] <kenvandine> robru, i think the only thing i didn't understand was the status field
[01:05] <robru> It's down atm due to redeploying issues.
[01:05] <kenvandine> it's free form?
[01:05] <robru> kenvandine: yeah the status field will be set by Jenkins mostly.
[01:05] <kenvandine> ok, shouldn't let it be editable my me then :)
[01:05] <kenvandine> also there was no choice for dual landing
[01:05] <kenvandine> but i typed it in
[01:06] <robru> kenvandine: yeah all the fields are free form
[01:06] <kenvandine> s/my/by/
[01:06] <robru> I'll add dual as an option
[01:06] <kenvandine> i think those were the only issues i noticed
[01:06] <kenvandine> i expected status to be read-only
[01:06] <kenvandine> it's all VERY exciting though!
[01:08] <robru> kenvandine: thanks, yeah I'm hoping to have this ready in a week + however long it takes for #is to do the production rollout
[01:09] <kenvandine> awesome!
=== Amy is now known as Guest27974
=== Amy is now known as Guest55075
[07:38] <sil2100> jibel, davmor2, popey, ogra_: I suppose there's nothing to discuss today as well, right?
[08:05] <jibel> sil2100, works for me
[08:07]  * ogra_ has always something to discuss :P
[08:07] <davmor2> sil2100: probably not
[08:07] <ogra_> not particulary for this meeting though :)
[08:07] <sil2100> ;p
[08:10] <jibel> sil2100, I supposed your question implied that you'll cancel the meeting, hence my reply :)
[08:11] <ogra_> he did so, 15 min ago :)
[08:15] <mterry> rsalveti, hey btw, here's a little presentation I made.  I don't know how we are presenting stuff today, but you can use some of its slides maybe: https://docs.google.com/presentation/d/1fQ_1kSp6nacLa5970GMl3RxALQR0216_UpOtj4SR-ZQ/edit#slide=id.gb5009c440_0_141
[08:16] <ogra_> mterry, echan ? :)
[08:16] <mterry> ogra_, ineed
[08:27] <dbarth> hola
[08:27] <dbarth> hey trainguards, can you help me reconfig silo 001; i have added a branch that the tool doesn't like me to add myself
[08:28] <sil2100> dbarth: hey! On it
[08:28] <sil2100> dbarth: reconfiguring
[08:28] <sil2100> Should be good now
[08:29] <ogra_> sil2100, bug 1465214 .... i wouldnt actually call "Add debugging to figure out what's happening.." being "Fix Released" :)
[08:29] <ubot5> bug 1465214 in unity8 (Ubuntu) "SIM unlock dialog can not be brought up on arale at all" [Critical,Incomplete] https://launchpad.net/bugs/1465214
[08:34] <jibel> ogra_, the commit message is wrong, it's more than just adding debug information.
[08:35] <ogra_> jibel, bah
[08:35]  * ogra_ did just set it back to "In Progess"
[08:35] <jibel> ogra_, the real fix is "Wait for SIM Manager interface to be fully initialised before we try and unlock any SIMs"
[08:36] <jibel> s/fix/message/
[08:37] <jibel> and it also fixes the case where you couldn't unlock your SIM if you boot with airplane mode on. 2 bugs with 1 fix :)
[08:37] <ogra_> i dont see that line anywhere in the changelog
[08:37] <jibel> https://code.launchpad.net/~pete-woods/indicator-network/sim-unlock-debugging-lp1465214/+merge/262108
[08:38] <jibel> this is what landed
[08:38] <pete-woods> jibel: yay :)
[08:38] <ogra_> jibel, right, but the package changelog (which is what counts) has some other message ...
[08:39] <pete-woods> dammit, forgot to rebuild after setting the commit message correctly
[08:39] <jibel> ogra_, yeah as I said the commit message was wrong
[08:39] <ogra_> pete-woods, you shouldnt have to ... changing it should auto-rebuild imho
=== alan_g is now known as alan_g|afk
[08:40] <ogra_> sil2100, ^^^ could the train check for that ?
[08:41] <ogra_> (so we dont end up with outdated changelogs)
[08:43] <sil2100> uh
[08:43] <sil2100> hm
[08:43] <sil2100> Need to look into the LP API
[08:43] <ogra_> pete-woods, hmm, that should be in todays image ... to which i just OTAed ... and on which i had to use the terminal to unlock :(
[08:43] <pete-woods> it wasn't landed when I eod'd last night
[08:44] <ogra_> phew
[08:44] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/vivid/20150626.changes has it listed
[08:44] <pete-woods> crap
[08:44] <ogra_> so why didnt it come to me with that OTA
[08:44] <ogra_> (i have the old one installed)
[08:44] <pete-woods> oh, that's a relief
[08:44] <ogra_> phablet@ubuntu-phablet:~$ dpkg -l |grep indicator-network
[08:44] <ogra_> ii  indicator-network                                    0.5.1+15.04.20150611-0ubuntu1                     armhf        Systems settings menu service - Network indicator
[08:45] <ogra_>  weird ... what did i just OTA to
[08:45] <ogra_> seems i'm on 38 ... now thats strange
[08:45]  * ogra_ checks for updates again
[08:46] <ogra_> ... and there is 39 waiting ... i wonder how thats possible
[08:46] <pete-woods> cosmic rays
[08:46] <ogra_> yeah, very weird
[08:47]  * ogra_ crosses fingers 
[08:47] <ogra_> and there is a SIM dialog :D
[08:50] <jibel> ogra_, do you mean you received an update notification and you OTA-ed to 38 instead of 39 or you didn't receive a notification for 39 at all?
[08:51] <ogra_> jibel, yeah
[08:51] <ogra_> well, i had 38 waiting when i got up
[08:51] <ogra_> seems it didnt update the info and downloaded 39 even though it was available
[08:52] <ogra_> might be some network glitch though ... i'll keep an eye open if it happens again
=== alan_g|afk is now known as alan_g
[08:54] <jibel> sil2100, there are lot of package built in silo and nothing ready to land really?
[08:54] <jibel> packages* even
[08:55] <sil2100> ;)
[08:55] <sil2100> jibel: eh...
[08:56] <sil2100> I blame summer
[08:58] <jibel> sil2100, if nothing lands soon, we'll be strict and won't accept any silo after the gates are closed
=== vrruiz_ is now known as rvr
[10:27] <bzoltan_> sil2100: robru: may I ask for a silo please?
[10:32] <sil2100> bzoltan_: sure thing!
[11:44] <jibel> pete-woods1, BTW, while running the indicator-network test plan I noticed that the test indicator-network/unlock-sim-connectivity-service-dbus-api fails. the query for ril_0 returns SIM2 and ril_1 returns SIM1
[11:44] <jibel> I'll file a bug
[11:45] <pete-woods1> jibel: will have a look at it
=== pete-woods1 is now known as pete-woods
[11:46] <pete-woods> (after I've finished crying that is)
[11:46] <jibel> pete-woods, the issue was already there without the silo
[11:47] <davmor2> jibel: I think there is already a bug for that
[11:48] <jibel> davmor2, probably, you need something, there is always a bug for it :)
[11:48] <jibel> davmor2, do you have the bug #?
[11:49]  * sil2100 needs to jump out for lunch
[11:49] <sil2100> o/
[11:49] <ogra_> use the stairs !
[11:49] <davmor2> jibel: not off the top of my head but I'm sure I was going to file it ages ago and it was already filed
=== MacSlow is now known as MacSlow|lunch
[11:53] <davmor2> joc_: ^ I think this was one of your bugs right?
=== MacSlow|lunch is now known as MacSlow
[13:11] <bzoltan_> sil2100:  thanks
[13:19] <sil2100> yw!
[13:41] <joc_> davmor2: i did raise a bug about SIM unlock dialog from indicators yes
[13:43] <joc_> bug 1449925
[13:43] <ubot5> bug 1449925 in indicator-network (Ubuntu) "SIM PIN unlock dialog mis-titled opening from indicator " [High,Confirmed] https://launchpad.net/bugs/1449925
[13:44] <davmor2> jibel: ^
[13:44] <davmor2> joc_: thanks
[13:47] <jibel> davmor2, it's different.
[13:47] <davmor2> jibel: ah fair enough just the description sounded similar
[13:49] <jibel> davmor2, yeah, in my case when you send the dbus call to unlock SIM1 it shows the prompt for SIM2 and not only the title is wrong. It really asks to unlock SIM2 (the pins are different on my 2 sims)
[13:50] <davmor2> jibel: ah right not just a title mis-match then
[13:54] <jgdx> is sjenkins down? I can't connect.
=== _salem is now known as salem_
=== salem_ is now known as _salem
[14:23] <jibel> davmor2, actually I might be wrong. I'll double check but I locked my SIM and have to find the PUK now :/
[14:57] <pete-woods> jibel: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1449925 ?
[14:57] <ubot5> Launchpad bug 1449925 in indicator-network (Ubuntu) "SIM PIN unlock dialog mis-titled opening from indicator " [High,Confirmed]
[14:57] <pete-woods> davmor2 ^
[14:57] <pete-woods> I think it's that known one
[15:01] <jgdx> pete-woods, s-jenkins was down for me til now, so the new wpa-ep debs has just been kicked off. Will take 1.5 hours-ish.
[15:01] <jgdx> so you know what to do on your friday evening :p
[15:11] <davmor2> pete-woods: it's jibel that has hit it I think
[15:19] <dbarth> trainguards: o/ i have a new silo requests on line 58
[15:19] <sil2100> dbarth: woohoo, on it
[15:27] <rvr> karni: ping
[15:27] <karni> rvr: soon, in meeting
[15:31] <dbarth> ok thanks
[15:44] <karni> rvr: hi :)
[15:44] <karni> rvr: how can I help
[15:44] <rvr> karni: Hi
[15:44] <rvr> karni: I'm testing telegram
[15:44] <karni> :)
[15:45] <rvr> karni: I figured out where the click package was, the document links to the scope twice
[15:45] <karni> oooh, I'm sorry!
[15:45]  * karni fixes right now
[15:45] <rvr> karni: No problem
[15:45] <karni> oh, you found it
[15:45] <rvr> karni: I found an issue that must be solved before approving
[15:45] <karni> rvr: yes?
[15:45] <rvr> karni: In the scope, the Telegram message is not translated
[15:46] <karni> rvr: you mean there's an unranslated string like "Telegram message"?
[15:47] <rvr> karni:  "Could not retrieve your telegram data"
[15:48]  * karni looks
[15:49] <karni> rvr: we're talking about spanish specifically? (or there's requirement for more languages explicitly to pass QA)
[15:49] <rvr> karni: Spanish, German, French...
[15:50] <karni> interesting. I see no strings missing from translation for the scope on lp, and this in the source:
[15:50] <karni> scope/src/query.cpp:     res["title"] = _("Could not retrieve your telegram data");
[15:50] <karni> rvr: looking into it now
[15:57] <karni> rvr: seems like this string is marked for translation, but not included in the pot file. I'll consult Kyle
[15:58] <rvr> karni: Ack
[16:10] <rvr> karni: There is also a bunch of translated but non-approved strings in Launchpad for Spanish
=== seb128_ is now known as seb128
=== dpm is now known as dpm-afk
=== alan_g is now known as alan_g|EOW
[17:17] <sil2100> davmor2, jibel: is the emulator working already in rc-proposed?
[17:17] <sil2100> I can't find the bug
[17:22] <jdstrand> hmm
[17:23] <jdstrand> so, silo 011 was setup for ubuntu-system-settings-online-accounts (fine)
[17:23] <jdstrand> but there is an apparmor-easyprof-ubuntu change that should be tested with it
[17:23] <jdstrand> (also fine)
[17:23] <jdstrand> so in the spreadsheet I added apparmor-easyprof-ubuntu to column G of line 53
[17:23] <jdstrand> (also fine)
[17:24] <jdstrand> I uploaded apparmor-easyprof-ubuntu to the ppa directly (also fine)
[17:24] <jdstrand> and then realized that I probably need to reconfigure the silo
[17:25] <jdstrand> I then looked in the ppa and saw that ubuntu-system-settings-online-accounts is there for both vivid and wily
[17:25] <jdstrand> but I only uploaded apparmor-easyprof-ubuntu for vivid, since wily already has the fix
[17:27] <jdstrand> so now I don't know how to proceed
[17:27] <jdstrand> sil2100: ^
[17:33] <jibel> sil2100, it doesn't work, cf bug 1458689 and its duplicate
[17:33] <ubot5> bug 1458689 in mir (Ubuntu) "[vivid-overlay] Servers can't start - input-stub.so fails to load on i386" [Critical,Confirmed] https://launchpad.net/bugs/1458689
=== dpm-afk is now known as dpm
[17:48] <anpok> ping trainguards hmm where can I reconfigure my silo?
[17:49] <robru> anpok: the "Landing tools" menu at the top of the sheet has the reconfigure link
[17:50] <robru> jdstrand: delete the wily package and reconfigure the silo for vivid rather than dual
[17:50] <robru> jdstrand: actually wait, it's dbarth's silo, does he not want his thing built for both wily and vivid?
[17:52] <jdstrand> robru: honestly, I was surprised to see the wily package. we didn't discuss that
[17:53] <robru> jdstrand: I would confirm with him before tinkering with stuff.
[17:53] <jdstrand> robru: that said, this isn't a dependency thing-- it is just that things will still be quite noisy without the apparmor-easyprof-ubuntu change
[17:53] <jdstrand> robru: ok, he seems offline so I'll send him an email
[17:53] <robru> jdstrand: yeah, sorry. only dbarth knows why he chose the silo to be dual.
[17:55] <awe> robru, jhodapp, I want to grab row54 in the citrain, but you both are shown as hovering over its columns.  Just wanted to ensure I wasn't going to conflict with either of you...
[17:55] <jhodapp> awe: it's all good, no worries on my end
[17:55] <jhodapp> thanks
[17:55] <awe> np
[17:55] <robru> awe: yep go for it
[18:00] <robru> anpok: congrats on being the first person to use my brand new silo reconfigure job ;-)
[18:02] <anpok> robru: was confused by the request_id
[18:03] <anpok> and managed to do lots of copy and paste errors :)
[18:03] <robru> anpok: oh, what? request_id should be generated for you.. what were you copy&pasting?
[18:03] <anpok> robru: I thought I need to use the request id from the spread sheet..
[18:03] <anpok> i guess I used the wrong job?
[18:04]  * anpok used -> https://ci-train.ubuntu.com/job/prepare-silo/
[18:04] <robru> anpok: yeah but how did you get there?
[18:04] <anpok> from the dashboard 'reconfigure silo' .. couldnt finde the landing tools on the spreadsheet
[18:04] <anpok> aerm 'Prepare silo'
[18:05] <anpok> btw have to make another reconfiguration for gtk
[18:05] <anpok> robru: so where is the real thing?
[18:06] <robru> anpok: top of the spreadsheet, "Landing tools > Assign/Reconfigure" menu. it pops up a link, you click it, and it fills out the form for you. No copy & pasting is necessary.
[18:06] <robru> awe: silo 20
[18:06] <awe> robru, thanks!
[18:07] <robru> awe: you're welcome
[18:07] <anpok> ahh the google spreadsheet menu.. didnt expect to find anything there
[18:08] <robru> anpok: yeah there. don't worry, spreadsheet will be gone in a couple weeks and you'll have to relearn the new system all over ;-)
[18:09] <anpok> robru: interesting behavior..
[18:10] <anpok> i had the first or second row of the spreadsheet selected..
[18:10] <anpok> and it tried to reconfigure "Landing Documentation"
[18:11] <robru> anpok: yeah you have to select the correct row first, that's how it figures out what row to assign.
[18:11] <robru> anpok: the replacement smoothes out all that crap. each row will have an "assign" link that just does the right thing without surprises.
[18:14] <robru> I'm about to go for lunch, anybody need anything before I go?
[18:25]  * robru -> lunch
[18:35] <bzoltan_> robru: how is this failure possible? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-003/+packages the non gles package builds well.. and the amd64 builds well.. also the 15.04 target builds well. magic... black one
[18:46] <robru> bzoltan_: in ci-train, anything is possible ;-)
[18:46] <robru> bzoltan_: checking
[18:48] <robru> bzoltan_: did you read the error log? https://launchpadlibrarian.net/210065299/buildlog_ubuntu-wily-i386.ubuntu-ui-toolkit-gles_1.3.1541%2B15.10.20150626-0ubuntu1_BUILDING.txt.gz looks like there's some kind of API difference there. could it arise from differences in underlying tooling between wily/vivid?
[18:48] <robru> bzoltan_: if you think it's a transient hiccup I'm happy to retry the job
[18:48] <robru> awe: oh, hmmmm
[18:49] <bzoltan_> robru:  the tool is indeed different, but should not be a diff between amd64 and i386
[18:49] <bzoltan_> robru:  thanks for pushing a retry
[18:53] <robru> awe: seems whitespace in column G screwed up the silo config, fixed, trying again: https://ci-train.ubuntu.com/view/1.%20Build/job/ubuntu-landing-020-1-build/162/console
=== nik90 is now known as nik90|Dinner
[19:31] <robru> bzoltan_: no idea about that failure, sorry
[19:31] <bzoltan_> robru:  Ok, I try to dig out something from the logs
=== nik90|Dinner is now known as nik90
[23:45] <robru> bregma: you need to rebuild 21.
[23:50] <robru> bregma: i don't know what's happened but the revision numbers are way wrong. It looks like 10 commits disappeared. Build log references revision 3967 but mp has up to 3957. Definitely needs a rebuild to account for whatever changes are there.