[00:36] <thezenguy> request features?
[00:39] <thezenguy> /?
[04:30] <TheMuso> robert_ancell: Is there a build of GTK with mir support in a PPA anywhere?
[04:30] <robert_ancell> TheMuso, ppa:ubuntu-desktop/gtk-mir
[04:30] <TheMuso> Great thanks.
[04:30] <robert_ancell> I'm trying to uploading it to main but the current GTK+ build fails
[04:30] <TheMuso> Awesome.
[04:34] <TheMuso> Hrm not installable. Depends on libmirclient7 which is not installable...
[05:06] <robert_ancell> TheMuso, ah, it probably needs a recompile against the newer Mir
[05:06] <robert_ancell> TheMuso, you can build from lp:~robert-ancell/gtk/ubuntu-mir
[05:06] <pitti> Godo morning
[05:07] <pitti> hey robert_ancell, how are you?
[05:07] <robert_ancell> I'll push a new version into the PPA
[05:07] <robert_ancell> pitti, good
[05:07] <robert_ancell> pitti, hey do you know the plan with systemd in utopic? I'd like to try some of the features from 208
[05:07] <pitti> robert_ancell: does current simple-scan work with your scanner?
[05:08] <robert_ancell> pitti, yes
[05:08] <pitti> robert_ancell: yes, I do; want to play with a 208 package? I have a working one
[05:08] <robert_ancell> pitti, yeah, if you have a PPA or something let me know
[05:08] <pitti> robert_ancell: we need to teach systemd-shim about the cgroup creation API
[05:08] <pitti> robert_ancell: as that moved from logind to pid 1
[05:09] <robert_ancell> pitti, file a bug with the simple-scan log if you're getting problems
[05:09] <TheMuso> robert_ancell: Thanks, will pull that branch.
[05:09] <robert_ancell> TheMuso, I've just uploaded to the PPA too
[05:11] <TheMuso> Ok, probably will just wait for that, since the install is on another boxz.
[05:11] <robert_ancell> TheMuso, yeah, the PPAs tend to outrun doing it locally too :)
[05:12] <robert_ancell> gtg, bye all
[06:51] <seb128> good morning desktopers
[06:53] <didrocks> morning seb128
[06:53] <seb128> didrocks, lut ;-)
[07:02] <pitti> bonjour didrocks et seb128
[07:02] <seb128> salut pitti, ça va bien ?
[07:02] <pitti> où est le seb128 qui se leve à 8 heures ? :-)
[07:02] <didrocks> bonjour pitti !
[07:02] <pitti> seb128: oui, merci ! et toi ?
[07:03] <didrocks> pitti: petit à petit, il se lève plus tard :p
[07:03] <seb128> pitti, j'étais levé à 8h15
[07:03] <seb128> just took a bit before starting IRC
[07:03] <seb128> didrocks, roh!
[07:04]  * didrocks will upload the sebowakeup app to the clic store
[07:04] <didrocks> metrics gathered on seb's wake up time :)
[07:14] <seb128> didrocks, that would be a boring application, everybody knows I get up a 8 every morning now!
[07:16] <didrocks> ahah, I'm sure it wouldn't be that flat!
[07:37] <mvo_> seb128: I still don't get why you get up at 8 when you don't have to :)
[07:38] <seb128> mvo_, good morning ;-)
[07:38] <seb128> to be honest I'm not sure either
[07:38] <seb128> but I don't want to think about it, might me change my mind on the topic ;-)
[07:38] <seb128> +make
[07:39] <mvo_> seb128: and good moring to you as well :)
[07:41] <seb128> (brb)
[08:04] <Laney> hey hey
[08:04] <didrocks> morning Laney
[08:04] <seb128> Laney, hey, how are you?
[08:05] <Laney> yeah great
[08:05] <Laney> it's already pretty warm, been having breakfast outside!
[08:05] <Laney> you?
[08:07] <seb128> I'm good thanks
[08:07] <seb128> just had some croissant and drinking coffee, going to be a nice day here as well ;-)
[08:08] <pitti> c'est bien d'avoir l'été :)
[08:08] <pitti> hey Laney
[08:08] <seb128> oh oui, mais pas trop chaud c'est mieux !
[08:09] <Laney> hey hey pitti
[08:21] <Laney> that ringtone scrolling thing is weird
[08:22] <seb128> how weird?
[08:22] <Laney> maybe 5/10
[08:22] <seb128> my guess is that the componentloaded arrives late and setting the index is what makes it scroll
[08:23] <seb128> lol
[08:23] <seb128> I meant, what do you find weird there? the fact that the loading is so slow?
[08:23] <Laney> the panel takes a while to load
[08:23] <seb128> could be accountsservice use...
[08:23] <Laney> I am suspicious that something is slow
[08:29] <Laney> weird
[08:29] <Laney> you get the index change straight away
[08:30] <Laney> but it scrolls after a delay
[08:31] <seb128> toolkit issue?
[08:31] <Laney> maybe
[08:31] <seb128> though I see the same on trusty, so nothing new there
[08:31] <Laney> oh
[08:31] <Laney> well add an onSelectedIndexChanged: console.warn('Index: ' + selectedIndex) and you see it come in early
[08:32] <seb128> if you do a "oncomponentcomplete" on the listview, when does it come?
[08:33] <Laney> before even the selectedIndexChanged
[08:35] <seb128> weirdness
[08:51] <seb128> Laney, dealing with the sdk team is no fun
[08:52] <Laney> seb128: yeah, might have to ping someone directly
[08:52]  * seb128 tries some more nagging first
[08:52] <Laney> i'll leave this one with you
[08:52]  * Laney goes back to fixing tests
[08:52] <seb128> thanks
[08:53] <ochosi> hey seb128, do you have a minute to push https://code.launchpad.net/~ochosi/xdg-utils/support_xfce/+merge/224076 ? (sorry, i know the 14.04.1 deadline is approaching)
[08:53] <seb128> larsu, did you see that robert_ancell is having another gtk build failure issue?
[08:54] <larsu> seb128: yes he pinged me last night. I'll have a look at it today
[08:54] <seb128> ochosi, hey, oh, right, I started on merging xdg-utils from Debian but didn't wrap that up yet ... I should perhaps upload your easy patch first there ;-)
[08:54] <seb128> larsu, thanks
[08:54] <ochosi> seb128: heh, yeah, that would be nice ;) i'm not counting on this making it for 14.04.1 anymore, but it still would be great, cause the screenblanking during video-playback blows :>
[08:56] <seb128> ochosi, should be fine still for .1
[08:56] <ochosi> that'd be really great
[08:57] <seb128> we should get didrocks to review/upload that, I see that he had his patch pilot shift on monday which was an holiday here ;-)
[08:57] <ochosi> hehe
[08:57] <didrocks> seb128: it was at the end of the week and barry changed it for me
[08:57] <didrocks> I don't know why though
[08:57] <didrocks> I think a mistake from him
[08:57] <seb128> he though maybe you needed to stay on the same day and moved himself?
[08:57] <didrocks> but yeah, can have a look at this
[08:57] <didrocks> not sure
[08:58] <seb128> didrocks, thanks, the xubuntu team would appreciate it ;-)
[08:58] <ochosi> indeed!
[08:58]  * ochosi bows
[08:59] <didrocks> seb128: hum, you started to look at it though?
[09:00] <seb128> didrocks, not really, just did some "from a glance" review comments
[09:00] <seb128> I didn't look at the code/code change
[09:01] <ochosi> if you have any questions, i'm around
[09:01] <didrocks> ochosi: I'm only looking from a non-sru standpoint for now
[09:02] <ochosi> ok
[09:02] <didrocks> ochosi: seems that you are doing an inline patch
[09:02] <didrocks> would be better to add it as a patch
[09:02] <didrocks> also, I think you can break other use case with replacing '' by 'xfce'
[09:02] <ochosi> no
[09:02] <didrocks> shouldn't you just append (before the '') the 'xfce' case?
[09:02] <ochosi> the thing is, that there is a second ''
[09:03] <ochosi> i submitted another bug report about that
[09:03] <ochosi> ubuntu is carrying a useless patch, which duplicates code
[09:03] <didrocks> ah indeed
[09:03] <ochosi> so i thought i'd use that duplication to my advantage for now
[09:03] <didrocks> so yeah, the replacement is fine
[09:03] <ochosi> simply to produce the most minimal patch
[09:03] <ochosi> to get SRU'd ;)
[09:03] <didrocks> however, this should be carried as a patch, not an inline change?
[09:03] <ochosi> sure, i'm fine with that
[09:04] <didrocks> ochosi: ok, just do that change and I'll +1 for utopic
[09:04] <ochosi> although after it's SRU'd I think it should be done properly
[09:04] <didrocks> ochosi: yeah, try to get it into debian/upstream to not have that as a patch :)
[09:04] <ochosi> i've gotten in touch with upstream, but after the initial reply i haven't heard back...
[09:04] <ochosi> ofc :)
[09:04] <ochosi> i know it's a bit silly
[09:04] <didrocks> but let's do it as a patch first to unblock your SRU
[09:04] <ochosi> yup, thanks!
[09:05] <didrocks> yw, just ping me back :)
[09:05] <didrocks> (also provides a changelog with the bug ref and so on)
[09:05] <ochosi> ok, i haven't ever done a debian patch, but i'll give it a shot
[09:05]  * ochosi isn't a coder anyways...
[09:06] <didrocks> ochosi: poke me if you need any help, look for "quilt" ;)
[09:06] <didrocks> ochosi: https://wiki.debian.org/UsingQuilt
[09:06]  * ochosi only understands "scotland"
[09:07] <didrocks> and http://packaging.ubuntu.com/html/patches-to-packages.html
[09:07] <didrocks> heh ;)
[09:12] <ochosi> didrocks: quick question, after modifying scripts/xdg-screensaver i run "quilt add.." but the diff/patch is still empty..?
[09:13]  * ochosi is afraid he overlooked something obvious
[09:13] <didrocks> ochosi: yeah, you need first to restore the original file
[09:13] <didrocks> then, quilt add
[09:13] <didrocks> then making your change
[09:13] <didrocks> and finally quilt refresh
[09:13] <ochosi> i pulled a clean branch
[09:13] <ochosi> so it is the original file
[09:13] <ochosi> ah
[09:13] <ochosi> ok
[09:14] <didrocks> ok, so just quilt new and then add
[09:14] <didrocks> to say "I want to create this patch and add this file to it"
[09:14] <ochosi> i thought i have to modify before add...
[09:14] <didrocks> (it will store the original state)
[09:14] <didrocks> then, make the modification
[09:14] <didrocks> and quilt refresh to say "please register the diff for my quilt added files into my current patch"
[09:16] <ochosi> ok
[09:16]  * ochosi tries again
[09:22] <ochosi> didrocks: ok, shall i push this to a new branch?
[09:22] <ochosi> or: can i
[09:22] <didrocks> ochosi: you can, or with the same with --force-overwrite
[09:22] <didrocks> nobody else will be interested into that branch :)
[09:22] <ochosi> true :)
[09:22] <ochosi> bzr: ERROR: no such option: --force-overwrite
[09:22] <didrocks> ochosi: do not forget to bzr add the patch
[09:22] <didrocks> hum, --overwrite
[09:23] <ochosi> http://bazaar.launchpad.net/~ochosi/xdg-utils/support_xfce/revision/22
[09:23] <ochosi> didrocks: lemme know if that ^ is okay
[09:24] <didrocks> I'm looking, one sec
[09:24] <ochosi> sure, sorry, no rush ;)
[09:24] <didrocks> looking good at first side, at least :)
[09:26] <didrocks> ochosi: ok, technically, it's perfect
[09:26] <didrocks> you just need to add the patch tagging guidelines now :)
[09:26] <didrocks> this is to easily retrieve why this patch and if it's still valid
[09:26] <didrocks> ochosi: http://dep.debian.net/deps/dep3/
[09:27] <didrocks> you have some examples at the bottom
[09:27] <ochosi> whoa, wall of text...
[09:27] <didrocks> the important fields are bugs and forwarded
[09:27] <didrocks> ochosi: debian/patches/xdg-screensaver-dbus.patch
[09:27] <didrocks> it's a nice example
[09:28]  * ochosi looks again
[09:28] <didrocks> just add the forwarded to it as there is no Applied-Upstream:
[09:29] <ochosi> ok, one sec
[09:31] <ochosi> didrocks: i'm wondering though, i *have* forwarded the patch and all, but this specific patch is in a way "not needed" as xdg-screensaver upstream is a bit different (without the duplication patch)
[09:31] <didrocks> ochosi: just reference what yo udid forward
[09:31] <didrocks> you*
[09:31] <ochosi> ok
[09:31] <didrocks> as it's equivalent, that's fine :)
[09:33] <ochosi> does that look ok? http://dpaste.com/10JKBPG
[09:33] <ochosi> (i used the upstream bug title as a description now)
[09:34] <ochosi> (added author meanwhile)
[09:34] <didrocks> ochosi: just add yourself as the author, have the description wrapped up on 80 char and it's perfect :)
[09:36] <ochosi> didrocks: pushed!
[09:37] <didrocks> ochosi: perfect! sponsoring it :)
[09:37] <didrocks> (to utopic)
[09:37] <ochosi> weeee!
[09:37] <ochosi> ok, then i guess i need to do the SRU paperwork
[09:37] <didrocks> exactly
[09:38] <ochosi> thanks a bunch, didrocks
[09:38] <ochosi> for your patience and your help
[09:38] <didrocks> ochosi: thank you! no worry :)
[10:18] <ochosi> didrocks: hmm, could you take a (very quick) peek whether this looks ok? https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1342634
[10:38] <Laney> bah
[10:38] <Laney> the about panel actually reads some random hidden file
[10:39] <Laney> to get the last updated date
[10:56] <seb128> Laney, https://bugs.launchpad.net/ubuntu-system-image/+bug/1280169
[10:56] <seb128> ups, wrong bug
[10:56] <Laney> it's there now
[10:59] <seb128> Laney, not sure if the system image service was there/providing that info when we added that, though I think they use the same file/timestamp info
[11:00] <Laney> yeah it's just not that helpful when mocking the dbus service to give a fake date ;-)
[11:00] <Laney> seeing if the about panel can use info from the updates panel now
[11:00] <seb128> oh, right ;-)
[11:30] <didrocks> ochosi: not today, but before EOW is good?
[11:30] <didrocks> ochosi: ah, you should have reused the other bug
[11:30] <didrocks> change the description
[11:30] <didrocks> and add the trusty target
[11:40] <ochosi> didrocks: ok, i can move that over to the original bugreport
[11:40] <didrocks> ochosi: yeah, do that + tag + nominate for series
[11:40] <didrocks> ochosi: I'll accept the nomination once done
[11:40] <ochosi> does EOW mean it'll too late for 14.04.1?
[11:41] <didrocks> not sure when 14.04.1 freeze is, don't have the calendar handy
[11:41] <Laney> 14.04.1 *release* is in 8 days
[11:42] <didrocks> Laney: is there any freeze? I don't see on the calendar
[11:42] <Laney> I don't know of any in particular
[11:42] <didrocks> yeah, so should be done today at latest
[11:42] <didrocks> with the week of SRU
[11:42] <ochosi> humm
[11:42] <didrocks> or I guess, to be frank, it's already too late
[11:42] <didrocks> time for the SRU team to approve
[11:42] <ochosi> ok, i was afraid so
[11:42] <Laney> they might stop processing SRUs a bit before maybe
[11:42] <didrocks> for it to migrate
[11:43] <Laney> but you could speak to the SRU team if xubuntu considers it important
[11:43] <didrocks> and the iso will be built quite some days before
[11:43] <didrocks> yeah
[11:43] <didrocks> ochosi: ping me once you have everything ready
[11:43] <didrocks> ochosi: *ubuntu7.1 for the version btw
[11:43] <didrocks> so that it's < to the utopic one
[11:44] <ochosi> copied over the SRU info now to the original bug: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1309744
[11:44] <ochosi> sorry, what else is needed?
[11:44]  * ochosi isn't very packaging proficient
[11:45] <didrocks> ochosi: subscribe the sru team, nominate for release and provide a debdiff
[11:45] <didrocks> ochosi: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
[11:45] <seb128> hum, I wonder if they are going to respect that schedule
[11:46] <seb128> I didn't see any activity related to .1 yet, but maybe I didn't pay enough attention
[11:46] <seb128> they usually try to flush the queue/packages in proposed which are not verified, etc
[11:46] <ochosi> didrocks: sorry, have never done a debdiff before... i guess i'll ask someone from the xubuntu team to help
[11:46] <Laney> yeah I didn't either
[11:46] <Laney> ochosi: debdiff <current trusty.dsc> <your new dsc>
[11:48] <ochosi> Laney: thanks, but as i don't know how to create my new dsc i'd rather leave this to people who know/do packaging...
[11:49] <Laney> debuild -S :-)
[12:34]  * Laney screams
[12:35]  * ogra_ shades his ears
[12:40]  * Laney goes for a brain-cleansing lunch and crossword
[12:40] <seb128> Laney, enjoy
[13:04] <attente> seb128: hey, can we SRU https://code.launchpad.net/~attente/unity-gtk-module/1208019-2/+merge/216964?
[13:07] <ChrisTownsend> pitti: Hi, per the discussion a couple of weeks ago, we now have a new Unity package in trusty-proposed (accepted yesterday) that has new strings that need translated.
[13:09] <ChrisTownsend> dpm: I think you may have been part of that conversation as well.  ^^^^^
[13:09] <pitti> ChrisTownsend: oh, I thought that already happened some weeks ago; we got new langpacks into -proposed last week which are currently being tested, so I assume they don't have the new strings yet?
[13:09] <ChrisTownsend> pitti: D'oh, no I don't think so.
[13:10] <ChrisTownsend> pitti: Unless it took strings from Utopic.
[13:10] <dpm> hi ChrisTownsend, I had a conversation with Trevinho about it, and my impression was that it was taken care of?
[13:10] <pitti> ChrisTownsend: I think it only does that when the trusty PO template gets updated
[13:10] <pitti> but 14.04.1 is next week, so we couldn't delay them any further anyway
[13:11] <ChrisTownsend> dpm: Yeah.  We are still working it out.
[13:11] <ChrisTownsend> pitti: Ok, well, looks like we might have missed that boat then.  We got blocked behind another SRU, so it took longer than anticipated.
[13:13] <ChrisTownsend> pitti: So, even though we are going to miss the 14.04.1 release, is it possible to speed up the next langpack for the current Unity SRU?  I guess we can keep Unity in -proposed until that's done.
[13:15] <Trevinho> Or, going untranslated...
[13:19] <pitti> ChrisTownsend: yes, sure; this will only require new update packages, which are much faster to build; the main limiting factor there is how fast can people verify them
[13:20] <ChrisTownsend> pitti: Ok, I see.  I assume we are talking about after 14.04.1 is released, right?  No way to get this before, right?
[13:20] <pitti> ChrisTownsend: I think verifying the Unity SRU, get people to translate the new string into sufficiently many languages, build new packs and test them will take longer than 3 days
[13:21] <ChrisTownsend> pitti: Ok
[13:21] <pitti> ChrisTownsend: but this is just new install media, which aren't that interesting from this POV
[13:21] <Trevinho> ChrisTownsend: at this point I don't know if it's better to just go without that bug, and try to release the rest...
[13:21] <pitti> ChrisTownsend: unless it's a crucial new feature on the life system/installer
[13:21] <pitti> ChrisTownsend: but existing installs or new 14.04.1 installs will get the update either way once it hits -updates
[13:21] <Trevinho> pitti: no, in fact people with updates will get it soon... so nothing crucial, just nice to have
[13:22] <pitti> so the microreleases are mostly interesting for hw enablement
[13:22] <ChrisTownsend> pitti: It is an OEM priority, so it may be important from a pre-load perspective.
[13:23] <ChrisTownsend> pitti: ara has been tracking this
[13:26] <ChrisTownsend> Trevinho: Well, even if we pulled that fix, we still need to verify all bugs (again) and then wait a few days to make sure no regressions pop up and by that time, we probably still missed the cut-off.
[13:26] <Trevinho> ChrisTownsend: I see
[13:27] <Trevinho> well, updated systems will get it... There's nothing more we might do. We probably should have pinged the translation guys before
[13:30] <seb128> attente, do we need to SRU gtk with that patch first?
[13:32] <attente> seb128: yeah, i've just attached it here: https://launchpadlibrarian.net/180076505/gtk+3.0_3.10.8-0ubuntu1.2.debdiff
[13:34] <seb128> attente, thanks, we need a bug affecting gtk (we can use the one mentioned, just adding gtk to the components list), with SRU info (impact, test case, regression potential) ... that bug already had the testcase but not the other ones
[13:34] <attente> ok. should it be two separate sections for the two different components?
[13:35] <seb128> ChrisTownsend, Trevinho, pitti, dpm: the template seems to not be approved yet, it's in https://translations.launchpad.net/ubuntu/trusty/+source/unity/+imports?field.filter_status=all&field.filter_extension=pot ... maybe pitti or dpm can approve it (I seem to not have the acl to do that)
[13:35] <pitti> I can't
[13:35] <ChrisTownsend> seb128: Yeah, saw that.  I wasn't sure of the process...
[13:36] <dpm> seb128, I can, let me have a look. I'm a bit puzzled that it didn't get auto-approved, though
[13:36] <seb128> pitti, dpm, unping, seems like I just did that, the UI is confusing
[13:36] <seb128> I had to click on the "no import target selected yet" and validate the screen
[13:36] <seb128> not the first time I hit that one
[13:36] <seb128> the statuses on the right didn't have "approve" before that
[13:37] <ChrisTownsend> seb128: Thanks
[13:37] <seb128> seems like that worked
[13:37] <seb128> https://translations.launchpad.net/ubuntu/trusty/+source/unity/+pots/unity/fr/+translate?batch=10&show=all&search=Restarting
[13:37] <seb128> it's listed and using the utopic string
[13:38] <ChrisTownsend> seb128: Well, that seems to make this a bit easier:)
[13:39] <dpm> hm, still no idea why the auto-approval didn't work...
[13:40]  * didrocks added 15 tests for the new command line parser pre-mangler, 14 pass, one fail (the trivial case) and it was a real bug in the new code written after the tests went in \o/
[13:48] <seb128> didrocks, working tests for the win ;-)
[13:51] <didrocks> yeah ;)
[13:58] <attente> seb128: ok, updated the bug report with the required info, will it be possible to have both uploaded simultaneously to trusty-proposed since the changes are dependent on each other?
[13:58] <seb128> attente, yes
[13:59] <attente> ok, great, thanks again!
[14:01] <seb128> yw!
[14:40] <didrocks> Ran 262 tests in 710.681s
[14:40] <didrocks> coverage at 95% :)
[14:42] <seb128> we almost do as good on the timing for u-s-s
[14:42] <seb128> we have like 50 tests though :-(
[14:43] <Laney> autopiloooooootttttttttttttt
[14:43] <didrocks> yeah, as told somewhere else, I have 250 tests taking 40s and 12 taking the rest :p
[14:46] <Laney> I think the py3 test in u-s-s is borked
[14:47] <Laney> running pep8 manually shows errors ._.
[14:47] <didrocks> I have some nice ways to run pep8 as part of the testsuite if you want
[14:47] <Laney> it's supposed to work
[14:47] <Laney> probably just being called on the wrong directory
[15:09] <seb128> Laney, would it make sense to split the "get update date" change out of the ap cleanup merge request?
[15:10] <didrocks> do you still have the system-image crash btw?
[15:12] <Laney> seb128: it could be a prerequisite ...
[15:12] <seb128> I'm still on trusty so yeah
[15:12] <seb128> Laney, wfm
[15:14] <Laney> going to be tedious to split that out
[15:15] <seb128> Laney, don't bother then
[15:16] <seb128> I'm not that picky
[15:16] <Laney> up to you, I can just cherry pick and chop out the not needed bits
[15:16] <seb128> it feels nicer to have it a separate commit/logical unit, but it's not the end of the world if it's not
[15:16] <seb128> your call, I'm going to accept either way
[15:17] <seb128> it was more a reminder for next time ;-)
[15:17] <seb128> if you keep it there, please update the commit message to mention it at least
[15:17] <Laney> thought I did
[15:17] <seb128> oh, you did
[15:17] <Laney> let's wait for CI at any rate
[15:17] <seb128> I was reading the description of the change
[15:21] <Laney> oh it wasn't that bad
[15:40] <Laney> kay there we go, let's see if CI is happy
[15:40] <Laney> seriously, if it's not ...
[16:11]  * didrocks waves good evening
[16:12] <Laney> see you didrocks!
[16:12] <seb128> didrocks, night
[16:12] <didrocks> Laney: thanks, you too :)
[16:12] <seb128> see, people see goodbye to you ;-)
[16:12] <didrocks> seb128: enjoy tennis :p
[16:13] <didrocks> seb128: not like… yesterday! ;)
[16:13]  * seb128 was afraid didrocks would close IRC before he responded
[16:13] <seb128> lol
[16:13] <seb128> didrocks, thanks
[16:13] <seb128> see you tomorrow!
[16:13] <didrocks> thanks, see you ;)
[16:13] <Laney> I did check tab completion to make sure you hadn't quit
[16:13] <Laney> :P
[16:13] <didrocks> ahah
[21:07] <robert_ancell> yay, 13.10 EOL today! Less things for me to support!