[01:27] <micahg> hi bluesabre , I noticed an RC for blueman was in Debian, did we want that nowish or is later ok
[01:38] <bluesabre> micahg: no hurry
[01:43] <micahg> ok
[01:43] <bluesabre> micahg: have you had a chance to glance over the greeter package?  I think it's okay, files are migrated as I expect, so it should be safe
[01:43] <micahg> no, sorry, will try soon
[01:59] <micahg> bluesabre: it seems that you are missing a slash before usr in a few places
[02:00] <micahg> also, conf files in /usr/share seem wrong
[02:01] <Unit193> Depends on the config, that's where the lightdm xubuntu session is, and is good there.
[02:06] <micahg> well, I would think it violates FHS, /etc is for configuration files
[02:07] <micahg> I see the lightdm files there...
[02:07] <Unit193> They aren't meant to be changed.
[02:08] <micahg> doesn't matter
[02:08] <micahg> hrm
[02:08] <micahg> well, does matter :)
[02:08] <micahg> but still feels wrong
[02:11] <micahg> violates Debian policy 10.7.2, https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
[02:14] <bluesabre> debian did it first at least
[02:14] <bluesabre> override_dh_install:
[02:14] <bluesabre> 	dh_install debian/01_debian.conf usr/share/lightdm/lightdm-gtk-greeter.conf.d/
[02:16] <micahg> in lightdm?
[02:16] <Unit193> No, the greeter.  To override defaults, create a config file in /etc/
[02:16] <Unit193> micahg: pbuilder ships defaults in /usr/share/ where you're supposed to override in /etc/
[02:24] <micahg> hrm
[02:28] <micahg> seems like this needs clarifying
[02:28] <micahg> I have to run right now though
[02:35] <Unit193> OK.
[02:36] <bluesabre> so maybe in the case of this package, 01_ubuntu.conf should go in /usr, and the existing conf should migrate to /etc
[06:43] <ochosi> Unit193: btw, wanna take on patching ubiquity to use feh instead of xfdesktop (since you've worked on that part before) ?
[06:45] <Unit193> Not specifically...
[06:45] <Unit193> Can't say I know it or python well.
[07:01] <ochosi> Unit193: if you change your mind and take a look, that'd be appreciated anyway ;)
[08:08]  * knome cheers for Unit193 
[10:46] <bluesabre> Team members read below
[10:46] <bluesabre> :)
[10:46] <knome> wut
[10:47] <bluesabre> I'm trying to guage interest in meeting times since I suck at making it to meetings
[10:47] <bluesabre> gauge
[10:47] <knome> we can simply run yet another doodle poll (tm)
[10:49] <bluesabre> M-F, 0:00 - 2:00 UTC, 9:00 - 12:00 UTC, 20:00 - 23:59 UTC
[10:49] <bluesabre> Weekends, any time
[10:49] <bluesabre> knome: yeah, that might require more effort and less chiming in
[10:49]  * knome shrugs
[10:49] <bluesabre> !team
[10:49] <knome> i can set it up
[10:49] <bluesabre> (See above)
[10:50] <knome> leaving your schedule there is easy
[10:50] <knome> but sure, whatever works
[10:50] <bluesabre> knome: sure, if you'd like to set it up, we can go from there
[10:50] <bluesabre> :)
[10:50] <knome> ok, just a sec
[10:58] <knome> http://doodle.com/vmzrybyw9r9929wt
[11:02] <knome> !team | please fill in the doodle poll at http://doodle.com/vmzrybyw9r9929wt for meeting time coordination
[11:03] <knome> oh stupid bot :)
[11:03] <knome> !conga-rats-#ubuntustudio-devel | bluesabre 
[11:03] <knome> !team | please fill in the doodle poll at http://doodle.com/vmzrybyw9r9929wt for meeting time coordination
[11:03] <knome> ubottu, please? :)
[11:04] <knome> my luck has turned!
[11:04] <knome> !team | please fill in the doodle poll at http://doodle.com/vmzrybyw9r9929wt for meeting time coordination
[11:04]  * knome slaps ubottu
[11:05] <knome> !team
[11:05] <knome> ^
[11:06] <knome> 22UTC... wasn't that our previous fixed meeting time :)
[11:06] <knome> seems like it still works
[11:07] <bluesabre> edit my previous since I am UTC dumb... M-F, 0:00 - 6:00 UTC, 9:00 - 12:00 UTC, 22:00 - 23:59 UTC
[11:07] <slickymasterWork> done bluesabre, but please take in consideration that I'm just filling for DST
[11:07] <bluesabre> but yeah, up there on doodle
[11:07] <knome> lol
[11:07] <knome> doodle makes it so much easier to figure out the results <3
[11:07] <knome> that just works
[11:07] <slickymasterWork> when I'm not under DST my time frame goes back one hour
[11:07] <bluesabre> slickymasterWork: np, this will help me get a general overview
[11:08] <slickymasterWork> weekends generally any hour is good, provided I'm awake :P
[11:08] <slickymasterWork> and not hanged over 
[11:08] <knome> slickymasterWork, likely sameish for most
[11:08] <slickymasterWork> lol, not being hanged over?
[11:09] <knome> slickymasterWork, but you didn't fill in any weekend time?
[11:09] <knome> was referring to DST...
[11:09] <slickymasterWork> see above knome 
[11:09] <slickymasterWork> I know you were
[11:09] <knome> i know but it would be great if you could slap in all the times there then
[11:10] <knome> this isn't "you promised you can do that time on every occasion, pay us 1M$ since you didn't"
[11:10] <bluesabre> gotta run now, bbl
[11:10] <knome> it's "let's see when we generally are all available"
[11:10] <knome> hf bluesabre 
[11:10] <slickymasterWork> ok ok ok, it's done
[11:10] <knome> thanks ;)
[11:11] <slickymasterWork> hf bluesabre 
[11:11] <knome> slickymasterWork, i don't see it though :P
[11:12] <knome> oh, there it is
[11:12] <slickymasterWork> blame google
[11:12] <knome> ;)
[11:12] <knome> always...
[11:12] <slickymasterWork> :)
[12:56] <ochosi> afternoon ppls
[13:14] <knome> hullo
[13:15] <ochosi> knome: i've got a free hour or so today, wanna work on some LO icons together or something?
[13:16] <knome> with YOU?
[13:16] <knome> :P
[13:16] <ochosi> yeah, i know... does that make it weird?
[13:17] <knome> let's see
[13:17] <knome> i'm having a nice break now
[13:22] <sorinb> Hello :)
[13:23] <ochosi> knome: uhm, you mean a break in the sense that you're going afk? or a break in the sense that you wanna do something? :)
[13:23] <ochosi> hi sorinb 
[13:23] <sorinb> i'm also sorinello, the guy from last night with the eclipse import issues :)
[13:24] <ochosi> i supposed so :)
[13:24]  * ochosi is wearing his sherlock hat
[13:25]  * sorinb is still wearing his end-user hat :)
[13:30] <knome> ochosi, heh, break in the sense that i'm not doing work/foss work
[13:30] <knome> not exactly afk either though
[13:48] <brainwash> sorinb: did you read bug bug 1388922 ?
[13:56] <sorinb> brainwash, yes, but there is a thing I don't understand
[13:56] <sorinb> it states that the but was opened on 
[13:56] <sorinb> Bug #1388922 reported by Danila Poyarkov on 2014-11-03
[13:56] <sorinb> yet, the first comment is from wrote on 2011-01-20: 
[13:57] <knome> sorinb, it's linked to a bugzilla bug that was reported earlier
[13:57] <brainwash> sorinb: the first comments are synced from the upstream report
[13:59] <sorinb> ok, I understand. Not sure what is freedesktop.org, but it's quite olf idf this is from 2011 
[14:01] <brainwash> the package in ubuntu is old. some patches were added over time
[14:01] <sorinb> so I guess I can close my issue, since it's not related to xfce at all. I have no experience on how packages from different entities interfere, so I was expecting exo to have full authonomy and apply whatever background command it needed to achieve the functionality. I implied that exo-open should call xdg-open
[14:01] <brainwash> ubuntu 12.04 has version 1.1.0~rc1 too
[14:02] <brainwash> the other way round, xdg-open should open exo-open
[14:03] <brainwash> you should test xdg-open from upstream git before closing your report
[14:30] <sorinb> brainwash, what do you mean ? checkout, build, install and test ?
[15:10] <knome> pleia2, ygm re: -contacts
[15:12] <brainwash> sorinb: yes. it's just a shell script after all, so not much can go wrong
[15:12] <knome> having seen what $users do... yes, a lot of things *can* go wrong ;)
[15:20] <sorinello> indeed. I only ran autogen.sh and then built. I don't even know where the packabe is created so I can install it. Even more, I don't know what to test. The fact that it's not working ?
[15:21] <knome> the reason why you would check with upstream is if it's working with the upstream version, eg. if the bug you have found is already fixed, but just not landed into ubuntu yet
[15:22] <brainwash> how did you build it? why do you expect a package?
[15:23] <sorinello> knome, yeah, I understand. But the bug on launchpad doesn't seem fixed
[15:23] <knome> sorinello, when using the upstream version?
[15:23] <brainwash> ubuntu is downstream, freedesktop is upstream
[15:23] <sorinello> knome, : https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1388922 this seems open
[15:23] <knome> sorinello, yes, i've seen the bug...
[15:24] <sorinello> so if the bug is still open, I guess there is no fix in the code
[15:24] <knome> sorinello, you should follow what brainwash is telling/asking you to check
[15:24] <knome> sorinello, in ubuntu, yes.
[15:24] <brainwash> sorinello: mmh, strange logic
[15:24] <knome> sorinello, the upstream status is "fix released" though
[15:24] <knome> sorinello, so it should be fixed in upstream
[15:25] <knome> sorinello, but as i said, maybe not in ubuntu yet
[15:25] <sorinello> brainwash, I understand. I'm totally new to these, it seems I can't even read correctly launchpad :)
[15:25] <knome> sorinello, that's why brainwash tried to ask you if the bug is fixed for you in the upstream version
[15:26] <brainwash> sorinello: so, from now on you should post all the commands you are using to pull/build/install software
[15:26] <sorinello> brainwash, I ran autogen.sh fomr the exo root dir, then I did "make". And I was expecting something like a deb ? again, I am totally new to this. If you have any documentation on how to get me up to speed, please give me
[15:26] <sorinello> a deb which I would install with dpkg
[15:26] <knome> sorinello, building with make *never* gives you a drb.
[15:26] <knome> *deb
[15:27] <knome> sorinello, it builds the code to a binary from the sources
[15:27] <brainwash> build this -> http://cgit.freedesktop.org/xdg/xdg-utils/
[15:28] <sorinello> ok, I'll remember that. Also I'm very new with C, I have more like a Java background
[15:28] <brainwash> forget about exo for a moment :)
[15:28] <brainwash> xdg-open is part of xdg-utils
[15:28] <brainwash> which is outdated in ubuntu (several years old)
[15:28] <sorinello> any reason why they use such an old version in ubuntu ?
[15:29] <brainwash> the new version seems to fix a lot issues
[15:29] <brainwash> mainly because of debian which also has an old version
[15:29] <brainwash> usually new packages are synced from debian
[15:30] <sorinello> I see
[15:30] <sorinello> interesting
[15:30] <sorinello> at least for me, since this gives me some clues on how the whole Ubuntu echosystem works :)
[15:30] <sorinello> *ecosystem
[15:31] <brainwash> it can be a mess
[15:32] <sorinello> so basically the flow is like this: I want to open a link from xchat, xchat runs xdg-open, then xdg-open should figure out that I have xfce, then xdg-open should call exo-open ?
[15:33] <brainwash> yes
[15:33] <sorinello> and a fix has been made in vanilla xdg (freedesktop) but has not been ported into ubuntu/xubuntu yet
[15:33] <brainwash> yes
[15:34] <sorinello> and you want me to get the v anilla xdg, build it locally and see if the new xdg works as expected
[15:34] <brainwash> indeed
[15:36] <sorinello> and the bug in xdg vanilla (freedesktop) has been reported in 2011, so this functionality is broken for 3+ years ?
[15:36] <sorinello> broken in xubuntu
[15:36] <sorinello> and xfce
[15:37] <brainwash> I don't know, maybe it was not broken completely in the beginning.
[15:41] <brainwash> sorinello: also, the ubuntu package is heavily patched (some upstream changes have been picked over time, even custom tweaks were added)
[15:42] <sorinello> odd, because from pov of the functionality, this doesn't sound so complex.. it's not rocket science... I wonder what was t he rationale of these small patches
[15:44] <knome> fix other bugs.
[15:46] <sorinello> seems to be more an integration/armonization problem ...
[15:46] <sorinello> *harmonization between packages, so they fit better in *buntu
[19:47] <dkessel> welcome SwissBot
[19:53] <knome> Unit193, does it offer free swiss chocolate samples?
[19:57] <Noskcaj> ochosi, yes, only since 1.5 (maybe 1.5.1)
[20:57] <Unit193> knome: No, it eats them.  It ate mine. :(
[21:01]  * knome sighs
[21:03] <SwissBot> Heya, dkessel.
[21:03] <dkessel> good night, SwissBot!
[21:42] <ochosi> evening all
[21:45] <Unit193> Howdy.
[22:13] <ochosi> Noskcaj: hm, can't reproduce. guess we need to find more people who can reproduce your problem, as i said, we haven't changed anything in the brightness key handling
[22:14] <Noskcaj> strange. I'll look through some logs today and try and find the issue
[22:15] <ochosi> ok, that'd be great, thanks!
[22:15] <ochosi> i've heard of the issue before, but it seemed to be very isolated, singular cases, and i could never reproduce
[22:16] <ochosi> some folks messed up their installs so the brightness stuff couldn't be handled because of wrong policies / missing rights for xfpm
[22:47] <ali1234> brightness?
[22:47] <ali1234> like display backlight brightness?
[22:48] <ali1234> because i had an issue with that not working
[22:49] <ali1234> actually...  still do
[22:49] <ali1234> and i know it's not my install because over the past two weeks i put my xubuntu disk into four different laptops
[22:50] <ali1234> and on all but my usual one the brightness control worked
[22:50] <Unit193> bluesabre, knome: Also, I'll say this one more time.  You cannot direct factoid calls to links, it's an anti-spam measure.
[22:50] <knome> Unit193, aha.
[22:50] <knome> Unit193, i'll never remember that, so... keep on reminding. :)
[22:50] <Unit193> knome: Or just silently laugh.
[22:50] <knome> yep.
[22:50] <knome> fair.
[23:00] <bluesabre> Unit193: np, I'll continue just talking, then pinging
[23:01] <Unit193> bluesabre: Hello!
[23:01] <bluesabre> ochosi: can reproduce
[23:01] <bluesabre> can change brightness with scroll wheel on panel plugin, not with hardware keys
[23:02] <bluesabre> hi Unit193
[23:09] <ali1234> bluesabre: do you see the brightness notification popup when using keys?
[23:11] <bluesabre> ali1234: for keyboard brightness yes, screen brightness no
[23:11] <ali1234> i don't have a backlit keyboard
[23:12] <ali1234> what happens here is that i see the notification and the bar moves left/right, but the display brightness never changes
[23:12] <ali1234> but only on this one laptop. same disk in a different laptop and it works
[23:13] <bluesabre> yeah, different problem than here
[23:13] <bluesabre> are you able to change your brightness with mouse wheel on the panel plugin?
[23:13] <ali1234> i dunno, how do i get the panel plugin?
[23:13] <ali1234> what does it look like?
[23:14] <bluesabre> battery icon, labeled as the Power Manager Plugin in the applet list
[23:14] <ali1234> i just tried directly setting the backlight brightness in /sys/class/backlight/ and that worked
[23:15] <ali1234> doesn't seem to be installed
[23:17] <bluesabre> what release are you running?
[23:18] <ali1234> oh... 14.04
[23:19] <bluesabre> it might have a different name on that release... ochosi could give you a better idea (since he keeps renaming it)
[23:19] <ali1234> i usually run the dev ppas
[23:19] <ali1234> not sure if this laptop has it or not, i don't use it very often
[23:20] <bluesabre> I think 14.04 used indicator-power since the xfce4-power-manager was a bit unmaintained at the time
[23:20] <ali1234> yes, i do have that
[23:21] <bluesabre> https://launchpad.net/~xubuntu-dev/+archive/ubuntu/xfce-4.12 has a newer power-manager release
[23:22] <ochosi> thing is, some ppl report brightness keys not working with xfpm 1.4, some claim it only stopped working with 1.5
[23:22] <ochosi> it always worked for me (i'm mostly using dell laptops though)
[23:22] <ochosi> what i'm trying to say is that the reports so far were rather inconsistent
[23:22] <bluesabre> worked for me with 1.4, I've had plenty of issues with upower in vivid though
[23:22] <ochosi> right
[23:22] <ali1234> yeah, my question still stands though: does the notification show up?
[23:23] <ochosi> for me, the notification shows up, only with the buttons though (as intended)
[23:23] <ali1234> i mean for the people for whom it does not work :)
[23:24] <bluesabre> :)
[23:24] <bluesabre> for me, no notification, no worky
[23:26] <ochosi> fyi, xfpm uses RandR to change the display brightness
[23:26] <ochosi> alternatively, you can use the kernel's display brightness support directly
[23:26] <ochosi> works better with some laptops, which is why the brightness key support is optional
[23:27] <ochosi> bluesabre: have you tried disabling the brightness key support in xfpm yet?
[23:27] <bluesabre> ochosi: nope, how?
[23:27] <bluesabre> oh!
[23:28] <bluesabre> ochosi: that setting was off, turned it on andddddd.
[23:28] <bluesabre> nope
[23:28] <bluesabre> still no work
[23:28] <bluesabre> :D
[23:28] <bluesabre> D:
[23:28] <ochosi> also, you can try to run "xfpm-power-backlight-helper --set-brightness $percentage" from cli
[23:29] <bluesabre> cruel
[23:29] <bluesabre> bluesabre@sean-asus-linux:~
[23:29] <bluesabre> $ xfpm-power-backlight-helper --set-brightness 100
[23:29] <bluesabre> This program can only be used by the root user
[23:29] <bluesabre> bluesabre@sean-asus-linux:~
[23:29] <bluesabre> $ sudo xfpm-power-backlight-helper --set-brightness 100
[23:30] <bluesabre> [sudo] password for bluesabre:
[23:30] <bluesabre> This program must only be run through pkexec
[23:30] <bluesabre> bluesabre@sean-asus-linux:~
[23:30] <ochosi> :)
[23:30] <bluesabre> $ pkexec  xfpm-power-backlight-helper --set-brightness 100
[23:30] <bluesabre> now its very dark
[23:30] <ochosi> yeah, sorry, $percentage was misleading
[23:30] <ochosi> the values are set by the hardware/driver
[23:30] <ochosi> so it's not always up to 100
[23:30] <ochosi> could be 1000 even
[23:30] <ali1234> mine goes up to ~13000
[23:30] <bluesabre> I think mine is in the 800s
[23:30] <ochosi> depends on how many brightness steps you have
[23:31] <bluesabre> how do I check that again?
[23:31] <ochosi> odd though if that helper script works
[23:31] <ali1234> look in /sys/class/backlight/*/brightness
[23:31] <bluesabre> scrolling works
[23:31] <bluesabre> 937
[23:31] <ochosi> ok, lemme quickly check something
[23:34] <ochosi> you definitely need polkit support
[23:34] <ochosi> otherwise that script won't be called successfully from within xfpm
[23:34] <bluesabre> yeah, np
[23:34] <bluesabre> I just thought it was amusing
[23:36] <ochosi> another option is that your brightness keys aren't recognized by the kernel as such
[23:37] <ochosi> have you tried xev?
[23:37] <ochosi> generally speaking, the plugin calls the same function as the media-key listener
[23:38] <bluesabre> aha
[23:38] <ochosi> and that function first tries to go through RandR (if the driver supports it) and if that doesn't work, it uses the helper script
[23:38] <bluesabre> the kernel no longer supports my hardware keys
[23:38] <ochosi> fun
[23:38] <bluesabre> x.x
[23:38] <ochosi> problem solved
[23:38] <ochosi> well, "solved" :D
[23:38] <ochosi> i meant: not my problem anymore ;)
[23:38] <bluesabre> :p
[23:39] <ochosi> Noskcaj: please check whether this is the case for you too ^
[23:39] <ochosi> bluesabre: well at least now you can map that helper script to a fun keyboard shortcut of your choice
[23:40] <ochosi> also, since that is out of the way, feel free to review my MR ;)
[23:40] <ochosi> (not that i really want to put more effort into light-locker-settings, but it seemed like an easy and worthwhile improvement)
[23:41] <bluesabre> oh right
[23:41] <bluesabre> I'll take a look at that shortly
[23:41] <ochosi> sure no rush
[23:42] <ochosi> just didn't want it to rot
[23:42] <bluesabre> also replied to your email
[23:42] <ochosi> yes, read that
[23:43] <ochosi> not sure what milestones mate is participating in, i'm not in touch with any of them
[23:43] <bluesabre> flexiondotorg: poke
[23:43] <bluesabre> :)
[23:43] <flexiondotorg> bluesabre, :)
[23:43] <bluesabre> handy
[23:43] <ochosi> that was quick :)
[23:43] <flexiondotorg> I was just about to turn in. 
[23:43] <flexiondotorg> What can I do you for?
[23:43] <bluesabre> do you know the milestones ubuntu mate is participating in this cycle?
[23:44] <flexiondotorg> You mean aplha and beta?
[23:44] <bluesabre> yeah
[23:44] <flexiondotorg> All of them. Although I've not communicated that to anyone.
[23:44] <bluesabre> ok, cool
[23:44] <ochosi> from what i know, you can only participate in the milestones you release yourself
[23:44] <flexiondotorg> You cught me because I've just be releasing MATE 1.10 :)
[23:44] <ochosi> so it means actively taking charge of that
[23:45] <flexiondotorg> ochosi, I saw the email. Didn't understand what it was asking of me.
[23:45] <ochosi> otherwise you can only participate in the milestones ubuntu does (i think they only do final beta)
[23:45] <flexiondotorg> On my list of stuff to do.
[23:45] <flexiondotorg> ochosi, They do.
[23:45] <flexiondotorg> ochosi, So are Xubuntu wanting to do all milestones?
[23:46] <bluesabre> we might line up with you guys this cycle since we have at least the toolkit and lightdm apps in common
[23:46] <ochosi> personally, i don't see much benefit in doing alphas
[23:46] <bluesabre> yeah
[23:46] <flexiondotorg> I guess this is because elfy was a causality after the recent community debacle?
[23:46] <bluesabre> at least the first one
[23:47] <flexiondotorg> I'm happy to join up with you guys.
[23:47] <bluesabre> yeah, ochosi and I are taking a more active role in the release decisions with elfy's absense
[23:47] <ochosi> could start with b1
[23:47] <flexiondotorg> Although I have no idea what I am signing up to.
[23:47] <flexiondotorg> I'd like to do the alpha.
[23:47] <bluesabre> we can help your team out as well to an extent since you're still fresh :)
[23:48] <flexiondotorg> Was really sad to see elfy go. Some real arse hats out there.
[23:48] <ochosi> i think Laney also said there
[23:48] <ochosi> 'd be help
[23:48] <flexiondotorg> Well, I'm totally up for it.
[23:48] <bluesabre> but yeah, there's definitely a benefit to keeping our communication chains up :)
[23:49] <flexiondotorg> Are Lubuntu interested?
[23:49] <flexiondotorg> They are introducing LXQt this cycle. 
[23:49] <flexiondotorg> Lots of change.
[23:49] <flexiondotorg> I imagine they'd want to do the aplha.
[23:49] <flexiondotorg> Have you discussed this with Kubuntu?
[23:50] <bluesabre> it was just an initial discussion/passing thought
[23:50] <flexiondotorg> OK. 
[23:50] <flexiondotorg> Well nearly 01:00 here.
[23:50] <flexiondotorg> So, I'm in.
[23:50] <bluesabre> yeah, you're free to go
[23:50] <flexiondotorg> But off to bed now :-)
[23:50] <bluesabre> thanks for taking the time to chat with us
[23:50] <flexiondotorg> No probs. Most welcome.
[23:50]  * flexiondotorg Goes to sleep Z Z Z z z z . .
[23:51] <bluesabre> ochosi: so there's that at least
[23:51] <bluesabre> :)
[23:53] <ochosi> yup
[23:53] <ochosi> personally, i'm not 100% sure we really get more testers by doing more milestones
[23:54] <bluesabre> I agree that the first alpha at least is not particularly useful, since everything changes after that point
[23:54] <ochosi> yeah
[23:55] <ochosi> will you be around tomorrow at some point?
[23:55] <ochosi> cause i really gotta hit the sack
[23:55] <bluesabre> and with the revised package testing plan this cycle (run wily or PPAs and report), it should be okay
[23:55] <bluesabre> I'll probably be around at least in the morning
[23:55] <ochosi> ok
[23:55] <bluesabre> and maybe the evening
[23:55] <ochosi> let's talk in the morning (your morning)
[23:55] <bluesabre> fridays are always up in the air
[23:55] <bluesabre> alrighty
[23:56] <ochosi> i'll look up the release schedule and maybe i'll drop elfy a few lines
[23:56] <bluesabre> cool
[23:56] <ochosi> who knows, maybe he gets back to me with his experiences in terms of how many testers contributed
[23:56] <bluesabre> oh, we generally have all that info
[23:57] <bluesabre> but yeah
[23:57] <bluesabre> go to bed
[23:57] <bluesabre> I need to undo my hour walk in the sun :)
[23:57] <ochosi> yeah, let's talk when i'm less tired :)
[23:57] <bluesabre> sure thing
[23:57] <bluesabre> nighty ochosi
[23:58] <ochosi> alrighty, nighty!