=== best_pony is now known as Mapley [00:56] Mapley, hold your... ponies [00:57] bbl -> [04:41] The ISOs are getting awefully large... [04:42] Unit193, current size? [04:43] ~900MB. [04:43] that's shot up quick [04:45] I wonder what could be used to reduce it [04:46] http://paste.openstack.org/show/K6vzagtj8MuyXd3TFyUU/ [04:48] nothing shows up for the paste [04:48] Weirdly nothing does unless you hit raw: http://paste.openstack.org/raw/dFvG9B7pMueL843yqKWX/ [04:50] gnome-settings-*, gnome-session*, gnome-control*, and gnome-desktop* should be able to, if we can change what's pulling them. :/ [04:50] Biggest part is, we have 3 python versions, right? [04:51] Yep. [04:52] i think so [04:52] What do we have to do to drop 3.3 or 3.4 for the final iso? [04:52] also a lot of new cups stuff seems to be in [04:52] Don't know offhand. [04:53] Nice part of do-release-upgrade, you get the full list of things being installed (a lot of which gets purged. :P ) [04:54] gdisk seems to be a new recommend of udisks2 [04:55] Recommends are killers. :/ [04:56] I wonder how much smaller our iso would be with --no-recommends [04:56] On the bright side, we're about to bump them up with menulibre, mugshot, and xubuntu-community-wallpapers! :P [04:57] :) [04:57] well, we should only end up with 2 versions of python by fonal [04:57] fina [04:57] final [04:57] Nice. [04:58] indicator-sound now has an alt dep on pavucontrol, so that shouldn't pull in one of the control centers... [07:31] knome: ok - I'll look later [08:49] knome: looked now - mucked about with it a bit [08:51] zequence: many of our testcases are - open it, start a new , save it, close it, does saved open, does help work [08:52] really basic stuff [08:53] if you want someone to start running through them - I can find some time for it [08:58] once the basic test is written it's not as bad to flesh them out - where it's required, the worst bit is actually getting them on the tracker - wasn't a great deal of fun last cycle, but it was worth it in the end [09:30] elfy: Simple is best :). I think cub would be a good candidate to work on testing, if he can find some time for it [09:31] It has happened that we released, and there have been some pretty serious, yet fixable bugs [09:31] zequence: well I can start working on writing them today, I'll just work from the testcase bugs for your stuff [09:31] That's mainly what I would like to prevent with testing [09:32] elfy: We only need testcased for our multimedia applications, though [09:32] yep - ok [09:42] morning all [09:42] hi slickymaster-job [09:44] hi elfy. Did you have a good weekeend? [09:44] pretty good thanks :) [09:45] he had a pretty heavy storm here, yesterday [09:52] zequence: I'll work with the 5 'menu' groups you have - Audio Production etc [10:42] knome: somethings up with whatever package deals with keyboard settings, not sure which package it would be - but updates set keyboard layout to US - which can play havoc with passwords [10:42] ochosi - maybe you know which it is [11:12] it's a issue with ubuntu in general [11:13] ok ali1234 thanks [12:54] bbl -> [14:15] knome, slickymaster-job, my first cut of the MenuLibre section in the Settings & Preferences chapter: http://imagebin.org/292590 [14:15] subject to change pending the decision on whiskermenu [14:16] if I'm going to work on the upstream version, I'm going to need a tutorial from bluesabre :) [14:17] jjfrv8: we're planning on taking a decision in this week's meeting to finalize the panel stuff [14:17] cool [14:18] let's hope enough people turn up then :) [14:18] jjfrv8: it looks great, so far [14:19] but we really do need a tuto on it [14:21] elfy: yeah, sorry for not being there for the last few meetings, it wasn't that i didn't want to attend [14:22] ochosi: lol - I didn't mean anyone in particular, just if there's not many about it won't help with the whisker menu thing :) [14:22] well depends, we've voted on it once before [14:23] the general idea yea [14:23] the proposed panel layout would work without it as well [14:23] just not as nicely [14:23] and not whisker - but the proposed layout is what I was meaning too [14:23] ochosi: which looks fine to me :) [14:24] yeah, it's not a real departure imo [14:24] so there's no need to make a huge fuss about it [14:24] I agree [14:24] it's just a reduction of the current layout [14:24] yea [14:24] since it's easy enough for ppl to customize it, i think that makes sense [14:25] exactly - I'd love the default to be exactly like mine - but no-one else is likely to :) [14:30] :) [14:30] everyone would like the default to be like theirs i guess [14:30] I'd guess so - being human and inherently bone idle :) [17:09] knome: ping [17:09] slickymaster-job, pong [17:10] lol, i chased you on -off [17:10] heh [17:10] slickymaster-job, so yeah, i'll look at that [17:10] thanks :) [21:04] pleia2, did you have something done re: the website updates? [21:05] we should really look into getting a new docs upload for beta 1 [21:06] that would also close a lot of the -docs blueprint work items, so it would be more accurate [21:10] Some are pending, like shipping translations. :P [21:10] yep. [21:10] a lot of stuff is [21:11] Also did that http://paste.openstack.org/show/iPSpyiAk8MSRAog8pQR3 [21:11] :) [21:12] I'm trying to make it so people don't try rm -r for fun, thus used rm -ir === Mapley is now known as Queen_Mapley === Queen_Mapley is now known as Mapley [22:25] knome: no, I was missing all weekend [22:26] ali1234: have you bothered tedg about indicators lately? [22:29] not this week no [22:31] can you link the bug report pls? [22:31] we could bump it a bit [22:31] pleia2, great to hear you've been found [22:31] :) [22:33] ali1234: feel like launching a combined "attack" on him now that he's around? [22:34] is he around? [22:34] * knome ponders: hmm, pink wallpaper for trusty [22:35] yeah, he just was on #ubuntu-desktop [22:35] I LIEK PINK [22:37] ali1234: do you know what he has to fix technically speaking? [22:37] sure, i sent a MR [22:38] oh, i didn't know that [22:38] sry, seems i don't know the full backstory [22:39] i thought i mentioned it [22:39] you probably did, i wasn't at a few of the last meetings though [22:50] hey knome, you still around? [22:50] hey knome, you still around? [22:52] slickymaster, flooding the channel, aye? [22:52] :) [22:53] nah, I hardly can feel my fingers [22:53] got get myself some gloves :P [22:53] yep [22:53] did you manage to browse through the wallpaper section? [22:54] nope, not yet [22:54] though you can poke jjfrv8 with them now [22:54] he's able to merge as well [22:54] and you don't need my ack for everything really :) [22:54] yeah, good idea [22:54] well, just playing on the safe side, even know you got a ton of issues between hands [22:55] I'll try not to overload you so much [22:55] i did look really quickly at it, and what i saw looked fine [22:55] I'll ping jjfrv8 on it [22:56] if he's also ok with it, I'll make a MP for review [22:58] jjfrv8: here's my proposal for the xfdestop of the settings-preferences chapter: http://paste.ubuntu.com/6911856/ [22:58] jjfrv8: please ping on your opinion [23:04] Noskcaj: ping [23:04] micahg: ping [23:09] knome: just to give you a quick heads up, since ali1234 and i just talked to tedg about gtk3 indicators in #ubuntu-desktop [23:09] okay [23:09] there's no clear ETA on fixing the indicators on the ubuntu side [23:09] but i guess it [23:09] they just pushed the half-borked stuff to get more time [23:09] * bluesabre starts working on menulibre upstream documentation [23:09] ...it's happening before T? [23:09] bluesabre, :) [23:10] because FF doesn't apply to this "bugfix" [23:10] i don't think they did it on purpose [23:10] i think it's a bit nasty, but we should do the same [23:10] ochosi, yep. [23:10] yeah, ali1234 is right i guess, and i didn't mean to make it sound like they did it on purpose [23:10] it was pushed months ago [23:10] just unhappy phrasing [23:11] i'm pretty sure this will get fixed in time [23:11] for T [23:11] but not for FF [23:11] ACK, i'm fine with that [23:11] and i also think there'll be no panel-release on the xfce-side before FF [23:11] so we should push what we have [23:11] it has to get fixed really, otherwise unity will be broken, as previously stated [23:11] (is my conclusion) [23:12] ochosi, as long as it doesn't render anything completely unusable, sure [23:12] if we're pushing a git snapshot anyway, i recommend somehow putting in the workaround if possible [23:12] ali1234: is unity really broken too? indicators seem to work fine like they always did [23:12] ali1234, that means more work though [23:13] brainwash: it's a race condition [23:13] ali1234, we've just concluded that we shouldn't do workarounds [23:13] bluesabre: ? [23:13] the workaround = putting a variable in the environment [23:13] ali1234: oh, never encountered it :) [23:13] bluesabre: whoopsie, that wasn't intended like that :) [23:13] ? [23:14] at the very least we should tell testers to apply the workaround manually [23:14] and then add it to the release notes if it's still not fixed by then [23:14] +1 [23:16] the workaround is "echo INDICATOR_ALLOW_NO_WATCHERS=yes | sudo tee -a /etc/environment" [23:17] it should check for the current session [23:17] no, it shouldn't, because it is broken on all sessions [23:17] including unity [23:17] ali1234: session restart needed after that i presume? [23:17] right [23:19] ali1234: indicator-application still doesn't want to start [23:19] or do i have to reboot? [23:20] hmm. yeah you might have to reboot [23:20] check env? [23:20] yup, need reboot [23:20] check the /etc/environment is okay too [23:21] it might have put it on the same line or something [23:21] PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:INDICATOR_ALLOW_NO_WATCHERS=yes" [23:22] yeah that's wrong [23:22] should be in a separate line? [23:22] yes [23:22] also it shouldn't be inside the quotes like that [23:22] you did it manually? [23:22] no, used your suggested command [23:22] where did the extra : come from? ;) [23:23] oh, hm [23:23] might've added that manually some other time then :) [23:23] i don't know if /etc/environment has a trailing newline by default, but it should do [23:24] yup, that worked