[14:32] <bencer> stgraber: how are you going with the zentyal packageset thing?
[14:32] <stgraber> bencer: I'm waiting to have a team to give the rights to
[14:33] <bencer> uhm and i guess zentyal team doesnt work
[14:33] <bencer> because there are more people in there
[14:33] <bencer> right?
[14:34] <stgraber> right, micahg was supposed to create a package set team owned by the DMB for that and add you to it
[14:34] <bencer> so he has to create the team?
[14:36] <stgraber> yes
[15:06] <micahg> bencer: I told you that yesterday
[15:22] <bencer> micahg: ok, didnt read that, true
[15:22] <bencer> when do you expect to have time for that?
[15:23] <micahg> yeah
[15:23] <micahg> I have a long day today, will try to squeeze it in
[15:24] <bencer> ok, we have a fix here ready for the reported bugs, i will have to read on SRU to see if its worth it
[15:25] <mhall119> first contribution to edubuntu in about 2 years
[15:25] <mhall119> \o/
[15:25] <mhall119> hopefully it won't be another 2 years before the next one
[15:26] <stgraber> ;)
[15:26] <mhall119> stgraber: highvoltage: https://wiki.ubuntu.com/Edubuntu/AppGuide is updated for precise, and links to apps.ubuntu.com now
[15:26] <stgraber> mhall119: cool, thanks
[15:29] <micahg> bencer: you still probably won't be able to upload to precise unless stgraber creates the packageset there as well (usually not done, not sure of the difficulty_
[15:32] <stgraber> micahg: I added a "copy" function to edit_acl for that ;)
[15:33] <stgraber> I don't usually do it unless I get asked though, keeping the packagesets up to date for every release is a bit of a pain, so I only copy when needed
[15:51] <bencer> stgraber: micahg dont do it for precise by now, i want to read/discuss if its worth it to make a SRU
[15:52] <bencer> is a bug when upgrading from lucid
[15:53] <jacalvo> from any previous distro, also affects natty, oneiric...
[15:53] <jacalvo> but the fix is in the postinst of the precise package
[15:54] <bencer> stgraber: micahg what do you think? does it work it a SRU? whats the policy on these cases?
[15:57] <micahg> upgrade bugs are generally good SRU candidates
[17:49] <Pictix> Bonsoir tout le monde / Hi everybody
[17:55] <alkisg> Καλησπέρα
[18:07] <Er_> hello to alll
[18:08] <Er_> hello everyone
[18:11] <alkisg> Hello
[18:11] <Hyperbyte> Hi alkisg :)
[18:34] <highvoltage> and I miss alkisg again
[18:37] <Hyperbyte> It's ok... I miss him too.
[18:37]  * Hyperbyte comforts highvoltage
[18:37] <highvoltage> hehe
[19:27] <edu-sysadmin> hello
[19:27] <edu-sysadmin> anyone here?
[19:28] <edu-sysadmin> I had a question about the WebLive sessions, they aren't working for me
[19:28] <edu-sysadmin> the client launches then closes after I click OK
[19:30] <stgraber> edu-sysadmin: looking
[19:30] <edu-sysadmin> stgraber: thank you, I appreciate it
[19:30] <edu-sysadmin> might also have something to do with my location, I'm in Hawaii
[19:31] <stgraber> unless someone is blocking port 6522 or port 6622, it shouldn't
[19:31] <edu-sysadmin> wouldn't that prevent the client from launching though?
[19:32] <stgraber> yeah, it'd
[19:32] <edu-sysadmin> I can start the nomachine client and see the desktop background as it connects, but then it just terminates right after I click OK
[19:33] <stgraber> k. I'm currently applying the pending updates on both servers, then will reboot them so they run all the session cleanup scripts, maybe that'll be enough, otherwise I'll have to investigate later
[19:34] <edu-sysadmin> okay, thank you!
[20:12] <highvoltage> mgariepy, stgraber: hopefully this pans out: http://tranzistors.wordpress.com/2012/05/23/progress-on-gnome-lockdown-1-feature-list/
[20:13] <stgraber> highvoltage: yeah, I think I saw it on planet gnome earlier this week, that's good news
[20:24] <mgariepy> stgraber, is ionice working in lxc containers ?
[20:24] <stgraber> it should, yes
[20:24] <mgariepy> kk
[20:24] <stgraber> root@mediatomb01:~# ionice -c 1 ls
[20:24] <stgraber> root@mediatomb01:~#
[20:25] <mgariepy> http://paste.ubuntu.com/1005428/
[20:25] <stgraber> as the IO scheduler is container aware, it "should" do the right thing and not let a container kill the whole host
[20:25] <mgariepy> it's not on openvz ;) hehe
[20:26] <stgraber> yeah, OpenVZ is weird like that, it does something similar with the OOM kill protection
[20:27] <mgariepy> can we sru this in ubuntu ?
[20:27] <stgraber> instead of doing the obviously correct thing of grouping all the processes of a given pid namespace and consider the group as a single regular-priority task outside of the pid namespace (that's what the linux scheduler does)
[20:28] <stgraber> just to be annoying, I'll say no ;) if it was breaking with LXC, it'd be a bug, but considering we don't support OpenVZ since 8.04, it's not technically a bug :)
[20:28] <stgraber> I'm not against SRUing it with some other fixes, just won't push it on its own
[20:30] <stgraber> mgariepy: can you file a bug against ltsp in Ubuntu, targeted for quantal+precise with an ltsp upstream task and tagged with needsru?
[20:30] <mgariepy> stgraber, k thanks
[20:45] <mgariepy> https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1004158
[20:45] <ubottu> Launchpad bug 1004158 in ltsp (Ubuntu) "ltsp-update-image doesn't work on precise in an openvz container" [Undecided,New]
[20:45] <stgraber> thanks
[20:46] <mgariepy> welcome
[20:46] <stgraber> mgariepy: already fixed upstream?
[20:46] <mgariepy> yeah
[20:46] <mgariepy> j'ai pris le test de /etc/cron.daily/mlocate ;)
[20:47] <mgariepy> sur ce, cya
[20:47] <mgariepy> stgraber, http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2242
[20:49] <stgraber> a+