[02:10] <imgbot> [03:40] <imgbot> [03:40] <imgbot> [07:02] <oSoMoN> jibel, good morning! ubuntu-rtm/landing-008 has incorrectly appeared in the "Need QA Sign-off" lane, it’s not ready for sign-off, can it be removed?
[07:03] <oSoMoN> (the "Testing pass" column of the CI train spreadsheet had "Yes" with no valid image number, tester or device)
[07:54] <jibel> oSoMoN, good morning, done
[07:55] <oSoMoN> thanks!
[09:00] <sil2100> huh, it's snowing here
[09:13] <oSoMoN> jibel, how likely is it that silo 9 will be validated by QA today?
[09:14] <sil2100> seb128: silo assigned, but coordinate with Mirv as he has silo 18 with qt as well that's fixing a critical touch blocker (but it's still in the works)
[09:15] <seb128> sil2100, yeah, cf #ubuntu-desktop backlog ;-)
[09:15] <seb128> sil2100, thanks
[09:16] <jibel> oSoMoN, it should not be a problem to verify it today unless several RTM silos show up
[09:16] <oSoMoN> cool
[09:16]  * oSoMoN crosses fingers
[09:18] <sil2100> seb128: ah :) Yeah, then all's ok
[09:20] <dbarth> sil2100: can i send you a source package for the oxide silo? (forcing the use of gcc-4.8); i can't dput it into our current ppa, because of a later version
[09:21] <sil2100> dbarth: could you upload it somewhere to people.canonical.com and send me the link? :)
[09:21] <sil2100> btw. you want to force 4.9 not 4.8, right?
[09:24] <seb128> sil2100, Mirv, how can I upload to a CI train ppa?
[09:25] <seb128> dput got rejected saying I don't have upload rights
[09:25] <seb128> shouldn't coredev be authorized?
[09:26] <sil2100> seb128: geh, yeah, they should, but I think it's not the case right now
[09:26] <sil2100> slangasek: ping
[09:26] <seb128> slangasek is likely sleeping at this hour no?
[09:27] <sil2100> asac: hey, are you around? Could you add ~ubuntu-core-dev do the ~ci-train-ppa-service team?
[09:27] <dbarth> sil2100: i want to force to 4.8, as 4.9 produces code that provides an incorrect rendering
[09:27] <sil2100> dbarth: ah, I thought it was the other way around, ok
[09:28] <sil2100> dbarth: that's for RTM?
[09:28] <sil2100> seb128: yeah, but he tends to be around at different hours by accident ;)
[09:29] <seb128> sil2100, :-)
[09:30] <dbarth> seb128: yes
[09:30] <Mirv> seb128: if you can push your changes already to lp:~kubuntu-packagers/kubuntu-packaging/qtbase-opensource-src (packaging branch only) I can include it in my next 018 silo upload
[09:30] <asac> sil2100: does slangasek agree?
[09:30] <sil2100> seb128: sadly, I am not the admin for this team, so not much we can do besides waiting or uploading for you
[09:31] <asac> sil2100: asking because in the past we got push back when trying to add core-dev to teams because of mail-spamming etc.
[09:31] <Laney> seb128: want a sponsor? ;-)
[09:31] <sil2100> asac: I suppose so, it was his proposition to give all core-devs the power to publish through the train - not sure about the spamming though
[09:32] <sil2100> asac: ok, let's wait for slangasek
[09:32] <asac> sil2100: lets double check. yeah
[09:32] <asac> let me know if you got the info
[09:32] <sil2100> Sure, thanks
[09:41] <seb128> Laney, if you want to dput people.canonical.com/~seb128/qtbase-opensource-src_5.4.1+dfsg-2ubuntu4.dsc to https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-012 please do :-)
[09:41] <seb128> thanks
[09:42] <Laney> okay
[09:42] <seb128> thanks
[09:42] <Laney> or asac could just add you individually ...
[09:45] <asac> who needs adding short term?
[09:46] <Laney> seb128
[09:46] <Laney> think he went afk though so I'll still dput this oen
[09:46] <asac> hmm. seb was trained and enabled for ci train, no?
[09:46]  * asac adds him
[09:46] <asac> yeah he left the team :P
[09:46] <asac> he is deactivated
[09:47] <Laney> all this team lets you do is dput to the PPAs, everything else is granted by core-dev
[09:47] <Laney> AFAIK
[09:47] <asac> right, but i think seb128 opted-out given that he is a deactivated member
[09:47] <Laney> nod
[09:47]  * asac will activate him
[09:47] <Laney> maybe wait for confirmation :)
[09:47]  * asac thinks he can deactivate if he doesnt like to be actiavted
[09:47] <asac> hehe
[09:47] <asac> seb128 reactivated :P
[09:49] <ogra_> iirc slangasek wanted some kind of separate group or some such since the mail spam you get is enormous ...
[09:49] <ogra_> (but i might mis-remember)
[09:51] <Laney> I never remember how launchpad mail works
[09:51] <Laney> doesn't core-dev having an email address set mean that they'll get filtered out?
[09:52] <ogra_> i think thats the question where the discussion ended last time :)
[09:54]  * Laney asked in #lp
[09:59] <Laney> Should be fine from the spam POV
[10:00] <ogra_> awesome
[10:01] <ogra_> then we should simply add it
[10:02] <sil2100> I would opt for that, yes
[10:02] <Laney> I think there's some policy issue around non-staff and de-virt PPAs
[10:02] <Laney> Someone with appropriate authority should rule it's okay. :)
[10:03] <sil2100> I think this was already discussed on other channels :)
[10:07] <dbarth> sil2100: quick update; dpkg-buildpackage is still running on the 350Mb+ tarball of oxide... :/ i will upload that to you just next
[10:08] <sil2100> dbarth: yeah, I know how that looks, I had to build the source package of oxide a few times already
[10:57] <dbarth> sil2100: ping; transfer ready
[11:02] <sil2100> dbarth: where did you upload it? :)
[11:02] <dbarth> sil2100: i pinged you on another channel
[11:02] <sil2100> Ah!
[11:04] <joc_> sil2100: hi
[11:04] <sil2100> joc_: hey
[11:05] <joc_> sil2100: i've been asked by the product managers to prep some phones with silo 4 however it looks like it needs a rebuild
[11:05] <joc_> sil2100: is there some way to get that done?
[11:06] <sil2100> joc_: yeah, it seems some other ubuntu-keyboard landed in the meantime - I could try rebuilding it for bfiller
[11:06] <sil2100> bfiller: you around? Any objections on rebuilding silo 4?
[11:08] <ogra_> imgbot, status 156 vivid
[11:09] <imgbot> Status: succeeded, Started: 2015-03-31 02:02:06 UTC, Finished: 2015-03-31 03:01:42 UTC
[11:09] <imgbot> Build URL: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-touch/+build/23785
[11:09] <imgbot> Changelog: http://people.canonical.com/~ogra/touch-image-stats/156.changes
[11:20] <pete-woods> trainguards: hi folks! could I get vivid silo 6 reconfigured please? I've added a new project (https://code.launchpad.net/~unity-api-team/libqtdbusmock/ofono-urfkill/+merge/246916) to the list of MRs
[11:21] <sil2100> pete-woods: on it!
[11:21] <pete-woods> sil2100: thanks!
[11:21]  * sil2100 off to prepare lunch
[11:37] <rvr> dbarth: alex-abreu: Silo 5 (twitter pic sharing) is tested and approved.
[11:45] <dbarth> rvr: cool; thanks
[11:46] <Mirv> dbarth: MP needs top-approve https://code.launchpad.net/~abreu-alexandre/unity-webapps-qml/rtm-tools-api/+merge/253530
[11:52] <seb128> asac, thanks
[11:53] <seb128> asac, Laney, I probably opted out because that team membership generates email spam for ppa build failures, etc
[11:53] <Laney> yeah I shitcanned those immediately
[12:08] <asac> right so thats why we shouldnt add ubuntu-core-dev to this team ... they will come back telling us to undo because of mailspam 99.99%
[12:08] <asac> :)
[12:11] <Laney> asac: we confirmed that the team will stop its members getting mail
[12:11] <Laney> it's only when direct individuals get added
[12:29] <dbarth> Mirv: done
[12:32] <Mirv> thanks dbarth
[12:53] <jgdx> citrain does not take --serial or something like it?
[12:54] <sil2100> What do you mean?
[12:54] <jgdx> sil2100, if I want to put a silo on one of my three devices, I can't choose which.
[12:54] <jgdx> they're all connected to my laptop
[12:55] <sil2100> Ah, you mean the citrain cli tool?
[12:55] <jgdx> sil2100, right
[12:55] <dbarth> sil2100: about the oxide silo; do you need me to trigger any build, or is that all handled by your source copy ?
[12:56] <sil2100> dbarth: no, it's just taking quite a while, since it re-uploads the tarball...
[13:02] <dbarth> sil2100: ok
[13:18] <Mirv> try debdiff:ing two oxide versions, that's fun for your machine
[13:27] <rvr> cyphermox: ping
[13:32] <rvr> cyphermox: I copied the /var/lib/ofono/<imsi> directory to a new one, but now, what? list-contexts hasn't changed.
[13:34] <sil2100> bfiller: ping
[13:34] <bfiller> sil2100: pong
[13:34] <sil2100> bfiller: QA signed-off gallery and we landed it in the archive, you can push to the store :)
[13:34] <sil2100> (if you didn't already)
[13:35] <bfiller> sil2100: yes, let me just rebuild the click from trunk now that it is landed and I will push
[13:35] <pmcgowan> seb128, think we should land that sound icon fix in rtm?
[13:43] <sil2100> bfiller: excellent, thanks
[13:43] <seb128> pmcgowan, that would be good if it's easy to backport
[13:44] <seb128> pmcgowan, it's easy to forget that you activated silent mode atm
[13:44] <pmcgowan> seb128, I checked the diff and it looks pretty good, asking to do it
[13:44] <pmcgowan> yes we have all done that
[13:44] <seb128> pmcgowan, thanks!
[13:45] <sil2100> ralsina: hey!
[13:46] <sil2100> ralsina: regarding the silo I just assigned for ubuntu-rtm ubuntu-push
[13:46] <sil2100> ralsina: can you make sure that all those fixes also land in vivid (if applicable)
[13:47] <sil2100> (to keep the delta between archives as low as possible)
[13:48] <ralsina> sil2100: yes
[13:48] <ralsina> sil2100: I have a silo requested for the system settings MR and the push changes are already in vivid
[13:49] <sil2100> Ah, ok, excellent, I see it now
[13:51] <sil2100> ralsina: had to fix the merge links though, since those were links to branches - could you double check if all is ok now on the spreadsheet?
[13:52] <ralsina> sil2100: oops, sry, checking
[13:53] <ralsina> sil2100: looks good
[13:53] <sil2100> ralsina: silos assigned :)
[13:54] <cyphermox> rvr: you also need to change the name of the contexts in the gprs file contained, then reboot
[13:54] <ralsina> yay
[13:54] <kenvandine> ralsina, keep in mind that will need a rebuild after silo 1 lands
[13:54] <cyphermox> rvr: like awe_ said, it may be easier to use two valid SIMs instead
[13:54] <sil2100> dbarth: oxide is building in silo 004 now (RTM)
[13:55] <sil2100> dbarth: had to change the silo as 006 had a different versioning scheme that's bigger than what we wanted to upload now
[13:55] <awe_> rvr, the easiest to confirm is to make sure that none of the contexts in either gprs will connect
[13:56] <awe_> ( ie. just give them fake AccessPointNames
[13:56] <awe_> )
[13:56] <sil2100> dbarth: the error on the silo is, well... known
[13:56] <awe_> the whole idea is that NM should only look at the <IMSI> directory that matches that of an installed SIM
[13:57] <awe_> where IMSI == SubscriberIdentity ( from list-modems )
[13:58] <ralsina> sil2100: I seem to have lied, push fixes are not on vivid, they will be landed tomorrow, just FYI
[14:00] <sil2100> ralsina: ok, as long as you keep that on your radar and make sure that happens - all is good
[14:00] <slangasek> sil2100, asac: was there still a question outstanding regarding adding core-dev to ci-train-ppa-service?  We certainly don't want core-devs to start getting ci-train-ppa-service spam
[14:00] <slangasek> but maybe that's not an issue?
[14:00] <bfiller> sil2100, popey: new gallery in store ready for review/publication
[14:00] <sil2100> slangasek: from what Laney said it's not an issue
[14:01] <popey> bfiller: on it
[14:01] <sil2100> slangasek: he poked on #lp and it seems he got an answer that in this case, where a core-dev team e-mail is set, no one will get any spam mail
[14:01] <slangasek> sil2100: are we sure about that? I know I set up a procmail rule to get rid of ci-train-ppa-service spam for myself
[14:01] <sil2100> (IIRC)
[14:01] <slangasek> ok
[14:01] <sil2100> Laney: ^ ?
[14:01] <slangasek> do you still need me to make the team addition?
[14:02] <sil2100> slangasek: I think yes, we didn't do that yet as we didn't know if there weren't any other objections
[14:03] <popey> bfiller: done.
[14:06] <asac> sil2100: slangasek: if its a non issue i think its fine to add core-dev. i leave the decision and execution of trying that to slangasek if you choose to do that :)
[14:06] <rvr> cyphermox: If I use two valid SIMs, what do I check?
[14:07] <asac> slangasek: sil2100: in all cases there should be a headss up to ubuntu-devel before we add them, also giving them some background etc. in case they wonder what to do with their powers etc.
[14:11] <cyphermox> rvr: in both cases you need to check that as you switch between SIMs, NM only considers the contexts from the valid SIM
[14:12] <cyphermox> ie. from the SIM that is currently inserted
[14:23] <rvr> cyphermox: Ok, I have now two SIMs.
[14:23] <rvr> cyphermox: Next?
[14:24] <rvr> cyphermox: How do I switch between SIMs?
[14:24] <cyphermox> by removing one and inserting the other?
[14:25] <rvr> cyphermox: Ahh, not inserted at the same time
[14:38] <rvr> cyphermox: Ok, these are the contexts in different situations. First, I had two inserted SIMs: http://paste.ubuntu.com/10712412/
[14:38] <sil2100> jibel, robru, davmor2, rvr, popey, ogra_: I would need to skip today's evening meeting - you fine with cancelling it altogether?
[14:38] <rvr> cyphermox: Then, I removed one of them, and rebooted: http://paste.ubuntu.com/10712413/
[14:38] <rvr> sil2100: Yes
[14:38] <popey> sil2100: yes
[14:38] <ogra_> sil2100, totally
[14:38] <rvr> cyphermox: And finally, I switched the SIM and rebooted: http://paste.ubuntu.com/10712414/
[14:38] <rvr> cyphermox: Is that correct?
[14:39] <jibel> sil2100, WFM
[14:39] <davmor2> sil2100: Whatever cancelmonger
[14:39] <sil2100> davmor2: ;)
[14:40] <rvr> davmor2: Get a life! He has more important things to do than joking around ;)
[14:40] <davmor2> rvr: No he doesn't ;)
[14:40] <rvr> davmor2: https://www.youtube.com/watch?v=P-7pgeD__qU
[14:44] <om26er> oSoMoN, Hi!
[14:44] <oSoMoN> hey om26er
[14:45] <om26er> oSoMoN, with silo9, I see this http://i.imgur.com/6NIJZNQ.png
[14:45] <om26er> I guess in this case the header should not be an overlay ?
[14:45] <oSoMoN> om26er, oh, good catch, I’ll fix that real quick, it’s a trivial one
[14:47] <cyphermox> rvr: that's not where you need to look, you need to check how NM behaves, not ofono; look in /var/log/syslog
[14:48] <om26er> oSoMoN, as per procedure I'll move the current card to failed and when the new silo is built it will automatically appear in trello and we'll pick it from there.
[14:48] <oSoMoN> om26er, ok
[14:48] <oSoMoN> om26er, will be ready in 2mins + the time to rebuild the silo
[14:50] <oSoMoN> om26er, PPA rebuilding
[14:51] <oSoMoN> om26er, oh, wait, that was in the webapp container, right? I fixed the same issue in the browser, will now fix it in the container
[14:52] <om26er> oSoMoN, yeah, thats a webapp
[14:52] <om26er> oSoMoN, is there a single code base for both ?
[14:52] <rvr> cyphermox: https://pastebin.canonical.com/128711/
[14:52] <oSoMoN> om26er, yes, that’s the same code base indeed
[14:58] <oSoMoN> om26er, ok, fixed in the container too, will wait for the current silo build to complete before triggering a new one, I’ll ping you when it’s built
[14:58] <om26er> oSoMoN, ok
[14:58] <oSoMoN> om26er, thanks again for catching this one, I had completely overlooked this issue
[14:59] <om26er> oSoMoN, no problem :)
[15:07] <rvr> cyphermox: ?
[15:07] <Saviq> trainguards, I can has silo for line 57 please?
[15:07] <sil2100> Saviq: on it!
[15:07] <sil2100> Sorry, in a meeting
[15:07] <Saviq> pete-woods wants one for line 58, too :)
[15:09] <cyphermox> rvr: looks fine
[15:09] <rvr> cyphermox: Is it ok then?
[15:09] <cyphermox> yes
[15:10] <rvr> cyphermox: Ok, approving the silo. To speed things up, next time please add test cases.
[15:11] <cyphermox> there is a test plan
[15:11] <cyphermox> (and test case for the bug is in the bug)
[15:12] <cyphermox> or so I've been told
[15:32] <om26er> jgdx, Hi!
[15:32] <jgdx> om26er, yo
[15:33] <om26er> jgdx, to verify the fix in [1] after editing the gprs file a reboot will do as well ?
[15:33] <om26er> [1] https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/apn-no-overwrite-1415495-rtm/+merge/254129
[15:34] <jgdx> om26er, restart's not working for you? Yes, it should.
[15:34] <om26er> jgdx, it didn't sims stayed Offline
[15:34] <jgdx> *ofono stop and start
[15:35] <jgdx> om26er, really. Hm, okay.
[15:35] <jgdx> om26er, to confirm, this [1] was the gprs file you used? [1] https://launchpadlibrarian.net/196032938/gprs
[15:36] <om26er> jgdx, yes, for both SIMs
[15:36] <om26er> jgdx, now gprs is not working for me
[15:37] <jgdx> om26er, please specify that which is not working?
[15:37] <om26er> jgdx, 2G/3G is not working on any of my SIMs after editing the apn file
[15:38] <jgdx> om26er, that's not a acceptance criteria for this particular bug, though.
[15:38] <jgdx> *an
[15:39] <jgdx> om26er, I can make 6. more specific. 2 sec
[15:40] <seb128> Mirv, still around?
[15:40] <om26er> jgdx, didn't get that last sentence
[15:41] <jgdx> om26er, I have made the test plan a bit more specific: https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/apn-no-overwrite-1415495-rtm/+merge/254129
[15:43] <om26er> jgdx, ah, ok. That seems to work as intended
[15:44] <jgdx> om26er, great. If you backed up your gprs file, you can restore it and reboot. If not, let me know.
[15:44] <om26er> jgdx, I didn't backup. It'll get restored when I start testing next silo
[15:44] <jgdx> om26er, oke doke
[15:48] <Laney> sil2100 / slangasek: Should be fine; the team's email address catches mail.
[15:48] <Laney> Ah, it's done already
[15:53] <rvr> Guys, is not good to ask for QA sign off and then rebuild the silo
[15:53] <rvr> oSoMoN: What did you change?
[15:54] <oSoMoN> rvr, I fixed the issue uncovered by om26er when he initially tested the silo, see the failed column
[15:54] <rvr> Ahhh, I see
[15:54] <rvr> Three cards right now
[15:54] <rvr> Meh
[15:54] <rvr> om26er: I re-assign the silo to you then
[15:55] <om26er> rvr, ok
[15:55] <om26er> will get to it after ubuntu-system-settings
[15:55] <oSoMoN> rvr, I had to rebuild the silo twice, I guess that’s the reason why there are two cards for it
[15:56] <rvr> oSoMoN: Yeah, sure, it's ok. Sorry, I wasn't aware that om26er already test it.
[15:57] <om26er> jgdx, whats the TestPlan to run except for these bug fixes ?
[15:59] <jgdx> om26er, we don't have proper one. We do have a task for that, though.
[16:01] <kenvandine> rvr, be aware that silo 16 is going to need a rebuild after silo 28 lands
[16:01] <kenvandine> rvr, but the changes won't effect each other
[16:02] <rvr> kenvandine: Hmm... I see.
[16:14] <rvr> kenvandine: Silo 16 works fine, Telegram is displayed once. But I am blocking it until a test is added, as it comes with no one.
[16:15] <kenvandine> ralsina, ^^
[16:19] <ralsina> rvr: test as in autopilot test?
[16:19] <rvr> ralsina: Yeah
[16:19] <ralsina> rvr: I have never done one, I guess I can try :-P
[16:22] <rvr> ralsina: Autopilot is not required per se, but at least a test that checks that Notifications group per package and not as before. Anyway, I think it can be done with autopilot easily.
[16:23] <ralsina> rvr: the only app that will show any difference at this point is telegram
[16:23] <ralsina> so the test needs to install telegram and check that there's only one item
[16:24] <rvr> ralsina: Yeah, so the test should be skipped if no Telegram is installed. So it would be something like: if there's a Telegram entry, it should be one. If there is none, pass.
[16:24] <dobey> citrain: can i get https://jenkins.qa.ubuntu.com/job/generic-click-builder-14.09-armhf/27/artifact/output/com.canonical.payui_15.01.120_armhf.click uploaded to the store please? thanks
[16:25] <ralsina> rvr: ok, I'll start llearning how to do it
[16:39] <bdmurray> cihelp: I'm looking for a refresher on how to sort out this test failure https://jenkins.qa.ubuntu.com/job/trusty-adt-ubuntu-release-upgrader/
[16:46] <plars> bdmurray: hmm, qa might be your best bet for that question, but looking at those runs, I find this:
[16:46] <plars> root: WARNING: file 'quantal.tar.gz.gpg' missing
[16:46] <plars> bdmurray: any chance ubuntu-release-upgrader has some bits in it hardcoded for quantal?
[16:47] <plars> bdmurray: the previous (passing) results were pre-EOL for quantal... may just be smoke but it raises a red flag for me just looking at the output
[16:49] <bzoltan_> robru: thank you
[16:49] <robru> bzoltan_: you're welcome
[16:52] <bdmurray> plars: looking
[16:53] <dobey> oops
[16:53] <dobey> cihelp: can i get  https://jenkins.qa.ubuntu.com/job/generic-click-builder-14.09-armhf/27/artifact/output/com.canonical.payui_15.01.120_armhf.click uploaded to the  store please? thanks
[16:55] <bdmurray> plars: no, nothing quantal specific
[17:13] <bdmurray> plars: oh, actually I found it and yeah its probably trying to the quantal release upgrdaer
[17:13] <robru> brb
[17:14] <bdmurray> plars: so what is the right way to proceed? It doesn't really seem worth an upload for that.
[17:26] <fginther> dobey, I can do that
[17:27] <boiko> trainguards: can I please get vivid silo 24 reconfigured? I added a new component there (telepathy-ofono)
[17:27] <fginther> dobey, upload finished
[17:34] <jhodapp> robru, can I get a silo for spreadsheet line 60 please?
[17:39] <plars> bdmurray: if it's part of a test in the packaging, I'm not sure how else you would fix it
[17:45] <jhodapp> sil2100, you still around? Can I get a silo for line 60 please?
[17:48] <robru> jhodapp: one sec
[17:48] <jhodapp> cool
[17:54] <robru> jhodapp: boiko: k should be good to go
[17:55] <boiko> robru: thanks
[17:58] <robru> boiko: you're welcome
[18:15] <dobey> fginther: thanks
[18:26] <jhodapp> robru, thanks
[18:27] <robru> jhodapp: you're welcome
[19:27] <robru> fginther: https://pastebin.canonical.com/128739/ can I get you to take a look at this venv issue? not sure what I'm missing here
[20:10] <oSoMoN> trainguards: hey, can I haz an RTM silo for line 61 ?
[20:10] <charles> hey, what happened to indicator-power and ubuntu-themes in line 61?
[20:10] <robru> oSoMoN: sure can't! because that's charles line
[20:11] <robru> charles: dunno, I assigned a silo for your line 61, you got silo 10 there ^^
[20:11] <charles> robru, want me to re-add it on line 62?
[20:11] <robru> oSoMoN: charles: hm just reloaded and it switched to osomon's
[20:12] <robru> charles: yeah please
[20:12] <charles> same here
[20:12] <charles> ack, adding to 62
[20:12] <oSoMoN> huh, line 61 was empty here, I wonder what the heck happened
[20:13] <robru> oSoMoN: spreadsheet is rubbish
[20:13] <oSoMoN> charles, I’m sorry if my request overwrote yours, when I input my name in the lander column that line was empty here
[20:13] <robru> oSoMoN: you got silo rtm 1
[20:13] <oSoMoN> robru, I couldn’t agree more
[20:13] <robru> brb
[20:13] <oSoMoN> robru, thanks!
[20:13] <charles> oSoMoN, no worries
[20:13] <charles> it's happened to everyone
[20:15] <robru> oSoMoN: you're welcome
[21:38] <fginther> robru, I'm looking that error. are you still using bootstack?
[21:39] <robru> fginther: yeah bootstack. just talking with slangasek apparently this is due to vivid having switched to systemd.
[21:41] <fginther> robru, ??? How does any change in vivid impact this? I'm very curious
[21:48] <pmcgowan> robru, scouple of silos are marked passed in trello but not in the train
[21:49] <pmcgowan> maybe just vivid 30
[21:57] <robru> pmcgowan: looking
[21:57] <slangasek> fginther: because there are precise containers on top of a trusty environment, and lxc support for systemd is/was in need of an SRU
[21:58] <fginther> slangasek, I see, thanks
[21:58] <robru> fginther: oh sorry, slangasek asked me to try deploying directly from vivid (eg without the trusty sandbox), and it almost worked, but apparently the systemd switch in vivid has broken lxc in precise/trusty (which depend on upstart) so I'll have to keep using the trusty sandbox which is known to work until lxc fixes get SRUd.
[21:58] <robru> heh
[22:00] <fginther> robru, that makes sense, thanks for clarifying
[22:00] <robru> fginther: you're welcome
[22:10] <robru> pmcgowan: is silo 30 urgent? because it got invalidated by a manual distro upload, it needs to be rebuilt and it's not an MP that I can just rebuild; needs cyphermox to merge the distro version back into this version.
[22:11] <pmcgowan> robru, oh heck, yeah it fixes vivid blockers
[22:11] <pmcgowan> robru, but tomorrow is fine
[22:11] <pmcgowan> robru, wait manual distro upload?
[22:11] <robru> pmcgowan: k, if I publish it I'd be reverting https://launchpadlibrarian.net/201670718/network-manager_0.9.10.0-4ubuntu11_0.9.10.0-4ubuntu12.diff.gz which is pitti's work
[22:11] <robru> yeah
[22:12] <pmcgowan> um I thought vivid was froze
[22:12] <pmcgowan> ish
[22:12] <robru> pmcgowan: well it's a bugfix
[22:13] <pmcgowan> robru, thanks for the info
[22:13] <robru> pmcgowan: you're welcome.
[22:17] <cyphermox> ugh
[22:17] <cyphermox> don't worry too much about NM, i'll fix it
[22:17] <cyphermox> land some other fixes with it too
[22:18] <pmcgowan> cyphermox, sorry and thanks
[22:18] <cyphermox> pmcgowan: no worries
[22:18] <awe_> cyphermox, which other fixes?
[22:18] <pmcgowan> robru, what would have happened if I didnt notice it didnt land?
[22:19] <cyphermox> awe_: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1436330
[22:20] <robru> pmcgowan: hmmm, well at some point the spreadsheet would have updated to say qa had signed off (spreadsheet hiccups are why i didn't notice it myself), and then i would have published it later and found this conflict.
[22:20] <awe_> cyphermox, ok
[22:21] <pmcgowan> robru, ok, but am a bit concerned
[22:22] <robru> pmcgowan: yes, it's the spreadsheet. it's been failing to sync all day. earlier there was a case where two different people were adding a new landing request at the same time and neither one saw the other one, so they wrote on the same row
[22:23] <robru> pmcgowan: in this case, either the qa person who approved the silo didn't mark it in the spreadsheet, or they did mark it but it wasn't saved (there's no way to say for sure which one of those possibilities is what happened).
[22:24] <robru> pmcgowan: either way, the lack of the status in the spreadsheet means that I didn't get the ping to publish it, so it just sat there
[22:24] <pmcgowan> robru, ok