[00:07] <mhall119> wow, trolling #edubuntu?
[00:07] <mhall119> you know you have no life when....
[00:29] <highvoltage> heh, yeah
[06:54] <gurkhali69> hello can anyone help me to build fat client image offline? i have done online installation using < ltsp-build-client --fat-client --fat-client-desktop edubuntu-desktop --arch i386 --skipimage > . now i need to install it without using internet connection. plz help...
[14:38] <robehend1> is it possible to use the Edubuntu menu-editor to assign different profiles to likewise-open AD groups? e.g. students profile to the DOMAIN\Students, staff to DOMAIN\Staff, etc
[14:53] <highvoltage> robehend1: I don't know for sure, but since it works pretty much like normal groups, it should really be fine. if it isn't, then it should probably get a bug for that
[14:54] <robehend1> highvoltage: only issue I'm having is getting them to show up in the gui for profile assignment. only likewise-related one i see is LTSPHOST\Likewise Users
[14:56] <highvoltage> ah right, because you only see your own groups right?
[14:56] <robehend1> correct
[14:56] <robehend1> have the same issue with Sabayon, now that i think about it.
[14:57] <highvoltage> mgariepy: any ideas? perhaps menueditor could get a custom field for that? sounds like a very common use case :)
[15:10] <robehend1> highvoltage: would it make sense to just add the group to the /etc/group file? it looks like that is where the editor is reading from. I'm not sure of the syntax though, since its an AD group, not local
[15:12] <highvoltage> robehend1: I'm not sure what happens if you have groups with backslashes in there, it might work with a bit of trial and error, perhaps you might need to escape a backslash in there, I have no idea but it sounds worth trying
[15:13] <robehend1> highvoltage: likewise *does* let you change the domain seperate from a backslash to say, a hyphen. guess i've got an afternoon project
[15:15] <highvoltage> robehend1: I just played around with it, addgroup doesn't allow you to use backslashes, but it does work if you manually put it in /etc/group
[15:15] <robehend1> how did you add it. DOMAIN\\Group ?
[15:15] <highvoltage> DOMAIN\group
[15:16] <robehend1> hmm, alright. now to give it a shot. any services I have to restart after fiddling with that file/
[15:16] <highvoltage> that's how I added it in /etc/group, then I added the user to the group by doing a adduser testuser TEST\\group
[15:16] <highvoltage> nope
[15:17] <robehend1> you just give it a random number? So it'd be like...DOMAIN\Group:x:8283 or something?
[15:17] <highvoltage> I just incremented the last used group ID, but you can choose a higher number too
[15:18] <robehend1> hmm. Now to see if its actually using the AD group, or if we just made a group called DOMAIN\Group
[15:19] <highvoltage> well, it won't actually be the AD group, I thought you just wanted it to add users to the group in menueditor?
[15:25] <mgariepy> robehend1, you probably can use desktop-profile with likewise groups
[15:25] <robehend1> I'm wanting to be able to assign profiles in menu editor to members of the AD group
[15:25] <robehend1> i could be explaining it wrong, as well
[15:25] <mgariepy> i guess the simplest way would be to edit the file manually
[15:25] <robehend1> the /etc/group file?
[15:26] <mgariepy> nop, the /etc/desktop-profiles/whatever.listing file
[15:26] <mgariepy> can you try to asign the profile to a random group, then edit the file it createsd
[15:27] <robehend1> hmm, let me give it a shot
[15:27] <mgariepy> not sure how it will react with "\" in group name tho
[15:28] <robehend1> well, that can be changed in likewise to be a - or something
[15:28] <mgariepy> with ldap it works correctly
[15:29] <robehend1> ack, student calls. i'll have to come back to this. thanks though!
[19:08] <stgraber> highvoltage: edubuntu ?
[19:08] <stgraber> as in meeting (unless I got mixed up with timezones again)
[19:08] <stgraber> mgariepy: ^
[19:10] <mhall119> I think it's early for a meeting
[19:10] <highvoltage> stgraber: hi!
[19:10] <stgraber> ok, so got mixed up with the timezones again :)
[19:10] <highvoltage> mgariepy I think is in a meeting
[19:10] <stgraber> so that's in 50 minutes ?
[19:11] <stgraber> just wondering because I saw that the QA meeting is about to begin and it's usually conflicting with ours + my cell meeting reminder rang 30min ago :)
[19:12] <stgraber> oh, and it's 19:11 UTC so I think I'm right ;)
[19:12] <stgraber> highvoltage: can you confirm ? :)
[19:12] <highvoltage> this wednesday kind of snuck up on me
[19:12] <highvoltage> yep, it's the right time
[19:12] <stgraber> yeah !
[19:12] <stgraber> (not that I have anything to say at the meeting anyway)
[19:13] <highvoltage> I'm just digging up my tomboy notes so that I can remember what I did the last week :)
[19:13] <stgraber> I guess we should switch to -meeting, even if it's to say that we don't have anything to say :)
[19:14] <highvoltage> well, we have some seed changes, kstars has been dropped (in favour of kstars) and there's a bunch of other seed changes too but I don't have them open right now
[19:15] <highvoltage> I've been talking to LibreCAD upstream a bit off-list
[19:16] <highvoltage> they are eagre to have it in Edubuntu, they're just finalising logos, etc. then I'll review it for universe
[19:16] <stgraber> => -meeting ?
[19:16] <highvoltage> d'oh
[20:25] <maco> i think the desktop is in kdepim-runtime because the other akonadi packages are either the lib or the server, but the client and server probably dont have to be on the same system
[20:26] <maco> then again, its used to start/stop the server, so id be inclined to put it into akonadi-server
[20:26] <highvoltage> ah right
[20:27] <highvoltage> we could just hide those menus, but that feels more like covering up the problem than fixing it
[20:27] <highvoltage> but as you said that's kind of hard to avoid since that's how kde upstream works
[20:28] <maco> i think it should be possible to make akonaditray a separate package and have the actual kdepim applications depend on it instead of the whole runtime, maybe?
[20:28] <maco> er i mean instead of including it in the whole runtime
[20:29] <maco> like, to split up that package a bit
[20:29] <highvoltage> that would be nice
[20:34] <maco> highvoltage: do you end up with akonadi-server installed too?
[20:35] <maco> nvm. answer's yes
[20:35] <maco> kdepim-runtime depends on it
[20:35] <maco> yeah...python-kde4 just needs to be broken up so packages can depend on some subset of the kde platform
[22:58] <salvy> Hi