[00:06]  * woo6 was finally able to install xub 14.04 on win10....HyperV created some challenges
[00:31] <micahg> knome: I'll try to take a look this week
[09:34] <knome> micahg, thanks - and please tell us if it looks like you have no time, because then we'll have more time to track down other people who can do stuff
[09:34] <knome> hello slickymasterWork 
[09:35] <slickymasterWork> hey knome 
[09:39] <akxwi-dave> Morning All
[09:40] <knome> slickymasterWork, did you see how the PDF files are linked in the documentation yet?
[09:53] <dkessel> !team | 8-minutes-before-meeting-ping
[09:57] <knome> dkessel, but that was 7 minutes...
[09:58] <dkessel> not in my own timezone
[09:58] <knome> wait, what?
[09:58] <knome> :PP
[09:58] <knome> is your timezone misaligned by one minute? that's very silly..
[09:59] <slickymasterWork> !team | meeting time!
[10:00] <slickymasterWork> #startmeeting
[10:00] <meetingology> Meeting started Wed Sep  2 10:00:08 2015 UTC.  The chair is slickymasterWork. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[10:00] <meetingology> Available commands: action commands idea info link nick
[10:00] <slickymasterWork> So, who's here for the meeting?
[10:01] <dkessel> o/
[10:01] <slickymasterWork> hmmm wondering where Unit193 and knome might be hiding?
[10:01] <Unit193> I am not here.
[10:01] <bluesabre> oh, actually made it
[10:02] <slickymasterWork> apparently not Unit193 :P
[10:02] <knome> of course i'm hiding
[10:02] <slickymasterWork> #chair bluesabre, knome
[10:02] <meetingology> Current chairs: bluesabre knome slickymasterWork
[10:02] <slickymasterWork> #topic Open action items
[10:02] <slickymasterWork> there doesn't seems to be none 
[10:03] <slickymasterWork> anyone has anything?
[10:05] <bluesabre> nothing here
[10:05] <bluesabre> still collecting myself
[10:06] <knome> of course not, if there aren't any, there aren't any... ;)
[10:06] <slickymasterWork> knome, I believe the update of the debian/copyright for the documentation is done, right?
[10:07] <slickymasterWork> ok, moving along then
[10:07] <slickymasterWork> #topic Team updates
[10:07] <slickymasterWork> gentlemen, the floor is your's
[10:07] <slickymasterWork> please use #info for your items
[10:07] <knome> slickymasterWork, yes
[10:07] <bluesabre> #info xfpanel-switch and patched xfce4-panel now available in wily and included on daily image
[10:08]  * knome refers to tracker.xubuntu.org
[10:08] <slickymasterWork> can you please #info that knome 
[10:08] <knome> #info knome updated debian/copyright for documentation
[10:08] <slickymasterWork> thanks
[10:08] <knome> #info knome made the "Official Documentation" part on the startpage more prominent
[10:08] <knome> #info knome created a timeline of finished work items in the status tracker
[10:09] <knome> #info flocculant sent exploratory testing information to testers via ML
[10:09] <knome> #info pleia2 got first batch of flyers printed
[10:09] <slickymasterWork> dkessel, anything new in the use of jenkins for automated image testing front?
[10:09] <dkessel> slickymasterWork: no, now news
[10:09] <dkessel> argh. no news
[10:09] <slickymasterWork> ok, thanks
[10:10] <slickymasterWork> anything else bluesabre?
[10:10] <knome> i think we might want to stop doing these updates at some point if the tracker serves us them anyway
[10:10] <knome> (just use work items to notify about important things)
[10:10] <bluesabre> slickymasterWork: nothing noteworthy yet, just a lot of things in progress (see tracker)
[10:11] <slickymasterWork> oki doke
[10:11] <slickymasterWork> apparently I'm going to set a new record time for a team meeting
[10:11] <slickymasterWork> beating Unit193's record :P
[10:11] <knome> i've had short ones too
[10:12] <bluesabre> good luck, I think ochosi might have set that pretty low once
[10:12] <slickymasterWork> lol
[10:12] <slickymasterWork> #topic Team updates
[10:12] <knome> slickymasterWork, we did that already...
[10:12]  * bluesabre can info his items again
[10:13] <slickymasterWork> sorry my bad (multitasking with some work stuff) :P
[10:13] <slickymasterWork> #topic Discussion
[10:13] <slickymasterWork> there's noting set in the wiki, so does anyone has any last minute items?
[10:14] <knome> i guess i could start this here
[10:14] <bluesabre> any questions or anything needed from me (uploads, patches, etc?)
[10:14] <slickymasterWork> go ahead knome, please
[10:14] <knome> #subtopic Stop doing team updates on meetings
[10:14] <knome> so, as i just said, since the tracker gives us most of that information already, i think this might be more or less useless
[10:15] <bluesabre> as long as people link bugs and document work items thoroughly, yeah
[10:15] <knome> especially since it means people have to wait until the meeting to see the updates - the tracker serves them more or less live
[10:15] <slickymasterWork> fair point knome 
[10:15] <knome> the original reason for doing the updates on the meetings was to help gathering the monthly team report
[10:16] <knome> but we haven't been doing that since april
[10:16] <knome> and still, the tracker is much more reliable
[10:16] <knome> but of course, it requires that people add work items for anything worth mentioning
[10:16] <slickymasterWork> yes
[10:17] <bluesabre> knome: the tracker is excellent, thanks for getting it together and being responsive with requests and updates ;)
[10:17] <knome> but since it's one less task to do (to remember the work items for the meeting), and you already need to work with the work items...
[10:17]  * knome bows
[10:17] <knome> i'll send a mail about this to the ML
[10:17] <slickymasterWork> aha
[10:17] <knome> #action knome to send a mail to the mailing list about phasing out "Team updates" in the meetings
[10:17] <meetingology> ACTION: knome to send a mail to the mailing list about phasing out "Team updates" in the meetings
[10:18] <slickymasterWork> thanks also for that knome 
[10:18] <knome> np
[10:18] <knome> i think i might have had something else
[10:18] <knome> give me 5 minutes to think about it
[10:18] <slickymasterWork> take your time
[10:18] <knome> or 2...
[10:19] <knome> nah, i don't think it was anything for the meeting :)
[10:21] <slickymasterWork> lol
[10:21] <knome> we do have a few things to discuss about docs together though
[10:21] <slickymasterWork> yeah, but I was thinking on this evening knome 
[10:21] <knome> sure, finish the meeting first
[10:22] <slickymasterWork> #action pleia2 to schedule the next meeting
[10:22] <meetingology> ACTION: pleia2 to schedule the next meeting
[10:22] <slickymasterWork> #endmeeting
[10:22] <meetingology> Meeting ended Wed Sep  2 10:22:32 2015 UTC.  
[10:22] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/xubuntu-devel/2015/xubuntu-devel.2015-09-02-10.00.moin.txt
[10:22] <knome> thanks david
[10:22] <slickymasterWork> sure, np
[10:22] <knome> so, the few things, just that you know what to expect:
[10:23] <knome> - did you look how the pdf is linked from in the documentation?
[10:23] <knome> - installer slideshow stuff
[10:23] <Unit193> Team updates are a nice thing if it wasn't on the blueprint, just something out of the blue that got done.  Also a nice dumping grounds.
[10:23] <knome> - installer slideshow translations
[10:23] <Unit193> bluesabre: xfdesktop, the new point release?
[10:23] <knome> - faq stuff for website?
[10:23] <slickymasterWork> ok knome 
[10:24] <knome> slickymasterWork, what time would work for you?
[10:24] <slickymasterWork> 21:00 UTC
[10:24] <knome> Unit193, if it wasn't on the blueprint but is something that would be worth mentioning and of interest generally, then it can be added to  blueprint
[10:24] <slickymasterWork> today is going to be very busy dirung the day
[10:24] <slickymasterWork> * during
[10:25] <slickymasterWork> does that work for you knome?
[10:25] <knome> Unit193, but sure, we can still do updates about general tasks that aren't really important enough to put on the blueprints
[10:25] <knome> slickymasterWork, should do, i'll let you know in advance if it doesn't
[10:25] <slickymasterWork> ok, thanks
[10:28] <bluesabre> Unit193: yeah, that sounds like a nice release. Want to add it to the -dev bp?
[10:28] <bluesabre> otherwise I'll just keep forgetting about it
[10:28] <bluesabre> :D
[10:28] <slickymasterWork> Minutes are up
[10:29] <knome> thanks slickymasterWork 
[10:29] <slickymasterWork> ta
[10:30] <bluesabre> thanks for hosting the meeting slickymasterWork!
[15:22] <sidi> Anybody here running 14.04 or 15.04, who wants to make a bit of money in exchange for letting me log stuff on their computer? It's for science! You can get up to ~£50 / €68... Ideally UK based, or EU based
[15:23] <sidi> https://study.cs.ucl.ac.uk/multitasking/web/hello (haven't updated but I dumped Unity in favour of Xfce for my study, because reasons)
[18:46] <krytarik> Sorry for being AWOL for so long, but I finally just got my internet back! \o/  And picked up with stuff a bit already, but now it's time for dinner.
[18:47] <knome> bon appetit :)
[18:47] <krytarik> Well. :)
[18:54] <krytarik> knome: Btw, did you notice the rather excessive margin below the translation links on  https://unit193.net/xubuntu/docs/  after your recent changes?
[18:55] <knome> i did, it's ok
[18:55] <knome> there's a dotted line there
[18:55] <knome> and padding and stuff
[18:57] <krytarik> I think the bottom padding of '#documentation' could be set to zero or something like that.
[18:58] <knome> oh gosh no
[18:58] <knome> don't you see it has a different bg color?
[18:58] <krytarik> Nope, not here.
[18:58] <knome> it's likely not easy to see on lousier monitors, but there it is
[18:58] <knome> ok.
[18:58] <knome> it does
[18:59] <knome> it is #fff while the rest is something else
[18:59] <knome> #fafafa or #f1f1f1 iirc
[18:59] <krytarik> Yeah, lousy, old CRT here. :P
[18:59] <knome> sure, it's slight
[18:59] <knome> but it's there
[18:59] <krytarik> The first, yes.
[18:59] <knome> brb
[19:02] <flocculant> welcome back krytarik :)
[19:02] <krytarik> Thanks! \o/
[19:03] <flocculant> so it seems the way to get people to disappear is add them to Xubuntu Team :D
[19:03] <krytarik> Yep, at least that works for me. :P
[19:03] <flocculant> ha ha 
[19:05] <Unit193> Didn't work for me, sorry.
[19:10] <krytarik> knome: Hah, on switching it off and on, I can see it here now! :P
[19:14] <krytarik> knome: PDF links are still 'DONE', btw - unless you disapprove, of course.
[19:27] <knome> krytarik, well, i don't think they are perfect...
[19:27] <knome> krytarik, but we're seeing with slickymaster in 1,5 hours, let's see what he says (and feel free to join the docs sprint)
[19:28] <Unit193> Oh, and do the thingy where it doesn't tell you about every rendered page.
[19:28] <knome> Unit193, like?
[20:50] <knome> i need the 10 minutes though
[20:50] <slickymaster> want to kick things os, knome?
[20:50] <slickymaster> ok, we'll wait
[20:50] <slickymaster> with both eyes on the TV
[20:50] <knome> well, feel free to start with things you don't need me for
[20:50] <knome> hah :P
[20:56] <ochosi> evening
[20:56] <slickymaster> hey ochosi 
[20:57] <ochosi> hey slickymaster 
[20:57] <slickymaster> how's everything?
[20:58] <ochosi> buuuuusy :)
[20:58] <ochosi> and tired tired tired
[20:58] <slickymaster> lol
[21:02] <ochosi> knome, bluesabre, flocculant: i pinged satya about numix and gtk3.16 support today, since UIF is creeping up. i haven't tested how bad it currently is - if you can, please take a look so we can decide whether we can continue shipping it as is
[21:02] <ochosi> i would take a look myself, but i'm too tired, sry
[21:03] <knome> i don't know numix well at all, but i could probably look at obvious bugs
[21:03] <ochosi> yeah, this is about visual regressions in gtk3 apps
[21:04] <ochosi> if there are none, then we shouldn't care too much
[21:04] <knome> who cares about gtk3 apps anyway?
[21:04]  * knome hides
[21:04] <ochosi> i know i had to fix many things for greybird to work ok
[21:04] <ochosi> eg. try an app with CSD but with xfwm4 compositing disabled
[21:04] <knome> slickymaster, more or less ready now, eating a night snack on the side ;)
[21:04] <ochosi> etc
[21:05] <knome> slickymaster, did you check the PDF linking krytarik made?
[21:05] <slickymaster> shall we start with how the pdfs are linked from in the documentation, knome?
[21:05] <knome> yep :P
[21:06] <slickymaster> nopes, not yet
[21:06] <knome> well do that
[21:06] <slickymaster> opening LP
[21:06] <knome> huh, this is going to take forever
[21:06] <ochosi> bluesabre: also, how's it going with the parole and mugshot bugs?
[21:06] <ochosi> lol
[21:08] <slickymaster> knome, that was by rev. 408, right?
[21:08] <knome> just pick the latest revision...
[21:09] <slickymaster> already doing that
[21:09] <slickymaster> was just asking if that was the one
[21:09] <knome> i don't know, probably
[21:12] <slickymaster> the it takes to build them now is huge
[21:12] <slickymaster> * time
[21:12] <knome> make startpage html
[21:12] <knome> doesn't do the translations...
[21:13] <slickymaster> hmm, where are the pdfs stored?
[21:14] <knome> who cares?
[21:14] <knome> just go see how the documentation shows them
[21:14] <knome> :P
[21:14] <knome> actually, you'll likely need "make startpage html pdf"
[21:14] <knome> but if you built all, you'll have it
[21:15] <slickymaster> ahah getting page not found from either a4 and us letter links
[21:15] <slickymaster> nopes
[21:15] <slickymaster> that's why I was asking
[21:15] <knome> should be in the same dir as the html files
[21:15] <knome> do you have all the build-deps?
[21:15] <slickymaster> krytarik: this is was I got:
[21:15] <slickymaster> ../scripts/pdf-create.sh de es fi fr pt
[21:15] <slickymaster> ../scripts/pdf-create.sh: 5: ../scripts/pdf-create.sh: fop: not found
[21:15] <slickymaster> ../scripts/pdf-create.sh: 7: ../scripts/pdf-create.sh: fop: not found
[21:15] <slickymaster> ../scripts/pdf-create.sh: 5: ../scripts/pdf-create.sh: fop: not found
[21:15] <slickymaster> ../scripts/pdf-create.sh: 7: ../scripts/pdf-create.sh: fop: not found
[21:15] <slickymaster> ../scripts/pdf-create.sh: 5: ../scripts/pdf-create.sh: fop: not found
[21:16] <slickymaster> ../scripts/pdf-create.sh: 7: ../scripts/pdf-create.sh: fop: not found
[21:16] <slickymaster> ../scripts/pdf-create.sh: 5: ../scripts/pdf-create.sh: fop: not found
[21:16] <knome> slickymaster, sudo apt-get install fop
[21:16] <slickymaster> ../scripts/pdf-create.sh: 7: ../scripts/pdf-create.sh: fop: not found
[21:16] <slickymaster> ../scripts/pdf-create.sh: 5: ../scripts/pdf-create.sh: fop: not found
[21:16] <knome> slickymaster, awwwh, you should know better
[21:16] <slickymaster> ../scripts/pdf-create.sh: 7: ../scripts/pdf-create.sh: fop: not foundnow he tells me :P
[21:16] <knome> :)
[21:16] <knome> you might want to make sure you also have fonts-droid
[21:16] <knome> but you likely do..
[21:16] <slickymaster> I think I have
[21:17] <knome> ANYWAY
[21:17] <knome> the question is the way the PDFs are linked to
[21:17] <slickymaster> wow 32.2 MB of additional disk space will be used
[21:17] <knome> well, it's a small amount to be able to... fop
[21:17] <knome> you know. :P
[21:17] <slickymaster> :P
[21:17] <ochosi> night all
[21:17] <knome> nighty ochosi :)
[21:18] <slickymaster> night ochosi 
[21:18] <slickymaster> bulding 
[21:18] <knome> slickymaster, make startpage html pdf
[21:18] <knome> slickymaster, then it's a lot quicker
[21:18] <slickymaster> just about finishing
[21:20] <slickymaster> now it's naging about java
[21:20] <knome> huh?
[21:21] <knome> krytarik, forgot something from the build-deps?
[21:21] <slickymaster> /usr/bin/fop: 304: exec: /usr/local/java/jdk1.7.0_51/bin/java: not found
[21:21] <slickymaster> and I do have java
[21:22] <krytarik> knome: Nope.
[21:22] <slickymaster> what do you think it might be then, krytarik?
[21:23] <slickymaster> knome, I'll build them tomorrow at work in my VB box, so we can move on now
[21:24] <knome> yeah, the question was about the linking anyway
[21:24] <knome> not the PDFs
[21:24] <krytarik> slickymaster: What *Ubuntu version are you on then? Should be Wily, of course.
[21:24] <slickymaster> what about it?, their placement
[21:24] <knome> krytarik, works for me in vivid
[21:24] <knome> slickymaster, yes, that, and potentially the appearance
[21:24] <slickymaster> nopes, this one is still 14.04 krytarik 
[21:24] <knome> the current place isn't my favorite - it's a bit disrupting
[21:24] <slickymaster> haven't update my laptop yet :P
[21:25] <slickymaster> I don't particulary like where they are now
[21:25] <slickymaster> * particularly
[21:25] <knome> ideally, as i see it, they'd only appear on the front page of the documentation
[21:26] <knome> (eg. NOT the startpage, but the docs main page with ToC)
[21:26] <knome> probably before "welcome"
[21:26] <knome> "Would you rather like to read this documentation in PDF? ..."
[21:26] <knome> or sth
[21:26] <slickymaster> I would place them between the last paragraph ant the ToC
[21:27] <knome> that works for me as well
[21:27] <knome> the only question with that is "should/how do we check if the files exist"
[21:27] <slickymaster> and I would prefer a sentence rather then a dry PDF: A$ US Letter
[21:27] <knome> it would be nice if that paragraph wasn't there when the PDF files weren't around
[21:27] <knome> but meh
[21:28] <knome> it would have to be a build-time thing
[21:28] <knome> like the languages on the startpage
[21:28] <slickymaster> well it will be a trade of, unless krytarik manages to script something
[21:28] <knome> but i really don't want to split up the xml...
[21:28] <knome> so the question is:
[21:28] <knome> by default, do we always commit to build the PDFs for all languages?
[21:29] <slickymaster> my opinion is yes, we do
[21:29] <knome> i don't care if james from jamaica does "make html" and then has a broken link
[21:29] <knome> (but of course it would be nice if he didn't)
[21:30] <slickymaster> of course, but the way I see it if we're shipping it why wouldn't commit to build the pdf's in all shipped languages?
[21:30] <slickymaster> s/wouldn't/wouldn't we
[21:31] <slickymaster> put it like this, if we weren't to commit the build for all languages, to which ones would we build?
[21:31] <slickymaster> what would be the criteria?
[21:31] <knome> http://www.sagehill.net/docbookxsl/ModularDoc.html#XIncludeFallback
[21:32] <knome> slickymaster, none, i guess
[21:32]  * slickymaster opens the link
[21:32] <knome> though that doesn't totally fix the issue
[21:33] <knome> we should probably use that mechanism for the translators though
[21:33] <knome> krytarik, you listening?
[21:33] <slickymaster> but does provides some margin knome 
[21:33] <krytarik> knome: Yep.
[21:33] <slickymaster> + us
[21:33] <slickymaster> what's your opinion krytarik?
[21:34] <knome> slickymaster, yes, at least we can build the xml file to be included dynamically only when pdf files exist
[21:34] <knome> the problem is...
[21:34] <knome> how are the translations handled?
[21:34] <slickymaster> at build time?
[21:34] <knome> strings we want to translate should be in the templates
[21:34] <slickymaster> yes
[21:34] <knome> LP can't pick up something we land with a script
[21:35] <knome> unless we figure out some other way to translate those strings
[21:35] <knome> or add them to the translation template
[21:35] <slickymaster> the last would be the fast and easier one
[21:36] <slickymaster> thing is we start the all process and there's a lot of work done
[21:37] <slickymaster> what in both your opinions is the best scenario??
[21:37] <krytarik> knome: If you want to include an elaborate sentence that'll have to be translated, it'll have to be in an XML file that's not just generated at build time.
[21:37] <krytarik> Like the translators one.
[21:37] <knome> krytarik, yeah, i was thinking about that
[21:41] <knome> krytarik, currently, scripts/get-pot.sh only builds the pot for files that are shipped
[21:41] <knome> so the translators xml isn't translater
[21:41] <knome> - not that it should, it's always replaced with other info
[21:42] <krytarik> It's not there in the first place either.
[21:42] <knome> except if we want to move the other string there as well
[21:42] <knome> The contributors to the various translations of this documentation are:
[21:42] <knome> Attributed on each translation's page.
[21:42] <knome> this is a bit clunky
[21:43]  * slickymaster goes to smoke in the meanwhile
[21:43] <knome> i would just leave it out from the english version
[21:44] <krytarik> knome: Yep, apply some DocBook magic then. :)
[21:47] <knome> the problem is that translators.xml is built dynamically
[21:48] <knome> so maybe we should include translator-credits.xml (when translators exist) which then shows the message and includes translators.xml with the translator names
[21:48] <knome> brb
[21:48] <slickymaster> in a separate xml file knome
[21:49] <slickymaster> translator-credits.xml, that is
[21:49] <knome> yes
[21:51] <slickymaster> that would solve your issue of not wanting to split up the xml
[21:51] <knome> i mean split the same way as we split up the html
[21:52] <slickymaster> yes
[21:52]  * knome thinks
[21:58] <krytarik> slickymaster: Ftm, the rationale behind linking to the respective PDFs from every page is better accessibility, and them possibly being accessed directly from a web search.
[21:59] <knome> krytarik, then we should look to put them in the header or sth
[21:59] <knome> that place is meh
[21:59] <slickymaster> yes, I know that. Regarding that I have no doubts
[21:59] <krytarik> Like I said earlier, I tried verious places already.
[21:59] <krytarik> * various
[22:00] <slickymaster> my objections are purely aesthetic krytarik 
[22:00] <slickymaster> just that
[22:03] <knome> krytarik, are we using the build_creds_alt function?
[22:04] <krytarik> Nope.
[22:04] <slickymaster> knome, should we move on to the other items so you and krytarik can mature a possible solution for this
[22:04] <knome> i'm brewing it
[22:04] <slickymaster> ok
[22:09] <knome> well sigh
[22:09] <knome> the slideshow stuff isn't happening today
[22:09] <knome> well, we can surface it
[22:10] <slickymaster> tomorrow I'll have a good day at work knome 
[22:10] <knome> when have you looked at it the last time?
[22:10] <slickymaster> last sunday I took a quick look at it, after branching it
[22:11] <knome> ok, do we need a lot of changes?
[22:11] <slickymaster> I wouldn't say a lot
[22:11] <slickymaster> we should address LO, of course
[22:12] <knome> yes...
[22:12] <slickymaster> and maybe find a way to add the panle switch to one of the existing slides
[22:12] <slickymaster> * panel
[22:13] <slickymaster> and also referring the fact that the -docs will also be available as pdf's
[22:13] <knome> maybe
[22:13] <slickymaster> but like I said, tomorrow I'm planning on a calm day, so we can start with this in the morning
[22:14] <knome> i should be around at least for some time
[22:14] <knome> well, i'll be around a lot
[22:14] <knome> but available...
[22:14] <slickymaster> so will I, after these frantic last few weeks
[22:15] <slickymaster> I'll ping you as soon as I get there
[22:15] <knome> sure
[22:15] <slickymaster> and we still have the installer translations to deal with knome 
[22:16] <slickymaster> we didn't have no answers from dylan
[22:16] <knome> yeah
[22:16] <slickymaster> or Graber for that matter
[22:17] <slickymaster> ok, that's a 'date' then for tomorrow knome 
[22:17] <knome> huhu
[22:17] <slickymaster> ahahaha
[22:17] <knome> not a three-way this time?
[22:17]  * slickymaster doesn't see krytarik agrreing on a three-way
[22:17] <slickymaster> * agreeing
[22:17] <krytarik> lol
[22:17] <slickymaster> :P
[22:18] <krytarik> I'll be there only from around 12 UTC though.
[22:18] <knome> that's fine...
[22:18] <slickymaster> until when krytarik?
[22:18] <krytarik> Open end of course. :P
[22:19] <knome> huh
[22:19] <slickymaster> lol
[22:19] <knome> let's see if i broke stuf...
[22:19] <knome> +f
[22:20] <slickymaster> I'll go and try to compensate the three hours of sleep I had last night
[22:20] <knome> good night
[22:20] <slickymaster> ttyt
[22:20] <slickymaster> thanks knome 
[22:20] <slickymaster> mañana krytarik 
[22:20] <knome> always
[22:20] <krytarik> Night slickymaster.
[23:48] <sidi> bluesabre, slickymaster cant remember which of you two told me how to fix the compiling issue with thunar by using --enable-maintainer-mode
[23:48] <sidi> i still have the same problem though
[23:49] <sidi> i cant build them... there's something missing in the Makefile somehow