[00:09] <robru> ok, if anybody is around, I am now going to take the spreadsheet offline and migrate all requests into bileto.
[00:09] <veebers> robru: should I hold off trying to make an entry to bilto 'till you're done?
[00:20] <robru> veebers: yes please. running some scripts.
[00:22] <robru> heh
[00:22] <veebers> robru: ack, I'll hold off :-)
[00:23] <robru> veebers: almost done actually
[00:30] <robru> veebers: ok moment of truth
[00:31] <robru> veebers: success! ok go ahead with whatever you were doing
[00:32] <veebers> robru: cool, I'm just out the door though :-P I'll fire one off when I get back though
[00:32] <robru> veebers: sorry about that, should be settling down now ;-)
[00:32] <veebers> robru: nw :-)
[04:25] <robru> kgunn: veebers: everything working OK? ^^
[04:26] <kgunn> robru: uh,  i didn't reconfig or anything...
[04:26] <kgunn> want me to look at something on my end
[04:27] <robru> kgunn: you ran the build job though? looks like it worked. need any help?
[04:27] <robru> kgunn: I'm just paranoid after the issues I've been seeing yesterday and today
[04:28] <veebers> robru: oh, as far as i can tell, I built the ppa but haven't used it yet
[04:28] <kgunn> robru: i had built mir and qtmir earlier...yeah
[04:29] <veebers> robru: packages seem to have built fine
[04:30] <robru> veebers: you made the request in bileto ok? no weird errors?
[04:36] <veebers> robru: yeah I did. Nothing odd that I saw
[04:36] <robru> veebers: cool
[08:06] <sil2100> jibel, davmor2, popey, ogra_: how about we skip today?
[08:06] <popey> awwww
[08:06] <popey> I had a shower and put a shirt on and everything!
[08:06] <sil2100> oh!
[08:06] <popey> I have nothing to discuss today.
[08:09] <jibel> sil2100, it's fine by me
[08:12] <davmor2> sil2100: but I'm no good at skipping I always get tangled in the rope
[08:16] <ogra_> sil2100, apart from feeling sorry for popey i got nothing either :)
[08:19] <davmor2> michi: have a word with sil2100 about your silo QA don't really deal with that side at all
[08:20] <michi> davmor2: OK, thanks for letting me know!
[08:21] <michi> sil2100: ping
[08:21] <michi> Can you help with this one? https://ci-train.ubuntu.com/job/ubuntu-landing-051-2-publish/6/console
[08:27] <sil2100> michi: what's up?
[08:27] <sil2100> Ah, looking in a min
[08:27] <michi> Thanks!
[08:39] <jibel> sil2100, robru the bot should be fixed now, it freaked out on errors 500 and created duplicates
[08:39] <mandel> sil2100, sorry to be a PITA, what was the patter to add in the CI to set the version, something like revno0 or the like, right? I'm updating the symbols files
[08:39] <jibel> I marked silo 8 as ready for QA
[08:42] <mandel> sil2100, no need, I found and old MR with what I needed :)
[09:02] <michi> sil2100: sorry, was off-line for a while
[09:10] <sil2100> michi: reviewing :)
[09:10] <michi> Thanks!
[09:56] <jibel> sil2100, is there just really 1 silo ready for QA in bileto?
[09:56] <jibel> sil2100, or something went wrong with the migration?
[09:59] <sil2100> jibel: no idea...
[10:00] <jibel> sil2100, I think it's the second option, something is wrong
[10:01] <sil2100> jibel: well, what I do know is that bileto says there are 2 landings assigned to silo landing-002
[10:02] <jibel> sil2100, probable one from yesterday and the import
[10:02] <jibel> sil2100, I think you can safely cancel the one that is not granted
[10:04] <sil2100> One of them is landed probably, so I put it to landed
[10:05] <sil2100> jibel: actually, comparing with the spreadsheet, it looks like that indeed
[10:06] <sil2100> When grepping for silos that were marked as ready for QA, none of them are assigned right now anymore
[10:06] <sil2100> jibel: oh, no, wait
[10:07] <sil2100> jibel: ok, bileto really looks somehow b0rken
[10:08] <sil2100> jibel: accoridning to bileto, only a few requests are assigned to silos
[10:19] <sil2100> robru: ^
[10:21] <sil2100> jibel: anyway, trying to manually correct this
[10:26] <sil2100> jibel: could you take care of landing-011?
[10:34] <sil2100> jibel: silo 11 is for the gcc-5 transition
[10:35] <greyback> sil2100: quick question, is the "assign" button like hte old "assign/reconfigure" button in the spreadsheet? I want to add to my silo
[10:36] <sil2100> Yes :)
[10:36] <greyback> cool, thanks
[10:37] <davmor2> sil2100, jibel: just looking through the silos why does silo43 exist?
[10:38] <jibel> sil2100, rvr is on silo 11
[10:38] <jibel> davmor2, what is islo 43?
[10:38] <jibel> silo*
[10:39] <rvr> There is no silo 43 on trello
[10:39] <jibel> davmor2, it's a wily silo
[10:40] <davmor2> jibel: wily and unity7
[10:40] <rvr> No QA Needed some exciting Compiz/Unity7 fixes desktop only Original requestid: 1438117605011
[10:40] <rvr> Ah, wily
[10:44] <jibel> sil2100, now there are requests ready for QA without a silo
[10:44] <sil2100> Yes, as I migrated that data manually
[10:44] <jibel> sil2100, 72 for example
[10:45] <sil2100> jibel: ah, ok, misread what you said
[10:45] <sil2100> Yes, that's what I mentioned above
[10:46] <pete-woods> trainguards: doko seems to have manually uploaded libusermetrics to one of my silos, can you guys strip it out? (https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-049/+packages)
[10:47] <sil2100> pete-woods: it's unrelated to your landing?
[10:47] <sil2100> pete-woods: I can remove it
[10:47] <Laney> I'm guessing it was a typo
[10:47] <Laney> 49 -> 39
[10:47] <Laney> you should check with him
[10:47] <pete-woods> sil2100: completely. I don't have any idea why it's in there
[10:47] <pete-woods> indeed, I already landed the gcc5 fix for libusermetrics to the archive
[10:48] <pete-woods> I've let him know you guys are removing it
[10:49] <Laney> probably want to copy it to 39
[10:49] <Laney> (minus binaries)
[10:49] <pete-woods> while you guys are at it could you also remove the unity-notifications stuff?
[10:49] <pete-woods> it turns out there's nothing wrong with that library
[10:49] <pete-woods> so don't want to make any changes to it
[10:50] <pete-woods> I've just removed the unity-notifications MR from the request (thanks for migrating it to the new system btw)
[10:50] <pete-woods> and run the assign job again
[10:57] <sil2100> pete-woods: ok, will remove those
[10:58] <jibel> sil2100, I'll had some error handling when the silo is missing in bileto but the result won't be nice :)
[10:58] <jibel> at least that'll unblock qa
[11:02] <pete-woods> sil2100: awesome, thanks :)
[11:35] <sil2100> jibel: filled in a bug for this bileto issue
[11:37] <jibel> sil2100, I fixed the bot to not explode when no silo is assigned even if it doesn't really make sense. But at least all the requests are on the board
[11:46] <bzoltan_> sil2100: do you have any idea why the qtbase5-private-gles-dev could be missing from the UITK gles build? https://ci-train.ubuntu.com/job/ubuntu-landing-013-1-build/186/consoleFull ?
[12:10] <jibel> sil2100, why is /home/ubuntu/bin/silo_notifier.run
[12:10] <jibel> oops paste failed
[12:10] <jibel> sil2100, why is https://requests.ci-train.ubuntu.com/#/?req=56 ready for QA while it is for wily?
[12:15] <sil2100> jibel: not sure, it was the same thing on the spreadsheet
[12:17] <jibel> dbarth__, ^ it's yours, do you know?
[12:19] <jgdx> alesage, hey, is the button gray or grayed out?
[12:20] <jgdx> vrruiz^
[12:26] <jgdx> rvr, commented on the silo 33 board item
[12:27] <sil2100> jibel: maybe it was a dual landing silo that got converted
[12:28] <sil2100> Anyway, no landings for now
[12:30] <rvr> jgdx: I see. Let's wait until alesage is awake.
[12:31] <jgdx> rvr, okay
[12:40] <bzoltan_> sil2100: ^^^^ any idea?
[12:45] <alesage> jgdx, rvr hi, when resetting the LTE check item doesn't come back green as I expect
[12:47] <jgdx> alesage, hi! I don't quite follow. The LTE check is unchecked and cannot be checked?
[12:50] <jgdx> alesage, ah, you do a "APN reset" and the LTE comes back unchecked.
[12:55] <alesage> jgdx, correct
[12:55] <sil2100> bzoltan_: let me take a look once I'm back from lunch :)
[12:56] <bzoltan_> sil2100:  OK, thank you
[12:58] <jgdx> alesage, could I have the output of $ /usr/share/ofono/scripts/list-contexts please ?
[13:00] <alesage> jgdx, sent privately
[13:01] <jgdx> alesage, thanks. Is this after you manually checked the lte item?
[13:01] <dbarth__> jibel. sil2100: yes, ours
[13:01] <dbarth__> and yes, it was dual landing converted back to wily only
[13:01] <jibel> dbarth__, okay, deleted from the board
[13:02] <alesage> jgdx, yes--the item shows up green on boot
[13:02] <alesage> jgdx, doesn't seem to appear here, don't know if it's supposed to
[13:02] <alesage> jgdx performing another test
[13:02] <rvr> sil2100: How can I approve silo 11?
[13:03] <sil2100> rvr: in bileto, go to the request that has silo 11, press edit and switch the status from the dropdown list there
[13:03] <sil2100> dbarth__: ok, I'll do it a not-requires-QA then
[13:03]  * sil2100 still fighting his hardware problems
[13:05] <rvr> sil2100: I don't find silo 11 at https://requests.ci-train.ubuntu.com/
[13:05] <sil2100> rvr: yeah, that's a known bug, that's why you should use the dashboard and then click on the requestID there - it'll bring you to the bileto entry
[13:05] <jgdx> abeato, is anyone setting ia contexts' preferred prop to 1 on boot?
[13:05] <rvr> sil2100: Hmm
[13:06] <abeato> jgdx, yes, ofono does that
[13:06] <sil2100>  https://bugs.launchpad.net/bileto/+bug/1480249 <- teh bug
[13:06] <rvr> sil2100: Ah, I see
[13:06] <jgdx> abeato, hmm.. why not immediately after a ResetContexts?
[13:06] <abeato> jgdx, well, you do not use the IA context at that moment
[13:06] <rvr> sil2100: Error submitting form 401
[13:06] <abeato> jgdx, it is used just when ofono starts
[13:07] <jgdx> abeato, okay, thanks!
[13:07] <abeato> jgdx, np
[13:07] <sil2100> rvr: uh
[13:07] <sil2100> o_O
[13:07] <sil2100> Try retrying
[13:07] <rvr> sil2100: Same result, error 401
[13:07] <sil2100> hm, let me try
[13:08] <sil2100> Works here, maybe you don't have teh permissions
[13:08] <sil2100> Let me check that
[13:08] <alesage> jgdx, sent another result privately
[13:09] <sil2100> rvr: is that you? https://launchpad.net/~victor-ruiz+qa
[13:09] <rvr> sil2100: Yes and no
[13:09] <jgdx> alesage, right. That's currently due to design.
[13:09] <sil2100> Give me your launchpad ID
[13:09] <rvr> sil2100: It's an account I created for some tests
[13:09] <rvr> sil2100: ~vrruiz
[13:10] <sil2100> rvr: added, try switching it to something else now
[13:10] <sil2100> You might need to re-log to bileto
[13:11] <rvr> sil2100: Ack
[13:11] <alesage> jgdx one more note on the trello card
[13:12] <jgdx> alesage, it's a normal sdk button :P
[13:13] <rvr> sil2100:
[13:13] <alesage> jgdx, ok thanks for clarifying :)
[13:13] <rvr> sil2100: I still see Error 401, but the status is QA granted.
[13:13] <sil2100> bzoltan_: one more moment, now still in a meeting ;p
[13:13] <sil2100> rvr: I set it to QA granted myself
[13:13] <sil2100> rvr: anyway, poke robru once he's up, it's his stuff ;p
[13:14] <jgdx> alesage, the grayed out one is substantially less opaque. Do you want me to file a bug against the uitk+ux?
[13:14] <rvr> sil2100: Ok, thanks anyway
[13:14] <rvr> robru: Where is the test plan of bileto? }:)
[13:15] <alesage> jgdx whether or not that's a bug is a grey area for me ;P
[13:15] <rvr> robru: I have error 401 trying to approve a silo
[13:17] <jgdx> alesage, lol
[13:22] <alesage> silo ppl I got rvr's same 401 whilst approving 33 << sil2100
[13:23] <sil2100> alesage: let me check if you're added to the team too
[13:23] <alesage> sil2100, ah
[13:23] <sil2100> alesage: hm, strange, you're already added - did you check the 'ci-train-users' checkbox when logging into bileto?
[13:24] <alesage> sil2100, don't think so
[13:24] <alesage> sil2100, will log out and repeat
[13:24] <sil2100> alesage: log out and log in while checking the team membership :) Maybe that will help
[13:25] <rvr> sil2100: Ahh, I didn't check that box
[13:25] <sil2100> Ah ha!
[13:25] <sil2100> Ok, so all is clear
[13:25] <rvr> sil2100: Yeah, seems ok now
[13:28] <kenvandine> sil2100, i just noticed bileto doesn't show which silo has a landing, is there a place i can file a bug about that?
[13:28] <sil2100> There is a bug for that already ;)
[13:28] <kenvandine> great
[13:29] <sil2100> https://bugs.launchpad.net/bileto/+bug/1480249
[13:29] <kenvandine> sil2100, oh, is that just for landings from the spreadsheet?
[13:29] <kenvandine> cool
[13:30] <kenvandine> alesage, are you still trying to approve silo 33?
[13:30] <alesage> kenvandine, you caught me still trying to approve silo 33
[13:30] <kenvandine> :)
[13:30] <alesage> sil2100, I'm finding that setting the combo and pressing save has no effect :(
[13:31] <sil2100> bzoltan_: ok, on your request now
[13:31] <alesage> sil2100, but weirdly some data in the form is missing
[13:32] <sil2100> alesage: uh?
[13:32] <sil2100> kenvandine: I hope it's only for those entries
[13:34] <kenvandine> sil2100, alesage is looking at req=28
[13:34] <kenvandine> since there's no easy map of 33 to 28 :)
[13:35] <alesage> sil2100, FWIW http://i.imgur.com/KBm2GhM.png
[13:39] <jhodapp> sil2100, are you able to do a source package upload to a silo?
[13:39] <sil2100> jhodapp: sure
[13:40] <jhodapp> sil2100, alright, let me get things situated and I'll ping you with the details shortly
[13:41] <sil2100> bzoltan_: hey! What did you mean exactly? I only see that your -gles packages failed to build because of some qmake error
[13:41] <sil2100> bzoltan_: did I miss something?
[13:43] <bzoltan_> sil2100:  where do you see that? I see there missing dependencies
[13:43] <sil2100> https://launchpadlibrarian.net/213129613/buildlog_ubuntu-wily-i386.ubuntu-ui-toolkit-gles_1.3.1584%2B15.10.20150730-0ubuntu1_BUILDING.txt.gz <- I see this
[13:44] <sil2100> Project ERROR: Project has no top-level .qmake.conf file.
[13:44] <sil2100> And because of this probably the dh_auto_configure fails
[13:45] <kenvandine> alesage, looks like you created 3 new landings with qa granted?
[13:45] <kenvandine> but all blank
[13:45] <bzoltan_> sil2100: ehh... you look at the actual build log file ... bingo. Sorry, let me try to parse that
[13:45] <alesage> kenvandine, landings for everyone!
[13:46] <sil2100> bzoltan_: yeah ;) When the trains says that there's a build failed, I usually check the logs then, since the train doesn't parse those in any way
[13:46] <bzoltan_> sil2100: true, thank you
[13:46] <sil2100> alesage, kenvandine: I have a bug for that too ;)
[13:46] <kenvandine> sil2100, ok... so how do we mark it as qa verified?
[13:46] <kenvandine> qa granted, whatever
[13:46] <sil2100> alesage, kenvandine: https://bugs.launchpad.net/bileto/+bug/1480251
[13:47] <sil2100> kenvandine: ok, let me just do that
[13:47] <sil2100> But remember, no wily publishings for now!
[13:47] <kenvandine> oh?
[13:47] <kenvandine> why not?
[13:47] <kenvandine> are we in a freeze?
[13:47] <ogra_> yes
[13:47] <sil2100> kenvandine: didn't you see doko's e-mail and my follow up?
[13:47] <ogra_> gcc
[13:47] <kenvandine> oh... no i didn't
[13:47] <kenvandine> damn
[13:47] <sil2100> gcc-5 is landing, we don't want to land anything that might require a re-build
[13:49] <jhodapp> sil2100, shared the source package files with you via google drive
[13:49] <jhodapp> sil2100, this needs to go into silo 38
[13:50] <kenvandine> sil2100, ok... so silo 33 will need a rebuild after that lands
[13:53] <sil2100> jhodapp: ok, will upload in a sec
[13:53] <jhodapp> sil2100, thanks!
[13:58] <sil2100> jhodapp: uploaded! Just a reminder: you need to change UNRELEASED to wily (or vivid, depending where you want to build the package)
[13:58] <sil2100> I changed it for you :)
[14:00] <jhodapp> sil2100, oh didn't know that bit...I was told to leave it as UNRELEASED
[14:04] <pmcgowan> jibel, the trello cards have nice bug references but the links are not to launchpad but rather back to trello
[14:04] <pmcgowan> can that be fixed?
[14:12] <jibel> pmcgowan, yeah trello interprets #NNNN as its own references. It can be fixed.
[14:12] <jibel> and will be
[14:15] <pmcgowan> jibel, thanks, I find it convenient
[14:15] <greyback_> sil2100: hey, my silo11 has been acked by QA. I clicked the publish link but was told I don't have right to do that. That expected?
[14:16] <greyback_> note, it is a vivid-overlay only silo
[14:20] <jhodapp> sil2100, can you let me know when silo 38 is ready? anything else that I need to do?
[14:30] <sil2100> pmcgowan: I might be a bit late to the meeting, start without me - I'll join in some mins
[14:31] <pmcgowan> oh I am late as well
[14:37] <Chipaca> has the train changed to run tests as root at any point since .. april?
[14:37] <Chipaca> s/tests/builds/
[14:40] <Chipaca> trainguards ^ i guess that's a question for you?
[14:40] <sil2100> Chipaca: why do you ask? The train builds everything as the same user as always
[14:41] <sil2100> I mean, building the source packages, as the binary packages are being built in the PPA
[14:41] <Chipaca> sil2100: and that user is not root
[14:41] <Chipaca> true
[14:41] <Chipaca> i'm going to blame tvoss with confusing me on this issue :)
[14:41] <Chipaca> sil2100: sorry, and thank you
[14:42] <sil2100> ;) No worries
[15:16] <jhodapp> sil2100, any update on silo 38?
[15:16] <greyback_> trainguards: any reason I can't publish silo11? It's vivid+overlay, ACKed by QA.
[15:17] <sil2100> greyback_: only trainguards can publish, and we're in a freeze right now
[15:17] <sil2100> See topic
[15:18] <greyback_> sil2100: I saw wily gates closed, but not vivid, hence question
[15:18] <sil2100> Ah! Overlay! Ok, publishing in a momento :)
[15:19] <greyback_> sil2100: thanks man, sorry for poking
[15:19] <jhodapp> sil2100, thanks :)
[15:23] <davmor2> sil2100: robru: I'm trying to set silo 008 to qa granted but I'm getting a 401 error do I need to be in a group or anything that I'm not in?
[15:23] <sil2100> davmor2: sure, I'll add you, you need to re-login once that's done
[15:24] <davmor2> sil2100: no worries
[15:40] <davmor2> sil2100: did you add me yet?
[15:41] <jibel> pmcgowan, lp friendly bug link in trello cards https://trello.com/c/Fz4noUoF/2088-38-ubuntu-landing-047-systemd-anpok
[15:41] <jibel> enjoy
[15:42] <pmcgowan> now thats service :)
[15:43] <sil2100> davmor2: I thought I did
[15:43] <sil2100> oh, I got a timeout
[15:45] <rvr> mzanetti: Approving silo 35
[15:47] <davmor2> sil2100: got it now thanks :)
[15:49]  * davmor2 waits on the bot to tell me it is approved before annoying sil2100  ;)
[15:49] <sil2100> uh
[15:50] <rvr> Hmm
[15:50] <sil2100> robru: remember - don't publish anything for wily or dual-landing until doko says the gcc-5 copying is done
[15:51] <davmor2> \o/ silo 008 qa granted \o/ sil2100 it's my first one through bileto leave me alone :P
[15:52] <rvr> davmor2: Congratulations, you've unlocked the bileto achievement!
[15:53] <davmor2> rvr: :)
[16:00] <AlbertA> davmor2: yey!
[16:05] <AlbertA> trainguards: ^ JSONDecodeError?
[16:05] <sil2100> AlbertA: looking
[16:06] <AlbertA> sil2100: ack thanks
[16:07] <sil2100> AlbertA: looks like an error connecting to bileto... not anything we should be worried about
[16:07] <sil2100> robru: ^ could you check https://ci-train.ubuntu.com/job/ubuntu-landing-008-2-publish/113/console ?
[16:08] <robru> sil2100: looks like lplib is not returning values. Lp down?
[16:09] <sil2100> Works, maybe it was transient?
[16:13] <robru> sil2100: jenkins never parses json from bileto, jsondecodeerror would never come from bileto. bileto errors aren't fatal in jenkins. jsondecodeerror means lplip is failing
[16:18] <pmcgowan> robru, sil2100 hey so I am confused, are all the silos that currently say wily and vivid blocked for the forseeable future?
[16:19] <robru> pmcgowan: yes.
[16:19] <pmcgowan> why are there so many dual landings queued if that no longer works?
[16:19] <pmcgowan> seems folks didnt get the message
[16:19] <robru> pmcgowan: because it only just started
[16:19] <sil2100> pmcgowan: not for long
[16:19] <robru> pmcgowan: if something needs to land urgently we can change it to vivid-only
[16:20] <sil2100> I mean, the freeze we have right now is only temporary
[16:20] <robru> sil2100: do you have an ETA on that?
[16:20] <pmcgowan> yeah but once gcc 5 is on nothing dual lands again right?
[16:20] <sil2100> Since doko is copying packages to the archive, we can't land anything before this finishes as we need to rebuild those silos that have been released, so that the new wily ones build against gcc-5
[16:20] <robru> pmcgowan: depends, lots of things aren't written in C that could still dual land after the transition
[16:21] <sil2100> pmcgowan: yeah, at least for those projects that don't need gcc-5 specific changes and had to branch
[16:21] <mzanetti> rvr, thanks
[16:21] <pmcgowan> I see
[16:21] <robru> pmcgowan: it would be up to the landers to know what language their projects are written in ;-)
[16:21] <pmcgowan> so it depends
[16:22] <pmcgowan> they are almost all c so not sure I get it
[16:22] <AlbertA> robru: pmcgowan: but if the project builds in both GCC5 and GCC4.9 can we dual land?
[16:22] <pmcgowan> sil2100, robru but you are saying even C projects that didnt need specific changes they are fine
[16:23] <robru> pmcgowan: AlbertA: that I'm not actually sure
[16:23] <sil2100> Most of the cases, yes
[16:23] <pmcgowan> whats the criteria then
[16:23] <AlbertA> tvoss: ^
[16:24] <sil2100> Libraries can have problems for instance, since a library that uses symbols can have problems maintaining them for both gcc-4.9 and gcc-5 at once
[16:25] <sil2100> But some projects can just deal with symbol files getting removed and replaced by abi-compliance-checker and shlibs, but not sure if that's an official way of dealing with things
[16:27] <sil2100> Since if the ABI changes between gcc-4.9 ad gcc-5 in a library, basically you just need to bump the soname for the library - thus making it un-dual-landable anymore...
[16:27] <sil2100> Anyway, the gcc-5 ABI changes are really a big pain in the ugh
[16:28] <pmcgowan> sil2100, it sounds to me the answer is effectively no you cannot expect to dual land
[16:28] <pmcgowan> and I suspect most of the queued silos are dead in the water right now
[16:28] <pmcgowan> or we dont know
[16:29] <sil2100> Let's wait for the transition to finish, I wouldn't say it's as bad as that, but we need to remember some components will not be dual-landable
[16:29] <pmcgowan> sil2100, how will we know? wait for stuff to break?
[16:43] <robru> pmcgowan: this is the time-honored tradition of the train guard ;-)
[16:43] <robru> pmcgowan: just kidding. if there's a way to predict, then we should do that. but I don't know what it is
[16:44] <sil2100> pmcgowan: sorry, was busy with something - but generally we'll know after we have all the projects released, we'll know for which projects the ABI changed and which projects need to be rebuilt
[16:44] <sil2100> But generally most of those things happened already in silo 16
[16:44] <sil2100> tvoss and slangasek were overseeing that
[16:47] <slangasek> robru, sil2100: gcc5 transition only affects the ability of libraries to dual-land; I don't know what's in the current set of silos, but there are a good number of non-libraries around
[16:48] <robru> slangasek: we ship things that aren't libraries?
[17:27] <sil2100> robru: as per doko's e-mail, copies are over - I suppose some of the silos that are ready might need to be re-built
[17:27] <sil2100> If not all of them
[17:27] <robru> sil2100: great. yeah probably all of them
[17:29] <sil2100> I'll be EODing in a minute, I'll just send out the e-mail
[17:40] <robru> slangasek: so what's the scoop, can I free silo 16 then?
[17:51] <cjwatson> robru: err, C++ surely, not C :)
[17:53] <cjwatson> unless I'm way out of touch, things written in C that don't link to C++ libraries are unaffected by a libstdc++ change
[17:54] <robru> cjwatson: nope, I am the one that's out of touch. Never written a line of C or C++ in my life ;-)
[17:56] <dobey> of all the requests on the ci train page, which are dual landing, very few of them will be able to continue being dual landings
[17:58] <dobey> hrmm
[17:58] <dobey> there are a couple on the list for ubuntu-rtm; i guess those can just be destroyed?
[17:59] <robru> dobey: yeah. Mark the status as 'Abandoned' to make them disappear.
[17:59] <dobey> or something is just really messed up
[18:00] <robru> dobey: what's messed up?
[18:01] <dobey> well now they seem to be gone; but one had a bunch of unrelated branches listed with it, that are also listed in another request
[18:02] <robru> dobey: the branches listed in the requests were copied verbatim from the spreadsheet, as far as I know nothing got corrupted in the copy
[18:02] <robru> dobey: if you see a mistake, please fix it.
[18:03] <dobey> well, as i said, that reuqest is gone now; it was disappeared from the view while i was poking about to see what might have happeened to cause that
[18:04] <robru> dobey: I marked a couple as Abandoned while we were talking: https://requests.ci-train.ubuntu.com/#/?q=Abandoned
[18:06] <dobey> robru: yeah; https://requests.ci-train.ubuntu.com/#/?req=16 is the one i was saying looked messed up. notice how the listed MPs have nothing to do with signon-apparmor-extension, or the seed
[18:07] <robru> dobey: spreadsheet row 6 has the same values.
[18:07] <dobey> weird
[18:07] <robru> dobey: probably some spreadsheet issue that just got copied over.
[18:08] <robru> dobey: some of those MPs are 'WIP' and one even was deleted so I think it's safe to say that that's not something that's ready to land.
[18:08] <dobey> yeah; looks like someone/something broke the spreadsheet
[18:09] <dobey> yeah, and a couple of them are in https://requests.ci-train.ubuntu.com/#/?req=15
[18:09] <dobey> looks like a very old landing too
[18:16] <AlbertA> trainguards: so any idea on the JSONDecodeError in silo 8?
[18:17] <robru> AlbertA: ah sorry, I told sil it was transient, I don't know why he didn't retry.
[18:18] <robru> AlbertA: ok published
[18:18] <AlbertA> robru: thanks!
[18:18] <robru> AlbertA: you're welcome
[18:19] <robru> brb
[18:42] <kgunn> trainguards so i've kinda been watching silo 35, i think it's had a QA +1 since my morning....wondering why it's not moving?
[18:42] <robru> kgunn: looking
[18:43] <robru> kgunn: yeah, so wily did the massive gcc5 transition today
[18:43] <robru> kgunn: I dont have a very good understanding of it, but apparently if your silo uses C++ it needs to be rebuilt. also there's some talk that dual builds will no longer work
[18:45] <robru> kgunn: also the dashboard isn't doing a good job of highlighting what can be published, I should fix that...
[18:46] <dobey> yeah, unity8 can't do dual landings any more
[18:55] <kgunn> typical
[18:57] <kgunn> robru: so we had that unity8 silo up and was ready for qa for a couple of days, thinking we'd make it in before this happened
[18:58] <kgunn> robru: so what's the recommended approach here ?
[18:58] <kgunn> i mean it's been tested on vivid+o....so we don't want to repeat
[18:58] <kgunn> the testing part
[18:58] <kgunn> but do we need to scrap that silo and do src sync landing ?
[19:04] <dobey> kgunn: i think it's time unity8 started using separate upstream source trees for wily and vivid
[19:05] <kgunn> well obviously dobey, but like i said the guys had this in the pipe for a while...pipe just slow
[19:05] <kgunn> dobey: actually for unity8 maybe not
[19:05] <dobey> yeah, and we're all going to have to waste some time syncing trunk with manual uploads to wily
[19:05] <kgunn> i don' tthink there is a reason there
[19:05] <dobey> why not?
[19:06] <dobey> a straight copy of the source package from one archive to the other, is incorrect
[19:06] <renato___> trainguards, I am having problems to build the address-book-service on silo 34 it is saying that there is a missing version
[19:06] <dobey> because then you'll have different binaries with the same version
[19:06] <kgunn> dobey: the bins would be rebuilt
[19:07] <kgunn> i'm talking source
[19:07] <dobey> kgunn: yes, and thus they would be different
[19:07] <boiko> robru: all the "~gcc5" stuff missing from changelogs, is that because it was done without merging contents back to trunk? or still in proposed?
[19:07] <kgunn> you're talkign bins
[19:07] <dobey> and thus the version numbers would be the same, but they would mean different things
[19:07] <dobey> kgunn: i'm takling about ubuntu archive policy
[19:08] <kgunn> dobey: nope, cause you'd have 15.10 on one and 15.04 on the other ....wouldn't we ?
[19:08] <dobey> no
[19:08] <robru> kgunn: so, your vivid packages that have been QA'd can be copied to the overlay ppa
[19:08] <dobey> not if you copy the source packages
[19:08] <robru> kgunn: but yeah, for the wily half of your landing, that's in trouble
[19:08] <dobey> the only way you'd have that, would be if you had two separate upstream branches, and did separate landings into both
[19:09] <robru> dobey: I'm not sure what you're talking about with the version numbers. in dual silos it makes version-appropriate copies and rebuilds them.
[19:09] <kgunn> yeah
[19:09] <kgunn> https://launchpad.net/ubuntu/+source/unity8
[19:09] <dobey> robru: that is nuts
[19:09] <kgunn> see the package names
[19:10] <robru> dobey: what, more nuts than having the same version number with different binaries?
[19:10] <kgunn> dobey: why is that nuts ? the source is what matters....all i care about as a dev is to translate back to an acutal commit
[19:10] <kgunn> on a source file
[19:10] <dobey> robru: probably equally as nuts;
[19:10] <robru> dobey: see the PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-035/+packages versions have "15.10" or "15.04" as appropriate, with same source contents otherwise, but separately built binaries
[19:11] <dobey> kgunn: how do you translate back to a commit if there isn't a commit for that version?
[19:12] <kgunn> if i know the unity8 version, and there's one src branch used to feed that, i can see when it's released
[19:13] <dobey> but the version in the overlay PPA has no direct connection to the upstream branch. there's no commit to debian/changelog with the 15.04 version in it, and there's no tag on the branch for that release, is there?
[19:14] <robru> dobey: so you just have to know to s/15.04/15.10/ and then you find the commits just fine
[19:14] <kgunn> dobey: actually looks like you and i are wasting bits chatting about it
[19:14] <kgunn> i think michael prepped to stage
[19:14] <kgunn> https://code.launchpad.net/~ubuntu-branches/ubuntu/wily/unity8/wily-proposed
[19:15] <robru> kgunn: let me know if you want me to copy those vivid packages to the overlay ppa
[19:15] <kgunn> robru: yeah, for vivid+overlay please do
[19:15] <robru> kgunn: ok will do
[19:15] <kgunn> robru: and i guess we'll just do a seperate landing for wily on monday or something ?
[19:15] <robru> kgunn: yeah I'm not sure exactly what needs to be done for wily, sorry
[19:16] <robru> kgunn: I guess you want to merge those branches to trunk?
[19:16]  * kgunn plans onletting dust settle a little
[19:16] <robru> without releasing to wily
[19:16] <dobey> certainly needs rebuilt against gcc5 stuff
[19:16] <kgunn> no one disputes that ?
[19:17] <kgunn> robru: yeah, i gues we'll catch up to wily after the settling
[19:20] <robru> kgunn: alright sorry for the hassle
[19:20] <kgunn> robru: hey man, thanks for all the help...not your fault, we move slow, qa is slow, just victim of transition and timing
[19:21] <robru> kgunn: you're welcome!
[19:26] <dobey> trainguards, cihelp: so what's the best way to reconcile changes made in manual uploads, back into our trunk?
[19:26] <robru> dobey: get the diff from launchpad, commit it to your trunk
[19:28] <robru> dobey: eg: https://launchpadlibrarian.net/211730328/accounts-qml-module_0.5%2B15.04.20150415.1-0ubuntu1_0.5%2B15.04.20150415.1-0ubuntu2~gcc5.1.diff.gz
[19:28] <robru> just apply it right to trunk like a patch
[19:28] <dobey> right
[19:38] <slangasek> robru: if the landing gates are blocked, is there a hurry to free silo 16?  I /believe/ it's all been copied, but I didn't do the copying, I think doko did; we certainly don't want to lose anything from there and have to rebuild it
[19:40] <robru> slangasek: I heard we were unblocked. I guess there's no hurry, just curious.
[19:43] <slangasek> robru: hmm, who said we were unblocked?  It's possible that we're ok to land things on top of gcc5 now, but I didn't realize that call had been made yet
[19:43] <robru> slangasek: sil said there was an email from doko, I didn't actually verify myself
[19:44] <robru> slangasek: oh I misread
[19:44] <robru>  <sil2100> robru: as per doko's e-mail, copies are over - I suppose some of the silos that are ready might need to be re-built
[19:44] <slangasek> aha, yes
[19:44] <robru> slangasek: "copies are over" but not necessarily unblocked
[19:44] <slangasek> so that means silos 39 and 16 have been copied into -proposed
[19:56] <charles> robru, if I add another MR to a landing request, how do I reconfigure the silo -- do I go through the assignment steps again?
[19:56] <robru> charles: yep, the assignment will detect the silo is already assigned and reconfigure it.
[19:56] <charles> robru, great, thanks
[19:56] <robru> charles: you're welcome
[19:57] <charles> thought I'd ask and avoid assigning a second silo :)
[19:57] <robru> charles: no worries, apologies it's not clear. Was trying to save a bit of space rather than have "Assign/Reconfigure" repeated a thousand times.
[20:13] <jhodapp> robru, is there a way of getting around this error without Mirv being back (I'm assuming it's his key that it's complaining about here. I made sure that my public key has been uploaded)? https://ci-train.ubuntu.com/job/ubuntu-landing-038-1-build/44/console
[20:14] <jhodapp> robru, I signed the package today, but it's complaining about the signature from the 14th
[20:16] <robru> jhodapp: uh, your package failed to build on amd64. nothing to do with gpg signatures.
[20:17] <robru> jhodapp: scroll further back in the log. it shows the links to the PPA build failures.
[20:22] <jhodapp> robru, ah ok yeah missed that
[20:22] <jhodapp> thanks
[20:22] <robru> jhodapp: you're welcome
[20:22] <jhodapp> I've been working with signatures on a package lately, so it led me to a red-herring :)
[20:24] <jhodapp> robru, would my silo be gcc5 based now?
[20:25] <robru> jhodapp: sorry the details about that aren't very clear to me. The build log should say what version of gcc it's installing though
[20:25] <jhodapp> ah good point, yeah it's in front of me
[20:25] <jhodapp> 4.9
[20:26] <jhodapp> I wonder if dbus-cpp is gcc5 compiled already in that silo...there's some compat issues that seem odd that shouldn't have changed
[20:26] <jhodapp> robru, anyway thanks, will need to speak to tvoss
[20:26] <robru> jhodapp: actually the log seems to show it installing both 4.9 and 5. I'm not sure how to know which it's using.
[20:27] <tvoss> jhodapp, is that a wily silo?
[20:27] <jhodapp> yes
[20:27] <renato___> chihelp, I am having problems to build silo 34 it  keeps saying that there a missing version
[20:27] <tvoss> jhodapp, if so: does it have the latest fixes to remove the gcc4.9 pinning?
[20:27] <renato___> but there is nothing on project trunk
[20:28] <tvoss> renato___, is that wily silo?
[20:28] <renato___> tvoss, yes
[20:28] <jhodapp> tvoss, it does not
[20:28] <tvoss> jhodapp, here we go :)
[20:28] <tvoss> renato___, which project is that?
[20:28] <renato___> tvoss, it says: address-book-service 0.1.1+15.10.20150730-0ubuntu2~gcc5.1 is missing
[20:28] <jhodapp> tvoss, I saw a branch from you for getting rid of the 4.9 dependency...seems maybe I just need to merge with that yes?
[20:28] <tvoss> jhodapp, yup, very likely
[20:29] <tvoss> robru, I think you have to help renato___ in getting the version bumped as he is likely overridden by a package uploaded to gcc5 silo, which is now in wily proposed
[20:29] <jhodapp> tvoss, alright...can you ping me for any future branches or request a code review directly from me...I didn't get any emails about the request for review
[20:30] <jhodapp> tvoss, and thanks for preparing that
[20:31] <robru> renato___: you need to sync the distro upload back to your trunk.
[20:31] <renato___> robru, how I do that?
[20:31] <tvoss> jhodapp, I see you are the media-hub driver, probably some launchpad settingthat is missing for you to receive mp mails
[20:31] <robru> renato___: you have to get the diff from the distro release and commit it to your trunk.
[20:32] <tvoss> jhodapp, I get a bunch of mails for mps every day, actually have a filter for that setp
[20:32] <renato___> robru, where I can get this diff? (apt-get source???)
[20:32] <robru> renato___: eg this diff: http://launchpadlibrarian.net/213228395/address-book-service_0.1.1%2B15.10.20150730-0ubuntu1_0.1.1%2B15.10.20150730-0ubuntu2~gcc5.1.diff.gz
[20:32] <renato___> robru, ok thanks
[20:32] <robru> renato___: the package source page always has these diffs: https://launchpad.net/ubuntu/+source/address-book-service
[20:33] <robru> renato___: you're welcome
[20:33] <renato___> robru, nice to know, thanks
[20:37] <robru> charles: so this silo 8, this is all ok with the gcc5 transition? not going to interfere?
[20:39] <charles> robru, shouldn't interfere. I already landed the gcc5 fixes for pay-service yesterday
[20:39] <robru> charles: k, thanks
[20:39] <charles> dobey: ^
[20:40] <dobey> yes it's good
[20:41] <dobey> oh
[20:42] <dobey> i guess it was acked then
[20:44] <jhodapp> tvoss, yeah, not sure
[20:51] <robru> alright I'm off for a bit of a longer lunch, bbl
[21:26] <boiko> robru: so, for the ~gcc5 entries, do I need to update the trunk of the projects I am landing stuff in?
[22:14] <robru> boiko: yeah you'll have to sync the diff to trunk manually
[22:14] <boiko> :/
[22:26] <robru> boiko: I'm actually afk, can you file a bug against lp:cupstream2distro that says "feature request: sync distro back to trunk". It's a reasonable feature we need and shouldn't be hard to implement.
[22:28] <boiko> robru: sure
[22:29] <robru> boiko: thanks. Now that bileto is live i should have more time to fix little annoyances like this.
[22:34] <boiko> robru: https://bugs.launchpad.net/cupstream2distro/+bug/1480477
[22:37] <robru> boiko: thanks
[22:38] <boiko> robru: np
[23:25] <renato___> robru, now I getting the same error for address-book-app, but the diff is big: https://launchpad.net/ubuntu/+source/address-book-app/+changelog
[23:26] <renato___> robru, should I merge it manually again?
[23:27] <robru> renato___: yeah it will have to be manual
[23:27] <renato___> robru, what causes that?
[23:28] <robru> renato___: if somebody makes a manual upload to distro without using the train, then it doesn't get automatically merged to the trunk.
[23:28] <robru> renato___: http://launchpadlibrarian.net/213228380/address-book-app_0.2%2B15.10.20150701-0ubuntu1_0.2%2B15.10.20150731-0ubuntu2~ppa1.diff.gz most of this diff is just translations, other than the translations and the changelog there's only really one line in this diff
[23:28] <robru> renato___: and the translations are probably already in your trunk. so you really just need the changelog and that one line at the very bottom
[23:30] <renato___> robru, ok, pushing
[23:30] <renato___> thanks again
[23:30] <robru> renato___: you're welcome