=== manusheel is now known as manusheel_afk === manusheel_afk is now known as manusheel [11:39] ishan: Check this http://pastebin.com/KTh829tB === mukul_afk is now known as mukul === mukul is now known as mukul_afk [14:27] dfarning, are you here? [14:31] has anyone seen dfarning? [15:04] jelkner: Hello. [15:05] manusheel, hi! [15:05] jelkner: David seems to be offline at this juncture. You can send him an e-mail. [15:05] Thanks, manusheel, I'm doing just that right now ;-) [15:48] jelkner: unless the bug is directly related to something in the USR PPA or disk images, please file bugs against the specific packages in ubuntu [15:54] dfarning, Hii [15:55] dfarning, I am waiting for your reply for VM access to create USR for Tamil language [16:04] manusheel, Hii [16:17] thangam_arun, I don't understand how internationalization works. Every time I look into it my head starts to swim:( [16:17] thangam_arun, I really can't be of much help [16:18] thangam_arun, do you understand how to create a language specif iso? [16:18] dfarning, We are as a team trying to promote Sugar with Ubuntu [16:19] Ya, i have done customization for ubuntu-10.04 using UCK tool [16:20] dfarning, Here people in Tamil Nadu part of India speaks Tamil as the Mother tonque. So inorder reach them we need regional language support [16:21] thangam_arun, hmm so you can just take a ubuntu iso and respin it with language support using UCK? [16:21] * dfarning installs UCK [16:22] dfarning, i am not sure will that help [16:22] dfarning, i have not tried yet [16:23] thangam_arun, ok, do you know if sugar has been translated to tamil? [16:23] dfarning, Manusheel form seeta team refered to approach for this work [16:24] dfarning, I am the Tamil language admin for sugarlabs projects [16:24] dfarning, I have done the translation. Its 100% [16:25] thangam_arun, awesome. That is 95% of the work! [16:26] dfarning, yes :-) [16:27] Ian_Daniher, do you know how to make a language specific spin? [16:27] dfarning, Refer this link also: http://translate.sugarlabs.org/ta/ [16:30] thangam_arun, what is the iso code for tamil? [16:31] dfarning, You mean Locale ?? [16:32] ta_IN is the locale code for Tamil [16:32] thangam_arun, yes(i think) the two letter code for the lang. [16:33] thangam_arun, thanks [16:33] dfarning, YEs [16:38] thangam_arun, ok it looks like the ta .po files are correctly migrating from pootle to git.... see http://git.sugarlabs.org/projects/sugar/repos/mainline/trees/master/po [16:40] dfarning, oh good [16:42] thangam_arun, what happens if you install sugar on maverick and switch your local to ta? [16:45] thangam_arun, one thing I dont understan is that the version of sugar on maverick is .88 and I don't know if pootle applied your recent translations to that version or to .90(the most recent version. [16:46] dfarning, I have no Tamil Language option in the "USR-i386-20100907.iso" image [16:47] in .90 version the updates will be there [16:55] thangam_arun, I am going to try to use UCK to add tamil to the iso as a debugging step. [16:55] dfarning, okay [17:03] thangam_arun, it looks like the UCK method is working.... But I cant read tamil well enough to read the menus. [17:05] thangam_arun, would you mind 1) downloading the latestest usr iso 2) using UCK to modify the usr iso to set tamil as the default lang and 3) test the modified iso. [17:06] thangam_arun, if that works, I will modify the standard USR build process to make a tamil based iso by default. [17:11] dfarning, Sure [17:12] dfarning, I will that by tmw and will update you the status :-) [17:13] dfarning, Also i am willing to take part in USR creation. Would like to contribute for the same [17:13] thangam_arun, if that doesn't work we will have to create an iso of sugar .90 on maverick. [17:14] thangam_arun, are you familar with shell scripting? [17:14] dfarning, Yes i am Linux Sys admin [17:15] thangam_arun, nice! [17:15] dfarning, i use Linux as my Desktop/Server :-) [17:18] thangam_arun, nice. The build script is pretty straight forward.... but it contains a lot of magic and is pretty brittle. So we can't run it automatically. would you be interested in running builds? [17:19] Yes, I will be happy in doing this work [17:20] thangam_arun, NIICE. Can you send me you ssh key so I can give you access to the build machine? [17:21] dfarning, Sure [17:21] thangam_arun, are you familar with the basic concepts of building a ubuntu live CD? [17:21] dfarning, i will send through mail. is that okay? [17:22] dfarning, Yes [17:22] thangam_arun, yes dfarning@gmail.com [17:22] dfarning, okay i will send in 15 minutes. [17:23] dfarning, i am taking my dinner right now. :-) [17:24] thangam_arun, I m going to lunch too. I'll be back in about an hour. [17:24] dfarning, oh ok === mukul_afk is now known as mukul [18:14] alsroot: Around? [18:14] mukul: yup [18:15] alsroot: I intend to make some change in logging.py and give a bolean value to a new variable. Then using the bolean value I want add an alert. Can you tell me which file should I use for add the alert function? [18:17] mukul: do you mean popping up an alert from logging.py? [18:17] Yes [18:17] alsroot: But I guess that can't be done directly. It doesn't have the GUI functions. [18:18] mukul: that will be misusing of logging.py, it is only for non-gui stuff, you need to popup alerts from more high level [18:20] alsroot: Yes. I'll just create a new variable in logging.py which then would be used for popping up an alert. The problem is in which gui file should I use the variable and popup the alert. [18:21] dfarning, i am back [18:22] dfarning, Also sent a mail to your gmail with public ssh key [18:22] mukul: could you explain what use case you mean (with such variable in logging.py) [18:25] alsroot: This is what I intend to do. whenever a function logging.error or logging.warn or logging.warning or logging.exception is called. I want it to display an alert saying "The requested operation could not be performed. Please check the logviewer activity for more details.". All this is with reference to the bug#2063. Am I on the right track? [18:26] alsroot: This is what I made out of the conversation between bernie and eben. [18:31] mukul: well dunno about the way you've chosen, for me this feature smells bad -- for me, using something like bug report is more useful -- anyway about your Q about an alert, this exactly what don't like in this bug :) [18:31] s/what/what I/ [18:32] any method I can imagine sounds ugly [18:34] alsroot: Ok. I agree this might not be the ideal way. [18:35] mukul: I meant the your way, but this feature itself [18:35] s/your/not your/ [18:35] alsroot: However, wish if you could suggest a gui file which I could use to popup an alert. [18:36] mukul: alrert classes are in sugar-toolkit/src/sugar/graphic/alert.py [18:37] mukul: for the place alert might be popped up, well maybe from journal [18:37] alsroot: Yes but there alerts are defined. I need a GUI file as was (journalactivity.py) where in I could add an alert. [18:37] s/might be/only/ [18:38] mukul: sugar/src/jarabe/journal [18:39] JournalActivity is the main class [18:50] alsroot: One more question, when it is written import logging... which file is being imported. I mean there are multiple copies of logging.py with different paths. How do I ensure it is being imported from the one I am making changes in? [18:52] mukul: python uses PYTHONPATH envar + standard paths [18:52] ..including current one [19:12] dfarning, Did you receive my mail ?? [19:21] alsroot: journalactivity.py imports logging. I have introduced the a new variable at the logging.py. But when I use the variable using logging.CHECK_ALERT , the log says " The module object has no attribute CHECK_ALERT". There are 4 logging.py file in sugar-jhbuild. Any ideas how to resolve this? [19:23] mukul: btw you shouldn't override standard "logging" import, the right way is creating new module and use it instead of standard one [19:25] mukul: better to avoid name clashing [19:36] dfarning_, Did you receive my mail ?? [19:43] thangam_arun, yes, I just got back from lunch and my bike ride. [19:43] dfarning_, oh great [19:43] dfarning_, oh great [19:45] thangam_arun, did modifing the USR iso with UCK work? [19:46] dfarning_, Not yet. I have to dwonload the latest ISO. I will do it my tmw [19:47] s/my/by/ [19:48] thangam_arun, Great. what username should I use for your account on usr.sugarlabs.org? [19:49] thangam.arunx [19:57] thangam_arun, can you ssh thangam.arunx@usr.sugarlabs.org [19:57] dfarning, i will do that now [19:59] dfarning, I just logged in [20:01] thangam_arun, can you sudo? [20:02] dfarning, Yes, i can === mukul is now known as mukul_afk [20:02] thangam_arun, great you will need to sudo to do a build. [20:03] dfarning, Oh okay [20:04] all of the build stuff is in my home dir under the usr dir. can you copy that dir to your home dir, change the chown to your account and try to run a build? [20:05] thangam_arun, 'sudo ./usr-scratch.sh all i386' is the incantation to run a build. [20:06] sure sure [20:08] thangam_arun, I think user-scratch is pretty straight forward for a sysadmin with a knowledge of customzation. [20:08] dfarning, Yes, should be [20:12] dfarning, i have to copy the "usr" dir or "usr-scratch.sh" file alone ?? [20:13] dfarning, the build folder is 4.8GB size [20:18] thangam_arun, you need usr-scratch and template/ [20:18] dfarning, ok fine [20:20] thangam_arun, but the script might die. becuase of missing dir that you will have to add by hand.... or better yet have the script create the dirs as necessary [20:20] oh ok [20:21] dfarning,thse dir's build/ logs/ output/ ?? [20:21] s/thse/these [20:23] thangam_arun, I just deleted the contents of build. so yo can copy the whole usr dir. [20:24] dfarning, oh ok [20:24] thangam_arun, to reduce network load I cache everything between builds [20:25] dfarning, ok [20:25] thangam_arun, build/ contains the chroot and image for a build of each arch [20:25] output/ contains the isos [20:26] logs/ contain the build logs [20:26] dfarning, All right [20:26] tempplate/ contains some file to prime the process. [20:27] thangam_arun, I think there are about 25G free on the harddrive so space is not too much of an issue [20:29] dfarning, ok ok [20:45] dfarning, Sugar-88 is not yet added to ubuntu maverick repo ?? [20:46] dfarning, Some of the packages were need to be added in order to have suagr-0.88 or ?? [20:46] thangam_arun, everything should be coming from maverick universe. [20:47] dfarning, In the script the default version is suagr-0.86 [20:48] thangam_arun, where? sugar is install in line 134 [20:49] yes in 135 [20:50] thangam_arun, line 135 installs a group of activites [20:50] thangam_arun, core is installed in 134. [20:51] bernie, oh ok. then the versio is 0.88 or 0.86 ? [20:52] dfarning, oh ok. then the versio is 0.88 or 0.86 ? [20:52] s/versio/version [20:52] thangam_arun, actually as your first change to the script you can delete line 135. all of the activites are now included as part of usr-meta [20:54] thangam_arun, it is .88. there are a couple of activities name sugar-*activity-0.86 this is just a quirk that mean that activity only runs on ).86 or later. [20:54] dfarning, ok fine [20:54] dfarning, i will do that [20:55] thangam_arun, there was an api change between .84 and .86 which broke a bunch of activities [20:56] dfarning, Okay [20:58] thangam_arun, sugar-ubuntu-remix is the equivlent of installing ubuntu-desktop or ubuntu-netbook [20:59] dfarning, Fine, What else got added if you use "sugar-ubuntu-remix" other then "ubuntu-desktop or ubuntu-netbook" ?? [21:00] thangam_arun, it contain the entire distro stack. the casper, prober,ubiquity... stuff is for the live cd and installer [21:00] dfarning, Oh okay [21:01] thangam_arun, sugar-ubuntu-remix is auto generated from a seed file [21:01] thangam_arun, see http://usr.sugarlabs.org/seeds/ubuntu-sugar-remix.maverick/ubuntu-sugar-remix [21:02] dfarning, yes [21:03] thangam_arun, most of it is a very standard ubuntu install there are a couple of sugar specif stuff in the last 20 lines (or so) [21:03] dfarning, ok [21:03] thangam_arun, we have removed a couple of things to save space. [21:05] thangam_arun, the usr seed file is a very slightly modified from the seed file used by ubuntu-netbook [21:05] dfarning, Okay [21:06] thangam_arun, this means that usr will run on every machine on which ubuntu runs:) [21:06] dfarning, got it [21:11] thangam_arun, the use of the -meta, -setting, and other seed files is a bit convoluted. The goal was for the build system to exactly match the upstream ubuntu build process. [21:12] thangam_arun, this will allow us to add USR to the upstream ubuntu build farm with little modification. [21:12] dfarning, to avoid the build breakups ? [21:12] dfarning, thats good [21:14] thangam_arun, my goal is for USR to be a 'community supported distro' for 11.04 and a 'canonical supported distro' by 11.10 [21:14] thangam_arun, 11.10 will be a LTS release:) [21:14] dfarning, Okay [21:21] dfarning, Here in India its 2 am now :-) [21:22] thangam_arun, time for bed:) ping me tomorrow with any more questions. [21:22] dfarning, Sure [21:22] dfarning, Thanks a lot for your kind support [21:22] dfarning, Gud night [21:24] thangam_arun, good night. I hope we can be of use to you. [21:24] dfarning, Yes Really :-) [21:24] dfarning,See you tmw