[04:01] <plars> grr
[04:02] <plars> well I almost got mako to 100%, but new image arrived
[08:39] <popey> Morning
[08:43] <sil2100> Morning!
[09:04] <ev> morning folks
[09:05] <sil2100> Morning :)
[09:06] <sil2100> popey: 79 smoketesting results look promising! Could you do some manual tests for that one?
[09:06] <popey> doing it right now
[09:08] <sil2100> Thanks
[09:15] <popey> sil2100: testing done, #79 is good
[09:16] <sil2100> I guess Omer is out today already?
[09:18] <popey> he isnt marked on holiday in the calendar
[09:23]  * sil2100 feels a promotion in the air
[09:23] <sil2100> popey: can you feel it as well?!
[09:23] <sil2100> @_@
[09:24] <popey> I can feel something
[09:49] <sil2100> hm, I can't connect to my VPN - does anyone else have this problm?
[09:49] <sil2100> Ah, ok, works
[10:00] <sil2100> om26er: ! hello!
[10:00] <om26er> sil2100, hi
[10:00] <sil2100> om26er: you can't even imagine how happy we are to see you! Can you give image #79 a manual spin on maguro?
[10:01] <sil2100> It's a nice promotion candidate
[10:01] <om26er> sil2100, sure, how early do you want the results ?
[10:01] <om26er> sil2100, I have a call starting now for 30mins, I can test after that
[10:02] <sil2100> No haste, just give us a sign how it goes
[10:59] <alan_g> Can someone help? Jenkins isn't picking up https://code.launchpad.net/~andreas-pokorny/mir/allow-transparent-server-buffers/+merge/199405 - whereas other MPs to this target are reviewed by CI
[11:01] <sil2100> om26er: did you have a moment for testing #79 already?
[11:02] <om26er> sil2100, yes, already updated the doc :)
[11:02] <om26er> sil2100, its good to go.
[11:12] <sil2100> \o/
[11:12] <sil2100> cjwatson: hello! Are you around by any chance? We're looking for someone with knowledge that could promote an image for us :)
[11:14] <cjwatson> yes.  confirm it's #79?
[11:15] <sil2100> popey: can you confirm that you tested #79? :) SInce I just see smoketesting and 79 is what we want
[11:16] <cjwatson> 09:15 <popey> sil2100: testing done, #79 is good
[11:16] <cjwatson> seems clear enough
[11:16] <popey> you should check the spreadsheet
[11:16] <popey> https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Ai33BkOcORLLdE4xLTFtSE80ZkpITXZ3aV85cWtPX2c
[11:16] <sil2100> Just wanted someone to double check his device, but I guess yes
[11:17]  * sil2100 doesn't want to promote the wrong image right before holidays
[11:17] <popey> hah
[11:17] <popey> especially after http://www.markshuttleworth.com/archives/1306 ☻
[11:18] <popey> 79 is also a Sexy Prime, apparently
[11:19] <popey> According to https://en.wikipedia.org/wiki/79_(number)
[11:19] <cjwatson> promoted #79
[11:20] <popey> \o/
[11:20] <popey> thanks cjwatson
[11:20] <sil2100> cjwatson: thank yoU!
[11:20] <sil2100> popey: and thank you for testing ;)
[12:00] <sil2100> cihelp: does anone know why jenkins and everything is so very slow today?
[12:01] <cjwatson> sil2100: Is Jenkins in 1SS?
[12:02] <cjwatson> 11:47 -!- moon127 changed the topic of #is to:  Vanguard: moon127 || Known Issues: Network issues 1SS || Emergency number: +44 207 630 2499 || RT: rt@admin.canonical.com || http://status.admin.canonical.com/
[12:03] <sil2100> cjwatson: then I guess it could be that, since I'm getting 13.0 kB/s transfers in autopilot jobs on q-jenkins
[12:03] <sil2100> cjwatson: thanks
[12:09] <sil2100> Laney: hello! Do you have a moment to do a packaging change ACK for the need of unity8 release?
[12:09] <Laney> ok
[12:10] <Laney> sil2100: got to go out in 5 minutes ;-)
[12:11] <sil2100> Laney: !
[12:11] <sil2100> Laney: http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/Unity8/job/cu2d-unity8-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity8_7.84+14.04.20131220-0ubuntu1.diff
[12:11]  * sil2100 hastens
[12:12] <sil2100> From the packaging POV there's just a new install file, one file removed and one added and that's that
[12:12] <sil2100> *new installed file
[12:15] <Laney> sil2100: looks ok
[12:15] <sil2100> Laney: thank you :)
[12:15] <Laney> time to go, back in a bit
[12:16] <sil2100> Ok!
[12:38] <om26er> sil2100, do we do phone testing monday and tuesday ?
[12:39] <sil2100> om26er: you mean, next week?
[12:39] <om26er> sil2100, yes
[12:39] <sil2100> om26er: I think we're all shutting down already next week, so I guess no one will be around for that
[12:39] <sil2100> So I expect nothing besides automatic stuff to happen
[12:39] <om26er> sil2100, ok. good to know
[13:10] <sil2100> uh
[13:15] <sil2100> xnox: hi! Could you make sure to sync changelog entries back to bzr branches when you do direct pushes to the archive? For instance lp:autopilot - I already synced it if anything
[13:15] <fginther> morning
[13:15] <xnox> sil2100: autopilot is not daily released, is it? and the changes in the archive are present in the lp:autopilot.
[13:15] <sil2100> Morning
[13:16] <jdstrand> is anyone looking at the landing asks? I added some stuff yesterday but no feedback. if people aren't looking at it, I'll exercise core-dev for them, otherwise, please let me know how to coordinate
[13:16] <sil2100> xnox: it is, it's in cu2d
[13:16] <xnox> sil2100: hm, k.
[13:16] <sil2100> xnox: the changelog entry wasn't in trunk, and it was causing a problem with daily-building it
[13:17] <sil2100> But now it's ok
[13:18] <xnox> sil2100: how does one fork the package properly? so lp:autopilot has gazzion changes staged and is well ahead of the archive, is there a branch which actually matches the archive that can be daily-released without all the staged stuff?
[13:19] <xnox> sil2100: e.g. something like some upstreams have "master" match the last released, and everything else is on "pu" branch. And master is only moved when released.
[13:19] <sil2100> xnox: no, it's either releasing everything that's in trunk, or cherry-picking individual changes, releasing manually and then merging in the changelog entry back to trunk
[13:19] <sil2100> xnox: the truth is...
[13:19] <xnox> sil2100: gotcha.
[13:20] <sil2100> xnox: cu2d was not meant to work like it works like now
[13:20] <xnox> sil2100: so changelog entries is that bit i was missing.
[13:20] <sil2100> xnox: in the past it wasn't a problem, since cu2d was 'releasing to archive' packages one/few times a day, so there was no need to worry about cherry picking individual changes and manual uploads
[13:21] <sil2100> Nowadays we get a lot of stuff accumulated
[13:21] <xnox> sil2100: =))))) well, to me cu2d is opaque and I just follow instructions to hopefully not cause a lot of pain elsewhere =)
[13:21] <fginther> alan_g|lunch, I see the issue with https://code.launchpad.net/~andreas-pokorny/mir/allow-transparent-server-buffers/+merge/199405. The submitter is not on the white list. will have it fixed shortly
[13:22] <sil2100> xnox: nothing bad happened anyway! Also mistake on my side that I only now noticed that cu2d missing-changelog, again I was 'assuming' instead of making sure ;)
[13:22]  * sil2100 has that bad habit of assuming things
[13:22] <fginther> morning
[13:22] <xnox> too much good faith and not grumpy/bitter enough =)))))))
[13:23] <xnox> sil2100: which is a good thing ;-)
[13:31] <sergiusens> fginther, hey, long shot, but,  any progress on dh-golang?
[13:33] <fginther> sergiusens, not yet. I'm pursuing the the saucy upgrade path, but I need to  coordinate this so nothing blows up
[13:36] <sergiusens> fginther, so next year?
[13:37] <sergiusens> fginther, for me at least, I'm out after today :-)
[13:39] <fginther> sergiusens, that's a safe bet
[13:41] <sil2100> sergiusens: hi! Do you have the power to start image builds?
[13:43] <sergiusens> sil2100, yes, but from cdimage servers; not from that fancy button we are supposed to use ;-)
[13:44] <sil2100> sergiusens: ;) Could you somehow kick a touch image build for us? Would be grateful :)
[13:46] <sergiusens> sil2100, sure
[13:47] <sergiusens> sil2100, DONE
[13:48] <sergiusens> the trigger, not the build ;-)
[13:51] <sil2100> \o/
[13:51] <sil2100> Thanks
[13:51] <alan_g> fginther: thanks
[14:25]  * jdstrand uploads click-apparmor and apparmor-easyprof-ubuntu
[14:37] <sergiusens> sil2100, seems the cdimage side is done
[14:37] <sil2100> sergiusens: excellent :)
[14:38] <sil2100> kenvandine: hi!
[14:38] <kenvandine> hey sil2100
[14:38] <sil2100> kenvandine: do you know anything about ubuntu-system-settings-online-accounts ?\
[14:38] <kenvandine> yup
[14:38] <kenvandine> what's up?
[14:38] <sil2100> kenvandine: I'm trying to run the tests there and I get: ImportError: No module named oauth.oauth
[14:39] <kenvandine> got a log?
[14:40] <sil2100> http://paste.ubuntu.com/6606003/
[14:41] <sil2100> (I'm using the new autopilot and want to make sure that it's not the reason)
[14:41] <sil2100> But I don't think oauth has anything to do with ap? Or does it?
[14:41] <kenvandine> must be a mistting depnds on python-oauth
[14:41] <sil2100> hm, I already have it installed though
[14:41] <sil2100> python-oauth is already the newest version.
[14:42] <sil2100> All other tests pass flawlessly
[14:42] <sil2100> I'll try downgrading my autopilot later to see if it's at fault, but for me it doesn't make sense
[14:43] <kenvandine> unless something about the python path is mangled
[14:45] <sil2100> kenvandine: strange, running import oauth.oauth as foo in a new python env standalone also fails
[14:46] <sil2100> Not sure if autopilot could affect this, I'll try a reboot
[14:47] <kenvandine> python2.7 right?
[14:50] <kenvandine> sil2100, that works on my device
[14:51] <kenvandine> image 78 though
[14:51] <kenvandine> but that isn't part of the image
[15:01] <sergiusens> sil2100, kenvandine it's highly unlikely to be autopilot
[15:01] <kenvandine> sergiusens, it isn't
[15:01] <kenvandine> but seems like something broken for sil2100
[15:01] <kenvandine> env python -c 'import oauth.oauth'
[15:01] <kenvandine> that works on my device
[15:02] <kenvandine> but not for sil2100
[15:02] <sil2100> Might be only here, I'll check what could have affected that and why it's failing
[15:02] <sergiusens> sil2100, are you running autopilot for python3?
[15:03] <kenvandine> sergiusens, the oauth import fails for him even without autopilot
[15:03] <kenvandine> sil2100,  do a reinstall of python-oauth
[15:04] <sil2100> kenvandine: anyway, unrelated to this, but I have been testing the new autopilot and sadly we cannot release it :<
[15:05] <sil2100> kenvandine: there seems to be some regression and I cannot run any click tests
[15:06] <sergiusens> sil2100, do you have logs?
[15:06] <sergiusens> sil2100, just want to take a peek
[15:06] <kenvandine> :(
[15:09] <sil2100> sergiusens: sure, one moment
[15:09] <sil2100> I'll pastebin the error that we're getting
[15:10] <sil2100> sergiusens: http://paste.ubuntu.com/6606162/ <- this error we're getting for each and every click test
[15:10] <sil2100> It might be a small issue like with a variable renamed or something
[15:11] <sil2100> But still, I asked the TnT team to run all AP tests before submitting a landing request
[15:11] <sergiusens> sil2100, did we land any new ui toolkit thought as well?
[15:12] <sil2100> sergiusens: yes, why you ask?
[15:15] <sergiusens> sil2100, just because I'm fairly certain UbuntuUIToolkitEmulatorBase is provided by that package
[15:15] <sil2100> sergiusens: hm, not sure about that - but what I know is that downgrading autopilot fixed the issue
[15:16] <sergiusens> sil2100, ah, then you are already on track
[15:16] <sil2100> sergiusens: so, the same UITK + new autopilot = failure, + old autopilot = success
[15:16] <sil2100> :<
[15:16] <sergiusens> sil2100, what was the previous version?
[15:17] <sil2100> Autopilot? 1.4+14.04.20131125-0ubuntu3 was the previous, now I'm testing from daily-build PPA: 1.4+14.04.20131220-0ubuntu1
[15:17] <sil2100> Too bad, wanted to land this one but it seems I won't
[15:20] <sergiusens> sil2100, this seems to be the commit that breaks it http://bazaar.launchpad.net/~autopilot/autopilot/trunk/revision/402
[15:38] <plars> psivaa: I'm going to retry the desktop failures from today, I'm hoping the timeout was just because of the 1ss network problems reported in is
[15:39] <plars> psivaa, cjwatson: precise server/alternate installs still failing due to bug #1262053
[15:40] <psivaa> plars: go for it.. it dint look to me as impacted by the network slowness. but worth a try
[15:41] <plars> psivaa: I hadn't looked past the timeout before hoping that it was an easy one to hunt down, did you investigate more already and find something else?
[15:43] <psivaa> plars: it looked like exception during installation. could not try out to see where exactly though.
[15:44] <psivaa> plars: regarding the precise d-i iirc, infinity said this is because the packages were in transit on Monday.. i'm not sure if that's still the case
[15:46] <plars> psivaa: I was asked to followup if it wasn't corrected by yesterday's image, so I was just carrying through with that
[15:47] <psivaa> plars: ack
[16:07] <plars> psivaa: desktop/amd64 passing now
[16:11] <psivaa> plars: ohh. great. i should have tried that before.. thanks
[16:11] <cjwatson> plars: apt-setup/proposed=true when testing debian-installer from -proposed
[16:12] <plars> cjwatson: it's not blocking me from anything, you had just mentioned that it should be resolved soon
[16:12] <cjwatson> plars: I'm not in control of when linux-lts-raring gets promoted to -updates
[16:12] <plars> cjwatson: np
[16:13] <cjwatson> plars: that's https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1257165
[16:13] <cjwatson> oh, though I wonder if I need to fix some seeds
[16:14] <cjwatson> whoops, yes
[16:21] <sil2100> popey: are you super busy?
[16:22] <kgunn> sil2100: hiya!
[16:22] <kgunn> sil2100: so...we're still in landing ask mode right ?
[16:22] <kgunn> sil2100: meaning...my team sync'd the dev branch with our trunk....
[16:23] <sil2100> kgunn: yes, but I guess we won't be landing anything risky now ;) What's up?
[16:23] <kgunn> i don't want it to get pulled automagically...i need to do all the proper bumping
[16:23] <kgunn> sil2100: great
[16:23] <sil2100> What projects is that for?
[16:23] <kgunn> sil2100: lp:mir
[16:23] <kgunn> sil2100: but then associated deb bumps for rebuilding in papi, unity-mir & u-s-c
[16:24] <kgunn> sil2100: it can certainly wait till "next year" :)
[16:24] <kgunn> sil2100: i'll do all the proper bumping and queue up the MP's
[16:24] <kgunn> will send a mail later with all the details....
[16:24] <kgunn> sound ok ?
[16:25] <sil2100> kgunn: excellent! Right, I would prefer not to get these risky things merged and released on the last working Friday this year ;)
[16:26] <sil2100> plars: hello!
[16:26] <plars> sil2100: hi
[16:27] <sil2100> plars: do you know when and if smoketesting already is working on image 80?
[16:27] <plars> sil2100: let me look
[16:28] <plars> sil2100: odd, it's not
[16:28] <plars> sil2100: it looks like it showed up about 8 min. ago?
[16:28] <sil2100> plars: hm, maybe because it was triggered in some other way?
[16:29] <popey> sil2100: wassup?
[16:29] <plars> sil2100: it should see the new file out there and just start
[16:29] <popey> am on a call right now, but type at me
[16:29] <sil2100> plars: ah, ok, thanks ;) Then it's all good if it's on right now
[16:30] <plars> sil2100: no it's not
[16:30] <plars> sil2100: I don't know why it hasn't started yet
[16:30] <sil2100> popey: once you have a free moment, could you also do some manual testing for image #80 ?
[16:30] <popey> sil2100: sure, will do in 30 mins
[16:31] <sil2100> plars: hm, I'm a newbie in the process of image building so it might sound noobish, but sergiusens said he kicked the image from cdimage servers, so maybe that's why?
[16:32] <plars> sil2100: I don't think so, as long as http://system-image.ubuntu.com/trusty-proposed/mako/index.json get's updated (and the similar file for maguro), then jenkins should see the change in the file and go
[16:34] <plars> retoaded: have you ever seen the url change trigger die? know of a way to restart just that?
[16:35] <plars> sil2100: if nothing else, I can start it by hand, but prefer to have it triggered properly so that I don't get it twice
[16:35] <cjohnston> sil2100: is the landing instructions in the topic still accurate? what do we think about maybe moving that to a wiki page for now instead of a paste?
[16:35] <plars> sil2100: I can confirm that the last one it saved an md5sum for is indeed different, it just doesn't seem to have updated
[16:36] <sil2100> cjohnston: let me read that up, didn't look at it for a while - but I guess a wiki page would be indeed better
[16:36] <retoaded> plars, I've seen it die but that was related to putting jenkins in to "prepare to shutdown" mode then canceling it. In this case it may have been caused by the network outage. The only way I know of to resolve it is to restart the jenkins service.
[16:36] <sil2100> plars: hmmm
[16:37] <sil2100> plars: I would prefer it to be fixed properly as well I guess
[16:37] <plars> retoaded: ok, well there are other jobs running now, so I can kick it off manually and we can restart it later when there's a good opportunity?
[16:37] <retoaded> plars, ack.
[16:38] <retoaded> restart at your convenience since I'm not really here :-)
[16:38] <cjwatson> plars: ok, rebuilding images to fix that precise d-i failure, now that I've deconfused myself and spotted my novice mistake :)
[16:38] <cjwatson> sorry for the misdirection earlier
[16:38] <plars> cjwatson: np, thanks!
[16:39] <plars> sil2100: thanks for spotting that, they are running now. Is there going to be another build today?
[16:39] <sil2100> plars: np, I guess we'll fire one after a meeting, but since there are no new changes from our side it's not top-priority
[16:40] <sil2100> cjwatson: I actually *probably* have a favor to ask of you Colin!
[16:41] <sil2100> cjwatson: since ogra_ is away, we would need someone else to set up a cronjob to automatically fire image builds regularily more than once
[16:41] <ogra_> why would you want more than one a day ?
[16:42] <sil2100> ogra_: Alexander asked for that
[16:42] <sil2100> ogra_: he wants images 2 times a day during holidays
[16:42] <sil2100> Don't ask me why!
[16:42] <ogra_> (given that not much work should happen during company vacation, i think one build per day linke oon weekends is enough)
[16:43]  * ogra_ thinks its overkill ... but if asac thinks it is needed ...
[16:43] <cjwatson> there are autosyncs four times a day, so it's not particularly unreasonable - whatever
[16:44] <cjwatson> 02 3 * * *      for-project ubuntu-touch cron.daily-preinstalled --live
[16:44] <cjwatson> you have that at the moment, right?
[16:44] <ogra_> yep
[16:44] <ogra_> 3am
[16:44] <cjwatson> so if I just make that 3,15?
[16:44] <ogra_> yeah
[16:44] <cjwatson> as of now?
[16:44] <ogra_> seems like sil2100 wants that
[16:45] <cjwatson> done
[16:45] <ogra_> :)
[16:45] <cjwatson> sil2100: ^-
[16:46] <sil2100> Yes, that's what asac wants, yes ;)
[16:46] <sil2100> Thank you!
[16:56] <popey> sil2100: #80 is good
[16:57] <sil2100> popey: \o/ thanks!
[16:57] <sil2100> om26er: hi! Would you find a last moment today to test #80 on maguro? Once we have smoketesting result we'll be able to promote it then
[16:58] <om26er> sil2100, ok, upgrading
[16:59] <sil2100> om26er: thank you
[17:01] <sil2100> kenvandine, cyphermox, robru, plars, ev, popey: last meeting guys! Hangout?
[17:01] <ev> I've got to miss this one - need to head to bluefin to pick up some paperwork
[17:03] <kenvandine> doh!  be right there
[17:08] <sergiusens> sil2100, I thought we had broken click tests?
[17:12] <sil2100> sergiusens: click tests are broken for autopilot trunk
[17:12] <sil2100> So we just don't release it
[17:13] <sergiusens> ah, since I read promotion ;-)
[17:13] <sergiusens> all ok
[17:17] <cjwatson> plars: will https://jenkins.qa.ubuntu.com/job/precise-server-amd64_default/ auto-retest?  there's a 20131220.1 image now
[17:18] <plars> cjwatson: checking
[17:20] <plars> cjwatson: hmm, it looks like the url change trigger is broken on more than one jenkins server - retoaded was there an update recently or something? both q-jenkins and d-jenkins are having this problem now
[17:22] <plars> retoaded: I'm going to set d-jenkins in quietdown mode, you ok if I try restarting it?
[17:22] <plars> cjwatson: I'll make sure it gets rerun one way or another, but I'd like to clear up why jenkins isn't seeing it
[17:24] <plars> cjwatson: on a slightly unrelated note - did pitti happen to talk to you about the rsyslog issues? I had asked on the bug if we could add syslog to the dialout group so that it can work over /dev/ttyS0 without having to jump through some early_command hoops
[17:24] <plars> cjwatson: he said he wanted to ask you about it first
[17:24] <plars> cjwatson: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1258245 is the bug for reference
[17:28] <cjwatson> not sure - honestly I was just firefighting on that myself
[17:28] <cjwatson> it was slangasek who did the initial merge :)
[17:28] <cjwatson> plars: jenkins> thanks
[17:29] <plars> cjwatson: I've got it mostly worked around in preseeds for now, but it's not nice
[17:31] <plars> cihelp: restarting d-jenkins, it's in quietdown mode right now but the url change trigger is not working properly
[17:33] <dobey> is CI down right now? or just slow?
[17:34] <fginther> dobey, there are some network issues that IS is working on, it's causing some jenkins problems
[17:35] <dobey> ah ok
[17:36] <plars> cjwatson: that seems to have cleared things up, and the server jobs are running now
[17:37] <cjwatson> plars: great, thanks
[17:37] <om26er> sil2100, done
[17:49] <cjwatson> plars: oh good, precise server back to green - closing the bug
[17:57] <sil2100> om26er: thank you!
[17:58] <sil2100> kenvandine, popey: I guess you were right Alan, let's play it safe and not promote anything - I guess we're good with what we have ;)
[17:58] <sil2100> So no need poking anyone
[17:59] <sil2100> I think I'll finish for today and take care of some christmasish things
[18:00] <popey> sil2100: ok ☻
[18:00] <sil2100> Thanks for everything everyone!
[18:00] <popey> Happy christmas sil2100
[18:00] <sil2100> Have a great new year :)
[18:00] <sil2100> Thanks!
[18:00] <sil2100> I'll stay on IRC for a while in case I'm needed, but AFK
[18:05] <timp> why are many projects not included here? http://ci.ubuntu.com/smokeng/trusty/touch/mako/80:20131220.1:20131219.2/5599/
[18:05] <timp> like ubuntu-ui-toolkit?
[18:05] <timp> they are included for image 79 http://ci.ubuntu.com/smokeng/trusty/touch/mako/79:20131220:20131219.2/5583/
[18:09] <sil2100> timp: testing of image 80 is still in progress
[18:09] <timp> sil2100: ok, thanks
[18:10] <sil2100> timp: we're running testing of all components, so in a few hours this list should be complete
[18:16] <tedg> Trying to kick off an upstart-app-launch autolanding run, but it seems I've failed.
[18:16] <tedg> http://s-jenkins.ubuntu-ci:8080/job/upstart-app-launch-trusty-amd64-autolanding/
[18:16] <tedg> I thought I could just do "Build Now"
[18:16] <tedg> ?
[18:24] <slangasek> plars, cjwatson: rsyslog /dev/ttyS0, I'm not sure it makes logical sense for syslog to be a member of dialout by default fwiw
[18:25] <plars> slangasek: the problem we're running into is that we used to be able to do this, but the recent change, I think it made rsyslog no longer run as root iirc, causes it to no longer have permission to log our installs over serial
[18:27] <slangasek> plars: yes, I understand that, but logging to /dev/ttyS0 is not a stock configuration, so why should the stock permissions give rsyslog access to /dev/ttyS0?
[18:29] <plars> slangasek: it's something that used to work fine until the change. I'm not sure how many others might be using it as well for automated installs. If you have other ideas, I'm open to them though
[18:30] <slangasek> plars: it's something that used to work fine /by making a configuration change/.  Changing the group membership of syslog is another configuration change you will need to make
[18:31] <slangasek> I don't think it's a logical stock security policy to have syslog in dialout
[18:33] <dobey> https://code.launchpad.net/~dobey/cupstream2distro-config/add-purchase-service/+merge/199848 <- if anyone could review this please? getting it deployed once the current network issues are fixed would be nice too. :)
[19:02] <kenvandine> sil2100, sounds good!
[19:22] <fginther> cihelp, restarting s-jenkins, it stopped triggering jobs during the network outage
[19:32] <fginther> dobey, regardig https://code.launchpad.net/~dobey/cupstream2distro-config/add-purchase-service/+merge/199848. Has the integration team reviewed ubuntu-purchase-service for daily-release?
[19:33] <dobey> fginther: i wasn't aware any team needed to do that, so no.
[19:34] <fginther> dobey, ok, I'll ask them to chime in
[19:36] <dobey> what integaration team, btw?
[19:39] <fginther> dobey, https://launchpad.net/~ubuntu-unity. This isn't really documented anywhere, this is just our process for adding projects. Most people don't propose MPs :-)
[19:39] <fginther> cyphermox, kenvandine, robru, are any of you around to review https://code.launchpad.net/~dobey/cupstream2distro-config/add-purchase-service/+merge/199848 ?
[19:39] <dobey> weird :)
[19:40] <robru> fginther, sure, just a sec
[20:24] <bregma> hey guise, is it possible for me to re-kick my failed CI builds once in a while when necessary?  The 'click here' schlumphed into the MP is a little misleading
[20:29] <cjohnston> bregma: link
[22:11] <fginther> bregma, I can give you an account to enable the rebuilds
[22:14] <bregma> fginther, is that's what required to have 'Click here to trigger a rebuild:' trigger a rebuild when clicked?
[22:14] <fginther> bregma, yes
[22:14] <fginther> that will actually take you to the correct jenkins page to do the rebuild
[22:14] <fginther> (assuming you are logged in)
[22:17] <bregma> OK, then I guess that's what I would need
[22:21] <fginther> cihelp, I need to restart s-jenkins again due to a defunct process which is blocking access to the VM server
[22:22] <sil2100>  /quit
[22:22] <sil2100> ...
[22:22] <sil2100> ;)
[22:22] <fginther> sil2100, sorry to hear that
[22:22]  * sil2100 sighs
[22:22] <sil2100> So many f**k-ups right before holidays!
[22:22] <sil2100> So, once again, happy christmas everyone!