[06:12] <hikiko> Hi
[06:53] <didrocks> good morning!
[07:07] <pitti> Good morning
[07:08] <didrocks> hey pitti
[07:09] <pitti> bonjour didrocks !
[07:25] <seb128> good morning desktopers
[07:26] <didrocks> re seb128
[07:26] <seb128> re didrocks :-)
[07:29] <darkxst> hey seb128 pitti didrocks
[07:29] <seb128> hey darkxst
[07:29] <didrocks> good evening darkxst, it's been a long time :)
[07:30] <darkxst> didrocks, I was away for a couple of weeks with no internet
[07:30] <darkxst> and been sick with a cold the last week
[07:30] <pitti> hey darkxst, how are yoU?
[07:30] <pitti> oh, I hope you feel better now!
[07:30] <darkxst> pitti, on the mend though
[07:31] <didrocks> yeah, seems like it's sick time all around me! ;)
[07:31] <darkxst> heat waves here, aren't they meant to kill the germs!
[07:32] <darkxst> though we have been bouncing between high 30's to 40 for a few days, then 15 wet and windy
[07:32] <seb128> hey pitti
[07:33] <didrocks> darkxst: typical weather to get sick then ;) (btw, 15 wet and windy is what we had end of last week/early this week :p)
[07:34] <pitti> bonjour seb128, ça va ?
[07:34] <seb128> pitti, oui, et toi ?
[07:35] <pitti> ça va bien !
[07:42] <darkxst> pitti, is it possible to get the adt artifacts for s390x builds?
[07:42] <pitti> darkxst: sure, they are all exposed on swift and linked from on autopkgtest.u.c., regardless of arch and release
[07:44] <darkxst> oh da, I was looking on jenkins ;(
[07:45] <didrocks> pitti: what's your opinion if I use something like "python3 -m compileall" in setup to avoid the xenial issue?
[07:45] <didrocks> (or rather, the issue I'm seeing on xenial)
[07:45] <darkxst> though I could have sworn I added scripts to copy out tracker test-suite.log's, they not there!
[07:47] <darkxst> maybe I never uploaded those ;(
[07:49] <darkxst> or they got dropped in some merge
[07:51] <pitti> didrocks: or clean the git tree after every test?
[07:52] <pitti> didrocks: not sure if compileall would help -- creating *more* root owned files isn't going to fix the "no permission to write to the file" issue
[07:52] <didrocks> pitti: I meant, doing that in setup is basically "all user-owned compile file"
[07:52] <didrocks> so no more root owned ones
[07:52] <pitti> ah, as user
[07:53] <pitti> didrocks: if it works, sure
[07:53] <pitti> I wonder if there's an env var or so to completely disable writing __pycache__ files
[07:54] <didrocks> pitti: hum, that's another tempting idea
[07:55] <pitti> didrocks: compileall as user should do the trick too, if it works ;)
[07:55] <pitti> http://stackoverflow.com/questions/154443/how-to-avoid-pyc-files
[07:56] <pitti> $PYTHONDONTWRITEBYTECODE ?
[07:56] <didrocks> pitti: sounds promising, I still need to be careful because of docker container
[07:56] <didrocks> as the env isn't passed completely
[07:56] <didrocks> (and that's where the root execution is done
[07:56] <didrocks> )
[07:56] <didrocks> sharing the same volume
[07:57] <didrocks> so, let's try compileall first and reassess :)
[07:57] <didrocks> pushed, will see at next attempt I guess
[07:57] <pitti> ah, right
[07:58] <didrocks> pitti: I wonder why it doesn't show up on wily though, when setting it "all tests", I always have:
[07:58] <didrocks> - in docker, running a local test server as root (that was the compiled files it was complaining about)
[07:59] <didrocks> - then, some large tests use a local test server as non root
[07:59] <didrocks> and that's medium, then large tests
[07:59] <didrocks> so, no tricks here, I wonder it never complained, can't read the file or whatsoever even on xenial adt
[08:01] <pitti> didrocks: I'm quite sure the difference is because of 3.4 vs. 3.5, perhaps the docker guest uses 3.4?
[08:01] <pitti> didrocks: and since a previous test was running with 3.5 on xenial, we would have pre-compiled __pycache__ for 3.4 on wily, but for 3.5 on xenial, so docker has to re-compile for 3.4 (as root)
[08:02] <didrocks> pitti: yeah, it does and make sense (and means that probably my compileall trick will fail then :p), but that would be reproduceable on a xenial qemu, right?
[08:02] <pitti> yes, should
[08:02] <didrocks> on which, or my memory fails me, I did some TESTS=all on it
[08:02] <didrocks> hum, let's give it a try
[08:03] <pitti> didrocks: you just need to run compileall for all python versions that are involved
[08:03] <pitti> didrocks: that'll get trickier once we drop 3.4 from xenial, if your guests as root use 3.4 still
[08:03] <pitti> didrocks: but why are they using a shared storage?
[08:03] <didrocks> yeah, not a bad idea
[08:04] <pitti> didrocks: I think it's more robust to either reset and clean the git tree between tests, or copy it into a temp dir for every docker run
[08:04] <didrocks> pitti: it could have been a cp, but it's the easier way to share code with docker
[08:04] <pitti> then the test can do whatever it wants to in docker
[08:04] <didrocks> yeah, reset maybe
[08:04] <didrocks> pitti: copy it -> not a fan, as I need to be compatible in system and master tests
[08:04] <didrocks> and so, using the some paths outside (where the tests are launched) and inside
[08:05] <didrocks> to abstract from the fact it's running in a container
[08:05] <didrocks> but yeah, let's see how this goes, ther are options anyway
[08:05] <didrocks> (clean-tree between tests being the most obvious one)
[08:09] <pitti> didrocks: right, "git clean -fdx", and "git reset --hard origin"
[08:09] <didrocks> yeah, familiar with those 2 :)
[08:09] <pitti> it might fail with root-owned dirs,  though
[08:09] <didrocks> well, let's see next run after failure though
[08:09] <didrocks> can use sudo -n ;)
[08:09] <pitti> ah, right
[08:33] <larsu> good morning!
[08:33] <larsu> happy Friday everyone!
[08:36] <pitti> hey larsu !
[08:36] <larsu> morgen pitti!
[08:37] <seb128> hey larsu
[08:37] <seb128> happy friday!
[08:37] <larsu> bonjour seb128!
[08:39] <seb128> larsu, how are things going?
[08:41] <larsu> seb128: good thanks :) How about you?
[08:42] <seb128> I'm good thanks!
[08:42] <seb128> larsu, what are you working on now? still nautilus? (we should stop investing in that update)
[08:42] <larsu> no, took a break from that and doing i18n support and alternate names in geonames
[08:43] <larsu> I figured since we're not decided if we take that or not, it doesn't make time to work on that further
[08:43] <seb128> great
[08:43] <seb128> yeah, I was just unsure since you didn't mention anything else since
[08:43] <larsu> ah, sorry
[08:43] <seb128> no worry
[08:43] <seb128> when you have free slots, could you look at merging your gedit menubar patch upstream?
[08:43] <seb128> they said on the bug they were +1 mostly
[08:44] <larsu> sure. Do you have a bug # handy?
[08:44] <seb128> I noticed that there are no keybinding displayed in the menu
[08:44] <seb128> so might be something to fix
[08:44] <larsu> yeah, can add that to the xml
[08:44] <seb128> gnome
[08:44] <seb128> gnome bug 741904
[08:44] <seb128> danke
[08:45] <seb128> finish your geonames work first
[08:45] <seb128> we have the patch in gedit and there is no hurry
[08:45] <seb128> it's just one things more upstream once it's merged
[08:46] <larsu> seb128: nah let me do it now. It's quick and I want another ok from them (accepted-commit_now)
[08:46] <seb128> k
[08:46] <seb128> maybe add the keybindings to the xml first though?
[08:47] <larsu> ya, of course
[08:47] <seb128> but I guess that part is not too much work
[08:49]  * larsu nods
[08:56] <pitti> Laney, seb128, didrocks: in case anyone is interested: http://pad.ubuntu.com/autopkgtest-sprint
[08:57] <pitti> didrocks: killing current ubuntu-make run, as it again tmpfailed on the "large-stdout: No such file" error
[08:58] <pitti> didrocks: I will investigate/fix that ASAP, sorry
[08:58] <didrocks> pitti: ok, I was going to wonder if anything happened :p
[08:59] <didrocks> keep me posted!
[08:59]  * didrocks reruns manually meanwhile
[08:59] <pitti> didrocks: ah, do you have a fix/workaround for the EPERM?
[08:59] <pitti> (in git now, I mean)
[09:00] <didrocks> pitti: it's in git, wily didn't get it on this run, but previous xenial run should have got it
[09:00] <didrocks> and this one restarted as well apparently
[09:00] <pitti> right
[09:00] <pitti> cool
[09:00] <pitti> oh, it wasn't a problem in wily in the first place, so maybe I killed the wrong one
[09:02] <seb128> pitti, noted
[09:02] <didrocks> yeah
[09:02] <willcooke> o/
[09:02] <didrocks> hey willcooke
[09:04] <Laney> hey hey
[09:04] <pitti> good morning Laney and willcooke!
[09:05] <willcooke> Happy Friday
[09:06] <larsu> seb128: hm, _ are missing as well, but that would introduce new strings
[09:06] <larsu> seb128: should be fine though, right?
[09:06] <larsu> g'day willcooke!
[09:13] <seb128> larsu, yes, we are early enough in the cycle for that
[09:13] <seb128> hey willcooke Laney
[09:14] <Laney> yo
[09:14] <Laney> happy friday!
[09:14]  * Laney checks
[09:14] <Laney> yes
[09:14] <Laney> happy friday!
[09:16] <didrocks> morning willcooke!
[09:16] <didrocks> oupss
[09:16] <didrocks> Laney:
[09:16] <didrocks> still re-good morning though :-)
[09:16] <Laney> oh didrocks
[09:16] <Laney> every morning feels a bit sad!
[09:17] <didrocks> why?
[09:17] <Laney> closer...
[09:17] <Laney> to a dark future
[09:17] <seb128> I guess to know you are moving away from us
[09:18] <seb128> Laney, happy friday!
[09:18] <didrocks> so cute!!!
[09:20] <larsu> :)
[09:20] <larsu> bonjour didrocks!
[09:20] <didrocks> guten morgen larsu!
[09:21] <didrocks> pitti: would you record your infra introduction? I will be travelling during the autopkg sprint
[09:22] <pitti> didrocks: ah, I'll see to doing that (not sure how yet, but I'll ask around)
[09:23] <didrocks> pitti: do you mind if I rerun a wily full test? (the one you killed by mistake was close to completion, again :p). I would at least love to see one full suite running :)
[09:23] <pitti> didrocks: argh, sorry; sure, please do
[09:24]  * didrocks runssss
[09:24] <pitti> I'll be more careful next time
[09:24] <didrocks> thx ;)
[09:24] <Laney> if it's a hangout on air(?) I think they are saved to youtube automatically
[09:24] <pitti> Laney: I suppose I need a G+ profile for that?
[09:25] <pitti> Laney: I only have screenshare and chat in a HO
[09:25] <pitti> or maybe I'll try one with my public G+
[09:25] <Laney> I don't know
[09:25] <Laney> should be the same as we do for UOS and there's some instructions for that somewhere
[09:25]  * Laney looks
[09:25] <didrocks> you can do that with your canonical account as well
[09:26] <Laney> think he's saying that he has no G+ on that one
[09:28] <Laney> meh
[09:28] <Laney> can't find the page
[09:29] <didrocks> it's https://hangouts.google.com/
[09:29] <pitti> Laney: I've never done that, I can't find it on my personal G+ profile hangout either
[09:29] <pitti> ah! got it
[09:30] <Laney> https://wiki.ubuntu.com/UDS/Sessions
[09:30] <pitti> but for the life of me I don't see how this works on my canonical account
[09:30] <pitti> Laney: well, that's outdated, Google chnaged the UI
[09:30] <didrocks> pitti: did you try the url I gave? ^
[09:31] <pitti> didrocks: yes, and that works with my personal account, but not with my Canonical one
[09:31] <pitti> I'll try to add a G+ profile again
[09:31] <didrocks> interesting
[09:32] <Laney> ah
[09:32] <Laney> never before did I see anything out of date on the wiki :)
[09:32] <didrocks> ;)
[09:37] <pitti> https://plus.google.com/u/1/events/cgbs40huhrq94tp4qehc8n7qpao?hl=en
[09:37] <Laney> yay
[09:37] <pitti> now, how do I get the hangout URL for participants?
[09:37] <pitti> this only provides the youtube link, AFAIUI
[09:38] <pitti> oh, nevermind
[09:43] <willcooke> ochosi, hey - larsu mentioned you have some branches with theme fixes in.  Mind giving me some links?  Maybe I can reuse in the other theme fixes which are going on
[10:06]  * Laney discovers a transition
[10:12] <Sweet5hark> Laney: what does one do in that situation: Dance the transition? Whack it until it stops moving? Crumble and smoke it?
[10:14] <Laney> cry in a corner and hope it goes away
[10:14] <Sweet5hark> popey: what kind of update? bumping vanilla to 5.0.4?
[10:15] <Sweet5hark> Laney: well yeah, thats the obvious choice.
[10:15] <popey> Sweet5hark, morning. So we're currently on 5.0.3
[10:15] <Laney> it's the only one
[10:15] <Laney> soon I'll call a bigger boy to come and save me
[10:16] <popey> Sweet5hark, we were just looking to see if there was an update worth taking as we haven't updated for a few months
[10:18] <Sweet5hark> popey: https://wiki.documentfoundation.org/ReleasePlan <- currently there is 5.0.4, 5.0.5 is due very soon.
[10:19] <Sweet5hark> popey: I would recommend against going 5.1.0 right away (which will appear roughly at the same time as 5.0.5)
[10:19] <popey> Sweet5hark, 5.0.5 seems the best course for us, skipping 5.0.4 IMO
[10:19] <popey> What do you think?
[10:19] <Sweet5hark> popey: yes, thinking the same.
[10:19] <popey> We don't want to update right now, as we're preparing a store upload for a week or twos time
[10:20] <popey> and want to push new LO to the next DocViewer release
[10:20] <popey> Ok, good.
[10:20] <popey> Thanks.
[10:28] <ochosi> willcooke: mostly look at the last few commits of github.com/shimmerproject/Greybird/, nothing too fancy for now, seems like the gtk3.18 theme breaks are not too bad (just the linked buttons mess sucks a bit, i'll probably just take whatever SASS adwaita uses and convert it to CSS with a converter for now...)
[10:29] <willcooke> thanks ochosi
[10:29] <willcooke> Laney, haz updates
[10:30] <willcooke> Laney, attached a new HTML file for you
[10:30] <Laney> boom
[10:30] <Laney> hey you know how to do merge proposals right?
[10:30] <Laney> :D
[10:30] <willcooke> damn it
[10:30] <Laney> haha
[10:30] <willcooke> I knew you'd say that
[10:30] <Laney> nah it's okay
[10:30] <willcooke> I thought about it, but it will take me like 20 mins to work out and I've got a meeting in a mo
[10:32] <darkxst> willcooke, if you did more MP's it would take you like 1min ;)
[10:33] <willcooke> darkxst, :) fair point
[10:33] <willcooke> but then I'd end up writing code, and _no one_ wants that
[10:34] <darkxst> willcooke, lol right, because your just here to manage the code writers? ;)
[10:35] <Laney> cracking the whip
[10:35] <pitti> didrocks: BTW, I now figured out how to hand out ssh access to scalingstack instances
[10:35] <pitti> in case you need this
[10:35] <didrocks> oh nice!
[10:36] <darkxst> Laney, crocodile dundee had a bigger whip
[10:38] <Sweet5hark> ochosi: heya, saw your mail btw, just didnt get to reply yet (still trying to get on top of the after-christmas backlog). Awesome that you'll be at FOSDEM!
[10:39] <Laney> you aussies
[10:39] <Sweet5hark> ochosi: lets try to meet at the booth (or the LibreOffice dev room, where the talks happen).
[10:40] <didrocks> bbiab
[10:47] <hikiko> Trevinho! :) did you say before that in multi-monitor we always use direct rendering and in single-monitor we use redirected?
[10:48] <Trevinho> hikiko: well, no... If there's a fullscreen window (like a game) that uses the whole screen, then we don't need to use the compositor, so we bypass that
[10:48] <hikiko> oh, ok
[10:48] <hikiko> and this on single monitor
[10:48] <hikiko> that's normal :)
[10:49] <hikiko> I misunderstood you
[10:49] <hikiko> thanks
[10:59] <hikiko> Trevinho, willcooke, https://code.launchpad.net/~hikiko/compiz/compiz.handles-chrome-chromium-windows-in-fullscreen could you top approve it if it works for you?
[10:59] <hikiko> (so that it gets merged)
[11:01] <hikiko> oh wait I just saw marko's review sec
[11:05] <willcooke> :)
[11:10] <davmor2> willcooke: open a nautilus window, can you see little black triangles in the top corners that look like they should be rounded (put it on a light back ground to highlight it)
[11:11] <hikiko> done
[11:11] <hikiko> now you can top approve i think :)
[11:18] <willcooke> davmor2, known issue
[11:18] <willcooke> I thin
[11:18] <willcooke> k
[11:18] <willcooke> larsu, ^
[11:19] <davmor2> willcooke: only seem to affect nautilus here which is why triggered the question :)
[11:19] <larsu> (a) known issue with header bars, being fixed by Trevinho & hikiko
[11:19] <larsu> (b) we'll probably revert to an older nautilus which doesn't have a header bar
[11:19] <davmor2> larsu: awesome :)
[11:23] <hikiko> larsu, I am not currently working on header bars and I think marco is working on other stuff right now
[11:23] <Trevinho> hikiko: well, your work is related ot that
[11:23] <hikiko> shadows?
[11:24] <larsu> ya, that's what I meant
[11:24] <larsu> we can't have argb non-titlebar windows without you shadow work
[11:24] <hikiko> ok that's in progress
[11:25] <hikiko> I didn't notice that nautilus has pseudo-shadows
[11:25] <hikiko> no wait
[11:25] <hikiko> I just saw what you mean
[11:25] <hikiko> how this is related to shadows?
[11:26] <hikiko> I am not changing Trevinho's code for decorations
[11:26] <larsu> I hope Trevinho will after you're done "P
[11:26] <larsu> :P
[11:26] <hikiko> I am adding shadows for windows that don't have already like chromium/chrome, shaped windows etc
[11:27] <hikiko> ok :) basically my shadows have 2 big bugs I am trying to fix and then I push the branch.. :) sorry guys :)
[12:07] <Sweet5hark> willcooke: around?
[12:08] <willcooke> Sweet5hark, ya
[12:18] <larsu> seb128: I've updated the gedit bug (sorry, lunch in between)
[13:02] <seb128> larsu, thanks
[13:08] <seb128> Laney, that u-c-c html diff is first class
[13:09] <seb128> "something change in that file which is on one line"
[13:10] <Laney> hahaha
[13:10] <Laney> I didn't even bother to diff it
[13:10] <Laney> I did open it in vim though
[13:10] <Laney> for about 0.5 seconds
[13:30] <larsu> seb128: ok, commmiting to master in a bit (some changes needed :( ) but I don't think this is something for the 3.18 branch - or what do you think?
[13:31] <seb128> larsu, no it's not, we should keep it as distro patch for this cycle
[13:31] <larsu> seb128: ok. Will you update it? (the ones on the bug apply cleanly to 3.18)
[13:31] <larsu> I can do as well
[13:31] <seb128> I can do it
[13:31] <larsu> coolio, thank
[13:31] <larsu> s
[14:00] <didrocks> pitti: phew, one full run at last: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-wily-ubuntu-desktop-ubuntu-make/wily/amd64/u/ubuntu-make-git/20160115_111825@/log.gz :)
[14:01] <didrocks> 501 tests passing :-)
[14:03]  * desrt yawns
[14:03] <desrt> hihi.
[14:03] <larsu> morning desrt
[14:04] <didrocks> hey desrt
[14:04] <desrt> morning larsu, didrocks
[14:04] <Laney> greetings desrt
[14:04] <desrt> and laney :)
[14:05] <desrt> happy friday, everyone
[14:05] <Laney> it is!
[14:06] <attente> hi guys
[14:06] <desrt> attente: i misssss you!
[14:06] <seb128> hey attente desrt, happy friday
[14:06] <desrt> haven't seen you in day!
[14:06] <attente> <3
[14:07] <didrocks> hey attente!
[14:07] <attente> hi didrocks!
[14:08] <attente> congrats on the new job :)
[14:08] <didrocks> thx ;-)
[14:10] <Laney> hey attente
[14:11] <larsu> morning attente!
[14:11] <Laney> why is there an old maliit-inputcontext-gtk in the queue as well as the one I uploaded?
[14:11] <Laney> looks like that should be rejected
[14:11] <attente> hi Laney, larsu
[14:12] <attente> Laney: sounds old, what's the version number?
[14:12] <Laney> same
[14:12] <Laney> someone probably uploaded the silo for some reason
[14:13] <attente> probably robru, he was helping me upload it
[14:14] <Laney> ho hum
[14:14] <Laney> didrocks: you want to hit ZE reject button? :)
[14:17] <didrocks> Laney: no punt intended, isn't it? ;)
[14:18]  * didrocks flushes
[14:18] <didrocks> and done
[14:19] <Laney> what great service!
[14:19] <willcooke> would use again?
[14:20] <Laney> I killed attente's silo
[14:20] <Laney> hope I get the chance to use again
[14:20]  * Laney weeps
[14:20] <attente> :o
[14:22] <Laney> time for lunchables
[14:22] <didrocks> Laney: next time, some tea while proceeding
[14:22] <didrocks> (and some music ofc)
[14:24] <seb128> Laney, enjoy!
[15:20] <pitti> didrocks: yay!
[15:46] <didrocks> time for week-end (have an appointment right now and started early the whole week :))
[15:46] <didrocks> see you on Monday guys, have a good week-end!
[15:47] <Laney> see you didrocks!
[15:47] <didrocks> bye Laney!
[16:04] <Sweet5hark> oh great, someone ripped off credit cards right at the ATM next to CCC congress. https://twitter.com/Linuzifer/status/688025478972702720
[16:04] <Sweet5hark> i guess in makes sense, you can hide in over 9000 suspects ...
[16:05] <Sweet5hark> Then again hiding from 10.000 angry nerds chasing you down rarely worked of anyone either.
[16:14] <willcooke> ha
[16:42] <Trevinho> seb128: https://code.launchpad.net/~3v1n0/nautilus/folders-in-new-windows/+merge/280130 this didn't hit the archive yet, right?
[17:01] <seb128> Trevinho, not yet, mitya57 did an upload but ignoring the vcs
[17:01] <seb128> Trevinho, we are looking at reverting to the wily version of nautilus though
[17:03] <Trevinho> seb128: oh... why? Because of the headerbar?
[17:03]  * pitti waves good weekend!
[17:03] <seb128> pitti, have a good w.e!
[17:03] <Trevinho> seb128: no way to backport the embedded transfer window? as it would be a good benefit...
[17:04] <seb128> Trevinho, would it?
[17:04] <seb128> it's one of the issues
[17:04] <Trevinho> ah
[17:04] <seb128> users don't notice copies starting or being done
[17:04] <seb128> it's too subtle
[17:04] <Trevinho> I remember you said you liked it :-D
[17:04] <seb128> I found it cool
[17:04] <Trevinho> seb128: well, if the launcher progress stays it should be enough, isn't it?
[17:04] <seb128> but I was unsure if that was too much of a change
[17:04] <seb128> well it's not the only issue
[17:05] <seb128> the icons size
[17:05] <seb128> 3 values only and no small ones
[17:05] <seb128> the headerbar
[17:05] <seb128> the lack of menubar (and it's not easy to add one back, larsu spent quite some time on it to hit walls)
[17:05] <Trevinho> I see
[17:05] <seb128> several bugs and features dropped (making symlinks, deleting bypassing the trash)
[17:06] <Trevinho> Ok, let me know when the things are happening, since I've to update a couple of my patches
[17:06] <seb128> right
[17:06] <seb128> sorry about that, I was still unsure what to do
[17:06] <Trevinho> The change should be small, but we'd need it
[17:06] <seb128> but read the irc log from the weekly meeting
[17:06] <seb128> k
[17:06] <Trevinho> seb128: yeah, i read something in the lines, but not the full discussion
[17:08] <Trevinho> seb128: so... At this point it's probably better to wait before landing the unity launcher integration branch? Not that it shouldn't work with older nautilus, but...
[17:09] <seb128> Trevinho, up to you
[17:09] <seb128> you can downgrade nautilus to make sure if you want
[17:23]  * Trevinho waves... see you mon...
[17:24] <seb128> Trevinho, have a good w.e!
[17:54] <willcooke> happy weekend all, see you next week
[18:00] <seb128> happyaron, do you plan to upload https://code.launchpad.net/~brunonova/ubuntu/trusty/ibus/lp1240198_2/+merge/278226 ?
[18:00] <seb128> it's still in the sponsoring queue
[18:04] <seb128> ok, done with patch piloting now
[18:04] <seb128> I'm calling it a week
[18:04] <seb128> having a good w.e everyone!
[18:04] <Laney> me too
[18:04] <Laney> bye!
[18:04] <Laney> be good!
[19:51] <robru> attente: https://requests.ci-train.ubuntu.com/#/ticket/861 published by timo in fact
[19:52] <attente> robru: ah, ok
[19:52] <robru> attente: (click 'show audit logs' to see who did what)
[19:53] <attente> cool, thanks :)
[19:56] <robru> you're welcome