[02:30] <veebers> trainguards, silly question, if I update the MP that is preposed for the silo, do I need to reconfigure or just re-build the silo ppa?
[02:31] <robru> veebers: rebuild if it's the same mp. Reconfigure if there's a new mp, including of its superceding a previous mp.
[02:32] <veebers> robru: ah cool thanks, the MP was updated due to new code in trunk so I'll rebuild the silo.
[02:32] <robru> veebers: sounds good
[02:33] <veebers> oops
[02:34] <veebers> ticked the right box this time :-)
[06:03] <Mirv> (and morning too)
[08:38] <Mirv> eh
[08:38] <Mirv> ah, device tarball
[08:45] <sil2100> Mirv: ;)
[09:05] <mandel> sil2100, is launchpad down for you?
[09:05] <mandel> sil2100, my manners, good morning!
[09:05] <mandel> rearrange those please :)
[09:05] <sil2100> mandel: morning! ;)
[09:06] <sil2100> mandel: huh, indeed it is
[09:06] <Mirv> launchpad down :(
[09:06] <sil2100> I asked on launchpad-ops if anything
[09:06] <Mirv> modern human is so impatient. "it's been down for 2 mins already!"
[09:07] <sil2100> Ah, update
[09:07] <Mirv> "but... but... I've important stuff building and I need to keep hitting refresh!"
[09:07] <sil2100> 2 minutes?!?!?! OUTRAGE
[09:07] <mandel> Mirv, yes, I don't consider it important, yet manager do
[09:08] <mandel> Mirv, I just suffer their impatience :P
[09:08] <mandel> also, compiling cpp takes longer than getting lp back hehe
[09:13] <sil2100> LP is an important factor for almost everyone, so good that it's back up agaon
[09:14]  * Mirv is satisfied with what the refreshing shows
[09:27] <sil2100> oSoMoN: hey! Were you able to fill in an FFe for the oxide landing?
[09:28] <oSoMoN> sil2100, I did (bug #1425599), but chrisccoulson said that we don't use this process for oxide (or firefox & chromium), because all releases get the latest updates anyway
[09:28] <oSoMoN> so the FFe process is fairly redundant - if it's rejected, the latest release still lands anyway
[09:29] <sil2100> hmm
[09:29] <sil2100> Is that something that has been agreed with the release team?
[09:30] <ogra_> hmpf
[09:30] <ogra_> i just woke up my krillin for the first time today ...
[09:30] <ogra_> the clock shows 5:04
[09:30] <ogra_> and i cant convince it to show the right time it seems
[09:31] <oSoMoN> sil2100, pretty sure it has, chrisccoulson can you comment on this?
[09:31] <ogra_> hmm, suspend/resume fixed it for the lockscreen, but the clock indicator is gone
[09:35] <chrisccoulson> sil2100, oSoMoN - yeah, I'm quite sure it has too, considering we are regularly pushing the same updates out to stable releases. And having an evergreen webengine was one of the reasons we created Oxide
[09:35] <chrisccoulson> ISTR going through this every cycle :)
[09:37] <ogra_> chrisccoulson, and you havent set up macros for it in your IRC client yet ?
[09:37] <chrisccoulson> heh
[09:38] <mandel> sil2100, is there a way to create 2 silos, one for rtm with udm and its dependencies, and a second silo for vivid with the same branch of udm and its dependencies
[09:38] <mandel> sil2100, the issue is that its dependencies have a branch for rtm, yet I keep udm as updated as possible (trunk) in rtm
[10:08] <sil2100> davmor2, jibel, john-mcaleely: so, following up on my earlier question, do we know if the U1 deletion bug has a fix ready/released?
[10:15] <davmor2> sil2100: not yet
[10:16] <jibel> sil2100, bug fixed in devel but not in rtm
[10:16] <jibel> bug 1413655
[10:16] <john-mcaleely> sil2100, I do not know
[10:18] <sil2100> Thanks
[10:19] <sil2100> dobey: hey!
[10:19] <sil2100> dobey: we would need LP: #1413655 fixed for ubuntu-rtm as well, do you have some work done on getting this bug backported to 14.09?
[10:39] <mandel> sil2100, Mirv is this normal -> https://ci-train.ubuntu.com/job/ubuntu-landing-014-1-build/163/console
[10:39] <mandel> sil2100, Mirv ignore me, ppc symbol issues
[10:40] <sil2100> mandel: it looks like all architectures failed to build
[10:40] <sil2100> mandel: because of symbol issues
[10:40] <mandel> sil2100, yet, it just fails on ppc and the symbols files are not separated per arch
[10:41] <mandel> sil2100, if it failed due to the symbols in should be in all the archs.. right?
[10:44] <sil2100> mandel: it looks like it failed on all archs
[10:44] <sil2100> ;)
[10:44] <sil2100> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-014/+sourcepub/4804160/+listing-archive-extra
[10:44] <mandel> sil2100, indeed, I'm stupid, I just updated the symbols
[10:44] <mandel> sil2100, I forgot a push
[10:44] <mandel> spanish lesson: soy gilipollas
[11:01] <dbarth> sil2100: o/ hey can i get a silo for that quick fix?
[11:02] <dbarth> i hear there is a window open to land that one in rtm
[11:03] <dbarth> or any trainguards available
[11:06] <sil2100> Sure
[11:07] <davmor2> dbarth: ^ and sil2100 is already on it apparently
[11:07] <sil2100> dbarth: we've been actually discussing this one
[11:07] <sil2100> We even wanted to land it ASAP ;)
[11:07] <dbarth> thanks guys
[11:08] <dbarth> excellent
[11:15] <Saviq> sil2100, thanks
[11:47] <Saviq> trainguards, reconfigure on vivid silo 19 please, have added qtmir
[11:47] <sil2100> Saviq: on it
[11:47] <Mirv> sil 'Lightning' 2100
[11:48] <Saviq> ;)
[11:48] <sil2100> ;p Only sometimes though ;)
[12:31] <om26er> renatu, Hi!
[12:38] <renatu> om26er, hi
[12:39] <om26er> renatu, it was regarding sync-monitor, it failed to sync for me on the first try
[12:39] <om26er> renatu, http://paste.ubuntu.com/10428002/
[12:39] <om26er> but now its working
[12:40] <renatu> om26er, strange it should not try to sync if there is no network
[12:40] <renatu> looks like it try to sync with device offline
[12:40] <om26er> renatu, device was always connected
[12:42] <renatu> om26er, the error says: Network is unreachable
[12:43] <om26er> renatu, we can blame my internet then :)
[12:50] <renatu> om26er, maybe in that time when you tried to sync the device was connected to wifi but without internet access
[13:00]  * sil2100 goes off to lunch
[13:02] <john-mcaleely> sil2100, I understand I have a +1 on the device tarball. is now good to push it?
[13:09] <dobey> sil2100: yes i'll have a branch today
[13:14] <Saviq> can you guys access the spreadsheet?
[13:14] <Saviq> gdocs say it's too popular
[13:14] <Mirv> Saviq: same here
[13:14] <Mirv> it was "trying to reach" and after reaching it said that
[13:14] <Saviq> yup
[13:14] <Saviq> DoS :/
[13:15] <Mirv> s/reaching/refreshing/ :)
[13:25] <Saviq> Mirv, seems to be back
[13:26] <Mirv> confirming
[14:06] <john-mcaleely> sil2100, ping
[14:08] <sil2100> john-mcaleely: pong
[14:08] <john-mcaleely> sil2100, can I push the tarball, davmor2 is +1 on it?
[14:08] <sil2100> john-mcaleely: sorry, was on lunch - where would you push the tarball to?
[14:08] <john-mcaleely> normal RTM
[14:08] <davmor2> john-mcaleely: 1 second
[14:08] <sil2100> Sure :)
[14:09] <sil2100> Oh
[14:09] <sil2100> davmor2: ?
[14:09]  * john-mcaleely waits one second
[14:09] <john-mcaleely> ...
[14:09] <john-mcaleely> done!
[14:09] <sil2100> ;D
[14:09] <davmor2> sil2100: nearly tested silo10 for the u1 account fix
[14:09] <davmor2> john-mcaleely: ^
[14:09] <john-mcaleely> we can land them as two builds? good to get them separate in rtm
[14:09] <john-mcaleely> and device tarballs are quick builds
[14:09] <sil2100> davmor2: we won't have time for that this round anyway, since we didn't prepare the derived series yet
[14:10] <john-mcaleely> sil2100, ?
[14:10] <sil2100> I would say let's land the tarball now
[14:10] <john-mcaleely> yeah
[14:10] <sil2100> And if anything, have a new image built later with the u1 fix
[14:11] <sil2100> john-mcaleely: push it ;)
[14:11] <john-mcaleely> sil2100, pushed!
[14:11] <sil2100> \o/
[14:31] <cjwatson> sil2100: if you're going to need a derived series please give us maximal warning this time
[14:32] <cjwatson> don't want another last-thing-on-Friday panic
[14:32] <sil2100> cjwatson: sure, for now we're trying to figure out how to copy only a device tarball from one channel to another ;)
[16:38] <seb128> rsalveti, do you plan to land the agent rework silo? the comment from Mirv on the status is a bit confusing
[16:40] <rsalveti> seb128: yup, in my list for testing & landing today
[16:40] <rsalveti> takes a while to validate with all the bt devices, but will get it done today
[16:41] <seb128> rsalveti, I tested & approved the mp yesterday :-)
[16:42] <rsalveti> seb128: sure, but I want to test with my other devices as well because I had quite a few issues with that previous version of that mr
[16:42] <seb128> rsalveti, do you plan to do the backport to rtm as well?
[16:42] <rsalveti> seb128: which car did you use to test?
[16:42] <rsalveti> seb128: that's the idea, yeah
[16:43] <seb128> rsalveti, a peugeot one
[16:43] <rsalveti> seb128: which model?
[16:43] <seb128> 207
[16:43] <rsalveti> mine is a peugeot as well, but 208
[16:43] <rsalveti> cool, different one
[16:43] <seb128> 207 business pack
[16:43] <rsalveti> great
[16:43] <seb128> I also tested ssp pairing on a k480 keyboard
[16:43] <seb128> and an audio receiver
[16:44] <seb128> so should be fine
[16:44] <seb128> the previous version of the mp was making the per-device agent buggy
[16:44] <seb128> that one should work for scenarios with adaptor agents and per device ones
[16:45] <rsalveti> yeah, cool
[16:50] <Mirv> sil2100: robru: ^ silo 020 qml cache for vivid, when/if FFe approved. or rsalveti too, whoever stays the longest :)
[16:58] <sil2100> ;)
[16:58] <sil2100> \o/
[17:02] <sil2100> mandel: ping
[17:08] <oSoMoN> trainguards: can you assist with silo 25 ? not really sure what happened
[17:09] <robru> oSoMoN: looking
[17:15] <robru> oSoMoN: yeah merge conflict against trunk, not sure, train has code to handle that, not sure what's wrong with it now. anyway I manually merged it and pushed
[17:16] <popey> sil2100: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc&usp=drive_web#gid=0
[17:16] <popey> is that the right sheet?
[17:17] <popey> sil2100: did you say I just email you and you enter it, or I enter it? Because this looks like a computed sheet
[17:19] <oSoMoN> thanks robru
[17:19] <robru> oSoMoN: you're welcome
[17:19] <sil2100> popey: you can e-mail me all the info :)
[17:20] <rsalveti> sil2100: robru: can't create silo for line 64
[17:20] <sil2100> One day we can go through adding a line together
[17:20] <rsalveti> getting fata error in the spreadsheet and jenkins also failing
[17:20] <sil2100> uh
[17:21] <sil2100> The spreadsheet was acting strangely some hours ago indeed
[17:21] <sil2100> rsalveti: let me try
[17:21] <robru> rsalveti: log? line 64 was blank for me until I just reloaded the page just now
[17:21] <popey> sil2100: correct answer! :D
[17:21] <sil2100> huh
[17:22] <rsalveti> robru: not blank here
[17:22] <sil2100> robru, rsalveti: getting the same thing here
[17:22] <sil2100> I mean, it's not blank, but a fatal error
[17:22] <sil2100> Let me refresh the spreadsheet completelt
[17:22] <robru> sil2100: fatal error where? in jenkins? or in the spreadhseet?
[17:22] <sil2100> robru: on the spreadsheet
[17:23] <robru> sil2100: rsalveti: worked fine for me, assigned silo 17
[17:23] <sil2100> rsalveti: maybe it was broken since we had the spreadsheet open for too long?
[17:23] <sil2100> robru probably loaded it just recently
[17:23] <robru> rsalveti: yeah when in doubt, reload the spreadsheet.
[17:24] <sil2100> popey: ;)
[17:24] <oSoMoN> trainguards: can I have a silo for line 65, please?
[17:24] <rsalveti> sil2100: robru: I opened it again in another browser
[17:24] <rsalveti> and still had the same issue
[17:24] <sil2100> huh
[17:24] <rsalveti> well, it seems it'sfine now
[17:24] <sil2100> Well, spreadsheet
[17:25] <sil2100> So, looking at the failure summary from Google I get, there was some fatal error happening in syncstatus
[17:25] <sil2100> But it might just have simply fixed itself magically, as always
[17:26] <greyback> trainguards: can I get a silo for line 62 please
[17:26] <robru> sil2100: you want to assign or should I?
[17:27] <sil2100> robru: please do ;)
[17:27] <robru> k
[17:28] <robru> sil2100: oh I'm getting the fatal error now
[17:28] <robru> greyback: bfiller: spreadsheet is imploding will assign when I can
[17:29] <greyback> robru: thanks :)
[17:30] <Mirv> good riddance...
[17:30] <Mirv> for the imploding spreadsheet :)
[17:31] <robru> greyback: ok rtm 12
[17:31] <greyback> robru: cheers
[17:31] <bfiller> robru: thanks, noticing that
[17:31] <robru> greyback: you're welcome
[17:32] <robru> oSoMoN: silo 21
[17:33] <robru> bfiller: silo 25
[17:33] <robru> sil2100: seems I have to prepare manually by copy & pasting from the spreadsheet. yey
[17:38] <oSoMoN> robru, cheers
[17:39] <robru> oSoMoN: you're welcome
[17:44] <robru> Saviq: https://ci-train.ubuntu.com/view/1.%20Build/job/ubuntu-landing-019-1-build/119/console eh, qtmir-gles isn't in the silo...
[17:45] <robru> or in the ppa, I mean
[17:45] <robru> also wtf, that's supposed to timeout...
[17:45] <Saviq> robru, huh, that job was supposed to *build* qtmir-gles... but obviously I forgot to reconf
[17:46] <Saviq> robru, but found a bug for you then ;)
[17:46] <robru> Saviq: you have an MP prepared already?
[18:12] <robru> bfiller: 6, 26, 28
[18:12] <bfiller> robru: thanks
[18:13] <robru> bfiller: you're welcome
[18:39] <robru> bfiller: WATCH_ONLY in silo 26 means "don't merge my merges, only look at PPA", but there's nothing in your PPA yet. FORCE_REBUILD also wasn't necessary, just run that job with no options.
[18:40] <bfiller> robru: I must have pressed that by accident
[18:40] <robru> bfiller: no worries, I'm just watching over builds ;-)
[18:40] <bfiller> robru: I usually click "force rebuild" and "ignore missing twins" by habit. I guess I don't usually need these?
[18:41] <robru> bfiller: force rebuild is only needed if you're rebuilding an already-built MP (due to new commits). also ignore_missing_twins is only to do with -gles packages so pretty much only used by kgunn & friends.
[18:42] <bfiller> robru: ok
[18:42] <robru> bfiller: I mean they don't *hurt* per se, but yeah, not often necessary.
[19:30] <greyback_> trainguards: could I have a hand for a second, I'm proposing something for qtmir for RTM, but the build appears to be taking qtmir trunk and applying my patch, not the qtmir-rtm branch. How do I specify the RTM branch to the train?
[19:34] <greyback_> trainguards: unping, my bad
[19:36] <robru> greyback_: train goes by MPs, if the train is grabbing trunk it's because your MP points at trunk.
[19:37] <greyback_> robru: yeah I realized I pointed it to the wrong branch, and needed to reconfigure
[19:37] <greyback_> should be ok now
[19:40] <rsalveti> sil2100: for silo rtm 12, we actually want to land that asap
[19:40] <rsalveti> sil2100: the battery related fixes are fine for RTM
[19:40] <rsalveti> and this is one of them
[19:42] <robru> greyback_: no worries, I'm here to help if you need me
[19:42] <greyback_> robru: thanks
[19:42] <robru> greyback_: you're welcome
[19:45] <sil2100> rsalveti: ok, then in my opinion the bug priority should be changed
[19:45] <sil2100> rsalveti: since the battery fixes are critical prio IMO
[19:45] <rsalveti> yeah
[19:52] <robru> rsalveti: you did a WATCH_ONLY in silo 17 but there's no package there... I think you should cancel that build and rebuild without WATCH_ONLY
[19:52] <rsalveti> robru: ops, wasn't supposed to be watch-only
[19:53] <rsalveti> robru: done, thanks
[19:53] <robru> rsalveti: you're welcome
[20:12] <balloons> wgrant, ping
[20:36] <veebers> trainguards the commit message for a landing is pulled from the commit message from the proposed MP right?
[20:37] <rsalveti> veebers: yes
[20:37] <robru> veebers: yes, unless it is specified in debian/changelog, then that is preserved
[20:37] <veebers> and that's grabbed at the silo build time?
[20:37] <robru> veebers: yes
[20:37] <veebers> right, so I need to rebuild if I want that changed
[20:37] <robru> veebers: yes
[20:38] <veebers> cool thanks robru, rsalveti
[20:38] <robru> veebers: you're welcome
[20:38] <kdub> trainguards, with line 53/silo 7, what do I do about that source package? I've completed the testing, but that qtmir-gles source package has to land along with the other changes
[20:39] <robru> veebers: also note, the train doesn't handle bulleted lists well. if you're going to set the commit message on an MP, try to write just one sentence on one-ish lines. if you need a bulleted list you have to write your debian/changelog yourself
[20:39] <robru> veebers: (train can make a bulleted list, but each bullet represents one MP, so you'd have to have a bunch of MPs each with one sentence commit messages)
[20:39] <veebers> robru: ah ok, gotcha. How will it handle the current one?
[20:40] <robru> veebers: which one?
[20:40] <robru> kdub: I don't understand the problem. silo says packages built?
[20:41] <veebers> robru: sorry, any idea how the train will handle the current commit message?
[20:41] <robru> veebers: what MP though? I don't know what silo you're talking about :-)
[20:42] <veebers> robru: lol sorry I thought the fact you mentioned the bulleted lists you were looking at it, sorry about that
[20:42] <robru> kdub: something goofy going on there, spreadsheet says source package but the train config clearly has an MP listed in the dashbaord
[20:42] <robru> veebers: nah just some code I poked at recently.
[20:42] <kdub> robru, right, something seems off, but I'm not quite sure how source packages work
[20:42] <kdub> in the ci train
[20:43] <veebers> robru: heh, right so fyi it's this one, and I want to remove one of the bullet points, so I'll update, rebuild and re-run the test run (https://code.launchpad.net/~autopilot/autopilot/trunk/+merge/250402)
[20:44] <robru> kdub: well ostensible you manually upload those to teh PPA yourself. however in this case there's clearly an MP in the silo and the package is in the PPA as a result of that. it should be fine to just click publish. I have no idea why the spreadsheet shows different info. in cases of discrepancies, the dashboard is authoritative.
[20:45] <robru> veebers: well, this is what your last build resulted in: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-009/+sourcepub/4803556/+listing-archive-extra so consider that...
[20:45] <robru> veebers: you might want to make your own debian/changelog entry.
[20:46] <robru> brb
[20:46] <kdub> robru, so I think what happened was, the mp was in the mp-to-land column at the time the silo was set up, and then I wanted qtmir-gles as a source package, so i moved it to that column
[20:52] <robru> kdub: why do you want a source package? what's wrong with the MP?
[20:54] <robru> kdub: at any rate, if you need it to be a source package, it means you need to reconfigure the silo. but all that's going to accomplish is that it won't merge the MP that you built from, I don't understand why that would be desireable.
[20:55] <kdub> camako, any insight? I'm not quite sure why it should be a source package myself
[20:56] <robru> kdub: MPs are the primary use case for the train, I think you should change it back unless you have a good reason.
[20:56] <camako> robru, this is for the qtmir twin (qtmir-gles)
[20:57] <robru> camako: right, but you guys have an MP for that. what's wrong with it?
[20:57] <camako> robru, the right thing to do would be to add it to the MP list
[20:57] <kdub> okay, so I'll add the MP to the list
[20:57] <robru> camako: agreed
[20:57] <camako> robru, nothing... we weren't sure
[20:57] <camako> yep
[20:58] <robru> camako: kdub: yeah source packages are typically only used for things that we don't have lp branches for and thus have nothing to make an MP against.
[20:59] <camako> robru, yeah the intention was that we'd add the MP later and reconfig ourselves (i.e. don't ask the trainguards) .. But some info got crossed...
[20:59] <wgrant> balloons: Hi
[20:59] <robru> camako: oh I see, yeah that makes sense, to start as a source package and then switch it to the MP, since you need to know the silo # before you can make the MP.
[20:59] <robru> camako: kdub: but yeah, once you have the MP you're golden ;-)
[21:00] <camako> robru, exactly
[21:00] <veebers> robru: heh, thnks for the heads up, that isn't a very good change log, I'll make my own
[21:00] <balloons> wgrant, hey, I was just implementing what you proposed on https://bugs.launchpad.net/launchpad/+bug/810229
[21:00] <balloons> thanks for the thorough investigation. I hope I got it all correct, testing it out now
[21:00] <kdub> okay, thanks for the help robru / camako
[21:00] <veebers> robru: is there any magic I need to do other than just a dch -i  . . . commit and mp?
[21:00] <robru> veebers: yeah sorry about that, train is optimized for small isolated branches authored by one or two people. the changelog it generates in the case of "many authors, one giant MP" is pretty puke-y
[21:00] <veebers> robru: cure, makes sense
[21:00] <veebers> s/cure/sure/
[21:01] <robru> veebers: nope, no magic. train will detect that debian/changelog is modified and won't modify it further. just review it after you dch to make sure you got the desired result.
[21:01] <wgrant> balloons: Ah, great. Let me know if it doesn't go as planned.
[21:01] <robru> kdub: your'e welcome
[21:01] <veebers> robru: ack, thanks
[21:01] <robru> veebers: you're welcome
[21:02] <robru> veebers: oh, the only magic bit I guess is that your series should be UNRELEASED, not vivid.
[21:02] <veebers> robru: hmm, I fear that the version number might cause me grief, let me check
[21:03] <robru> veebers: hm, yeah, I don't understand that part of the code very well. I think if your first line of the changelog says 'vivid' then the train will think that's an old release and generate a new, empty changelog entry (literally a bullet point with no text). but if you say UNRELEASED it should mangle the version number and generally do the right thing.
[21:04] <dobey> i seem to recall having "vivid" as the release when i did custom debian/changelog for a landing, and it working fine :-/
[21:05] <robru> veebers: last build generated version number 1.5.0+15.04.20150226-0ubuntu1 so a rebuild should result in 1.5.0+15.04.20150226.1-0ubuntu1 and work fine. you shouldn't need to know that though, basically if the first line of your changelog says "autopilot (1.5.0) UNRELEASED; urgency=medium" then the train should convert that to "autopilot
[21:05] <robru> (1.5.0+15.04.20150226.1-0ubuntu1) vivid; urgency=medium" by itself
[21:06] <veebers> robru: awesome, thanks again (I should have store the count of beers I owe you in something bigger than a unit32 as it's going to overflow soon)
[21:07] <robru> dobey: yeah but I think if you say 'vivid' then you also have to pick your own version number. if you want the auto-version-number magic you need to say UNRELEASED. I can't remember exactly the details, I'd have to dig up the code
[21:07] <robru> veebers: lol, you're welcome
[21:11] <veebers> robru: so, one more question the debian/changelog in lp:autopilot has UNRELEASED from _ages_ ago as we've been using the train to land from lp:autopilot -> lp:autopilot/1.5 so it's happened automagically for us until now. Is it save to change that UNRLEASED to something else so dch -i gives me a new entry?
[21:13] <robru> veebers: you mean http://bazaar.launchpad.net/~autopilot/autopilot/trunk/view/head:/debian/changelog ?
[21:13] <veebers> robru: that's the one
[21:13] <robru> veebers: oh, don't use that one, since it's missing a ton of stuff. grab the one from the 1.5 branch and include that in the MP.
[21:13] <veebers> the changelog and release has been happening in http://bazaar.launchpad.net/~autopilot/autopilot/1.5/view/head:/debian/changelog
[21:14] <veebers> robru: ack, I'll merge that one back into lp:autopilot then go from there
[21:14] <robru> veebers: ok sounds good
[21:22] <dobey> hrmm
[21:22] <dobey> i thought we had autopilot runs enabled for lp:pay-ui
[21:23] <dobey> but i don't see an autopilot job run for my MP :-/
[21:23] <dobey> which is odd, because it did run on my MP from last week :-/
[21:23] <veebers> robru: if you have a moment could you sanity check this please? Then once that's merged to trunk I'll rebuild the silo: https://code.launchpad.net/~veebers/autopilot/add-changelog-for-release/+merge/251178
[21:24] <dobey> cihelp: why would the ap tests jobs not be run on https://code.launchpad.net/~dobey/pay-ui/mir-app-test/+merge/251163 when they should be enabled?
[21:25] <robru> veebers: seems fine generally. Assuming that you just took lp:autopilot/1.5:/debian/changelog and dumped it without modifications on top of lp:autopilot:/debian/changelog it should be correct.
[21:26] <veebers> robru: right, just merged that back into trunk. Sorry I meant the version line, that's what you suggested right (1.5.0) . . . .
[21:26] <robru> veebers: oh right, yeah that's fine
[21:26] <veebers> sweet, cheers
[21:27] <robru> veebers: it should be. ping me when the rebuild is done, I'm curious how that turns out. I might need to hotfix some code if it screws up
[21:27] <veebers> robru: lol, aight, will do :-)
[21:27] <fginther> dobey, there are two jobs that failed. Unfortunately the ap tests aren't able to run unless all the required sub jobs pass first
[21:29] <dobey> fginther: oh ok. can you trigger a rebuild then? the failure is due to a test failing, which is completely unrelated to anything i changed in the branch (i only changed autopilot tests, and this is a unit test failure)
[21:29] <dobey> not quite sure why it failed. seems maybe a timing issue during that run perhaps :-/
[21:29] <fginther> dobey, rebuilding now
[21:30] <dobey> thanks fginther
[22:20] <oSoMoN> kenvandine, hey, would you have a moment to review and ack the packaging changes in https://code.launchpad.net/~osomon/webbrowser-app/use-grabToImage/+merge/250223 ?
[22:31] <oSoMoN> trainguards: I’m trying to get hold of a core-dev to ack the packaging changes in silo 21, and it will be ready for publication
[22:32] <robru> oSoMoN: k, mterry or kenvandine are my go-to guys for that...
[22:32] <robru> oSoMoN: not sure who else is around
[22:32] <oSoMoN> already ask the latter, let’s poke the former
[22:32] <oSoMoN> darn, he’s not around it seems
[22:33] <robru> oSoMoN: yeah I don't see him
[22:33] <camako> robru, can you please publish Mir 0.12 (silo 7)?
[22:33] <robru> oSoMoN: https://launchpad.net/~ubuntu-core-dev there's lots of options though, see any names you recognize? ;-)
[22:33] <oSoMoN> ogra_, would you have a minute to review and ack the packaging changes in https://code.launchpad.net/~osomon/webbrowser-app/use-grabToImage/+merge/250223 ?
[22:34] <oSoMoN> robru, a bunch of them, yes :) trying a few options now
[22:35] <robru> camako: one sec
[22:40] <camako> Thanks robru
[22:40] <robru> camako: you're welcome!
[22:44] <camako> robru, @Packaging changes need manual ACKing, do I need to do get a core dev to do this or is it done already?
[22:45] <robru> camako: normally yes, however that was a trivial diff, so I just waived it through for you
[22:46] <camako> robru, okay thanks... That's what I thought.
[22:46] <robru> camako: you're welcome
[22:56] <oSoMoN> robru, I’m off to bed, hopefully kenvandine sees my request and acks the changes and you can do the publication dance while I’m asleep, otherwise I’ll follow up on it first thing tomorrow morning. cheers
[22:56] <robru> oSoMoN: k, goodnight