[00:00] <bjf> this is a precise system which had the lts-quantal installed on it
[00:00] <bryce> bjf, ahh
[00:00] <bjf> was working just fine until a reboot .. was using the ppa .. am wondering if something in that ppa hurt me
[00:01] <bjf> or with tim removing the kernel :-(
[00:01] <bjf> so now, i'm trying to get back to just plain precise (re-install looking more likely)
[00:01] <TheMuso> Oh ok.
[00:02] <bjf> TheMuso, but thanks, that was a good possibility
[00:02] <bryce> bjf, yeah could be.  there was a recent change to the prop drivers to make them install properly when the q stack is installed (so jockey won't suggest drivers that won't work).  Perhaps those changes messed with your dist upgrade?
[00:03] <bryce> bjf, it's possible your gpu just got confused; have you tried just rebooting, now that you've purged nvidia off?
[00:03] <bjf> bryce, no .. let me try that
[00:05] <bjf> bryce, looking better
[00:06] <bjf> bryce, i'm golden .. will teach me to try lts-backport on a system i care about.  thanks much
[00:07] <bryce> bjf, no prob
[02:50] <robert_ancell> Laney, we are gst 1.0 now?
[02:58] <TheMuso> Not completely, rhythmbox according to the package metadata still uses gst 0.10.
[02:58] <TheMuso> Same with totem.
[03:10] <cyphermox> hey robert_ancell
[03:10] <robert_ancell> cyphermox, hello
[03:10] <cyphermox> did you get any progress on the bluetooth indicator?
[03:10] <robert_ancell> cyphermox, yes, I'm just waiting for the libunity indicator changes before continuing
[03:11] <cyphermox> cool
[03:11] <robert_ancell> cyphermox, did you want to work on it?
[03:12] <cyphermox> I discussed urfkill with cjwatson and slangasek at UDS (sorry for not discussing this with you sooner), I wish we could figure out a way to tie the bluetooth and nm-applet indicators together and make them both properly handle "airplane mode" via urfkill
[03:12] <cyphermox> that said, it needs a ton more work, so it's just ideas for now
[03:14] <cyphermox> thoughts?
[03:14] <robert_ancell> cyphermox, oh that would be nice. The rfkill stuff seemed really hard to use (I wrapped it into a class). You should be able to substitute it for urfkill easily.
[03:14] <cyphermox> I think so
[03:14] <cyphermox> urfkill didn't exactly actually start with the init script though, last I tried ;)
[03:15] <robert_ancell> cyphermox, is my current implementation sufficient, or does urfkill add more than just interfacing with /dev/rfkill?
[03:15] <jbicha> the nm-applet will need to get rewritten anyway as a better indicator some day
[03:15] <cyphermox> jbicha: I hear you, but I'm not exactly looking forward to doing this :P
[03:15] <jbicha> cyphermox: I'm definitely not volunteering for it either :)
[03:16] <cyphermox> robert_ancell: think of it like upower for rfkill
[03:16] <robert_ancell> cyphermox, how complex is the nm-applet? Is it mostly just presenting the NM dbus interface to the user?
[03:16] <cyphermox> robert_ancell: see, I think it possibly is
[03:16] <robert_ancell> cyphermox, so it has some policies inside it?
[03:16] <cyphermox> and then the actual dialogs and prompts and list of connections could just use libnm-gtk
[03:17] <cyphermox> robert_ancell: not much. I think it's mostly just some extra logic specific to handling modems
[03:17] <robert_ancell> cyphermox, yeah, that's basically what the bluetooth indicator does. I might have a play and see how hard it would be to do the same thing with nm
[03:18] <cyphermox> robert_ancell: let me know if you play with it.. I was thinking of hacking on such a thing but I have no clue how to start writing an indicator, didn't have time to look into it yet
[03:18] <cyphermox> I keep hoping very soon I'll have a minute or two to do it
[03:18] <cyphermox> is there a quickly template or something available? :)
[03:22] <jbicha> ok, indicator-sync is the newest official indicator and it looks like charles wrote it
[03:22] <cyphermox> yes
[03:25] <cyphermox> jbicha: what about it?
[03:26] <jbicha> I guess I was talking to myself; I was hoping that whatever was the newest would be using the best, easiest way to write indicators
[03:26] <jbicha> but it's C and I don't have a strong enough background in C
[03:28] <jbicha> oh, there's example code at http://developer.ubuntu.com/resources/technologies/application-indicators/
[03:29] <Chucrute301> Hi jbicha
[03:31] <jbicha> Chucrute301: good morning
[03:34] <TheMuso> Indicators aren't that hard.
[03:34] <TheMuso> I wrote one for ubiquity in python.
[03:36] <cyphermox> jbicha: well, it's a good example (indicator-sync) but I was hoping more in the ways of a template
[03:38] <jbicha> cyphermox: I guess that other link I posted is the best we've got except looking at existing code
[03:38] <cyphermox> right
[03:38] <cyphermox> jbicha: not the same kind of indicator though :)
[03:40] <jbicha> cyphermox: really?
[03:40] <cyphermox> indicator-power looks like a great example to play with though, it's a little more concise and similar to what an indicator for network connections would be
[03:40] <jbicha> I give up then :(
[03:40] <cyphermox> jbicha: yeah.. the example code on there is using libappindicator
[03:40] <cyphermox> it's slightly different that the "system" indicators -sync, -power, etc. which use libindicator if i'm not mistaken
[03:42] <cyphermox> though I think the difference is probably only in what you can do with them, with libappindicator being a bit more restrictive
[03:42] <TheMuso> Correct.
[03:43] <TheMuso> System indicators have 2 parts. Their service, and their .so file which is loaded by the panel and loads the service.
[03:43] <TheMuso> App indicators are dealt with by a special system indicator and its 2 bits.
[03:47]  * cyphermox goes to sleep on the idea
[05:41] <BigWhale> Good Morning.
[06:10] <pitti> Bonjour mes amis
[06:11] <didrocks> good morning
[06:13] <RAOF> Whee! Laptop says: Y U Running me in this heat!
[06:13] <pitti> bonjour didrocks! tu es plus tôt que moi ajourd'hui :)
[06:14]  * pitti looks outside, sees snow and cold, and wants sun as well
[06:14] <didrocks> pitti: c'est toi qui est plus tard que moi! je me réveille toujours à la même heure à peu près :)
[06:14] <didrocks> pitti: winter weather! :-)
[06:14] <didrocks> RAOF: you laptop says "I need weekend" it seems ;)
[06:15] <RAOF> pitti: I'll ship you some 30℃ if you like.
[06:15] <pitti> didrocks: oui, je suis allé dormier tard
[06:16] <pitti> RAOF: oui, j'aime ça!
[06:16] <pitti> didrocks: I'm quite fine getting up with my wife at 5:10 during summer, but I just can't in winter; way too little light
[06:17] <didrocks> pitti: yeah, even 7 in the dark is a little bit hard here :)
[06:18] <didrocks> RAOF: how is the family btw? Succeeding in getting some sleep now? :)
[06:18] <RAOF> We've settled down into a wake-every-3-hours-or-so-then-go-back-to-sleep pattern overnight.
[06:18] <RAOF> At least, when it's not being 24℃ overnight.
[06:19] <achiang> don't they have aircon in .au?
[06:20] <RAOF> Not in Hobart; it's rarely this hot.
[06:20] <achiang> or does that cause something poisonous to precipitate out of the air?
[06:21] <RAOF> Heh.
[08:58] <chrisccoulson> happy friday!
[08:59] <mlankhorst> seems the more complex patches I do, the less likely I make mistakes..
[08:59] <mlankhorst> better known as: my 1 liners do the most damage
[09:03] <Laney> \o/
[09:09] <seb128> hey desktopers
[09:09] <seb128> hey Laney, how are you?
[09:11] <Laney> seb128: great thanks, looking forward to going on holiday! you?
[09:11] <seb128> Laney, I'm good thanks, looking forward the W.E :p
[09:12] <seb128> Laney, do you go anywhere during your holidays?
[09:12] <Laney> yep - to the lake district
[09:13] <Laney> good walking (or pubs if the weather is too bad [/me hopes the weather is bad])
[09:15] <seb128> lol
[09:15] <seb128> Laney, have fun there ;-)
[09:16] <pitti> hey seb128
[09:16] <pitti> good morning Laney
[09:16] <pitti> FYI, pygobject is fixed since yesterday, so please feel free to kick the FTBFS due to that
[09:17] <Laney> yeah, I uploaded
[09:17] <Laney> I can't remember what package it was that was FTFBSing
[09:18] <Laney> . o O ( speaking of that, gstreamer1.0-tools needs promoting - BD of totem )
[09:19] <seb128> pitti, hey, wie gehts?
[09:20] <pitti> seb128: gut, danke! fighting with canonistack..
[09:20] <seb128> pitti, I've been playing a bit with that this week as well ;-)
[09:20] <Laney> the machines will win, resistance is futile
[09:20] <seb128> Laney, looking at the promotion
[09:21] <Laney> ta
[09:21] <Laney> it's a binary built from gstreamer1.0 which is already in main
[09:21] <pitti> ATM it seems as reliable as a three year old
[09:21] <Laney> shouldn't be too onerous
[09:22] <seb128> Laney, done
[09:22] <Laney> thanks
[09:22] <Laney> wish you got mailed about those
[09:57] <mvo> seb128: good morning, do you happen to know if the default keyring is created on install already and if so, what is creating it?
[09:58] <seb128> mvo, I don't think it is, it's created the first time an app try to use it
[09:58] <seb128> mvo, it might be that pam_keyring create it for you if you use password login (e.g not autologin)
[09:58] <seb128> mvo, hey btw ;-)
[09:58] <mvo> seb128: cool, thanks
[09:59] <seb128> mvo, yw
[10:42] <chrisccoulson> are firefox translations broken for anyone else in raring?
[10:43] <didrocks> it's ok for me right now, but I didn't upgrade since yesterday evening
[10:52] <seb128> chrisccoulson, works for me
[10:52] <chrisccoulson> seb128, yeah, it works for me as well now, but it didn't a few moments ago
[10:52] <chrisccoulson> fantastic! :/
[10:52] <seb128> chrisccoulson, but I don't have the version that hit the archive and hour ago yet
[10:53] <didrocks> chrisccoulson: speaking of long time issue, did you succeed/found/need input for anything for the stalled thunderbird on my session when quitting?
[11:07] <chrisccoulson> didrocks, did you manage to get a trace with all threads yet?
[11:07] <didrocks> chrisccoulson: I think I gave it to you few weeks ago
[11:07] <chrisccoulson> i think i hit it once, the but the trace i got wasn't terribly useful, and i'm wondering whether it was caused by me running it in gdb anyway
[11:07] <chrisccoulson> didrocks, i think you gave me a trace of the main thread
[11:08] <didrocks> 2012-11-06 09:08:49didrockschrisccoulson: http://paste.ubuntu.com/1336807/
[11:08] <didrocks> that one?
[11:12] <chrisccoulson> didrocks, ah, thanks. sorry, i must have missed that one (or just forgotten) :(
[11:13] <didrocks> chrisccoulson: no worry ;) keep me posted please!
[11:16] <seb128> chrisccoulson, thanks for making sure nothing reachs raring until the end of week ;-)
[11:25] <chrisccoulson> seb128, oh, what did i do?
[11:25] <seb128> chrisccoulson, the powerpc buildds are lagging by a day which blocks everything to build on raring and to move out of raring-proposed
[11:25] <seb128> chrisccoulson, I blame it on firefox :p
[11:25] <chrisccoulson> heh
[11:25] <chrisccoulson> that sucks
[11:25] <chrisccoulson> kill it!
[11:26] <seb128> yeah, I'm trying...
[11:26] <seb128> I emailed Rick on the topic :p
[11:26] <chrisccoulson> cool :)
[11:26] <Laney> I did just do an 11¼ hour webkit build on ppc too :-)
[11:27] <chrisccoulson> Laney, do you run unit tests on the webkit build too?
[11:27] <seb128> Laney starts sounding like a webkit maintainer to me ;-)
[11:28] <Laney> didn't we hire one of those? :P
[11:28] <Laney> I don't think it runs a testsuite during the build
[11:29] <Laney> that's a package that certainly should get an autopkgtest
[11:31] <chrisccoulson> i turned off unit tests for firefox on powerpc builds
[11:31] <chrisccoulson> they cause the builders to die
[11:31] <chrisccoulson> probably not a good sign ;)
[11:31] <Laney> I think it's the best buildd that went awol too
[11:33]  * Laney updates the seeds
[11:35] <chrisccoulson> http://cdn.memegenerator.net/instances/400x/31057672.jpg
[11:37] <xnox> chrisccoulson: LOL =))))
[11:38] <Laney> haha
[11:46] <seb128> pitti, did you ever figure out why e.g
[11:46] <seb128> $ fakeroot dbus-launch gedit
[11:46] <seb128> ** (gedit:24146): WARNING **: Could not connect to session bus
[11:46] <seb128> didrocks, ^ btw that's why the indicator-session test fails, it can't connect to the session bus under fakeroot
[11:46] <seb128> dunno why though...
[11:47] <didrocks> seb128: yeah, I know why it's failing, I also know that I asked some people to look at it :p
[11:48] <Laney> fakeroot env -u LD_PRELOAD dbus-launch gedit
[11:48] <pitti> seb128: hm, I vaguely remember that we discussed this before, but I haven't looked into it since then
[11:48] <didrocks> seb128: but I wonder why those are failing, and not the other ones
[11:49] <Laney> which drops the fakerootery
[11:50] <didrocks> ah LD_PRELOAD=libfakeroot-sysv.so
[11:50] <didrocks> Laney: but, is it really safe to run the tests under this non restricted env?
[11:50]  * didrocks wonders why dbus-test-runner works
[11:51] <didrocks> there is no trace of the drop
[11:52] <Laney> perhaps it cleans the environment
[11:53] <Laney> looks like it spawns the process with an empty environment
[11:53] <seb128> Laney, pitti: oh right, pitti suggested the "env -u LD_PRELOAD" last time
[11:53] <Laney> yeah, that says "don't really run me under fakeroot"
[11:54] <Laney> those tests probably don't need to pretend to be root anyway i suppose
[11:55] <didrocks> Laney: where do you see it in dbus-test-runner? just for the info :)
[11:58] <Laney> didrocks: I think it's libdbustest/service.c start_daemon()
[11:59] <didrocks> ok     gchar * blank[1] = {NULL};
[11:59] <didrocks> and that's what is set to the env :)
[11:59] <didrocks> I think we shuld just have indicator-session using it
[11:59] <Laney> I think so
[11:59] <didrocks> thanks Laney :)
[11:59] <Laney> didn't read it too deeply
[12:00] <didrocks> Laney: yeah, but it makes sense
[12:00] <didrocks> good thing to know about anyway :)
[12:00] <Laney> http://developer.gnome.org/glib/2.28/glib-Spawning-Processes.html#g-spawn-command-line-async
[12:00] <Laney> envp is a NULL-terminated array of strings, where each string has the form KEY=VALUE. This will become the child's environment. If envp is NULL, the child inherits its parent's environment.
[12:00] <Laney> so yeah a one element NULL array does that
[12:00] <didrocks> yep :)
[12:00] <didrocks> thanks Laney for the help! :)
[12:00] <Laney> which means you could write a wrapper to unset it for dbus-launch and re-set it for the process to be run
[12:00] <Laney> np!
[12:15] <seb128> Laney, hum, are you sure dbus-test-runner clean the env?
[12:15] <seb128> $ fakeroot dbus-test-runner dbus-launch -t gedit
[12:15] <seb128> ** (gedit:24367): WARNING **: Could not connect to session bus
[12:15] <seb128> Laney, fakeroot env -u LD_PRELOAD dbus-launch gedit works
[12:15] <seb128> e.G
[12:15] <Laney> well didrocks said it worked, so I looked for an explanation in the code
[12:15] <seb128> override_dh_auto_test:
[12:15] <seb128>    env -u LD_PRELOAD dh_auto_test
[12:15] <seb128> works
[12:15] <Laney> I didn't run it myself ;-)
[12:16] <Laney> do you need to do dbus-test-runner dbus-launch? Is that how you run it?
[12:16] <didrocks> Laney: did I say it work? I did say that other are using it :)
[12:16] <didrocks> I think you don't need dbus-launch, I'm looking at projects that are using it right now
[12:16] <Laney> I would say that's where the problem is
[12:17] <Laney> dbus-test-runner doesn't clean the env for the program it's testing, just the dbus daemon it spawns
[12:17] <didrocks> I tried without, but maybe still not the right syntax
[12:17] <didrocks>     @echo xvfb-run $(DBUS_RUNNER) --task ./test-application-info >> $@
[12:18] <didrocks> with DBUS_RUNNER=dbus-test-runner --max-wait=0
[12:18] <Laney> so you probably don't need the additional dbus-launch
[12:19] <seb128> Laney, right, the dbus-launch gedit was just my base test command
[12:19] <Laney> hum but it breaks with fakeroot dbus-test-runner -t gedit
[12:19] <seb128> that's to emulate something that needs to connect to dbus
[12:20] <Laney> why is there no manpage?!
[12:21] <didrocks> fakeroot dbus-test-runner --max-wait=0 --task ./test-service
[12:21] <didrocks> doesn't work either
[12:39] <xnox> ogra_: it's ok. channel management is not important.
[12:39] <ogra_> haha
[13:10] <Sweetshark> seb128: I uploaded libcmis-0.3.0-1~ubuntu2 to chinstrap. The trivial fix was upstreamed and the package now build on i386 too: https://launchpad.net/~bjoern-michaelsen/+archive/libreoffice-nattytest2/+build/4024506
[13:10] <Sweetshark> seb128: pls sponsor
[13:10] <seb128> Sweetshark, ok
[13:15] <Sweetshark> seb128: ah, and did you look at liblangtag_0.4.0-2~ubuntu1.dsc? it should have the licnensing fixed. I kinda lost count with the upload galore yesterday.
[13:16] <seb128> Sweetshark, http://launchpadlibrarian.net/124438253/liblangtag_0.4.0-2~ubuntu1_source.changes
[13:16] <seb128> (it's in NEW)
[13:16] <Sweetshark> seb128: cool
[13:18] <Sweetshark> seb128: btw is there a better way to check the upload queue than https://launchpad.net/ubuntu/raring/+queue ? because that one times out every second time i try to use it.
[13:19] <Laney> Sweetshark: you could try bzr branch lp:ubuntu-archive-tools ; cd ubuntu-archive-tools ; ./queue -Q new -s raring-proposed info
[14:21] <seb128> mvo, hey, could you have a look to https://code.launchpad.net/~straemer/ubuntu/quantal/software-properties/fix-for-1058070/+merge/136547 ? what do you think about it ? did you do single instance code in python before ?
[14:24] <mvo> seb128: yeah, that looks similar to what software-center is doing also I believe nowdays there is a better way in GtkApplication or something
[14:25] <seb128> mvo, right, but software-properties doesn't use GtkApplication atm I think
[14:26] <seb128> mvo, does the code there looks fine to you? I'm not sure why the SoftwarePropertiesController() class is needed
[14:29] <mvo> seb128: it looks fine, its just needed so that there is something sitting on the dbus
[14:29] <mvo> seb128: I guess it could be done differently, i.e. by folding this into the main class, but it looks ok to me as it is
[14:29] <seb128> mvo, ok, I'm merging it in then, thanks
[14:29] <mvo> thank you!
[14:36] <seb128> tseliot, hey, do you have a packaging vcs for fglrx-installer? could you queue those trivial fixes for the next upload (they are on the sponsoring queue)
[14:36] <seb128> https://code.launchpad.net/~bkerensa/ubuntu/raring/fglrx-installer-updates/depends-fix1/+merge/135994
[14:36] <seb128> https://code.launchpad.net/~bkerensa/ubuntu/raring/fglrx-installer/depends-fix1/+merge/135993
[14:37] <seb128> those are just misc:Depends to add to control
[16:38] <seb128> tseliot, can you review https://code.launchpad.net/~andrikos/ubuntu/quantal/fglrx-installer/fix-switch-to-igpu/+merge/132962 as well?
[16:47] <mhr3> desrt, ping?
[16:51] <mhr3> desrt, i was reading http://www.mesa3d.org/dispatch.html and in section 3.2 they mention interesting stuff, i wonder why doesn't glib's slice allocator use that, would make it crazy fast, wouldn't it?
[16:51] <didrocks> pitti: still around?
[16:51] <pitti> didrocks: oui
[16:51] <pitti> preparing an apport upload, then I'll sign off
[16:52] <didrocks> pitti: \o/ can you bump the build score for https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/4024139? it's pending for a long time and fixing a crasher in raring
[16:52] <didrocks> pitti: 4h ago, it was telling "about to build in 2h"
[16:52] <pitti> done
[16:52] <pitti> yeah, this morning ppc built webkit and firefox
[16:52] <didrocks> pitti: and I don't want to enable the copy cron job without me being around
[16:52] <didrocks> yep
[16:52] <didrocks> I was more hopeful :)
[16:52] <didrocks> thanks pitti!
[16:52] <pitti> queue is still 25 hours long :(
[17:02] <desrt> mhr3: don't know about the slice allocator
[17:03] <Laney> got to go out, be back in 1 hour
[17:05] <seb128> pitti, and it's not going to get any better, new KDE planned for upload soon apparently
[17:15] <mhr3> desrt, wow, i found something you don't know about? *achievement unlocked*
[17:15] <desrt> mhr3: usually i have more time to pretend that i know about things.  not today :p
[17:16] <mhr3> heh
[17:32] <tseliot> seb128:  sure, I'll check and merge those commits
[17:33] <seb128> tseliot, thanks a lot!
[18:03]  * didrocks waves good evening and good week-end
[18:17] <Laney> hmm
[18:18] <Laney> so gnome-sound-recorder is borked
[18:18] <seb128> it's easy to port to gstreamer1
[18:18] <seb128> I will do it next week
[18:18] <Laney> I guess I'll have a look at porting that when I get back, but should we unseed it? (for now? forever?)
[18:19] <Laney> oh, sweet
[18:19] <seb128> it's basically porting the profile code
[18:19] <seb128> and I looked at the sound-juicer commit
[18:19] <seb128> it was fairly simple
[18:19] <Laney> it records but when you play back it breaks
[18:19] <Laney> there will be some actual gstreamer code in there
[18:20] <seb128> Laney, http://git.gnome.org/browse/sound-juicer/commit/?id=862e7756ca714ad873afcab9b603e5ca8e59b862
[18:21] <seb128> Laney, ok, maybe it's different, I was looking at dropping libgnome-media-profile when I looked at that
[18:21] <seb128> since s-j and rb having been ported to the equivalent gst feature
[18:21] <Laney> I expect it's not that complicated
[18:21] <Laney> but there will likely be a little bit of porting to do
[18:22] <seb128> Laney, unseed ... is that needed, does it create any installability issue or is that just runtime?
[18:22] <seb128> and dropping it: no, or we need to replace it
[18:22] <Laney> no it's just broken at runtime
[18:23] <seb128> seeing the number of bugs/requests we got from oem team about bugs in the sound recorder, some people think it's a feature we should have :p
[18:23] <Laney> it's "should we seed broken apps?" and then "do we need a mic recorder?"
[18:23] <Laney> heh ok
[18:23] <seb128> I will unseed it next week if it's not fixing
[18:23] <seb128> but I want to have a good at the porting/fixing on monday
[18:23] <Laney> for libgnome-media-profiles I just switched the BDs and it built against 1.0 fine
[18:23] <seb128> ok, cool
[18:23] <Laney> doesn't necessarily mean that it works, of course
[18:24] <seb128> that lib is unmaintained though so I wouldn't mind dropping it ;-)
[18:24] <Laney> but there is very little code in there
[18:26] <Laney> btw I got a mail about gstreamer1.0 stuck in moderation for ubuntu-desktop@
[18:26] <Laney> dunno who can fix that
[18:27] <seb128> Laney, you are not subscribed to the list?
[18:27] <Laney> it was over the size limit
[18:27] <Laney> because I attached a build log
[18:27] <Laney> should have linked to it
[18:29] <seb128> Laney, what's the title?
[18:29] <seb128> oh, found it
[18:29] <seb128> Laney, accepted
[18:30] <Laney> great, thanks
[18:51] <jbicha_> Laney: are you going to do a ubuntu-meta upload since it explicitly depends on gstreamer0.10?
[18:52] <Laney> jbicha_: I did to add 1.0 stuff
[18:52] <Laney> won't drop 0.10 until we get rid of all of those apps from the default install
[18:53] <jbicha_> oh I see
[18:53] <Laney> it's just some audio sinks
[21:21] <ricotz> Laney, hi, if you are still around, i hope you can fix your typo in gnome-video-effects ;)
[21:22] <ricotz> gstreame1.0-plugins-bad, missing "r"
[21:23] <Laney> lolz, yeah, can do
[21:29] <Laney> ricotz: done, ta for spotting
[21:29] <Laney> though i hopefully would have checked excuses tomorrow and noticed
[21:29] <ricotz> Laney, thanks ;)
[21:29]  * Laney gets back to killing bad guys