[00:10] could you be more specific? :) [00:11] #ilovexubuntu preparing [00:11] ah, no work done on that yet [00:11] should we schedule a meeting? [00:12] or if you feel super motivated to work on it now, that works as well [00:12] have other tasks today, will have to pencil in some time later [00:12] okay - i will be most likely in bed by then [00:13] like, not today later :) [00:13] ah :) [00:13] any idea on more specific time? [00:13] not sure, drowning in book deadlines at the moment [00:13] mhm [00:14] let's try to meet impromptu then [00:14] k [00:14] something like 10pm-> UTC is usually "free" for me [00:14] in local time, think "two hours earlier from now" [00:15] k [00:16] or maybe 9pm on some days [00:16] so if you happen to be around about then, you can try to ping me [00:16] (well you can always try, but likely with worse results...) [00:26] pleia2, also updated the front page with usb flash drive button [00:26] (and cleaned up the widget a bit) [00:27] i'm starting to think i might want to OCD about the button placement [00:27] neat [00:27] so they would always be bottom aligned in the container [11:06] knome: just quickly does ^^ mean the new docs will land soon? [11:06] flocculant, referring to which one? :) [11:07] flocculant, re: the discussion with pleia2, it means we will have the google code-in stuff prepared [11:08] well the docs talk ... [11:08] flocculant, but now that you say it, yes, we should have covered the actual docs too [11:08] so the cont stuff will go live soon? and land in xenial too? [11:08] pleia2, ping; when you have time, can you build the 16.04 docs on docs.xubuntu.org with "make" - this builds the contributor docs too [11:09] pleia2, i will also prepare the branch for the subdomain root [11:09] is that fixed now? [11:09] yes, everything should work - but none is uploaded yet [11:09] and when we do the next upload to repository, the contributor docs are in too [11:10] oh yea - xenial builds except on xenial - I forgot we did that discussion :p [11:10] do we want one push there before a1? [11:10] heh [11:10] i'm not sure xenial builds are done on xenial machines though [11:10] so it's not a problem - yet [11:10] ack [11:10] at some point around trusty or sth i remember hearing some build machine running lucid [11:11] I would say push as soon as we can - I need to deal with the x.org/contributor/qa page when the help is live [11:11] ha ha [11:11] let me elaborate: [11:12] i will make sure the online docs have contributor stuff ASAP [11:12] do we need them ASAP in the xenial builds too? [11:12] because those are two different things [11:12] yea - I'd like to see then building on xenial asap [11:12] because [11:12] oki [11:12] oh, building [11:13] that's the third thing [11:13] :D [11:13] when i say xenial builds, i refer to the documentation being shipped with the ISO [11:13] I can't say - 'do exploratory in xenial' run a vm of wily to read the qa docs :p [11:13] yes - I assumed that's what you mean [11:13] t [11:13] ok [11:13] bluesabre, ping; please prepare a new upload for the docs ASAP [11:13] and when it's built it'll land as update for existing xenial installs? [11:14] and yes I assume it will then :D [11:14] yes, it should do that [11:14] knome: Doesn't it not build in Xenial? [11:14] Unit193: no - pdf issue [11:14] Unit193, yes, but are the packages built for xenial on xenial machines? [11:14] i mean no, it doesn't build [11:15] I assume Unit193 means locally ... [11:15] Ummm, that's kind of the point, yeah.. [11:15] well then we should get that fixed [11:15] sigh [11:15] Unit193: make errors because of pdf - so cont docs don't build [11:15] one thing we could do for a small while is disable pdf building [11:16] so we could get the package to build for now [11:16] this might be a hard way of doing this - not sure, but could we not build docs, build cont docs, build pdf [11:16] so it errors when the docs are built [11:16] or disable pdf's :) [11:16] that would be possible too [11:16] s/when/once [11:17] but i don't know, it feels kind of dirty :P [11:17] heh [11:17] i mean fixing the order [11:17] yea - it felt a bit dirty writing it :D [11:17] hehe [11:17] and ultimately, i don't know what happens if make reports it fails [11:17] it might just report FTBFS and the package isn't updated [11:18] right [11:18] Unit193 might know if that's how things go [11:18] Unit193: still bug 1515361 afaik [11:18] bug 1515361 in fop (Ubuntu) "Fop FTBFS on Ubuntu Xenial (synced version in -proposed)" [High,Confirmed] https://launchpad.net/bugs/1515361 [11:18] so disabling pdf would mean that we can get the package to build without errors [11:18] yep [11:18] but it also means we need to patch the package to *build* the pdfs later [11:18] right [11:18] kind of crappy situation [11:19] that's trivial though [11:19] it's a one-line change [11:19] and we do need to do something because pdf is useful imo [11:19] it has its merits and i would definitely like that it builds now that we have it, but fortunately it's not critical [11:19] it's not like our docs do not build at all [11:19] yea [11:20] * knome knocks wood [11:20] :) [11:20] oww ... [11:25] flocculant: apt list | grep installed,loc [11:26] and then? [11:27] Anything come out? [11:27] oh yea [11:28] 1. That many? 2. fop one of 'em? [11:28] http://pastebin.com/3cYc2zYQ [11:28] fop isn't no [11:34] Unit193: fwiw http://pastebin.com/8NeKmv9v [11:38] Ah, thanks. [11:47] Test build is taking a while, Ubuntu mirror decided to give me sloooooooooooow speeds. At least I have a few things to try in the meantime. [11:48] :) [12:01] 2 [12:01] oops [12:01] vacuuming [12:02] next the pc [12:02] bbl [12:06] So does it count if I get the docs, contrib docs, and pdfs to build? [12:06] it does if you did it on a xenial install :p [13:09] keeping an eye on the docs status [13:09] let me know when we think they're ready to roll [13:09] and then Unit193 or myself can upload them [13:10] Will have to disable PDFs. [13:10] k