[14:32] <aarmelvin> ?
[14:33] <aarmelvin> is there any Library Management Software available for Edubuntu..?
[14:37] <aarmelvin> any OSS alternative for Library Management application
[14:37] <aarmelvin> ?


[07:08] <lifeless> bob2: I'm on leave.
[07:08] <bob2> lifeless: oh, have fun :-)
[07:08] <bob2> and say hi to lynne.
[07:10] <lifeless> roger wilco
[12:40] <Kinnison> Anyone using dogfood? I want to upgrade it
[12:46] <Kinnison> Okay, upgrading...
[01:32] <Kinnison> Upgrade completed, dogfood back
[03:54] <mpt> Hey morgs, did you get lots of hacking and caregiving done while the rest of us were sunning ourselves in Brazil?
[03:56] <morgs> mpt: I got blocked and lonely... bring the wiki back!
[03:56] <mpt> Wiki's coming back today
[03:56] <mpt> if elmo has time to do it
[03:56] <mpt> and/or kiko
[03:59] <morgs> hacking and caregiving are not very compatible... but /me is getting more productive again...
[03:59] <morgs> Get some new specs done in between mosquitos and sunburn?
[04:00] <mpt> oh! actually, I think http://lpwiki.async.com.br/ is accessible from outside Async now
[04:00] <mpt> at least, until the wiki is transferred back
[04:00] <mpt> so if you want to do any wikiing before then, you can
[04:01] <mpt> So yeah, http://lpwiki.async.com.br/RecentChanges
[04:01] <morgs> Hmm, maybe accessible from specific places outside async that do not include Cape Town though...
[04:02] <morgs> "The hostname was not found during the DNS lookup."
[04:07] <mpt> morgs: Well, in the meantime, there are 9 bugs assigned to you :-)
[04:07] <SteveA> hi
[04:08] <SteveA> morgs: i know exactly how to fix that error you were getting with rdf stuff
[04:08] <mpt> hi SteveA, https://launchpad.net/malone/bugs/1244 is an example of docstrings not being suitable for help
[04:10] <SteveA> mpt: right.  which is kinda what docstrings are for, for a python programmer
[04:10] <mpt> yes
[04:10] <SteveA> i'll need to think about how to fix this for us
[04:10] <SteveA> one way would be to make a new schema, that extends the old one
[04:10] <SteveA> with corrected "presentation type" docstrings
[04:10] <mpt> A schema for auto-generated forms?
[04:11] <SteveA> another way would be to see this as a problem that should be fixed upstream
[04:11] <SteveA> by having different programmer_description and user_description fields
[04:11] <SteveA> (with better names, i should think)
[04:11] <SteveA> mpt: yes
[04:11] <SteveA> we're going to be moving all the schemas that are used only for autogenerated forms into browser/
[04:12] <mpt> I was sure I'd started writing a spec on how auto-generated forms should be presented, but I can't find it
[04:12] <SteveA> so, the simplest solution, at least for now, is to do that, and to extend "programmer schemas" with ones in launchpad/browser when we need to
[04:13] <morgs> SteveA, hi, great!
[04:13] <SteveA> morgs: here is what you need to do:
[04:14] <SteveA> 1. change how you wrote the page to include a ViewPageTemplateFile as an attribute of the class, rather than saying 'template="..."' in the zcml
[04:14] <SteveA> 2. make your zcml say that the page is rendered by calling your view class, using 'attribute="__call__"'
[04:16] <SteveA> 3. in your view class' '__call__' method, set the various http headers you need to, say 'unicodedata = self.template()' and then say 'encodeddata = unicodedata.encode('utf-8')' and then 'return encodeddata'
[04:16] <SteveA> of course, you can make it more succinct than that
[04:16] <morgs> SteveA, this would be in my ProductRdfView class, right
[04:17] <SteveA> morgs: um, whereever you are currently setting the content type stuff
[04:17] <SteveA> i'm at an airport -- not very convenient to look it up just now
[04:18] <morgs> Right, yes. ATM I'm setting it in __init__ of that class, so I'll put it in __call__ instead...
[04:18] <SteveA> ye
[04:18] <SteveA> yes
[04:18] <morgs> Great, I'll give this a shot.
[04:39] <morgs> SteveA, AttributeError: 'ProductRdfView' object has no attribute 'template'
[04:40] <morgs> SteveA, how do I set up self.template before calling it?
[04:40] <mpt> Is staging down?
[04:41] <SteveA> morgs: put your template in the class under the name 'template'
[04:42] <SteveA>  template = ViewPageTemplateFile('../templates/whatever.pt')
[04:44] <morgs> duh, right
[04:45] <morgs> SteveA, thanks, that fixes it.
[04:45] <SteveA> great
[04:48] <SteveA> jamesh: ping
[05:34] <elmo> ddaa/jblack?
[05:34] <ddaa> elmo: elmo?
[05:35] <elmo> ddaa: if we had to relocate arch.u.c to a new machine before lifeless came back from holiday,would you be in a position to help with that?
[05:35] <ddaa> Yes, I can handle that.
[05:35] <morgs> elmo: any ETA on wiki.launchpad being back?
[05:36] <elmo> morgs: not until someone gets me a tar ball of the wiki, nope
[05:36] <elmo> ddaa: ok, cool, thanks
[05:36] <ddaa> elmo: some help from stub might be needed though.
[05:37] <ddaa> elmo: note that I took some days off this week.
[05:37] <ddaa> though I will be there for emergencies.
[05:38] <elmo> ok - just out of interest, what happens to stuff if ssh connections were being refused from escudero?
[05:39] <elmo> [I'm not threatening to do that necessarily ;), just exploring migration options]
[05:49] <bradb> morning
[05:52] <bradb> the pilot had to choose between making the airport curfew, or loading the last 20-30 bags. he choose the former.
[05:53] <Kinnison> oh dear
[06:26] <Kinnison> still no stub :-(
[06:32] <ddaa> elmo: the task fails, it will be retried the next day
[06:33] <ddaa> that's actually the main cause of transient failures at the moment, and I see no way out
[06:33] <ddaa> since we are somehow triggering a bug in ssl muxing...
[06:33] <elmo> ok
[06:44] <bradb> hm, very interesting that i can only recall my social insurance number in english, and my postal code only in french
[06:45] <Kinnison> bradb: s'an occupational hazard of being multilingual
[06:46] <Kinnison> bradb: for a long time I could only remember my two times table in french
[06:46] <bradb> heh
[06:46] <Kinnison> Which made for amusing mumblings under my breath as I worked out the right shifts and adds to do a multiply quickly in assembler
[06:47] <bradb> in other news, i'm very glad that the letter i received from Revenue Qubec saying "You owe us $huge_amount_im_sure_i_already_paid" was only a side-effect of the strike, and that, in fact, i don't really owe them any (more) money
[06:48] <Kinnison> heh
[06:49] <Kinnison> Libr nous les libros!
[06:49] <Kinnison> erm, Librez ?
[06:50] <bradb> librez-nous des libraux
[06:50] <Kinnison> I could have sworn you said 'les' not 'des'
[06:51] <Kinnison> must be your funny blocked-up-nose^W^W^Wqbeqois accent
[06:51] <bradb> hh
[06:51] <Kinnison> hh
[06:55] <bradb> Kinnison: you should try and get ahold of some songs from les cowboys fringants. i'm not sure what kind of stuff you like, but if you can do folkish, you might really like them.
[06:55] <Kinnison> Hey, it'll be fun to try
[06:58] <bradb> la grand-messe is their latest album. les toiles filantes, 8 secondes, plus rien, lettre  lvesque, camping ste-germaine, symphonie pour caza...get your torrent on!
[06:59] <Kinnison> Heh
[06:59] <Kinnison> mail me a list
[07:02] <bradb> of good songs, or of torrents? :)
[07:03] <Kinnison> sonds
[07:03] <Kinnison> songs even
[07:04] <Kinnison> if there's a strong torrent of an album I'll take that too
[07:06] <bradb> i bought the cd; not sure where to download them from. as soon as i'm done catching-up with Real Life this afternoon, i'll send you a list of good stuff.
[07:06] <Kinnison> thanks
[08:08] <cprov> anyone who needs to talk with me, please send email or call, bye
[08:46] <JanC> is it possible that malone doesn't know all packages in breezy ?
[08:47] <mpt> JanC: It only knows about Universe packages at the moment
[08:48] <JanC> this is a universe package
[08:48] <JanC> and it doesn't know it (yet?)
[09:05] <mpt> that's odd
[09:06] <mpt> I don't know who would fix that, JanC
[09:06] <mpt> but my first guess would be morgs
[09:08] <JanC> the uploader of the package already knew about the bug & the fixed package will be available soon, so there is no hurry  :)
[09:09] <JanC> I found another bug in malone about a package not being available
[09:10] <mpt> ok, so assign your bug to the same person
[09:11] <JanC> it's not assigned  :)
[09:12] <mpt> aha
[09:12] <JanC> are packages automaticly added when they are added ?
[09:12] <JanC> added t omalone when they are added to the archive I mean
[09:12] <mpt> I don't know
[09:14] <salgado> JanC, not yet. soon they'll be. although with a small delay
[09:15] <JanC> ah, then I don't have to file a bug on "missing packages" ?
[09:17] <JanC> the package I couldn't find was xfce4-terminal (bug is already fixed now)
[09:17] <JanC> the other bug report about missing packages is: https://launchpad.net/malone/bugs/1413
[09:17] <salgado> JanC, I'm not 100% sure, but I think they're not yet automatically created in launchpad, so it's better to file the bug
[09:18] <JanC> a generic "missing packages" bug or for the specific package ?
[09:19] <salgado> a generic one, in the launchpad product
[09:20] <JanC> not the "malone" product ?
[09:20] <salgado> no, the launchpad one
[09:20] <JanC> okay, will do
[09:39] <dilys> Merge to<EMAIL_ADDRESS>[trivial]  Add milestone icon, bug priority icons, and remote bug icons (patch-2240<EMAIL_ADDRESS>[10:17] <philiKON> hi
[10:17] <philiKON> forgive me if i'm blind, but is there a way to send messages to all members of my team?
[10:20] <salgado> philiKON, no, there's no way to do that. although, if launchpad has to send a notification for your team (e.g. a bug was filed in a package maintained by your team), you can have this notification to each of the team's members
[10:20] <philiKON> dang
[10:20] <philiKON> such a functionality would be very useful
[10:20] <salgado> but I guess what you really want is a way for you to send a messate to all members, right?
[10:20] <philiKON> right
[10:20] <philiKON> soemthing like, "finish up translations, release is coming"
[10:22] <ddaa> Sound like something that would fit in the bug tracker.
[10:22] <philiKON> hmm
[10:22] <ddaa> "There might be unfinished translations" milestone="next release"
[10:23] <ddaa> close it when people have acked they've finished the translations
[10:50] <nakeee> Any idea when the rosetta bidi bug is going to be fixed?
[11:01] <bradb> mpt: nice work on the bug icons! where can i see the milestone icon in action? it didn't seem to appear for either /distros/debian or /products/firefox
[11:02] <mpt> bradb: object-portlet-milestones.pt was already expecting it
[11:02] <mpt> If you see anywhere else it should go, let me know
[11:03] <mpt> Milestones were implemented in rather a hurry, so there doesn't appear to be sampledata for them, which made things a bit difficult
[11:03] <bradb> i believe there's sample data for firefox
[11:04] <bradb> mpt: i expected to see it here: http://localhost:8086/distros/debian and here: http://localhost:8086/products/firefox in the milestones portlet
[11:05] <mpt> oo, that's odd
[11:05] <bradb> mpt: also, might you be able to make an icon to be shown in place of an input checkbox, which will mean "this distrorelease is already targetted for the fix"?
[11:06] <mpt> ah, a kludge in launchpad.css
[11:13] <mpt> bradb: <input type="checkbox" disabled="true">
[11:14] <bradb> we planned to use an icon in favour of that
[11:14] <mpt> bradb: For me, http://localhost:8086/distros/debian gives "No milestones defined"
[11:14] <bradb> mpt: you have to add one (as foo bar) to see what it looks like
[11:14] <mpt> bradb: I was going to say "Did you know checkboxes can be disabled", but y'all were discussing more important issues at the time
[11:15] <bradb> yeah, we thought it might be slightly confusing to show a disabled checkbox, as people might wonder why they aren't allowed to uncheck it
[11:15] <bradb> what do you think? is it confusing?
[11:16] <mpt> a checkmark graphic is appropriate for something that wasn't turned on in the first place
[11:16] <mpt> but this thing here (a release target) was already turned on, so a disabled checkbox is entirely appropriate
[11:16] <bradb> ok, i'll go with that instead, thanks
[11:39] <bradb> Kinnison: how often does a package change name between releases? also, how often does it happen that something i used to find in package "foo" is now instead found in package "bar" in a new release?
[11:42] <elmo> bradb: often enough
[11:42] <elmo> to be something you really have to deal with sooner or later; but relative to the number of packages in the distro, it's not a huge percentage
[11:42] <elmo> IANAKIJPOOI
[11:42] <bradb> hm. this would make the bug release targeting/backport UI somewhat more complex.
[11:43] <mpt> bradb: The greatest thing about Malone is that it will mean I no longer have to put up with the text-shadow CSS on bugzilla.ubuntu.com
[11:47] <bradb> Kinnison: a more soyuz-specific question then: will it/is it fairly straightforward to figure out what Hoary package "foo" was called in Warty?
[11:50] <elmo> it should be
[11:50] <elmo> the DB has been designed around that from the beginning, but I haven't seen it's current evolution
[11:50] <elmo> (sorry, I'll stop playing kinnison now)
[11:52] <elmo> AFAICR, the DB has a higher level concept of a package than source or binaries in the archive
[11:52] <elmo> so you can always  refer back to that, at least internally
[11:52] <elmo> if that makes sense?
[11:55] <bradb> yeah, i know about the packaging table, but i'm not sure if it would be able to tell me that the binary program "foo" used to be installed with the binary package "blah-utils", but now it's part of the binary package "fnorb-scripts"
[11:56] <bradb> maybe the best backporting/release targeting UI is a simple dropdown of release names and a package name widget (to avoid all this complexity.) thoughts? mpt?
[11:57] <bradb> the package name widget could at least default to the package that the "current" task is targeting (i.e. you can only get to this targeting/backport screen from the bugtask screen anyway, so we can probably figure out a reasonable default package name to put in there.)
[12:09] <Kinnison> bradb: You can't know about specific binary files anyway
[12:11] <bradb> Kinnison: from the soyuz perspective then, is it at least easy to follow he same source package as it changes names between releases?
[12:11] <bradb> s/he/the/
[12:12] <Kinnison> We certainly looked into that
[12:12] <Kinnison> assuming we can find a sane way to cope with source package renames wrt. superseding I'm sure we'll be able to do something sane
[12:12] <Kinnison> The publishing history retains what superseded what
[12:13] <bradb> if i can fairly easily figure that out, the checkbox UI for backporting/targeting can probably make sense, as long as I give the user the option to manually add a task on a completely different package for the release target, if for some reason that's required.
[12:13] <bradb> i.e. you'd get checkboxes like:
[12:13] <bradb> Target Fix to:
[12:13] <bradb> [ ]  warty mozilla-firefox


[03:40] <ScottK> jtaylor: No.
[05:59] <Logan_> micahg: Hey, can I PM?
[05:59] <micahg> Logan_: sure
[18:22] <jtaylor> yey another criticial cve for asterisk ._.


[08:01] <dholbach> good morning
[08:01] <elfy> hi dholbach
[08:02] <dholbach> hi elfy
[14:40] <AlanBell> erm, thought we had a new CC? https://launchpad.net/~communitycouncil/+members
[14:41] <popey> hah
[14:42] <AlanBell> I guess sabdfl needs to press some buttons
[14:43] <AlanBell> I will send him an email
[15:08] <jcastro> popey, pleia2 awww ... no one suggested deleting the wiki in that docs thread?
[15:14] <popey> bah!
[16:40] <pleia2> wiki4ever
[16:40] <pleia2> AlanBell: we've sent him a few emails, he's traveling at the moment so hasn't gotten around to it
[16:41] <AlanBell> ah, ok
[16:41] <pleia2> hoping he'll get to TB elections soon too
[16:42] <pleia2> which is actually higer priority, since the CC can still do most of our work w/o launchpad, the TB doesn't even *exist* at the moment
[16:43] <mhall119> pleia2: can we not simply extend TB memberships until an election happens?
[16:44] <pleia2> mhall119: could, but we'd have to ask them if they are willing, at least a couple aren't interested in serving any more
[16:45] <pleia2> and technically we need a +1 from sabdfl for that too I think
[16:46] <AlanBell> the IRCC stuff shouldn't block on sabdfl I think
[16:47] <pleia2> AlanBell: nope, we have quorum for that
[17:22] <dholbach> have a great rest of your day! see you tomorrow!
[20:52] <jono> jose, hey
[20:52] <jono> sorry, going to need to cancel our call
[20:52] <jono> I am sick


[23:46] <teward> Fallen: (RE: July 30 and matrix) keep in mind I also own/operate the matterbridge that links a few of the Ubuntu channels to Telegram/Matrix/other mechanisms, it can be modified to attach to Matrix channels, etc. if plumb doesn't work.
[23:46] <teward> Fallen: can I arrange a meeting with you or someone else on the CCT for some things that need to be relayed to Legal / up the ladder?
[23:47] <teward> or need status updates on


[00:22] <pkzip> will future releases of lubuntu no longer use lxde?
[00:31] <xangua> Lxqt is the new lxde
[00:33] <pkzip> ah, i see
[00:34] <xangua> Maybe next release, or the next one, who knows
[00:35] <lynorian_> do not want lxqt and make it worse
[00:36] <lynorian_> There are lxqt packages in the repos since 16.04
[07:16] <zblace> Hello Folks (quite and impressive number of you here)
[07:20] <zblace> I have used Lubuntu 13.04 (on some old machines frome time to time) and now wanted to update to recent 16.04...but it failed from my fisrt attempt. I used the the live install from USB stick I had plugged into my newer computer (used x86 iso I think) and I used it that way for a while (with sessions saving and few upgrades)...
[07:22] <zblace> Does anyone know if live USB Lubuntus can move computers with different hardware? Even if they were used much and stick was upgraded and is using with persistant file storage?
[07:40] <fishcooker> Invalid MIT-MAGIC-COOKIE-1 keyOpenbox-Message: Failed to open the display from the DISPLAY environment variable.
[07:56] <zblace> I would love to set one USB for work as https://wiki.ubuntu.com/BootToRAM, but then also use it to install on other computers - without need to do it all from vanila/clean install if possible.
[10:36] <xangua> Just wanted to share that finally got suspend and light DM working (no more black screen)
[14:20] <Ariaka> hello
[17:38] <maskara> im close! i can taste it!  so i installed lubuntu alongside pointlinux and updated grub from pointlinux desktop cuz it was the bootable os after lubuntu install  so now when i boot i get the option to start pointlinux or lubuntu but when i select lubuntu i only get a command line interface to login..i can login fine but my desktop doesnt start...anyone see this before?  do i have to update grub in lubuntu comandline as well? as well?


[00:51] <kafv2__> test
[00:51] <daftykins> passed
[06:15] <ducasse> good morning, everyone
[06:24] <lotuspsychje> good mornito all
[06:58] <EriC^^> morning all
[06:58] <lotuspsychje> hey EriC^^
[06:58] <EriC^^> hey lotuspsychje
[09:45] <lotuspsychje> bbl movie
[12:09] <lotuspsychje> re
[13:23] <firezep> hey guys, sorry for a the stupid question kinda new to ubunto[linux in general] do you guys recommend squirrelmail at all or should I look for another email option?
[13:57] <leftyfb> firezep: I definitely do not recommend squrrelmail for use as a ftp or media server
[13:58] <leftyfb> ^ jest
[13:58] <leftyfb> firezep: as for email, what services are you looking for? Why do you need webmail? What's the backend?
[13:58] <firezep> leftyfb, not for ftp just for email usage, also already blocked ftp ports and added failt2ban just in case
[13:59] <firezep> well you know to learn stuff and also have my own email :P
[14:00] <leftyfb> firezep: learn what?  You'll be spending hours upon hours of reading and learning to get it right. I'll be honest, I've been running an email server for about 20 years and I'm still learning and fixing mistakes
[14:04] <firezep> well gotta start somewhere tbh
[14:04] <firezep> I was just going to use for private trackers and such
[14:06] <firezep> not like I have a lot of stuff in my current vps that people could steal also.
[14:07] <leftyfb> firezep: if you want to be able to receive email from and check email from the internet, then you need to open up the relevant ports and services to the internet and setup the security properly. It doesn't matter what it's being used for
[14:08] <firezep> ducasse, what email client would you recommend me then?
[14:08] <leftyfb> firezep: it's also not a matter of what people "steal". It's a matter of creating another source of garbage on the internet
[14:08] <firezep> Well I guess I can do that to a certain extent leftyfb also its just to learn and test
[14:08] <firezep> not much tbh
[14:09] <firezep> Is ee what o mean firezep. that makes sense
[14:09] <leftyfb> firezep: you go into this with 100% security in mind and lock it down or don't do it at all
[14:10] <firezep> well but for what you say I can just opening some ports and services can you point me with some guidelines where I can learn or inform my self better, if I may ask
[14:11] <leftyfb> firezep: if you don't care to take the effort to lock it down properly and are going to proceed with setting it up anyway, I suggest adding your VPS public ip address to all available RBL's so the rest of the internet doesn't have to deal with the garbage that will most certainly be emanating from your server
[14:16] <firezep> sorry RBL? :P
[14:17] <leftyfb> exactly
[14:19] <leftyfb> I don't mean to discourage learning, but building something like an email server to learn how do to it with little to no thought put into securing it properly or spending the time to really understand how it all works is really not worth the amount of resources your server will waste when it starts sending garbage out
[14:20] <leftyfb> firezep: if you are really that interested in learning, the thing that I do is immediately google all possible names, services words I don't understand when someone or some article is explaining the thing I want to learn
[14:21] <firezep> When you say "garbage" you mean like people exploiting my email server of some how right?
[14:21] <leftyfb> yes
[14:21] <leftyfb> it WILL happen
[14:21] <leftyfb> if you do not work to prevent it
[14:22] <firezep> even with fail2ban and closed ports? :O
[14:22] <leftyfb> closing all email ports will prevent your email server from sending/receiving email to/from the internet
[14:23] <leftyfb> I highly suggest this method if you are not going to properly security it otherwise
[14:24] <firezep> I see,, well I'm going to do some more research about it then.
[14:24] <firezep> thanks leftyfb
[14:24] <leftyfb> firezep: I suggest reading everything you can about setting up a postfix server. Read everything you can about RBL's, open relays and how to properly authenticate using SSL ports/services
[14:25] <firezep> will do leftyfb thanks again in advance
[14:40] <BluesKaj> Hiyas all
[14:50] <firezep> \o
[22:03] <leftyfb> https://www.theverge.com/2018/4/1/17185732/cloudflare-dns-service-1-1-1-1
[22:03] <leftyfb> I don't know about anyone else, but that is night and day better performance for me
[22:20] <kostkon> nice


[00:07] <bluesabre> back
[00:08] <flocculant> welcome back Sean :)
[00:08] <bluesabre> thanks
[00:08] <flocculant> slideshow is looking good
[00:09] <flocculant> knome is just off working magic for the contribute one we think :)
[00:11] <bluesabre> cool
[00:11] <bluesabre> noticed the astrerisk stars went away
[00:11] <slickymaster> not sure which version is working on, though
[00:12] <flocculant> the words replace snow I think slickymaster :)
[00:12] <flocculant> as bluesabre noticed - no snow in Xubuntu land currently
[00:12] <slickymaster> or the words piling up into an X
[00:12] <bluesabre> oh, it was snow?
[00:12] <bluesabre> :D
[00:12] <slickymaster> lol
[00:12] <flocculant> bluesabre: no - I think it was stars :p
[00:13] <flocculant> but I saw snow - then couldn't see stars :(
[00:13] <Unit193> bluesabre: Anything I need to look at?
[00:13] <flocculant> though I would if he thumped me in the eye :p
[00:13] <flocculant> Unit193: core merge?
[00:13] <flocculant> :p
[00:13] <Unit193> No.
[00:13] <Unit193> :P
[00:13] <flocculant> :)
[00:13]  * flocculant adds it to agenda
[00:13] <slickymaster> poor core :(
[00:14] <slickymaster> no love
[00:14] <bluesabre> Unit193: last 2 commits here look good to you? https://bazaar.launchpad.net/~xubuntu-art/xubuntu-artwork/xenial/changes
[00:14] <flocculant> slickymaster: core was bad - he was core first
[00:15] <slickymaster> last cigarette of the day
[00:15]  * flocculant patiently reads these changes things waiting for the day
[00:15] <flocculant> slickymaster: it's tomorrow ...
[00:16] <flocculant> sorry and all that
[00:16] <slickymaster> only technically, flocculant :P
[00:16] <Unit193> Big commit. :(
[00:16]  * flocculant doesn't patiently read the second one - assume it's all Greek anyway
[00:19] <bluesabre> Unit193: mostly a bunch of deleted files
[00:19] <Unit193> Mhmm.
[01:06] <flocculant> knome slickymaster - dragging the discussion back here
[01:07] <slickymaster> consider me dragged flocculant
[01:07] <flocculant> nothing that I can see - I would really like to see what it looks like when installing in SSD
[01:07] <slickymaster> you rich you
[01:08] <flocculant> well I'm obviously loaded ...
[01:08] <flocculant> :p
[01:08] <slickymaster> :)
[01:10] <flocculant> not sure about slowing down slide #1 - looks procactive to me
[01:10] <flocculant> there is a distinct wait for the 'words'
[01:10] <slickymaster> my point is that the icons came too fast
[01:10] <flocculant> slickymaster: all at once?
[01:10] <slickymaster> and then just sit there until the transition to the next slide
[01:11] <flocculant> not sure that is an issue
[01:11] <slickymaster> not much an issue
[01:11] <flocculant> don't you get words a bit later?
[01:11] <flocculant> so
[01:11] <slickymaster> rather makes it unbalanced
[01:11] <flocculant> slide starts with left panel
[01:11] <flocculant> get icons
[01:11] <flocculant> get words
[01:11] <flocculant> is what I see
[01:12] <slickymaster> but after the words showing up, noting happens
[01:12] <slickymaster> for a period longer than it took them to appear
[01:12] <slickymaster> not sure if I'm making myself clear :P
[01:13] <flocculant> slickymaster: so what you'd like to see is the slide itself finish quicker?
[01:14] <slickymaster> no, no that
[01:14] <flocculant> slickymaster: so just a real general slowdown?
[01:15] <slickymaster> I'd like to have a proportional amount of time between the two distinct phases os the slide
[01:15] <flocculant> not sure tbh
[01:15] <flocculant> it was quite quick > ubuntu +xfce= xubuntu
[01:15] <slickymaster> x time until the icons first start to appear proportinal to all icons and words there
[01:16] <flocculant> we're advertising xubuntu here I guess
[01:16] <slickymaster> well, yeah
[01:16] <knome> we're not
[01:16] <knome> they are already installing xubuntu
[01:16] <flocculant> true
[01:16] <slickymaster> they could be just trying knome
[01:17] <slickymaster> not yet convinced
[01:17] <flocculant> but we're not overworrrying about them doing anythign but Xubuntu
[01:17] <flocculant> surely
[01:17] <knome> yep, they are trying our product out; if they like it, they'll keep it
[01:17] <knome> no need for cheesy marketing
[01:17] <slickymaster> does what I'm saying about the time makes any sense to you two?
[01:17] <flocculant> so - if this slide is quick - then the rest give them the reason to stay
[01:18] <flocculant> slickymaster: I know what you mean - I've installed on a vm too - but I've installed on SSD and it is quick
[01:18] <flocculant> so - slide too quick - don't restart and read things you missed
[01:18] <slickymaster> yeah, I can only imagine that
[01:19] <flocculant> is my position
[01:19] <flocculant> personally
[01:19] <slickymaster> I'l happily go with the consnsus on this one
[01:20] <slickymaster> * consensus
[01:20] <flocculant> I'd look for an arrow or something - I already know what Xubuntu is - and you'd have to be a bit slow to not know it's some sort of X with ubuntu :)
[01:20] <flocculant> is my position
[01:20] <flocculant> :)
[01:20] <flocculant> twice :D
[01:20] <slickymaster> lol
[01:20] <slickymaster> knome, what's your position?
[01:21] <knome> sofa
[01:21] <slickymaster> hah
[01:21] <slickymaster> same here
[01:21] <knome> i can look to make that first slide faster
[01:22] <slickymaster> can't you just change the icons fading time?
[01:22] <knome> i can, but what does that ultimately fix
[01:22] <slickymaster> that way there wouldn't be no need to change the slide time
[01:23] <knome> then the user would just sit looking at the slower than snail fadein
[01:23] <slickymaster> no, if it wasn't an abrupt change
[01:23] <flocculant> we could go on for hours about this - personally I'd like to see all of the slides fade really quick till the contribute one :p
[01:24] <knome> a small change won't make the waiting time with the fully animated stuff much shorter
[01:24] <knome> essentially, the first slide is boring, but it has to be there
[01:24] <slickymaster> yes
[01:24] <knome> so we could just make it progress faster
[01:25] <slickymaster> works for me
[01:25] <knome> helps with the "slideshow too slow" issue as well
[01:25] <slickymaster> yes
[01:26] <flocculant> so just change the time slide# takes to do stuff?
[01:26] <bluesabre> holy moly, this channel got busy
[01:26] <knome> flocculant, for that single slide, yeah
[01:26] <flocculant> bluesabre: well UI freeze in less than 24 hours and suddenly the slideshow is really important :p
[01:26] <knome> flocculant, keep the animation the same, but show the animated stuff for less time tbe
[01:26] <flocculant> knome: ack
[01:26] <slickymaster> yes, the others don't need to be changed
[01:27] <flocculant> bluesabre: I'm running QA like this next cycle :p
[01:27] <bluesabre> flocculant: great :D
[01:27] <flocculant> \o/
[01:27] <knome> that's not fair, the slideshow branch was there to look for quite some time :P
[01:27] <bluesabre> knome: working on the -artwork upload now
[01:28] <flocculant> knome: ha ha ha
[01:28] <slickymaster> knome, re. the contributors slide you went with the fading words option?
[01:28] <flocculant> knome: serious point now
[01:28] <knome> besides, it doesn't make sense to finish the slideshow at the beginning of a cycle because we need to make sure it's current
[01:28] <knome> flocculant, mhm?
[01:28] <knome> slickymaster, no, the *sliding* words, but i'll have to finish that tomorrow
[01:29] <slickymaster> ok
[01:29] <knome> bluesabre, goodie
[01:29] <flocculant> knome: given I can't get branch to work on livesession - can we push this out so it lands - if so Friday or Saturday in the iso?
[01:29] <knome> yes, my intention is to get it ready tomorrow for bluesabre to upload
[01:29] <flocculant> then I can quickly do a real install and see if we need to tweak time
[01:29] <knome> err
[01:29] <knome> bluesabre can't upload
[01:29] <knome> for somebody to upload
[01:30] <flocculant> ok
[01:30] <knome> i'll work on it tomorrow, don't worry
[01:30] <flocculant> I'd really like us to have a slideshow that can be seen for people installing to SSD
[01:30] <knome> yes
[01:30] <flocculant> especially given it's got to be good for 3 years
[01:31] <knome> :)
[01:31] <slickymaster> I'll have to be up in 5 hours, so bed time for me
[01:31] <knome> nighty slickymaster
[01:31] <flocculant> I don't have the quickest - but I do have one that's not a platter :p
[01:31] <flocculant> night slickymaster
[01:31] <slickymaster> flocculant, will you take a look at the docs during the day?
[01:32] <flocculant> slickymaster: I'm all up to date now :)
[01:32] <knome> flocculant, we already went from 50000 to 25000, that should be twice as fast :)
[01:32] <slickymaster> I won't be able to log to the channel until after dinner
[01:32] <flocculant> knome: or half as slow
[01:32] <knome> and as i said, 20000 should be okay as well
[01:32] <flocculant> yep
[01:32] <knome> nope, less is faster
[01:32] <flocculant> let's see what I get
[01:32] <knome> yeah
[01:33] <slickymaster> see you all later
[01:33] <bluesabre> nighty slickymaster
[01:33] <flocculant> night slickymaster :)
[01:34] <bluesabre> knome: if the installer is going to be faster, maybe we could have a link for the -offtopic channel on that last slide (we already mention it)
[01:34] <bluesabre> "Still around, want to chat?"
[01:34] <knome> heh
[01:34] <knome> maybe
[01:34] <bluesabre> just a thought
[01:35] <flocculant> bluesabre: good point
[01:35] <bluesabre> an unofficial, don't really consider it too hard, thought
[01:35] <knome> though then the expectation is that there is always somebody waiting to chat...
[01:35] <bluesabre> that's true too
[01:35] <flocculant> but on the other hand - someone might be
[01:35] <knome> sure
[01:36] <flocculant> bluesabre: currently the last slide shows the link - but doesn't link
[01:37] <flocculant> we could maybe fiddle words
[01:40] <flocculant> http://pad.ubuntu.com/xubuntu-1604-slideshow
[01:40] <flocculant> at the bottom
[01:42] <flocculant> knome: actually on the other hand given that the interwebs decided that we were 1 up from Lubuntu - people probably will be :)
[01:42] <knome> heh
[01:43] <bluesabre> :)
[01:43] <flocculant> that kind of takes care of people installing quickly - and those installing slowly, everyone else is kind of where they were
[01:44] <flocculant> I think I'm mostly done with words now :p
[01:44] <knome> mostly...
[01:45] <flocculant> well
[01:45] <flocculant> I could drone on - but it'll be a drone in my head too :)
[01:45] <knome> ;)
[02:00] <bluesabre> forgot to bump that version number to 16.04
[02:00] <bluesabre> I'll do another upload in the morning, probably a typo in there somewhere or something
[02:00] <knome> :P
[02:01] <bluesabre> it's too bad that folks that can upload to the archive can't auto-cancel their own uploads
[02:01] <knome> heh
[02:02] <knome> ẗhat'd be chaotic
[02:03] <bluesabre> :D
[02:03] <bluesabre> suppose so
[03:01] <Unit193> flocculant: So, -pa-plug was taking 40%cpu...
[06:24]  * Unit193 wonders if bluesabre was drunk uploading again...
[07:01] <pavlushka> Hi there!!
[07:01] <pavlushka> flocculant, Hi
[08:37] <flocculant> pavlushka: hi :)
[08:55] <pavlushka> flocculant, Hi
[09:13] <flocculant> knome: in the user docs, what-is-xubuntu calls ~&last-lts-version and -codename - where are they? can't find them - but they both point to 14.04 in 16.04 docs - or does that change automatically?
[09:50] <Unit193> flocculant: Do http://paste.openstack.org/show/584pGWSgPJGTisilLp1Y
[10:04] <bluesabre> Unit193: just forgetful
[10:05] <Unit193> Because of the weird version, and '16.o4' :)
[10:08] <Unit193> Wait, elementary-icon-theme is arch 'any' not arch 'all'?
[10:09] <bluesabre> holy crap, did I type 16.o4?
[10:09] <flocculant> Unit193: so confused now - what user.ent is that?
[10:10] <bluesabre> oh wow
[10:10] <bluesabre> I don't deserve to upload anymore
[10:10] <flocculant> 0h 0h :(
[10:10] <Unit193> That's not under your name, though. :P
[10:10] <bluesabre> there's the typo I wanted so I can re-upload
[10:10] <bluesabre> :D
[10:10] <flocculant> ha ha ha
[10:11] <knome> got it sorted?
[10:13] <flocculant> knome: me? I think so - just not sure where Unit193 gets 16.04 from :p
[10:13] <knome> :)
[10:14] <knome> nowhere
[10:14] <knome> it should be updated on http://bazaar.launchpad.net/~ubuntu-core-doc/xubuntu-docs/xenial/view/head:/user-docs/libs/xubuntu-user.ent
[10:16] <knome> and done
[10:17] <bluesabre> Unit193: https://launchpad.net/ubuntu/+source/xubuntu-artwork/16.04.0 :)
[10:17] <flocculant> knome: ok
[10:17] <Unit193> krytarik: ↑
[10:17] <knome> bluesabre, have you coordinated a -docs upload with slickymaster before the next beta?
[10:17] <Unit193> bluesabre: Nice.
[10:17] <bluesabre> slickymaster: let me know when you're ready to upload -docs
[10:18] <bluesabre> knome: yes
[10:18] <knome> good
[10:18] <bluesabre> :D
[10:18] <knome> slickymaster, make sure the translation templates are updated...
[10:18] <flocculant> :)
[10:19] <bluesabre> slickymaster: this will need to be before March 21, for b2 freeze
[10:20] <Unit193> Hoho, and fop is actually in universe, so everything should build even. :D
[10:20] <bluesabre> :o
[10:22] <flocculant> Unit193: well I have fop - I have no fop upgradable - pdf's don't build :)
[10:22] <flocculant> rather I have the same version locally as at universe
[10:22] <bluesabre> dun dun dunnnn
[10:23] <flocculant> but
[10:23] <knome> Unit193, maybe you should look why it doesn't work.....
[10:27] <Unit193> Well I'll check if I can confirm it.
[10:42] <Unit193> knome: Font issues, droid stuff.
[10:42] <knome> "nice"
[10:43] <knome> i should likely look at that
[10:44] <knome> flocculant, look at the slideshow! :)
[10:44] <knome> lunch -->
[10:47] <flocculant> knome: that's \o/
[10:47] <flocculant> assuming it'll be more than artwork and documentation :)
[10:47] <flocculant> and pretty much exactly what I had in mind eventually ;)
[11:05] <knome> flocculant, the slide can show about 6 and a half items, and if we have less, it'll wrap
[11:23] <bluesabre> knome: so, I can contribute to artwork or documentation?
[11:27] <knome> yes.
[11:27] <knome> i need to fix that
[11:27] <knome> try going back to that slide :X
[11:28] <bluesabre> :D
[11:28] <bluesabre> or switching back and forth between them
[11:29] <knome> yes, or that
[11:29] <knome> i've used more time in making sure the effects die graciously than making sure they look good
[11:29] <knome> >__<
[11:31] <bluesabre> https://youtu.be/rN6A9S4kKQo
[11:31] <bluesabre> :D
[11:31]  * bluesabre is a monster
[11:32] <knome> haha
[11:32] <knome> there's a "Noto Sans UI"
[11:32] <knome> ...
[11:32]  * knome looks
[11:33] <knome> hmm, it isn't visible in the font list
[11:33] <knome> so let's not use it
[11:33] <knome> le sigh
[11:40] <knome> bluesabre, can you confirm something for me?
[11:40] <knome> does the documentation package depend on droid now?
[11:40] <knome> if yes, can we get it to depend on noto?
[11:40] <knome> and since noto doesn't have a mono variant, i'm going to have to drop in dejavu sans too
[11:41] <knome> so maybe we should depend on that too
[11:41] <knome> or i think recommend
[11:41] <knome> because of course we have fallbacks
[11:42] <knome> actually the PDF's do require those fonts
[11:42] <knome> ...
[11:53] <knome> Unit193, can you check if the docs build on xenial with the latest revision?
[11:59] <knome> the font issues should be fixed now
[12:00] <ochosi> don't we use something else than dejavu for mono?
[12:00] <knome> the terminal is dejavu
[12:00] <ochosi> liberation mono
[12:00] <knome> no?
[12:01] <ochosi> we changed dejavu to liberation a few cycles ago
[12:01] <knome> sigh...
[12:01] <ochosi> (it was your request at the time)
[12:01] <knome> okay?
[12:01] <ochosi> okay!
[12:01]  * knome shrugs
[12:01] <knome> i'll go put the pieces back then...
[12:01] <knome> but i think it was your request
[12:02] <knome> i still use dejavu sans, so i can't think why i would have proposed liberation
[12:02] <knome> i'm sure i was "okay" with it
[12:05] <knome> i should make all commands replace "xubutnu" with "xubuntu"
[12:09] <bluesabre> knome, ochosi: definitely dejavu https://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-settings/trunk/view/head:/etc/xdg/xdg-xubuntu/xfce4/terminal/terminalrc
[12:10] <bluesabre> and https://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-settings/trunk/view/head:/debian/xubuntu-default-settings.gsettings-override#L18
[12:10] <bluesabre> knome: the package itself has no font depends http://packages.ubuntu.com/xenial/xubuntu-docs
[12:13] <bluesabre> and the mandatory okay with different punctuation...
[12:13] <bluesabre> okay.
[12:14] <bluesabre> and knome: http://packages.ubuntu.com/xenial/fonts-noto-mono
[12:18] <ochosi> odd, i wonder why i have liberation then
[12:18] <ochosi> i don't remember deliberately changing this (ever)
[12:26] <knome> ochosi, sigh :)
[12:26] <knome> bluesabre, what would you think about recommends?
[12:27] <knome> the pdf's look a bit crappy without the font (eg. fallback to fallback serif)
[12:29] <knome> i'll revert the revert to liberation commit then...
[12:32] <ochosi> sry bout that then
[12:32] <ochosi> i switched to inconsolata now to make it clear that i'm not using the default ;)
[12:32] <knome> hah
[12:33] <ochosi> and crap, is noto big
[12:33] <ochosi> still dl-ing that piece of work
[12:33] <knome> yeah....
[12:33] <knome> too big really
[12:33] <knome> :P
[12:33] <ochosi> ridiculous considering it's "only a font"
[12:33] <knome> yes
[12:36] <knome> ok, revert done
[12:36]  * knome slaps ochosi gently
[12:36] <knome> :<
[12:36] <bluesabre> :D
[12:37] <bluesabre> knome: recommends means it will pull it normally, but since that's the default font, seems reasonable to me
[12:37] <knome> yes, i'm aware, and exactly
[12:37] <knome> and it makes the documentation branded with the unified look
[12:37] <knome> or integrated, or whatever you want to call it
[12:38]  * knome goes fixing the slideshow
[12:38] <knome> so bluesabre can't troll more
[12:39] <knome> oh wow
[12:39] <knome> the jquery function returns the right value now
[12:39] <knome> good god
[12:39] <knome> how nice of it
[12:40] <bluesabre> js, love it or hate it, usually the latter
[12:40] <knome> though js !== jquery
[12:40] <bluesabre> yes
[12:41] <bluesabre> jquery further expands the love/hate relationship
[12:41] <knome> haha
[12:41] <knome> well it makes things so easy
[12:41] <bluesabre> yup
[12:41] <knome> and it's sometimes shameful to use it
[12:41] <knome> when there's a pure js alternative
[12:41] <knome> i'm just too lazy for that most of the time
[12:41] <bluesabre> ease of use/readability almost always wins out for me
[12:42] <knome> yeah
[12:43] <knome> so what are the keywords we want to use on the contribute slide?
[12:44] <bluesabre> ochosi, you think noto is big?
[12:44] <bluesabre> !info fonts-noto-hinted xenial
[12:44] <bluesabre> !info fonts-noto-cjk xenial
[12:53] <flocculant> knome: ok - 6 is more than enough I guess :)
[12:54] <knome> yes
[12:54] <knome> but what do we have in them?
[12:54] <knome> i don't think we want the current 4
[12:54] <knome> which are
[12:54] <knome> artwork, documentation, testing
[12:54] <knome> and
[12:54] <knome> xxx
[12:54] <flocculant> I didn't mean use 6 :D
[12:55] <flocculant> web?
[12:55] <knome> maybe social media
[12:55] <flocculant> mmm
[12:55] <knome> do we want them alphabetically?
[12:55] <flocculant> no
[12:55] <knome> or from easiest to hardest
[12:55] <knome> so in that case probably
[12:55] <knome> sm, t, d, a
[12:56] <knome> or am happy with t, sm, d, a too
[12:56] <bluesabre> bugs? dev?
[12:56] <flocculant> anything but alphapathetic and I'll be happy :p
[12:56] <flocculant> bugs is good
[12:56] <knome> bug triage?
[12:56] <knome> "bugs and other animals like cats"
[12:57] <flocculant> triage perhaps
[12:57] <knome>
testing

[12:57] <knome>
social media

[12:57] <knome>
documentation

[12:57] <knome>
bug triage

[12:57] <knome>
artwork

[12:57] <flocculant> best add dev for bluesabre :p
development for bluesabre

[12:58] <flocculant> \o/
bUg triage

[12:58] <knome> bug tirage
[12:58] <bluesabre> :D
[12:58] <flocculant> bug rage
[12:58] <flocculant> I win :p
[12:58] <bluesabre> yes
[12:58] <knome> that's clearly what we want new contributors to help with...
[12:58] <flocculant> rage?
[12:59] <knome> yes
[12:59] <bluesabre> adding to?
[12:59]  * knome shrugs
[12:59] <knome> pushed new revision
[12:59] <flocculant> bluesabre: last night my thinking was ' should we put dev in there, I would have expected that anyone who could code would know where to start anyway'
[12:59] <knome> are we happy to land this for beta (we will have time for fixes after that)
[13:00] <knome> flocculant, last night you had all of your beer too
[13:00] <bluesabre> I've gotta run out now, but I've been good with the current direction
[13:00] <knome> :X
[13:00]  * flocculant waits for bzr to catch up
[13:00] <flocculant> bluesabre: have a good one - cya later
[13:00] <flocculant> knome: ha ha
[13:00] <knome> think i'm going to push this to the main branch soon
[13:00] <knome> ...in one commit
[13:01] <flocculant> not pulling anything new here
[13:01] <knome> hmm
[13:01] <knome> helps if i push i guess
[13:01] <flocculant> might do :p
[13:01] <knome> and done, rev 748
[13:02]  * knome goes cleaning for a bit, when i get back and there are no loud whines, i'll push to the main branch
[13:02] <knome> :)
[13:02] <flocculant> and yes - I'm happy to land this for beta :D
[13:02] <bluesabre> same here
[13:02] <flocculant> looks good to me - thanks for the work on it knome :)
[13:02] <bluesabre> knome: https://bugs.launchpad.net/ubuntu/+source/shimmer-themes/+bug/1555046 if you want to nudge today
[13:03] <bluesabre> ->
[13:09] <slickymaster> bluesabre, just waiting to flocculant's hawk eyes to review the -docs for spelling and grammar errors, which he'll do today
[13:09] <slickymaster> so everything will be ready tonight
[13:09] <slickymaster> I'll make sure Grandpa knome :P
[13:10] <flocculant> hi slickymaster :)
[13:10] <slickymaster> going to branch now the slideshow knome, so I'll be able to have a look at it this afternoon at work
[13:10] <slickymaster> hey flocculant
[13:10] <slickymaster> saw you already started to review the docs
[13:11] <flocculant> yep
[13:11] <slickymaster> will you be done tonight?
[13:11] <flocculant> yea for sure
[13:11] <flocculant> slickymaster: I need to fiddle with contrib too - shall I do that seperately or all together?
[13:12] <slickymaster> do it all together flocculant, I'll have one single merge to do
[13:12] <flocculant> okey doke
[13:12] <slickymaster> after that I'll coordinate with bluesabre in order to upload
[13:12] <flocculant> yup
[13:13] <slickymaster> knome, will the font issue (regarding the PDFs build) be fixed by then
[13:13] <slickymaster> ?
[13:13] <slickymaster> ok, got lunch now and head on to work
[13:13] <slickymaster> see you later
[13:13] <slickymaster> ->
[13:14] <knome> the font stuff should be fixed now, but i'm waiting for Unit193 to confirm it works for him too
[13:14] <knome> ...or you should be waiting
[13:16] <knome> flocculant, one more thing... now that we have the keywords rolling on the slide, shoudl we reconsider the banner content?
[13:19] <flocculant> knome: how about losing the middle paragraph completely then add the contributor docs to the last paragraph
[13:19] <flocculant> the middle one isn't really any different than the keywords
[13:19] <flocculant> I'll move to pad
[13:20] <knome> sure
[13:30] <flocculant> back to reading the docs for a while
[14:02] <flocculant> for anyone who can answer ...
[14:03] <flocculant> docs for dvd points to gstreamer0.10-plugins-ugly - should that be gstreamer1.0-plugins-ugly
[14:06] <knome> flocculant, new draft for contrib slide on pad
[14:07] <flocculant> yep - that works
[14:07] <knome> ok, dropping that in
[14:07] <flocculant> cool
[14:19] <flocculant> knome: got a moment?
[14:21] <knome> yes
[14:21] <knome> a short one :)
[14:21] <flocculant> http://docs.xubuntu.org/1510/C/managing-applications.html
[14:21] <flocculant> that has warning about 2 package managers
[14:21] <knome> right
[14:21] <flocculant> that's not the case with gs
[14:22] <flocculant> so reword the warning to " ...  you may receive an error message"
[14:22] <knome> yes
[14:22] <knome> sounds good to me
[14:22] <knome> "In most cases, you can only use one package..."
[14:22] <knome> or sth like that might be good too
[14:22] <flocculant> and add a note about gs in it's preamble?
[14:22] <flocculant> yea - wfm
[14:23] <knome> i don't think we specifically need to mention that gs doesn't care about that
[14:23] <flocculant> then not bother with a gs note?
[14:23] <knome> it's minutiae
[14:23] <flocculant> yep - that wfm as well :)
[14:23] <flocculant> thanks :)
[14:23] <knome> most people can't even name two package managers
[14:23] <flocculant> ha ha ha
[14:23] <knome> (even if we just listed those for them...)
[14:23] <flocculant> lol
[14:24] <knome> ok, xubuntu slides are at the main branch, and have requested for an upload
[14:25] <flocculant> \o/
[14:26] <flocculant> did you add the whim wham for grinding smoke?
[14:26] <knome> ...what? :D
[14:26] <flocculant> :d
[14:57] <flocculant> ground to a halt on the docs re dvd's
[14:58] <flocculant> pretty sure it can be a lot simpler now - but don't have the hardware to check it out :)
[15:34] <flocculant> any real reason we warble on about 13.04 and 13.10 on the printer page?
[15:44] <knome> flocculant, nope
[15:46] <flocculant> knome: ta :)
[16:08] <knome> since the old documentation is kept intact, i don't see any reason to mention anything in the docs that it at least not supported any more
[16:10] <knome> bbl
[16:57] <Xsm> Hello all - waves.
[17:01] <akxwi-dave> o7
[17:16] <knome> ok, slideshow is in order (cyphermox will take care of that - thanks again)
[17:16] <cyphermox> not sure what code to take though
[17:21] <flocculant> slickymaster: all done
[17:21] <flocculant> well that's a bare faced lie ...
[17:23] <flocculant> all is done except the dvd and encryption bit - which needs looking at - we tell people to install a gstreamer 0.10 package - afaik they're on the bus out of town > https://lists.ubuntu.com/archives/ubuntu-desktop/2016-January/004780.html
[17:24] <flocculant> also we can point to libdvd-pkg for libdvdcss2
[17:24] <flocculant> I've added something to the docs blueprint for this so it doesn't get forgotten
[17:27] <knome> nice
[17:27] <knome> http://dev.xubuntu.org/#tab-timeline tells me i't been a productive week
[17:27] <knome> it's
[17:29]  * knome goes hacky-hack on the dev. website
[17:41] <knome> hurrah, looks totally broken
[17:41]  * knome proceeds to fixing things
[17:43] <xubuntu49w> Hey I'm looking to make a portable xubuntu derivative.  When I unzip the .iso to my flash drive, boot and remove the specified packages (see:  xubuntu-derivateives), I cannot generate a bootable image of the live session using dd
[17:43] <xubuntu49w> dd if=/dev/sdx of=path/to/isogenerated.iso
[17:46] <knome> so dev.xubuntu.org has now the tabs visible at all times, not under the menu
[17:52] <flocculant> knome: is there actually a difference between dev.x and the tracker?
[17:52] <knome> good question
[17:52] <knome> for the data, no
[17:52] <knome> for the looks, yes
[17:53] <knome> at some point i will redirect tracker to dev
[17:53] <flocculant> well yea I understood there was a visual difference - even I can see that :p
[17:54] <knome> hehe
[17:54] <knome> i was just answering your question though...
[17:54] <flocculant> :)
[17:54] <knome> so technically they both connect to the same database
[17:55] <knome> so there will be no difference in the data
[17:55] <flocculant> right
[17:55] <knome> the dev. code might be slightly improved for something more than just the "main" looks, but not much
[17:55] <knome> (or in other words once i set up dev., i haven't updated the tracker code any morE)
[17:56] <knome> that said, there aren't any "bugs" on the tracker
[17:56] <knome> it's just not that sleek code
[17:56] <flocculant> I see gaps between people's names if I look at tab-details/assignees
[17:57] <knome> in dev or traker?
[17:57] <knome> +c
[17:57] <flocculant> dev
[17:57] <knome> (have you noticed my C key is not working correctly?)
[17:57] <flocculant> not really notied that
[17:57] <knome> i have >__<
[17:57] <flocculant> :)
[17:58] <knome> oh right
[17:58] <knome> yeah
[17:58] <knome> that's broooken
[17:58] <knome> that's because the latest updates
[17:58] <flocculant> I lost q once - password had q in it - that was fun
[17:58] <knome> so back to fixing stuff
[17:58] <flocculant> ok - just wanted to make sure you knew :)
[17:58] <knome> i didn't - thanks
[17:58] <flocculant> oh right - your welcome :p
[18:04] <knome> flocculant, can you confirm there's no gaps or other wonkyness in there now?
[18:04] <flocculant> that looks better :)
[18:05] <knome> good
[18:05] <flocculant> :)
[18:06] <flocculant> didn't realise search box ...
[18:06] <flocculant> useful :)
[18:06] <knome> :D
[18:06] <knome> it's been there FOREVER
[18:07] <knome> and yeah, it's really useful when you are looking for a specific work item
[18:07] <knome> especially as it autoupdates live
[18:11] <knome> HEYY, the artwork blueprint is the first one to be complete again!
[18:12]  * knome high fives ochosi
[18:12] <xubuntu49w> Hey I'm looking to make a portable xubuntu derivative.  When I unzip the .iso to my flash drive, boot and remove the specified packages (see:  xubuntu-derivateives), I cannot generate a bootable image of the live session using dd [17:43] <xubuntu49w> dd if=/dev/sdx of=path/to/isogenerated.iso
[18:13] <knome> xubuntu49w, it sounds like you are having trouble with remastering rather than xubuntu itself; you might get better results asking somewhere else (maybe #ubuntu-devel?) on those issues
[18:13] <xubuntu49w> ty
[18:19] <xubuntu84w> Hey I'm looking to make a portable xubuntu derivative.  When I unzip the .iso to my flash drive, boot and remove the specified packages (see:  xubuntu-derivateives), I cannot generate a bootable image of the live session using  dd if=/dev/sdx of=path/to/isogenerated.iso
[18:19] <knome> ...but you just asked that question
[18:19] <xubuntu84w> sry messed up channels
[18:19] <xubuntu84w> forgive me
[18:20] <knome> no problem
[18:30] <xubuntu40w> what do you guys know about the packages that need to be removed to create a xubuntu derivative?  are any of them essential to boot, or to recreation of an .iso from a live session?
[18:45] <knome> none of the packages that need to be removed are essential in booting; they are all practically related to the xubuntu brand and artwork
[19:06] <flocculant> knome: I'll check slideshow speed tomorrow :)
[19:06] <knome> goodie
[19:06] <knome> great, i filled up my vbox HDD
[19:07] <flocculant> ha ha
[19:07] <flocculant> resize it :p
[19:07] <knome> maybe i should
[19:10] <knome> bbiab
[19:40] <krytarik> knome: Having looked through all your font changes for the docs earlier today, you thinking of updating the build depends too?
[19:41] <knome> i leave thinking for others...
[19:41] <knome> so maybe a MP? ;)
[19:41] <krytarik> Gah, no. :P
[19:41] <knome> oh yeah!
[19:41] <knome> you set yourself up...
[19:41] <knome> not my fault that
[20:35] <knome> so...
[20:35] <knome> i can get the PDF's to build on xenial
[20:35] <knome> there are a few caveats to that though
[20:36] <knome> krytarik, you available for a little chat?
[20:36] <flocculant> your upside down in the corner of the room ?
[20:36] <knome> boy that sounded harsh...
[20:36] <knome> no, i have to export one env variable and create one symlink
[20:36] <flocculant> knome: what's it failing on then?
[20:37] <flocculant> oh right ok :)
[20:37] <knome> first one is that fop doesn't find the java env
[20:37] <knome> so export JAVA_CMD=/usr/bin/java
[20:37] <knome> and actually one more thing;
[20:37] <knome> need to install the non-headless java, even if we don't run GUI app
[20:37] <knome> once that's done, it doesn't find some common files
[20:37] <knome> so,
[20:38] <knome> "ln -s ../libs-common libs-common" in both user-docs and contributor-docs
[20:38] <knome> after that, make works
[20:38] <knome> i'll test something that should fix the last part
[20:39] <knome> yep, that works
[20:41] <flocculant> duct tape and spit then
[20:46] <krytarik> knome: A bit busy picking up with today's things still - but it seems you got it figured anyway. :P
[20:46] <knome> still wondering about the headless stuff
[20:46] <knome> and what the best way to use the env var is, or if there's a way to avoid that
[20:58] <knome> i would really want to avoid pulling the non-headless java in at least.
[20:59] <knome> Unit193, your input please
[21:05] <flocculant> how did I manage that ...
[21:08] <knome> /part
[21:08] <flocculant> yes
[21:08] <knome> :)
[21:08] <flocculant> but I didn't
[21:09] <knome> yeah sure
[21:09] <flocculant> not saying it didn't happen
[21:12] <Unit193> knome: I would, but nothing to say on the subject really.  Just that setting the env var and fop not pulling in the deps it needs seems crappy.
[21:12] <knome> yeah, fop explicitly asks for headless
[21:13] <knome> and tbh, i think that should be enough
[21:13] <knome> https://bz.apache.org/bugzilla/show_bug.cgi?id=50062
[21:13] <knome> -> https://bz.apache.org/bugzilla/show_bug.cgi?id=50062#c9
[21:17] <knome> right, so the problem seems to be that after one runs fop in a headless mode, it can't find some accessibility stuff
[21:24] <knome> hmm.
[21:24] <knome> the JAVA_CMD env var isn't needed when the non-headless stuff is installed, it seesm
[21:24] <knome> seems too...
[22:30]  * ochosi high-fives knome back
[22:30] <ochosi> we almost fixed the burndown this week ;)
[22:33] <knome> :)
[22:44] <slickymaster> evening all
[22:50] <knome> 'lo
[22:50] <flocculant> evening ochosi slickymaster
[22:50] <slickymaster> hi flocculant, knome, ochosi
[22:54] <knome> slickymaster, did you notice i resolved the PDF building failure for docs?
[22:54] <slickymaster> yeaps, I did
[22:54] <knome> so where's the thanks?!
[22:54] <slickymaster> saw the changes in the blueprint
[22:54] <knome> :P
[22:54] <slickymaster> one thing at a time
[22:55] <knome> right, rum first, thanks then
[22:55] <knome> ;)
[22:55] <slickymaster> right now, seeing flocculant's hard labour
[23:00] <slickymaster> btw knome, great work on the slides
[23:01]  * slickymaster bows
[23:01] <knome> glad you enjoy it after all the whining :P
[23:01] <slickymaster> if I don't whine you take your graphical design skills as granted :P
[23:04] <knome> :P
[23:20] <slickymaster> flocculant, going to move you up, to keep the alphabetic consistency, in the contributors list
[23:20] <slickymaster> in user-docs/C/index.xml
[23:37] <flocculant> night all
[23:37] <knome> nighty flocculant
[23:39] <slickymaster> have a good one flocculant
[23:39] <slickymaster> and thanks
[23:43] <PaulW2U> y
[23:55] <slickymaster> bluesabre, -docs all ready for upload
[23:55] <slickymaster> \o/
[23:56] <slickymaster> knome, dkessel, krytarik, lots of news strings to be translated :P
[23:57] <slickymaster> knome, a warm and huge THANKS for solving the PDF building failures in the -docs
[23:58] <slickymaster> ;)
[23:58] <knome> :P