[00:07] <bluesabre> Unit193: poke
[00:08] <Unit193> bluesabre: I didn't do it, it was ochosi.
[00:08] <bluesabre> ah
[00:08] <bluesabre> ochosi: poke
[00:08] <Unit193> :D
[00:08] <bluesabre> Unit193: so, where is the xfwm4+patch hiding?
[00:09] <Unit193> https://sigma.unit193.net/source/xfwm4_4.11.2-0ubuntu2.dsc where it normally is.
[00:09] <bluesabre> thanks
[00:10] <Unit193> Sure thing.
[00:13] <bluesabre> looks good, pushed
[00:13] <Unit193> brainwash: ^
[00:13] <Unit193> Thanks.
[00:14] <bluesabre> power-manager time
[00:14] <bluesabre> :)
[00:14] <Unit193> Ah, at least one thing out of there.
[00:27] <Unit193> bluesabre: So, got it figured out or need a pointer?
[00:27] <bluesabre> have a pointer to give?
[00:27] <Unit193> In shlibs, -xxfce4-panel
[00:30] <Unit193> Tell me if it actually works, didn't look too far into it. :P
[00:31] <bluesabre> in shlibs...
[00:32] <bluesabre> debian/shlibs?
[00:32]  * bluesabre is in unknown territory
[00:35] <holstein> knome: ok :)
[00:36] <Unit193> override_dh_shlibdeps -- -xxfce4-panel, if I read correctly, bluesabre.
[00:37] <bluesabre> ah
[00:37] <bluesabre> ok, I know where that goes at least ;)
[00:38] <Unit193> If you read the manpage, you may get a different understanding than I do though.
[00:44] <bluesabre> hm, no good, Depends: libc6 (>= 2.4), libcairo2 (>= 1.2.4), libglib2.0-0 (>= 2.37.3), libgtk2.0-0 (>= 2.18.0), libupower-glib1 (>= 0.9.0), libx11-6, libxfce4ui-1-0 (>= 4.9.1), libxfce4util6 (>= 4.9.0), libxfconf-0-2 (>= 4.6.0), libxrandr2 (>= 2:1.2.99.2), xfce4-panel (>= 4.11), xfce4-panel (<< 4.13), xfce4-power-manager (>= 0.8.0~), xfce4-panel (>= 4.11.0) | lxpanel
[00:47] <bluesabre> oh wait
[00:47] <bluesabre> typo
[00:47] <Unit193> Not going to version that lxpanel ?
[00:47] <bluesabre> 1 thing at a time :)
[00:47] <Unit193> :D
[00:48] <Unit193> Another thing to think about when the time comes, looking at a bottom limit or a roof?
[00:49] <bluesabre> I think ochosi said the api is completely different with the next lxpanel release
[00:49] <bluesabre> so, << 0.7
[00:49] <Unit193> Exactly what I'm referring to, yep.
[00:49] <bluesabre> dang, still didn't work
[00:50] <Unit193> Yeeeep, read that one wrong, I see.
[00:50] <bluesabre> http://paste.ubuntu.com/8173916/
[00:51] <Unit193>  X != x
[00:52] <bluesabre>        -Xitem, --exclude=item
[00:52] <Unit193> -- means pass it to dpkg-shlibdeps.
[00:52] <Unit193> http://manpages.ubuntu.com/manpages/trusty/en/man1/dpkg-shlibdeps.1.html I could be reading that part wrong though, but looks right to me.
[00:53] <bluesabre> oh
[00:53] <bluesabre> manpage is different there
[00:53] <bluesabre> longer
[00:53] <bluesabre> I'll try little x now
[00:53] <Unit193> dh_shlibdeps != dpkg-shlibdeps
[00:53] <Unit193> (Also, why do you think I took the lxpanel side?)
[00:54] <bluesabre> :D
[01:07] <bluesabre> yay!
[01:07] <bluesabre> Depends: libc6 (>= 2.4), libcairo2 (>= 1.2.4), libglib2.0-0 (>= 2.37.3), libgtk2.0-0 (>= 2.18.0), libupower-glib1 (>= 0.9.0), libx11-6, libxfce4ui-1-0 (>= 4.9.1), libxfce4util6 (>= 4.9.0), libxfconf-0-2 (>= 4.6.0), libxrandr2 (>= 2:1.2.99.2), xfce4-power-manager (>= 0.8.0~), xfce4-panel (>= 4.11.0) | lxpanel
[01:12] <Unit193> There you go, sparky!
[01:13] <bluesabre> you still did all the work, but now I'll know for next time
[01:14] <Unit193> Heh, well there is that, yeah. >_>
[01:14] <Unit193> Remember to version the b-dep on 0.6.2-0ubuntu2 else you won't get the headers, and I guess we need to bump that bug now. :/
[01:15] <bluesabre> well, this won't build with that until we get the lxpanel in there
[01:15] <bluesabre> do we want to do it all at once?
[01:17] <Unit193> Just waiting on someone to sponsor lp 1361459
[01:18] <bluesabre> we could also subscribe gilir to that bug
[01:19] <Unit193> Might be good, also give a heads up he'll want to seed -plugins unless it's too late.
[01:19] <Unit193> +could, I meant could.
[01:20] <bluesabre> want to subscribe him?
[01:20] <bluesabre> :)
[01:22] <Unit193> Done.
[01:22] <bluesabre> yay!
[01:22] <bluesabre> :D
[01:23] <Unit193> And...
[01:23] <Unit193> For good luck and all.
[01:25] <bluesabre> nice
[01:27] <Unit193> Anything else I need to look at?
[01:27] <bluesabre> I think you're clear
[01:28] <bluesabre> go have some fun
[01:28] <bluesabre> :D
[01:28] <Unit193> Eh, no fun to be had.
[01:28] <bluesabre> D:
[01:31] <bluesabre> make one of these http://uk.reuters.com/video/2014/08/20/hoverbike-aims-to-take-aviation-to-a-new?videoId=340553849
[01:32] <Unit193> Hah, also funny because it redirected me to "Genetically modified mosquitoes to combat dengue in Brazil"
[01:33] <bluesabre> I tried
[01:35] <bluesabre> micahg_, mr_pouit: if either of you are around, would you mind adding me to https://launchpad.net/~gtk-theme-config-maintainers so I can make a release :)
[08:38] <elfy> good day peeps
[08:40] <elfy> ochosi: front page of xubuntu.org - do we want to add the beta to that - or replace LTS with the beta?
[09:24] <brainwash> Unit193: thanks for re-introducing the patch :)
[09:28] <ochosi> elfy: i think adding the beta might be a good idea. the lts announcement is still fairly recent and might interest
[09:28] <ochosi> as soon as we're at the final beta or RC of 14.10, we can always remove it
[10:06] <elfy> ochosi: agreed - and so did whoever did it :p
[10:22] <elfy> bug 1294209 got fixed then the fix was reverted - is the bug going to be fixed again for trusty?
[10:22] <elfy> bug 10778 is the bugzilla one
[10:22] <elfy> https://bugzilla.xfce.org/show_bug.cgi?id=10778
[10:23] <knome_> xfce 10778
[10:23] <knome> elfy, ^
[10:23] <elfy> knome: aah :)
[10:23] <elfy> thanks 
[10:23] <knome> np, and good afternoon
[10:23] <knome> wait, it's still morning there
[10:23] <elfy> it is :)
[10:24] <knome> calculation fail
[10:24] <elfy> I'll bank that for 36 minutes time :p
[10:24] <knome> heh
[10:27] <brainwash> elfy: bug 1319029
[10:27] <brainwash> ^ the reason why it got re-opened
[10:35] <elfy> brainwash: yes I know - I didn't see the need in spamming the channel with a whole bunch of bug lines :)
[10:36] <elfy> that though isn't what I'd like to know - what I'd like to know is if it's going to fixed - again :p
[10:37] <elfy> glorious - I'm stuck in nvidia/nouveau limbo again :( 
[10:37] <elfy> nvidia installed, nouveau being used 
[10:56] <ochosi> elfy: yeah, i changed it
[10:56] <ochosi> (i mean the frontpage)
[10:56] <elfy> ochosi: thanks 
[10:56] <elfy> yep - guessed 
[11:01] <brainwash> ochosi: should the 14.10 beta page inform the user about our compton config? some may want to test it
[11:01] <knome> brainwash, aren't you a bit late? we worked on the release announcement the other day
[11:02] <brainwash> beta 2
[11:02] <brainwash> :P
[11:02] <knome> right... is there a beta 2 page yet?
[11:02] <elfy> I'd say if we wanted people to do that - would be useful to do so seperately, much like the mucking about with core
[11:02] <ochosi> bluesabre was against it, since we're not actively endorsing compton (and i agree)
[11:02] <brainwash> the thing is, I've just noticed it 2 minutes ago
[11:02] <ochosi> brainwash: feel free to blog about it ;)
[11:03] <knome> i've been jumping on and off, so i might have missed something...
[11:04] <brainwash> ochosi: but we could need some feedback
[11:04] <ochosi> brainwash: not sure, we're supplying a config that might work for most
[11:04] <ochosi> but that's about it
[11:04] <ochosi> it might work great for some, not at all for others
[11:04] <ochosi> (which is also the reason why we won't ship compton by default)
[11:05] <ochosi> so yeah, it is exactly that, i don't want a bugreport with 100 different users endorsing different configs. with all the types of hardware and drivers we wouldn't know what to ship anyway
[11:07] <brainwash> mmh, so we should place the config somewhere else, so it's not picked by default when compton is installed
[11:08] <brainwash> these are not the default settings of compton
[11:08] <ochosi> yeah, ofc they're not. they're made to resemble our default theme visually
[11:10] <brainwash> ok fine
[12:45] <brainwash> where is mr_pouit ? I could need some help with cleaning up launchpad reports :P
[12:48] <knome> he's mostly inactive. why do you need him specifically?
[12:49] <brainwash> he used to be very active on launchpad, well, few years ago
[12:56] <brainwash> it's just that people do report bugs, but many don't receive an answer during the release cycle (if any answer at all)
[12:57] <knome> right... so replying is up to those who are actually available and active during the cycle, not people who used to be active 2 years ago, do you agree?
[12:57] <brainwash> I do
[12:57] <knome> so why do we need to poke lionel, who isn't really active any more?
[12:58] <brainwash> worth a try
[12:59] <brainwash> he might feel the urge to fight against army of zombie launchpad reports one more time :D
[12:59]  * ochosi doubts anyone has ever felt that urge
[12:59] <brainwash> it helps the project
[13:01] <brainwash> ideally the current package maintainer(s) would do this, but I know that it's a time consuming task
[13:09] <ochosi> brainwash: frankly, one bug tracker is enough for me
[13:09] <ochosi> i've been cleaning up bugs.xfce for quite a while now, mostly for the components i contribute to
[13:09] <ochosi> but another bugtracker would mean getting even less done
[13:09] <brainwash> I know that
[13:42] <brainwash> ochosi: I need some help with bug 1188065
[13:43] <brainwash> valid request?
[13:43] <brainwash> this has not been reported upstream yet
[13:47] <ochosi> it's somewhat valid, but i'm not sure what upower offers exactly
[13:47] <ochosi> we don't calculate these values ourselves
[13:49] <brainwash> ah I see
[18:49] <Unit193> brainwash: So yes, thanks for keeping the bug reports down.  Usually when I look, it's several "$package failed to install/upgrade: subprocess installed post-installation script returned error exit status 2" or one of those. :/
[21:28] <lbracher> Hi there! Do you know if it's possible to do a PXE boot using a xubuntu iso? TIA!
[21:29] <Unit193> Yep.
[21:30] <Unit193> Or if not, I better undo doing it. :P
[21:30] <Unit193> ...Though yeah this is the development channel.