[04:02] <bzoltan_> robru: good morning, what's up with OTA7?
[04:05] <robru> bzoltan_: dunno, sorry
[04:05] <robru> bzoltan_: mirv should be up soon & sil shortly after that
[04:13] <bzoltan_> robru: OK, thanks
[04:16] <Mirv> morning
[04:22] <robru> Mirv:  <bzoltan_> robru: good morning, what's up with OTA7?
[04:24] <bzoltan_> Mirv:  I have left the silo14 tested and approved yesterday, rvr said too that it is OK and he waits for my test results... I commented the QA card with my results. Pat said that OTA7 will close tonight. So  wonder if there is anything to be done.
[04:26] <Mirv> robru: I guess that UITK is the remaining excitement to be had, but we'll need jibel/sil2100 to weigh in on that in addition to bzoltan
[04:27] <Mirv> bzoltan: at this hour probably not other than gathering data to make informed decision
[04:27] <robru> bzoltan_: well if they said it can go in I don't see why it can't go in now. it's still tuesday for me ;-)
[04:28] <Mirv> I guess the results were a bit mixed?
[04:29] <bzoltan_> [18:09:25] <rvr> bzoltan_: Silo 14 waiting for automated test results.
[04:29] <bzoltan_> [22:19:48] <jibel> bzoltan_, I'll trust rvr's judgement.
[04:29] <bzoltan_> robru: Mirv: what is the planned release date of the OTA7?
[04:30] <bzoltan_> Mirv: The test results are as good as our testing tools and manual testing can provide.
[04:30] <Mirv> bzoltan_: ok
[04:30] <bzoltan_> Mirv:  the weather app's tests are acting up, but he app itself works fine
[04:31] <bzoltan_> Mirv:  the UITK AP tests finally are fixed and show meaningful results. That is an improvement...
[04:31] <Mirv> then the only blocker I can see is that in trello the card is not exactly in Passed column, if only because rvr waited for bzoltan's results
[04:32] <Mirv> robru: does it look to you to be ok to publish?
[04:32] <bzoltan_> Mirv: I do not wish to interpret rvr's acts...
[04:32] <robru> Mirv: oh I dunno I haven't been following it
[04:32] <bzoltan_> Mirv: robru: for real... when the OTA7 will go out?
[04:32] <Mirv> robru: ok. hmm.
[04:33] <robru> bzoltan_: I don't know. europeans handle that stuff
[04:33] <bzoltan_> robru: I mean.. today is the OTA7 freeze ... but is there a regression check period?
[04:33] <Mirv> I think since the morning's image is already rolled, there's no time to save by publishing it now, so we can just as well wait for jibel/sil2100/rvr to come online to see bzoltan's "automated tests ok" comment and mark the trello properly.
[04:34] <Mirv> bzoltan_: it will go out when ready :) but I guess in 1-2 weeks.
[04:34] <Mirv> bzoltan_: so we'll wait a couple of hours for QA to notice "ah yes it was ok" and allow publishing
[04:35] <Mirv> robru tends to be awake in our afternoon anyway so it's always Tuesday to him still :)
[04:35] <bzoltan_> Mirv: Ohh... so we have 1-2 weeks before release. I would push that UITK out ....
[04:40] <Mirv> bzoltan_: sure, but formal QA approval first
[04:40] <bzoltan_> Mirv:  OK... let's wait few hours
[07:50] <seb128> what is needed for a source to be ready for CI landing?
[07:51] <seb128> does the previous revision needs to be tagged so the CI knows where to start?
[07:53] <bzoltan_> seb128:  usually it is a changelog only MR what need to be landed first
[07:54] <bzoltan_> seb128: But Mirv gave me a wiki page last time with the checklist what need to be done for getting a ticket to the CI train
[07:54] <seb128> right, found it I think, https://wiki.ubuntu.com/DailyRelease/InlinePackaging
[07:54] <seb128> bzoltan_, thanks
[07:56] <Mirv> seb128: no tag needed, just the preparation like on the wiki page (above all the .bzr-builddeb), target branch owned by a team that includes the CI Train user, an MP and a new changelog entry with UNRELEASED (version number doesn't need a date, it will be added)
[07:56] <Mirv> roughly. it happens rarely enough that if anything is missed, it'll be seen when the train tries to build it.
[08:02] <seb128> Mirv, thanks, seems like ubuntuone-control-data is not ready for that
[08:02] <seb128> ubuntuone-client-data
[08:02] <seb128> rather
[08:07] <sil2100> bzoltan_: ping, did you give QA the final automated testing results?
[08:07] <bzoltan_> sil2100:  I did
[08:07] <bzoltan_> sil2100:  it is on the same place as used to be
[08:08] <sil2100> bzoltan_: hm, ok
[08:08] <bzoltan_> sil2100:  the directory is missleading -> http://people.canonical.com/~bzoltan/ap-2015_10_02-VIVID-SILO31-KRILLIN/ but the *014* files are from the Test Plan
[08:09] <sil2100> davmor2, jibel: can we land silo 14 then ^ Since I'd like to go to freeze but not without this fix
[08:13] <Mirv> sil2100: yeah, it seems all good but we need the ack formally on Trello/Bileto from QA
[08:14] <Mirv> since rvr wasn't up anymore when bzoltan_ added the "auto tests ok" results
[08:14] <jibel> sil2100, you can land 59 and 14. I think you can land 10 too, victor marked everything pass on the card but didn't move it to pass and there is no comment about why
[08:16] <jibel> sil2100, I passed 14 and 59
[08:16] <Mirv> jibel: thanks
[08:17] <sil2100> Thanks!
[08:18] <sil2100> uh oh
[08:19] <sil2100> There are no source syncs in there
[08:19] <Mirv> yeah, something's amiss a bit
[08:19] <Mirv> jibel: what about 41 and 15?
[08:20] <sil2100> Mirv: I wonder if robru tried publishing anything after the change in logic he made
[08:20] <sil2100> Mirv: it might be that the train now thinks that UITK and UITK-gles are manual sources in the silo
[08:20] <Mirv> robru: sil2100: yeah no publishing works
[08:20] <davmor2> Morning all
[08:21] <Mirv> robru: sil2100: or actually, 59 did work
[08:21] <Mirv> just not 14
[08:21] <sil2100> wwmiwas 59 dual?
[08:21] <Mirv> sil2100: no, it was not
[08:21] <sil2100> Yeah...
[08:21] <Mirv> jibel: 10 is wily...
[08:21] <sil2100> It's just duals that are busted, since only those have that one check
[08:21] <robru> oh cra
[08:22] <robru> i thought I fixed that when I was changing the sources field
[08:22] <robru> Mirv: sil2100: hang on, I'm here, I'll fix it
[08:23] <Mirv> robru: yeah, like I said it'll be Tuesday regarding the freeze as long as you're awake, so we've not frozen yet :)
[08:23] <robru> haha
[08:23] <robru> Mirv: sil2100: bugs like this happen because I can't publish anymore :-/
[08:23] <robru> way harder for me to test the publish job in the new regime
[08:26] <jibel> Mirv, meh, it's something we want in vivid
[08:27] <robru> Mirv: sil2100: are you guys in a hurry? I pushed a fix to trunk, it'll auto-roll to production in ~50 minutes (just missed the cutoff). if you need it sooner than that we can get IS to do a manual rollout
[08:27] <Mirv> pete-woods: ^ 010 alarm sound change was apparently supposed to go to vivid, but there's only wily silo now?
[08:27] <jibel> Mirv, 41 passed QA
[08:27] <jibel> Mirv, what is 15
[08:27] <jibel> ?
[08:28] <Mirv> jibel: camera, although it's the click that matters
[08:28] <Mirv> jibel: "Fix viewfinder short disappearance at startup."
[08:28] <jibel> Mirv, it passed QA too
[08:28] <pete-woods> Mirv: um, I'm just the code reviewer for that..
[08:28] <jibel> Mirv, what else do you need for these 2 silos?
[08:28] <pete-woods> will have a look and see what's happening, though
[08:28] <Mirv> jibel: yeah just double-checking since I wasn't sure publishing things "after" the date of freeze
[08:29] <Mirv> jibel: nothing else, thanks
[08:29] <Mirv> pete-woods: yeah charles is not around. I wonder why it was put towards QA while it was not the vivid silo, and I wonder if we'd get the vivid silo too soon.
[08:31] <Mirv> anyway, since the vivid branch is separate it will also need a separate landing
[08:31] <pete-woods> strange, I really don't know what charles' plan was
[08:31] <pete-woods> I had assumed it was going to be a dual landing like the other indicators
[08:33] <Mirv> pete-woods: it can't be dual landing as such as the branches have separated
[08:34] <bzoltan_> jibel:  who is the resident autopilot guru I can consult with?
[08:35] <pete-woods> Mirv: fair enough, then I guess we can only wait for charles' vivid branch..
[08:36] <Mirv> pete-woods: yeah. I added a task about it to the bug.
[08:36] <Mirv> robru: I guess we can wait that amount of time easily.
[08:37] <jibel> bzoltan_, you can ask brendand or rhuddie or om26er or veebers or cachio, they are all AP gurus
[08:37] <bzoltan_> jibel: cool, thanks
[08:37] <robru> Mirv: ok. I guess now's a good a time as any to fix dual silos to properly support manual packages.
[08:38]  * sil2100 checks if his removal of sync-monitor from the overlay did the right thing
[08:38] <robru> pstolowski: doh, sorry ^^^ that will be fixed in half an hour
[08:39] <sil2100> Pheew, yeah
[08:39] <pstolowski> robru, ah, ok, thanks
[08:40] <robru> pstolowski: totally my fault, I changed something that had unintended consequences.
[08:42] <pstolowski> robru, np, could you pls ping me when i can re-attempt?
[08:42] <robru> pstolowski: sure
[09:18] <sil2100> Mirv: could you re-publish UITK?
[09:19] <sil2100> https://ci-train.ubuntu.com/job/ubuntu-landing-041-2-publish/21/console <- geh...
[09:19] <robru> sil2100: Mirv pstolowski: fix is in production, please try again
[09:20] <sil2100> robru: I'm getting those errors from time to time in dual silos ^
[09:20] <sil2100> It fails to copy the wily binary usually then
[09:20] <sil2100> s/wily/vivid
[09:20] <robru> sil2100: that's a network issue with launchpad, nothing to do with dual (well you might see it more with dual since wily-only silos just write a file instead of calling copyPackage)
[09:21] <sil2100> Re-running should help?
[09:21] <robru> sil2100: usually actually the copy is successful if you look, lp just fails to send a response
[09:21] <robru> sil2100: yeah rerunning should be harmless
[09:21] <sil2100> Yeah, but since it gets and error, the train doesn't copy the rest
[09:21] <robru> right
[09:21] <robru> sil2100: that's your fault for having silos with more than one package!
[09:21] <sil2100> Oh noes!
[09:22] <sil2100> Actually, not mine, it's the landers fault!
[09:22] <sil2100> Anyway, thanks for the fix roll-out
[09:22] <robru> sil2100: what made you think multiple packages are supported? jeez
[09:22] <sil2100> I think you should be sleeping now!
[09:22] <robru> sil2100: you're welcome
[09:22] <robru> sil2100: maybe
[09:22] <sil2100> hmm, ok, now the train is dead for that silo, ouch!
[09:23] <sil2100> debdiff: fatal error at line 321: Can't read file:
[09:23] <sil2100> There are no packaging changes in this silo ;/
[09:25] <sil2100> robru: the re-run wasn't harmless just so you know ;p I'll try to look into how to fix it
[09:26] <robru> wat
[09:28] <robru> sil2100: no that's a red herring. 'can't read file' is a new normal for when the source package is new in the archive (as debdiff is trying to read a dsc that doesn't exist). the real thing there is you forgot to set the ack
[09:28] <sil2100> robru: there's no ACK
[09:28] <sil2100> robru: there are no packaging changes
[09:28] <sil2100> robru: the previous publish of the same silo was just running without an ACK and copying packages
[09:28] <oSoMoN> sil2100, hey
[09:29] <Mirv> bzoltan_: UITK published
[09:29] <sil2100> robru: if it would require an ACK, the previous one wouldn't start the copyPackage phase, right?
[09:29] <robru> sil2100: oh it's messaging-app wtf
[09:29] <oSoMoN> sil2100, re silo 57, not sure who copied the wily packages either, but it needs to be a source copy indeed
[09:29] <robru> sil2100: there's a diff file saying it's a brand new source package
[09:29] <sil2100> Uh oh
[09:29] <oSoMoN> sil2100, what can we do to fix that?
[09:29] <robru> sil2100: I'll clear the diffs and you try to republish.
[09:30] <sil2100> oSoMoN: ok, I'll remove both packages and now copy the wily source there with the overlay tag... but, I suppose I'll have to bump the ubuntu version or we need a different silo for this
[09:31] <robru> sil2100: try to publish 41 again? i'm a bit confused, i didn't see any diffs in the silo. publish with DEBUG please
[09:32] <oSoMoN> sil2100, can we do it in a different silo then? that sounds like it would be cleaner (and easier)
[09:32] <sil2100> robru: huh, now it works it seems
[09:33] <sil2100> oSoMoN: yeah... let me do that in a moment
[09:34] <sil2100> oSoMoN: sorry for the confusion, it was lateish and I just prepared the wrong source out of habit
[09:34] <robru> oSoMoN: also I did a binary copy of the right version thinking that'd save time, of course
[09:35] <Mirv> sil2100: so now, FREEEEZE!?
[09:35] <robru> sil2100: huh, I have no idea why 41 didn't work, but it's good that it worked now..
[09:35] <oSoMoN> sil2100, no worries, it was late indeed :)
[09:35] <robru> anyway, that's it for me I think
[09:35] <robru> goodnight
[09:36] <sil2100> GOodnight!
[09:36] <oSoMoN> robru, thanks but oxide needs rebuilding against the build deps that are in the overlay ppa, so a binary copy is not enough
[09:36] <oSoMoN> good night
[09:36] <robru> oSoMoN: didn't realize, good to know, thanks
[09:37] <sil2100> Mirv: yesss!
[09:40] <Mirv> \o/
[09:44] <sil2100> hmmm
[09:45] <sil2100> The only problem now is...
[09:45] <sil2100> Oh, neverming
[09:45] <sil2100> s/nevermind
[09:46] <sil2100> Let's wait for everything to migrate nicely, I'll build a new image and make a snapshot of the overlay state
[09:50] <bzoltan_> Mirv: thank you
[10:14] <jibel> oSoMoN, bug 1487090 is marked fixed but it doesn't seem to be fixed on latest image. Do you know that status of this bug?
[10:14] <ubot5`> bug 1487090 in Canonical System Image "Download initiated from context menu’s saveLink/saveMedia doesn’t expose a mime type" [High,Fix committed] https://launchpad.net/bugs/1487090
[10:16] <oSoMoN> jibel, the "fixed" status for the canonical-devices-system-image project is incorrect, it’s fixed in oxide 1.10, which hasn’t been released yet
[10:16] <jibel> oSoMoN, okay, I'll fix the status. Is the fix in a silo for OTA7?
[10:17] <oSoMoN> jibel, no, it won’t be in ota7
[10:18] <oSoMoN> that’s unfortunate, but when the fix was committed to trunk we didn’t anticipate there would be new releases of the 1.9 branch, so we didn’t backport it there
[10:21] <pstolowski> robru, yeah, it worked, thanks
[10:53] <rvr> sil2100: Is buteo reverted in the new image?
[10:54] <sil2100> rvr: should be
[10:54] <rvr> sil2100: Ok
[10:54] <sil2100> rvr: I reverted all the packages and saw them removed from the images - is there a problem?
[10:54] <rvr> sil2100: There was a translation regression in indicator transfer linked to buteo
[10:55] <rvr> sil2100: So if buteo is reverted, it should be gone
[10:55] <sil2100> I reverted indicator-transfer as well, so it should be as it was before
[10:55] <sil2100> Ok, I prepare the snapshotp
[10:55] <rvr> Yeesss
[10:56] <rvr> Translation is back
[10:56] <rvr> sil2100: Do you know whether we got new translation packs yesterday?
[10:56]  * rvr checks the packages
[10:57] <sil2100> hm
[10:57] <sil2100> No, we didn't
[10:57] <sil2100> ugh
[10:57]  * sil2100 goes to poke pitti
[10:57] <Mirv> good, then my fix to an annoying webbrowser translation gets in :)
[10:58] <rvr> Installed: 1:15.04+20150929
[11:00] <sil2100> uuuugh
[11:00]  * sil2100 noticed another CI Train bug
[11:01] <sil2100> Actually I have no idea what's up with unity-notifications versioning, but it's horribly wrong
[11:01] <davmor2> Mirv: why are you annoying the webbrowser what did it do to you?
[11:03] <Mirv> davmor2: there's a Finnish word "Lisää" which means both "Add" and "More". while the bookmarks in webbrowser has More/Less kind of usage. so that ambiguous "Lisää" together with it being a button lead me to think the button is for adding a bookmark manually, not showing "all" bookmarks and I was puzzled where my bookmarks are disappearing... and I might not be the only one
[11:04] <Mirv> so I now translated it with a longer word that really means just "More"
[11:04] <Mirv> and also rhymes with the translations of the Less counterpart
[11:04] <davmor2> Mirv: I see your issue there too many vowels
[11:06] <Mirv> davmor2: thnks, I cn fx tht. nglsh s ctll qt rdbl wtht vwels
[11:06] <Mirv> -I
[11:06] <Mirv> but the UI might be clearer too, not just the word
[11:07] <sil2100> ;)
[11:08] <Mirv> I was really puzzled for weeks about where my bookmarks were disappearing, and I avoided pressing the (in my mind) "Add" button since I didn't want to add a new bookmark
[11:08] <davmor2> Mirv: ctll has me thrown the rest is still fairly readable though :)
[11:08] <Mirv> davmor2: actually
[11:09] <sil2100> doh, so obvious!
[11:09] <davmor2> Mirv: ah :) thanks
[11:09] <davmor2> sil2100: don't make me come over there ;)
[11:54] <sil2100> rvr: not sure what's up with the translations, I don't have access to the langpack-o-matic machine ;/
[11:54] <rvr> sil2100: I see
[11:55] <sil2100> I can do a manual upload
[11:55] <rvr> sil2100: Did you talk to pitti?
[11:55] <sil2100> Yeah, but he didn't answer
[11:56] <sil2100> Oh, ok, now he answered on -devel
[11:56] <sil2100> Yaay, he's running it manually, he had to disable to cronjob as there were some desktop things he was working on
[12:08] <pmcgowan> alecu, jibel whats the status of silo 9, are we deferring?
[12:11] <alecu> pmcgowan: from our side it's ready for QA. I tested it on my krillin, installing new apps and old apps, and rebooting a couple of times, and it seems to be working as we expect.
[12:11] <pmcgowan> alecu, I dont think its marked ready is it?
[12:11] <pmcgowan> its not in the queue
[12:11] <alecu> ah, I see that it's been marked "Next Milestone" in the QA board
[12:12] <pmcgowan> I suppose thats ok
[12:12] <pmcgowan> not great
[12:12] <jibel> pmcgowan, we can land it today.
[12:13] <alecu> jibel: that would be great. Thanks!
[12:13] <jibel> it was not reviewed and approved yesterday evening
[12:13] <jibel> rvr, davmor2 can someone take silo 9 ?
[12:14] <jibel> rvr, davmor2 dobey reviewed it, it's a critical fix for this ota
[12:14] <rvr> jibel: Ack
[12:14] <alecu> jibel: rvr: davmor2: kyrofa will have spotty connection today, so ping me instead if anything arises
[12:15] <davmor2> rvr: thanks
[12:16] <rvr> alecu: kyrofa: Did you run the automated tests?
[12:17] <rvr> alecu: kyrofa: Also, how can the two fixes be checked?
[12:17] <alecu> rvr: I tested it manually on my bq with r143. I know that kyrofa added some unit tests, and I'm sure he must have ran them
[12:23] <jibel> rvr, if it's unit tests, they should run at build time and there is probably a trace in the build logs
[12:42] <jibel> pmcgowan, bug 1489037 didn't land yet and the silo is for wily only
[12:42] <ubot5`> bug 1489037 in indicator-datetime (Ubuntu) "Change default alarm sound to "Alarm clock.ogg"" [Undecided,In progress] https://launchpad.net/bugs/1489037
[12:42] <jibel> alecu, we need a vivid silo with this ^
[12:42] <pmcgowan> jibel, oh foo
[12:42] <pmcgowan> why not dual?
[12:43] <pmcgowan> alecu, ^^
[12:43] <alecu> pmcgowan: jibel: ack
[12:45] <Ursinha> kgunn: hi, sorry to ping you again, I'm trying to understand what are your QML current tests so I can figure out the slaves you need for jenkins, who should I talk to? I know there are two jobs, I want to know if that does what's supposed or if there are others
[12:46] <jibel> sil2100, robru isn't there something wrong with the train or bileto? It's the second time this week we receive requests for manual QA for wily only silos.
[12:48] <sil2100> jibel: the train is more and more a self-service, probably people pick the wrong things... since I can't think of any possibility that the train or bileto could switch vivid landings to wily
[12:48] <sil2100> Like automatically
[12:51] <jibel> k
[12:54] <kgunn> Ursinha: Saviq or mzanetti would be best... they're  at Qt summit for next 2 days tho
[12:54] <kgunn> Ursinha: dednick might also know
[12:57] <bfiller> jibel, sil2100 : has the revert of the buteo stuff happened yet?
[12:58] <jibel> bfiller, yes, latest build should have the revert
[12:58] <bfiller> jibel: ok cool, also I'll need to upload a new camera-app click to the store as I see the silo has landed
[12:59] <bfiller> doing that now
[12:59] <jibel> bfiller, correction: not latest but previous
[12:59] <jibel> anyway it's reverted
[13:01] <Ursinha> kgunn: thanks, I'll try dednick :)
[13:02] <kgunn> Ursinha: if not, others will be back to regular irc presence on Thurs i think
[13:02] <Ursinha> kgunn: right, thanks for the heads up
[13:24] <bfiller> popey: I need a manual review of camera-app I just uploaded to store, can't seem to find the button to request the manual review but am seeing this auto-failure here https://myapps.developer.ubuntu.com/dev/click-apps/506/r/30/
[13:27] <popey> bfiller: lemme see
[13:27] <popey> bfiller: request manual review is at the bottom of that page
[13:27] <popey> bfiller: underneath Available Actions
[13:28] <bfiller> popey: got it, just requested it
[13:35] <rsalveti> sil2100: hey, from the new interface, is there an easy way to list all the src package names that are in the landing requests?
[13:35] <rsalveti> sil2100: I see the requests, bugs and comments, but not the src itself
[13:35] <rsalveti> just to understand if an upload would conflict with anything
[13:35] <sil2100> rsalveti: you mean, you'd like to see all silos and all their packages?
[13:36] <sil2100> rsalveti: the only way currently to see all package names in a given silo is clicking its details page, so clicking on the request in the interface
[13:37] <rsalveti> sil2100: urgh, yeah
[13:37] <rsalveti> wanted just an easy, single page view :-)
[13:37] <sil2100> rsalveti: but conflicts are taken care of gracefully, your silo will be marked as 'dirty' if someone releases something that's also in your silo
[13:37] <sil2100> Yeah, sadly the interface is still being worked on ;p
[13:37] <rsalveti> sil2100: sure, that is fine, but wanted to avoid conflicts before requesting anything :-)
[13:37] <sil2100> You *can* look at the raw data though!
[13:37] <rsalveti> sil2100: is robru still the one to kick for that?
[13:37] <rsalveti> :P
[13:37] <rsalveti> sil2100: that might help, how to see the raw data?
[13:38] <sil2100> rsalveti: https://requests.ci-train.ubuntu.com/v1/tickets <- there's quite a lot of info there, but still!
[13:41] <popey> bfiller: approved
[13:41] <rsalveti> sil2100: thanks, "sources" is kind of what I wanted
[13:41] <bfiller> popey: thanks
[13:41] <popey> np
[13:43] <Mirv> rsalveti: if a single package, you can also search https://requests.ci-train.ubuntu.com/#/tickets?active_only&search=qtbase-opensource-src
[13:43] <rsalveti> Mirv: nice, thanks!
[13:43] <rsalveti> Mirv: btw, care to help reviewing https://codereview.qt-project.org/#/c/125784/ ?
[13:43] <rsalveti> I will check soon as well
[13:44] <Mirv> rsalveti: it's merged already to 5.6?
[13:44] <rsalveti> I think this was a patch I originally did
[13:44] <Mirv> rsalveti: yes, they basically took it from us and put it into correct non-generic place
[13:45] <rsalveti> Mirv: hm, is it merged?
[13:45] <rsalveti> it says it's merged, but it was cherry-picked into the staging branch
[13:45] <rsalveti> not sure what is the staging branch
[13:45] <rsalveti> let me check qtbase
[13:48] <Mirv> rsalveti: so the Status says: Merged. and the branch says dev (which is actually 5.7 already at that time), but I fail to actually find it easily from the dev branch myself
[13:49] <rsalveti> Mirv: 0d3464428e4632f3ec905766baf778d3355dd80c
[13:49] <rsalveti> yeah, dev branch
[13:49] <rsalveti> cool, then I guess there is nothing for us to do
[13:49] <Mirv> yes, I can see it in local checkout, just not in the web viewer but that's probably a limitation over there
[13:51] <Mirv> yep, it's done and waiting for the (far) future 5.6/5.7 releases to Ubuntu. first, 5.5 :D
[13:52] <rsalveti> Mirv: awesome
[14:00] <ChrisTownsend> sil2100: Hey, I have a question about silos in the "Ready for QA" phase.
[14:01] <ChrisTownsend> sil2100: We have had https://requests.ci-train.ubuntu.com/#/ticket/401 in Ready for QA for a couple of days now.  Is someone supposed to pick this up and do what's necessary or do I have to seek someone out to give it the sign off?
[14:07] <oSoMoN> sil2100, are you doing the source copy of oxide 1.9.5 to silo 10 ?
[14:07] <sil2100> oSoMoN: yes, the source package just built
[14:07] <sil2100> It takes ages to upload though ;)
[14:07] <oSoMoN> excellent, thanks
[14:07] <oSoMoN> yeah oxide is quite a big package
[14:08] <oSoMoN> blame upstream chromium :)
[14:08] <sil2100> ChrisTownsend: hmmm, looking
[14:09] <ChrisTownsend> sil2100: Ok, thanks.  I'm not sure of the process, so I don't know if I'm being impatient or not:)
[14:10] <sil2100> ChrisTownsend: ok, so I see it's in the QA queue but marked as blocked, probably because the MPs weren't approved back then
[14:10] <sil2100> ChrisTownsend: https://trello.com/c/2SPUwfml/2353-401-ubuntu-landing-060-click-mvo-christownsend
[14:11] <sil2100> ChrisTownsend: it could be that it was late when it happened, now we're in final freeze
[14:11] <ChrisTownsend> sil2100: Hmm, ok.  So you have to reference a Trello board to see QA progress?
[14:13] <ChrisTownsend> sil2100: Hmm, didn't realize they have been adding changes to the original MP.
[14:13] <sil2100> ChrisTownsend: yeah, the process is not ideal but the train does not offer such fine-tuned features yet - every train ticket that's set as ready is automatically turned into a trello card
[14:14] <sil2100> So to have all the info, we always advise to check their trello board
[14:14] <sil2100> (it's in the topic)
[14:14] <ChrisTownsend> sil2100: lol, who reads the topic?;-)
[14:14] <ChrisTownsend> sil2100: But thanks for setting me straight.
[14:15] <sil2100> uh oh! It's in my e-mails too! (just don't tell me you don't read my daily e-mails or I'll cry) ;p
[14:15] <ChrisTownsend> lol
[14:17] <davmor2> sil2100: I don't read your daily emails
[14:17]  * sil2100 bursts into tears
[14:17] <sil2100> ;)
[14:22] <sil2100> jibel, davmor2, rvr: I'll kick a new image with the new language packs
[14:22] <sil2100> jibel, davmor2, rvr: we intend to land anything else still for OTA-7?
[14:23] <rvr> sil2100: I'm checking silo 9
[14:24] <sil2100> ok, so I'll wait a bit still
[14:32] <rvr> ChrisTownsend: ping
[14:33] <rvr> ChrisTownsend: How can I test this? https://bugs.launchpad.net/ubuntu/+source/click/+bug/1496976
[14:33] <ubot5`> Ubuntu bug 1496976 in click (Ubuntu) "install/_unpack stage should not follow symlinks when stat'ing files" [Undecided,New]
[14:34]  * sil2100 copies the langpacks over to the snapshot in the meantime
[14:34] <ChrisTownsend> rvr: Hey, hmm, good question.  I guess the thing we want to make sure is that there isn't a regression, so making sure a click package installs successfully is a good start.
[14:34] <sil2100> I think to make things easier we'll leave the overlay closed today still for normal non-OTA-7 landings and open it up around tomorrow
[14:35] <rvr> ChrisTownsend: I already tested that... I wanted to check the bug fixes.
[14:35] <rvr> ChrisTownsend: Is there a click package for puritine that I can use on the phone?
[14:36] <ChrisTownsend> rvr: Yes, I'll give you a link to the click on my chinstrap.
[14:36] <ChrisTownsend> rvr: https://chinstrap.canonical.com/~townsend/puritine/com.ubuntu.puritine_0.2_armhf.click
[14:37] <rvr> ChrisTownsend: Thanks
[14:37] <ChrisTownsend> rvr: It'll take it a bit to install and then fail without the fix.  It's a big package:)
[14:37] <ChrisTownsend> rvr: No problem.  Let me know if I can help with anything else.
[14:38] <rvr> ChrisTownsend: : debsig: com.ubuntu.puritine_0.2_armhf.click does not appear to be a deb format package
[14:39] <ChrisTownsend> rvr: Right, use this command: ‘pkcon install-local --allow-untrusted com.ubuntu.puritine_0.2_armhf.click’
[14:39] <rvr> ChrisTownsend: Same problem
[14:40] <ChrisTownsend> rvr: Hmmm, so you have the click on the phone and then type that in?
[14:42] <rvr> Yes
[14:42] <rvr> ChrisTownsend: http://paste.ubuntu.com/12705005/
[14:43] <ChrisTownsend> rvr: Hmm, not sure.  I'll investigate.
[14:44] <ChrisTownsend> rvr: Is the click you downloaded around 435M?
[14:44] <rvr> ChrisTownsend: Hmm... nope
[14:44] <rvr> It downloaded a web page
[14:44] <ChrisTownsend> rvr: Oops!
[14:44] <rvr> Authorization is required to access ...
[14:45] <rvr> chmod 755 :)
[14:45] <ChrisTownsend> rvr: Are you a Canonical employee?
[14:45] <rvr> ChrisTownsend: Ah, chinstrap...
[14:45] <rvr> ChrisTownsend: Yes, but I downloaded that directly on the phone
[14:46] <ChrisTownsend> rvr: Ok, sorry that I didn't recognize your nick.
[14:46] <rvr> ChrisTownsend: vrruiz @canonical :)
[14:46] <ChrisTownsend> Ahhh, sure:)
[14:47] <ChrisTownsend> rvr: My people.c.c account doesn't seem to work and I've been too lazy to file an RT hence the chinstrap.
[14:48] <rvr> No problem, I am pushing it to the phone
[14:49] <ChrisTownsend> rvr: Ok, cool, thanks
[15:06] <rvr> ChrisTownsend: The package was installed correctly
[15:07] <rvr> alecu: Does Click Hooks test case cover #1479001?
[15:08] <alecu> rvr: I think it does. kyrofa added the last testcase in the plan for that bug. It's under "Click Hooks"
[15:08] <alecu> ah, right
[15:09] <alecu> it's the same section you just mentioned :P
[15:09] <rvr> hehe
[15:09] <rvr> alecu: Good, then it worked ok
[15:09] <alecu> wonderful.
[15:09] <alecu> rvr: I also manually tested installing packages, removing packages, and installing a system update and rebooting
[15:10] <alecu> rvr: and it seems to work as expected.
[15:11] <ChrisTownsend> rvr: Cool, thanks
[15:17] <rvr> alecu: ChrisTownsend: jibel: sil2100: Approving silo 9
[15:17] <sil2100> rvr: excellent, thanks!
[15:17] <sil2100> Ok, so this can still land, right?
[15:17] <sil2100> Anything else we waiting for..?
[15:18] <ChrisTownsend> rvr: Awesome, thanks!
[15:18] <ChrisTownsend> sil2100: I guess we can abandon silo 60 since silo 9 is being approved?
[15:19] <pmcgowan> sil2100, did the datetime indicator land with the new sound
[15:19] <pmcgowan> alecu, ?
[15:20] <jibel> alecu, I didn't see any vivid silo with this change
[15:20] <jibel> pmcgowan, ^
[15:21] <pmcgowan> yeah the card said ota so its confusing
[15:21] <sil2100> pmcgowan: no, it has a build failure...
[15:21] <alecu> jibel: pmcgowan: charles is working on that, and I think he has a silo building with it.
[15:21] <sil2100> https://requests.ci-train.ubuntu.com/#/ticket/489
[15:21] <sil2100> eh
[15:22] <jibel> rvr, I'm removing this card since it's the wrong target https://trello.com/c/Ucidnykj/2355-473-ubuntu-landing-010-indicator-datetime-charles
[15:22] <rvr> jibel: Ack
[15:27] <charles> trainguards, any suggestions on the best way to get https://requests.ci-train.ubuntu.com/#/ticket/489 unstuck? build failure log @ https://ci-train.ubuntu.com/job/ubuntu-landing-046-1-build/90/console
[15:27] <charles> the issue is the version number, I'm thinking a quick fix would be to manually bump the debian/changelog version in the branch
[15:27] <charles> the issue is that this has already landed in W so I can't resolve with a dual landing
[15:28] <sil2100> WTF
[15:28] <sil2100> Why did it use 14.04 as the series version
[15:29] <sil2100> charles: the way to go is modifying debian/changelog directly in the 15.04 trunk as you proposed and changing 15.10 to 15.04 there
[15:29] <sil2100> No, wait
[15:30] <sil2100> charles: the recent version was already released to wily from this branch?!
[15:30] <sil2100> charles: this looks like a 15.04 branch, why did anyone release a wily (15.10) project from it?
[15:30] <charles> sil2100, no, from a separate branch. It's been released in 15.10 from a separate branch
[15:30] <sil2100> Phew, ok
[15:31] <sil2100> hm...
[15:31] <charles> which, if it had been dual, would have avoided this mess :P
[15:31] <sil2100> So yeah, in that case I would say - just modify it in the branch directly, bzr push and rebuild
[15:31] <charles> sil2100, ack
[15:31] <sil2100> e.g. change the last version from 13.10.0+15.10.20150710.1-0ubuntu1 to 13.10.0+15.04.20150710.1-0ubuntu1
[15:31] <sil2100> I'm worried why suddenly the train came up with the 13.10.0+14.04.20151007-0ubuntu1 version in the build log
[15:32] <sil2100> As the silo looks properly configured
[15:32] <sil2100> I'm shocked that the build log says: "Series: trusty" while bileto has series set to vivid
[15:32] <sil2100> But let's see if it happens again when you rebuild
[15:33] <ogra_> still better than if it would say "serias: warty"
[15:33] <ogra_> :)
[15:45] <sil2100> ogra_: hey, you around to review, approve and (maybe) merge a seed change for meh? :)
[15:45] <sil2100> ogra_: https://code.launchpad.net/~sil2100/ubuntu-seeds/ubuntu-touch.wily-remove-friends/+merge/273715
[15:46] <sil2100> ogra_: I'll refresh the metapackage and upload it once it's merged :)
[15:47] <ogra_> nobody wants to have friends, tsk ...
[15:48] <sil2100> Friends are overrated
[15:53] <ogra_> sil2100, done
[15:53] <sil2100> Thank you!
[15:53]  * sil2100 hugs ogra_ 
[15:53] <sil2100> doko will be happy
[15:53]  * sil2100 prepares the meta package
[15:54] <ogra_> oh, so doko doesnt want to have friends ...
[15:54]  * ogra_ slowly gets the picture
[15:55] <sil2100> hah ;) It's actually Ken's bug!
[16:27] <sil2100> charles: how's the silo going?
[16:28] <charles> sil2100, still going
[16:28] <charles> watching it @ https://ci-train.ubuntu.com/job/ubuntu-landing-046-1-build/93/console
[16:57] <alecu> hi all, anybody else has noticed the Authenticator app crashing on r144?
[16:58] <alecu> it crashed on r143 as well (bq rc-proposed, that is)
[17:01] <alecu> it was last updated 9/9/2015, so I guess something must have changed in the image
[17:02] <jibel> rvr, can you start the verification of silo 46. Build is not completely done but it's ready for armhf. You'll have to add the silo and pin it manually
[17:03] <jibel> rvr, it is the last silo to have a first candidate for OTA7
[17:16]  * sil2100 can't wait for it to land
[17:17] <sil2100> I already disabled daily builds
[17:19] <rvr> jibel: Yes. I'll be back in 20 minutes and will start.
[17:43]  * rvr is back
[17:52] <sil2100> rvr: \o/
[17:52] <sil2100> rvr: give us a sign once it's signed-off
[18:30] <rvr> jibel: sil2100: charles: Fix work with calendar app and reminders app
[18:30] <rvr> Doing a couple of additional checks
[18:33] <charles> woot
[18:34] <charles> beautiful timing, there :-)
[18:36] <rvr> lol
[18:36] <rvr> What did it fail?
[18:36] <rvr> s/what/why/
[18:37] <rvr> sh: 1: -gcc-4.9: not found
[18:43] <robru> sil2100: if the build log says "series: trusty" I'm inclined to believe the request was set that way at the time then changed later.
[18:46] <robru> sil2100: indeed the build log reveals that charles was poking at the series field before and after the failures.
[18:46] <robru> The audit log rather
[18:47] <charles> yes, I did poke at the series to see if I could resolve the version number issue that way before pinging ci-eng
[18:48] <charles> I didn't poke it after starting the most recent build
[18:49] <charles> looks like the failure was due to the ppc64el build failing
[18:50] <charles> looks like it died after 150 minutes of activity in the unit tests, in a test that's unrelated to this change...
[18:51] <charles> built on the other platforms though.... let's try a rebuild to confirm it was a one-off
[18:53] <robru> charles: yeah, no. When you set the series that doesn't just change what version number is used, it affects where the package is uploaded to. Unless you plan to start making a phone based on trusty.
[18:56] <robru> jibel: thanks for requesting I put edits in the audit log, I'm finding that very useful ;-)
[18:58] <charles> robru, I made that change at someone's suggestion, when asked them for help they misread the ticket as a backport to trusty. No current plans to make a phone on trusty... :-)
[19:00] <robru> charles: blah
[19:00] <robru> charles: it looks like you got the build going, anything else you need help with?
[19:01] <charles> heh
[19:02] <charles> no. if I hit an issue like this in the future I'll ping -ci-eng for help sooner rather than later to avoid crap like this
[19:03] <robru> charles: this error is a pretty common one, not much we can do about it in the train side, you really aren't allowed to go backwards on the same branch, so it's necessary to either do dual or branch trunk and change the changelog for the older series.
[19:04] <charles> agreed. dual would have been The Right Thing here, but I made the mistake of landing the patch solo for Wily already.
[19:05] <charles> anyway, thank you for taking a look and for your help
[19:05] <robru> charles: you're welcome
[19:08] <sil2100> rvr, charles: so silo 46 was not built yet?
[19:08] <sil2100> rvr, charles: I thought it was set as ready for QA already - it wasn't built?
[19:09] <charles> sil2100, QA's signed off, we've both tested the armhf build
[19:09] <rvr> sil2100: Nope, it was still building. I downloaded the armhf package.
[19:09] <charles> sil2100, silo 46 failed in the ppc64el build on an apparently unrelated issue
[19:09] <sil2100> Ah, ok
[19:09] <sil2100> Phew!
[19:10] <charles> I restarted the build just for completeness to confirm it's a one-off in ppc64el
[19:10] <rvr> Silo 46 is approved
[19:17] <jibel> sil2100, if silo 46 is published can you build an image?
[19:17] <sil2100> jibel: sure
[19:17] <sil2100> Publishing
[19:17] <sil2100> Ah, ok, it's still building
[19:18] <sil2100> charles: failed to build again it seems...
[19:19] <charles> sil2100, no?
[19:19] <charles> sil2100, still building, pc64el worked this time
[19:19] <charles> sil2100, it's running at https://ci-train.ubuntu.com/job/ubuntu-landing-046-1-build/94/consoleFull
[19:20] <sil2100> charles: ah, ok, refresh helped ;)
[19:20] <charles> sil2100, maybe you're looking at the qtpurchasing silo rather than the datetime one?
[19:20] <charles> ok good :-)
[19:20] <sil2100> charles: sorry, it seems I didn't refresh the PPA page and saw ppc64el failed in the top right corner
[19:20] <sil2100> ugh
[19:20]  * sil2100 waits for powerpc now
[19:33] <sil2100> slangasek, infinity: could we get someone bumping the build score for https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-046/+build/8097143 ?
[19:34] <slangasek> yah looking
[19:34] <slangasek> bumped
[19:36] <sil2100> Thanks :)
[19:38] <charles> sil2100, lol
[19:39] <sil2100> Finally building
[19:49] <charles> looks good so far @ https://launchpadlibrarian.net/220554205/buildlog_ubuntu-vivid-powerpc.indicator-datetime_15.04.0%2B15.04.20151007.1-0ubuntu1_BUILDING.txt.gz...
[19:49] <charles> there we go
[19:49] <charles> sil2100, finished ^
[19:58] <sil2100> charles: publishing in a moment
[20:11]  * sil2100 waits for the packages to migrate
[20:26] <sil2100> Ok, kicking
[20:30] <sil2100> jibel: new image building o/