[04:54] <usr-Maverick> seems to work Ubuntu 10.10 maverick (development) I draged dropped applications to journal for surf 115 irc record.....
[04:55] <usr-Maverick> manusheel: Cd works  USR 804
[04:55] <usr-Maverick> I have avitars (XO ) in f1 neighborhood on jabber
[04:56] <satellit_afk> maverick only has non working read 76 which updates to 86 still no start
[04:56] <satellit_afk> good night
[12:15] <dfarning> manusheel, did you get a chance to talk to luke about uploading patches for packages?
[13:58] <satellit_> manusheel: I think I may understand dropping into sell on boot with USR 804:  The CD ejects too soon, before the writes complete to the USB drive?  At end of install to USB HD if you hit reboot button it ejects CD almost immediately leaving a screen full of errors saying ./dev/sro/ missing. It never procceedes from there and one has to use power off to shut down PC.
[13:59] <satellit_> it never finishes writing and reading to HD.
[14:01] <satellit_> Possible test: avoid the pop up and shut down normally.
[14:01] <satellit_> I will do another install to HD to test this
[14:01] <manusheel> satellit_: Thanks a lot. I hope we'll have a fresh set of observations after running this test.
[14:02] <satellit_> is this a possibility?
[14:02] <satellit_> testing now
[14:04] <manusheel> satellit_: Yes, I think there is a possibility. Let us see after the test.
[14:05] <satellit_> ok
[14:33] <satellit_> manusheel: no way arround the reboot pop up.[1669.166145] end_request: I/O error, dev sr0, sector 769860    full screen of these.....: ( no change after 2 minutes)
[14:35] <satellit_> The pop-up has nothing else on screen behind it......
[14:35] <satellit_> power off only way out
[14:37] <satellit_> dropped to BusyBox shell:
[14:37] <satellit_> "exit" and it boots
[14:38] <satellit_> ? BUG!
[14:38] <manusheel> satellit_: Bug indeed.
[14:38] <satellit_> Ubuntu Bug?
[14:38] <manusheel> satellit_: Kindly report this at ubuntu sugar mailing list. I'll ask the developers to look at it.
[14:39] <satellit_> what is mailing list e-mail?
[14:41] <manusheel> satellit_: "Ubuntu SugarTeam" <ubuntu-sugarteam@lists.ubuntu.com>.  Could you please let me know the date version of the software.
[14:43] <satellit_> http://140.186.70.115/isos/USR-i386-20100804.iso
[14:43] <satellit_> 4 aug 2010
[14:45] <satellit_> Ubuntu Maverick (development)? but about Ubuntu  on desktop says 10.04 Lucid Lynx
[14:46] <manusheel> satellit_: Ok, this is one of the very recent ones. Yes, this is another minor bug you just reported.
[14:46] <manusheel> satellit_: The text entry
[14:46] <manusheel> has not been updated
[14:46] <satellit_> ok
[14:47] <manusheel> It seems. For Maverick USR. It is still using 10.04 Lucid Lynx. So, two bug reports. Let me send you the format for sharing issues at ubuntu sugar mailing list. That would help in easy communication with engineers.
[14:47] <dfarning> satellit_ can you send a note to the ML about the ISO reporting the incorrect version number?  I forgot to update that:(
[14:48] <satellit_> ok
[14:48] <dfarning> satellit_ we need to assign the responsibility to someone more reliable then me:)
[14:49] <satellit_> I think what you have here is great....
[14:53] <satellit_> in CDROM/casper have filesystem.manifest and filesystem.manifest-desktop both have sugar entities is this supposed to be this way?
[14:54] <dfarning> satellit_ We are still looking for a build system maintainer to figure stuff like that out:(
[14:55] <satellit_> I am a nubie sorry just looking.....: )
[14:55] <dfarning> satellit_you are welcome to it:)
[15:14] <manusheel> kandarpk: Hi Kandarp.
[15:14] <manusheel> Around?
[15:22] <kandarpk> manusheel sir: hello sir.
[15:22] <kandarpk> dfarning: Good morning
[15:23] <satellit_> defarning: does the boot command "linux0' work in ubuntu? will it bypass shell. (It works in fedora when boot info is not correct)
[15:25] <manusheel> kandarpk: David has uploaded the source at git for exelearning.
[15:25] <kandarpk> manusheel sir: Ok.
[15:27]  * lfaraone is back.
[15:27] <lfaraone> apologies for the delays.
[15:28] <manusheel> lfaraone: Hi Luke.
[15:28] <kandarpk> hi lfaraone.
[15:29] <kandarpk> manusheel sir: the package will work for ubuntu as it is.
[15:29] <manusheel> kandarpk: Ok, great. For Debian?
[15:29] <kandarpk> manusheel sir: 2 files are required to be changed
[15:30] <kandarpk> manusheel sir: I was thinking of creating a separate branch for debian
[15:30] <kandarpk> manusheel sir: how do I do that ?
[15:32] <manusheel> kandarpk: There are good ways of doing it.
[15:33] <manusheel> Let me send you the git casts.
[15:33] <manusheel> kandarpk: Would like you to watch git videos and arrive at a method.
[15:34] <kandarpk> manusheel sir: text/tutorial will be preferred.
[15:37] <kandarpk> dfarning: can you run sugar ? you appear offline in my group view.
[15:38] <manusheel> kandarpk: watch http://140.186.70.115/gitcasts/
[15:38] <manusheel> kandarpk: you'll have to google search the problem if you need text/tutorial
[15:41] <lfaraone> kandarpk: do you have a moment? sugar-log-activity installs a duplicate COPYING file in "usr/share/sugar/activities/Log.activity/COPYING". Could you add the proper rule to remove it?
[15:42] <lfaraone> Other than that, log is ready.
[15:42] <kandarpk> lfaraone: I'll do it in 10min.
[15:43] <dfarning> kandarpk, I just started sugar on maverick and made you a friend.
[15:43] <lfaraone> kandarpk: awesome, thanks.
[15:44] <kandarpk> dfarning: great.
[15:45] <dfarning> kandarpk, I now see you in friend view.  I am running Sugar as a emulator on maverick if that make any difference.
[15:46] <kandarpk> dfarning: I did the same yesterday but you dont appear online
[15:47] <dfarning> I think there is a problem with the jabber server.... but that is an issue for another day.
[15:48] <satellit_> dfarning: I am up on HD maverick 804 on jabber working fine
[15:48] <kandarpk> dfarning: hmmm, I thought it was working fine, can see 7 people in my neighburhood view.
[15:48] <dfarning> satellit_didn't you reboot the jabber server yesterday?
[15:49] <lfaraone> kandarpk: btw, pull in my changes first :)
[15:49] <satellit_> see  David farning and kandarp Avitars on f1 neighborhood
[15:50] <satellit_> yes rebooted jabber yesterday now very fast
[15:50] <dfarning> kandarpk, it is currently working but it needs to be rebooted every once in a while.
[15:50] <kandarpk> lfaraone: I'll need to clone it, didn't package it.
[15:50] <kandarpk> dfarning: ok, by the way satellit_ is there in my neighbourhood view
[15:51] <kandarpk> lfaraone: when we make branches, do we add all the files that are already present in some other branch or just add files which are different ?
[15:53] <lfaraone> kandarpk: well, when you branch off master, the new branch should contain the contents of master.
[15:54] <kandarpk> lfaraone: Ok. and if we add files to it, they will be specific to that branch ?
[15:56] <satellitUSR-d206> works
[15:56] <lfaraone> kandarpk: well, your commits are only reflected in that branch
[15:56] <lfaraone> kandarpk: until you merge them, that is.
[15:57] <satellit_> USR 804 has no activities except for read which does not start
[15:58] <satellit_afk> backlater
[15:58] <kandarpk> lfaraone: Ok.
[16:15] <lfaraone> Poll has been uploaded.
[16:18] <manusheel> lfaraone: neat.
[16:26] <manusheel> kandarpk:
[16:26] <manusheel> Sending you the login details of dev@seeta.in
[16:26] <manusheel> Please use that
[16:27] <manusheel> for submitting patches at sugar-devel today.
[16:27] <manusheel> kandarpk: sugar-devel@lists.sugarlabs.org
[16:27] <manusheel> this is the e-mail
[16:28] <kandarpk> manusheel sir: sir, the two sources of presence service are very different
[16:31] <lfaraone> manusheel: is neeraj going to be around today?
[16:34] <alsroot> manusheel: pong
[16:34] <manusheel> lfaraone: yes.
[16:34] <manusheel> alsroot: Hi Aleksey.
[16:35] <alsroot> manusheel: Hi
[16:37] <kandarpk> manusheel sir: what should I do ?
[16:38] <manusheel> kandarpk: This is regarding?
[16:38] <kandarpk> manusheel sir: the source obtained from the tarball is very different, it has collabora in copyright as well
[16:38] <kandarpk> manusheel sir: the presence service package
[16:40] <manusheel> kandarpk: Ok, can you send an e-mail on it at list serv.
[16:40] <manusheel> kandarpk: We need answer on it at the earliest.
[16:40] <manusheel> alsroot: How have you been?
[16:43] <manusheel> alsroot: One of the missing pieces that the S.88 on F11 team is facing is the ability for a.sl.o to output results in a 'microformat'.  They have rewritten the updater code but still need to modify a.sl.o to output both xml and 'microformat'.
[16:43] <kandarpk> manusheel sir, dfarning : please see http://paste.ubuntu.com/476001/  and http://paste.ubuntu.com/476003/
[16:44] <manusheel> alsroot: Can you share pointers on how we can proceed on it?
[16:48] <alsroot> manusheel: you can take http://git.sugarlabs.org/projects/slo-activities/repos/mainline/blobs/master/site/app/webroot/services/update-aslo.php(to test it, try http://activities.sugarlabs.org/services/update-aslo.php?id=usbcreator&appVersion=0.86) as an example to create microformat updater
[16:49] <alsroot> manusheel: but keep in mind, current ASLO is inherited from old AMO and PHP based, new one will be django based
[16:49] <manusheel> kandarpk: Ok.
[16:50] <manusheel> alsroot: When are we shifting to Django?
[16:50] <alsroot> manusheel: when if found a doer for that :) (ASLO will be a part of 0sugar, and I will tweak it anyway, but it is not in my first-time plans)
[17:12] <kandarpk> manusheel sir: location of tarball :
[17:12] <kandarpk> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-presence-service/
[17:16] <manusheel> kandarpk: Thank you.
[17:19] <dfarning> kandarpk, what are you you looking for?  For information on presence service please ask tomeu in #sugar he is the expert.
[17:20] <kandarpk> dfarning: the source code of presence service is different
[17:20] <kandarpk> under sugar-jhbuild and the one in the tarball
[17:21] <dfarning> kandarpk, sugar-jhbuild is the current 'head' of development and the tarball will be snapshot from the day it was released.
[17:21] <dfarning> kandarpk, what are you working on?
[17:21] <kandarpk> dfarning: but the tarball looks more upto date
[17:22] <kandarpk> dfarning: please see http://paste.ubuntu.com/476001/  and http://paste.ubuntu.com/476003/
[17:22] <lfaraone> dfarning: re https://bugs.launchpad.net/ubuntu/+source/sugar-0.88/+bug/614388 , do we want sugar-emulator to start fullscreen? isn't fullscreen sugar what the GDM / KDM session is for?
[17:22] <manusheel> dfarning: Kandarp will be writing a request for review for docstrings for Sugar API documentation.
[17:23] <kandarpk> dfarning: first link is the file obtained from the tarball
[17:23] <manusheel> dfarning: Kandarp is working on the first request to be submitted at sugar-devel.
[17:23] <manusheel> list serv.
[17:24] <dfarning> kandarpk, please ask tomeu on Sugar what is happening. I thought that jhbuild was alway the most recent code.
[17:24] <ankur> hi dfarning :)
[17:24] <manusheel> kandarpk: Yes.
[17:25] <manusheel> kandarpk: If tomeu is not around, use the login e-mail provided to you. Send an e-mail at sugar-devel explaining what you are trying to do, and feedback if possible.
[17:26] <dfarning> lfaraone, sugar in a tiny window is pretty unusable.  Sugar in a full screen emulator is pretty handy.
[17:27] <dfarning> ankur, hello
[17:27] <ankur> I was getting confused somewhat,
[17:27] <ankur> can you help me right now?
[17:28] <lfaraone> dfarning: okay. this sounds like something to A) push upstream, B) push into Debian.
[17:28] <ankur> hi lfaraone :)
[17:28] <dfarning> lfaraone, especially since we have no window decorators to change from full screen to windowed.
[17:28] <lfaraone> dfarning: to get in B), it should be a properly documented patch.
[17:28] <dfarning> lfaraone,   +1 this should go into debian.
[17:28] <dfarning> ankur, sure
[17:29] <ankur> dfarning,  when we say debugging should be available by default
[17:29] <ankur> what exactly do we mean?
[17:30] <lfaraone> kandarpk: also, please specify in debian/gbp.conf of sugar-speak-activity that your tarballs are bz2 compressed, otherwise pristine-tar doens't find them.
[17:32] <kandarpk> lfaraone: Sure.
[17:32] <dfarning> ankur,  in .sugar/debug there are some setting to turn debugging on and off.
[17:33] <ankur> yes
[17:33] <ankur> i saw that
[17:33] <ankur> i just have to uncomment that?
[17:33] <lfaraone> dfarning: isn't there a reason that's off by default?
[17:33] <dfarning> ankur, in beta releases it is traditional to turn all debugging on becuase most users are developers anyway.
[17:34] <lfaraone> dfarning: so we'll need to reupload when we're released, I expect.
[17:34] <dfarning> lfaraone, yes.  We will turn them back off just before the maverick release.
[17:34] <dfarning> ankur, yes that is all you have to do.
[17:35] <dfarning> lfaraone, this one seems like it might be ubuntu specific.  I guess we don't to fill user's logs in debian,
[17:36] <lfaraone> dfarning: fair enough. https://wiki.ubuntu.com/Apport/DeveloperHowTo might be useful to automagically collect such information when using ubuntu-bug :)
[17:36] <dfarning> lfaraone, yes I also filed that request with manu.... I am not sure who he assigned it to yet.
[17:37] <lfaraone> dfarning: ideally, so we can avoid the second upload, we can say "if apport is enabled, then enable logging"
[17:37] <dfarning> lfaraone, I would a) like to add hooks to arport and b) add a report a bug button on the frame.
[17:38] <dfarning> lfaraone, I don't know how to do that?
[17:38] <lfaraone> dfarning: this has the benefit of automatically turning off when apport is off (which happens as we near RC status), and will work in Debian too. (since apport techically could be used in debian)
[17:38] <dfarning> lfaraone, can you show ankur how to set that up?
[17:38] <lfaraone> dfarning: .sugar/debug is a shell script, so I think you can just test for it.
[17:39] <ankur> dfarning, was on phn
[17:39] <ankur> just a min
[17:40] <dfarning> lfaraone, yes, sugar debug runs as startup time to set the variable.
[17:41] <lfaraone> dfarning: right. so, apport runs as a service. we can use `status` to test if apport is running
[17:42] <dfarning> lfaraone, that makes sense.
[17:43] <manusheel> neeraj: Hi Neeraj.
[17:43] <lfaraone> dfarning: I'm just not sure how to do tht other than using a string test.
[17:44] <dfarning> ankur, are you following this:)
[17:44] <neeraj_> manusheel, hi sir
[17:44] <ankur> dfarning,  reading , got a call , sry :(
[17:44] <dfarning> ankur, luke's suggestion is harder but more correct.
[17:44] <dfarning> ankur, np
[17:46] <ankur> dfarning,  read it and adding apport button /automatic bug report was assgined to me :)
[17:46] <lfaraone> ankur: I've been talking about the implementation details with micahg in #ubuntu-motu.
[17:46] <ankur> one thing
[17:47] <dfarning> ankur, well then you are all set.  apport is a debugging tool which is available in Ubuntu and Debian to help users create high quality bug reports.
[17:47] <ankur> i wante d to confim that report a bug will launch apport to file the bug?
[17:47] <ankur> i mean "report a bug" button in frame
[17:48] <dfarning> ankur, +1 it will use all apport to collect all of the necessary date, automatically create a bug report, and upload it to launchpad.
[17:48] <ankur> dfarning,  okay. well , i went thorugh the frame code and grasped some of it :) . Some pointers will help here to proceed and make task look more simpler :)
[17:48] <kandarpk> lfaraone: I tried to update read activity and pushed that at http://git.debian.org/?p=collab-maint/temp-read-activity.git;a=summary
[17:49] <ankur> i jsut wanted to confirm though , (acc. to human interface guidlines) the button will be added in bottom panel?
[17:49] <kandarpk> lfaraone: please see if the steps were ok.
[17:50] <lfaraone> kandarpk: I don't see anything there that is newer than 9 days ago...
[17:50] <dfarning> ankur, now lfaraone is looking a how to add a test to ./sugar/debug to 'test' in apport is on.  If apport on then create logs -- if apport off do not create log.
[17:50] <kandarpk> lfaraone: yeah, you were busy so I didn't ask earlier
[17:51] <lfaraone> kandarpk: is there a reason you didn't just push up to the normal repository?
[17:51] <dfarning> ankur, yes I think the bottom panel will be fine.
[17:52] <kandarpk> lfaraone: that is maintained by Jonas, and I made a lot of changes in some files ( commit messages will tell )
[17:52] <kandarpk> so I thought it will be better if you could verify the steps
[17:52] <ankur> dfarning,  one more thing , our patches will be included in next upstream release?
[17:52] <ankur> or we will carry them forward?
[17:53] <kandarpk> dfarning, manusheel sir: tomeu says one of the files I looked at is under sugar-toolkit.
[17:54] <kandarpk> and I am confused.
[17:55] <dfarning> ankur, I don't understand apport well enough to be much help.  I would start by looking at https://wiki.ubuntu.com/Apport and all of the pages to which it links.
[17:56] <lfaraone> kandarpk: few things: A) you renamed the package to sugar-read-activity, it was called sugar-read-activity-0.86 before.
[17:56] <kandarpk> lfaraone: that was for testing on all versions, will correct that to -0.86.
[17:56] <dfarning> ankur, then I would look for an example of a package in ubutu which uses the apport hook and start by copying what they did:)
[17:57] <lfaraone> kandarpk: B) for some reason you didn't properly apply the new version, when I build I get a giant diff.
[17:57] <ankur> dfarning,  okay :)
[17:57] <lfaraone> kandarpk: C) you added rules to recreate the upstream tarball. There is already handling for this in rules' upstream-tarball include.
[17:58] <lfaraone> kandarpk: D) you should ask Sayamindu to release a 87 tarball on download.sl.o
[17:59] <lfaraone> kandarpk: make snese?
[17:59] <kandarpk> lfaraone: a doubt in C
[17:59] <dfarning> ankur, and yes pushing upstream is my biggest concern.  We need to push as much upstream as possiable.
[18:00] <kandarpk> lfaraone: does the upstream-tarball include rule create a tarball if it doesn't fine it upstream
[18:00] <lfaraone> kandarpk: dimmi.
[18:00] <kandarpk> *s/fine/find/
[18:00] <lfaraone> kandarpk: no. the solution for that problem is to tell upstream nicely that they really should create a tarball.
[18:00] <lfaraone> kandarpk: ideally we'd only use the custom build-your-own tarball with unresponsive or uncooperative upstreams.
[18:01] <kandarpk> lfaraone: I did mail Syaamindu.
[18:01] <dfarning> ankur, every delta, or difference between Ubuntu, Debian, and Sugar Labs code is something we will need to maintain forever.  ie deal with at every release update.
[18:01] <kandarpk> on 23rd July.
[18:01] <kandarpk> lfaraone ^^
[18:02] <ankur> that means the thing which are ubuntu-specific are for ever?
[18:02] <lfaraone> kandarpk: has he said anything?
[18:02] <kandarpk> lfaraone: I'll need to confirm his email-id I think.
[18:02] <kandarpk> No reply
[18:02] <dfarning> ankur, in order to keep our maintenance burden as low as possiable we want to push as much upstream as possiable.
[18:02] <lfaraone> kandarpk: okay, hold off on read for now unless we *need* to upgrade.
[18:02] <ankur> dfarning,  okay :)
[18:03] <kandarpk> lfaraone: sure, was practicing updating a package if tarball wasn't there.
[18:03] <ankur> lfaraone,  i used sugar apt-get source etoys to get source of etoys
[18:04] <lfaraone> ankur: okay
[18:04] <ankur> then i was not able to look up from where i should look
[18:04] <ankur> for the section in which etoys come
[18:04] <lfaraone> ankur: well, we've established etoys is in non-free, right?
[18:05] <dfarning> ankur, and yes, we will be maintain some ubuntu specific stuff as patches.... forever.  But, If we keep the number and size of the patches to a minimum it can be done effectively.
[18:05] <ankur> lfaraone,  yes
[18:05] <ankur> i concluded that from the discussions we had on mailing list
[18:05] <ankur> dfarning,  sure :)
[18:06] <lfaraone> ankur: right, so to figure out how the package said it was in non-free, grepping debian/ for "non-free" would seem like a sensible way to find the right location, no?
[18:07] <ankur> yes, but i was not able to find d debian/ , and grep thing didn't struck my mind :) thanks
[18:09] <ankur> lfaraone,  done :)
[18:09] <lfaraone> ankur: cool, did you find the right spot?
[18:09] <ankur> it is non-free/games . now after i update etoys-activity can you review it again if it needs any more changes.?
[18:09] <ankur> yes lfaraone  i was jut not looking at right place :)
[18:10] <ankur> i will mark it for r? okay?
[18:10] <kandarpk> lfaraone: how do I specify the compression type in gbp.conf ?
[18:11] <ankur> lfaraone,  if there is some problem in make file of an activity , can that be cause of an activity not running? if the package has built successfully? where does in intallation to execution of activity, does make file roles come in?
[18:12] <lfaraone> ankur: cool, sure. your package will be in contrib, btw. (contrib/x11)
[18:12] <lfaraone> ankur: probably not, although the make file mgiht not have installed everythign in the right place.
[18:13] <kandarpk> dfarning, manusheel sir: what is sugar-toolkit ?
[18:13] <ankur> okay , did you receive a mail of Gonzalo in ubuntu -sugarteam mailing list as well?
[18:13] <ankur> my paint activity was not starting  , so he suggested some changes.
[18:14] <lfaraone> ankur: I didn't read it, but I remember a subject line like that.
[18:14] <ankur> now i was having a slight problem to replace what with what as it was a diff file and i have not worked much on diff files
[18:14] <lfaraone> kandarpk: see sugar's gbp.conf file. http://git.debian.org/?p=collab-maint/sugar.git;a=blob;f=debian/gbp.conf;
[18:14] <ankur> he suggested some changes in makefile
[18:16] <dfarning> kandarpk, see http://wiki.sugarlabs.org/go/Development_Team/Sugar_Architectual_Diagram
[18:17] <kandarpk> dfarning: Ok.
[18:17] <ankur> lfaraone,  this might help :) https://wiki.ubuntu.com/MeetingLogs/devweek0909/ApportPkgHooks
[18:18] <kandarpk> dfarning: is the code under sugar-jhbuild/install/lib/python2.6/site-packages/sugar/presence that of the sugar-toolkit module ?
[18:18] <kandarpk> that is what I think tomeu told.
[18:20] <lfaraone> ankur: re debug, you want to do an if "status dbus | grep -q start/running"
[18:20] <lfaraone> ankur: re debug, you want to do an if "LANG=C status dbus | grep -q start/running" *
[18:20] <dfarning> kandarpk, you would have to look (grep) under sugar-jhbuild/source/ to find which module the file(s) is in.
[18:22]  * lfaraone will brb.
[18:32] <ankur> dfarning, i will study about apport and get back to you , though might not today.............
[18:32] <dfarning> ankur, thanks it will take time.
[18:33] <ankur> dfarning,  :) bye
[18:33] <dfarning> ankur, bye
[18:47] <manusheel> kandarpk: Hi Kandarp.
[18:48] <kandarpk> manusheel sir: hello sir.
[18:48] <manusheel> kandarpk: Any help required on sugar toolkit? Saw your message.
[18:49] <kandarpk> manusheel sir: the module under sugar-jhbuild/install/lib/python2.6/site-packages/sugar/presence is that of sugar-toolkit
[18:50] <kandarpk> manusheel sir: the presence service code is present under /media/66300b7d-928f-48f9-a8ed-42508443b91b/home/kandarp/sugar-jhbuild/sugar-jhbuild/source/sugar-presence-service/src
[18:51] <manusheel> kandarpk: Ok.
[18:52] <manusheel> kandarpk: How does it affect the API documentation?
[18:52] <kandarpk> manusheel sir: the documentation is using sugar-toolkit source
[18:53] <kandarpk> the one made using epydocs too is using sugar-toolkit
[18:54] <manusheel> kandarpk: Ok.
[18:54] <manusheel> kandarpk: Any issues on this front?
[18:55] <kandarpk> manusheel sir: no issues if we are documenting the presence module( the sugar-toolkit one) and not sugar-presence-service
[18:55] <manusheel> kandarpk: What are the issues with sugar-presence-service?
[18:56] <kandarpk> manusheel sir: it is present in a different directory and our script isn't written to read that
[18:57] <manusheel> kandarpk: Ok, can we make our script to read that?
[18:57] <manusheel> kandarpk: Is there some other workaround for it?
[18:57] <kandarpk> manusheel sir: yes sir, that will be easy.
[18:57] <kandarpk> manusheel sir: we'll just need to copy the sugar-presence-service/src folder to our working directory
[18:59] <kandarpk> manusheel sir: we might be making the same mistake with other modules as well.
[19:01] <kandarpk> manusheel sir: datastore.py too are two different files
[19:10] <manusheel> kandarpk: Ok. I see.
[19:11] <kandarpk> manusheel sir: we need to understand what does the files under site-packages/sugar/  represent.
[19:21] <manusheel> kandarpk: Yes, Kandarp.
[19:21] <manusheel> Absolutely.
[19:21] <manusheel> kandarpk: We can ask about this at #sugar channel.
[19:22] <kandarpk> manusheel sir: how should I put this forward ?
[19:22] <kandarpk> I am confused myself
[19:26] <manusheel> kandarpk: You can
[19:26] <manusheel> ask it like this -
[19:26] <manusheel> "
[19:28] <manusheel> kandarpk: You can put it like this - "Wish to arrive at an understanding on the files under site-packages/sugar. Any pointers, appreciated."
[19:29] <kandarpk> manusheel sir: Ok.
[19:37]  * lfaraone is back
[19:46] <neeraj> lfaraone, Hi :)
[19:48] <neeraj> I have updated http://wiki.debian.org/Sugar/tasks. Also, I think we don't need lintian override as we discussed before. I am not getting that warning. I think you got that warning because previously there was a typo in Depends field.
[19:49] <neeraj> I used debian for running lintian command.
[19:51] <lfaraone> ✄
[19:56] <manusheel> lfaraone, neeraj: Are we at a consensus on this part?
[19:57] <lfaraone> neeraj: which override
[19:57] <neeraj> lfaraone, lintian override for warning http://irclogs.ubuntu.com/2010/07/30/%23ubuntu-sugarteam.html#t19:08
[19:58] <neeraj> *in sugar-record-activity
[19:58] <lfaraone> neeraj: I do not see that problem presenting itself, no.
[20:04] <neeraj> lfaraone, Ok. So you are not getting that warning now.. right?
[20:04] <lfaraone> I'm testing as much.
[20:07] <dfarning> kandarpk, did you figure out you question?
[20:07] <dfarning> with tomeu?
[20:07] <kandarpk> dfarning: yes.
[20:08] <kandarpk> dfarning: we need to start with basic code which we understand well.
[20:08] <dfarning> kandarpk, was it about how the various modules fit together?
[20:08] <dfarning> kandarpk, +1
[20:09] <kandarpk> dfarning: yes, trying to figure out how the code affects the UI.
[20:11] <lfaraone> neeraj: btw, what we've been referring to as the "other-X11" license should probably be called the Expat license. I'll make that change right now.
[20:12] <dfarning> neeraj, can you edit the debian wiki?
[20:12] <neeraj> lfaraone, ok.
[20:12] <neeraj> dfarning, task one?
[20:12] <dfarning> neeraj I can't log in
[20:12] <dfarning> neeraj yes
[20:12] <neeraj> Ok. what I have to edit?
[20:16] <dfarning> I was wondering if you could add some columes to the table to keep track of where the packages are in the flow to Marerick.
[20:17] <dfarning> neeraj, ie have they bee accepted in to unstable and have they been accepted into maverick.
[20:23] <neeraj> dfarning, I think some packages which were completed have been removed from task wiki. How we will  track them? Also, one extra column will be sufficient?
[20:26] <dfarning> neeraj can you add the completed packages back to the table?  How ever you chose to represent the data is fine.
[20:27] <kandarpk> lfaraone: I've updated s-speak-a and s-log-a. Please review them when you get time.
[20:27] <manusheel> kandarpk: Did we put an r?
[20:29] <lfaraone> kandarpk: sure.
[20:30] <kandarpk> manusheel sir: just did that
[20:30] <lfaraone> dfarning: why do we  need to manually maintain a table when we already  have multidistrotools?
[20:30] <lfaraone> dfarning: qa.ubuntuwire.org/multidistrotools/sugar.html
[20:31] <kandarpk> Ok thanks everyone, good night
[20:32] <dfarning> lfaraone, I would like to make sure we have a single place where we can see what is getting stuck and a place to note about what needs to be done to more it forward.
[20:34] <lfaraone> dfarning: okay, so it seems you'd like something like what we have with MDT but with comments?
[20:36] <dfarning> lfaraone, yes.  Once the package flow is ingrained and the number of package in the pipeline is back down to a more normal level we can use MDT.
[21:39] <neeraj> lfaraone,Acco to wiki, while patching, we update the changelog file also. But currently we are working on multiple issues related to  "sugar-0.88". So, suppose I create a debdiff file and update the version number.
[21:40] <lfaraone> neeraj: I'm not sure what you meant by the second part of the last sentense.
[21:40] <lfaraone> *sentce
[21:40] <lfaraone> *sentence
[21:41] <neeraj> Now if other team members have a patch for some other bug in sugar-0.88 and my patch is still in progress (not released) then what changes they should make in changelog.
[21:43] <neeraj> I mean suppose latest name in changelog file is <name-version>2ubuntu1, In my debdiff I will rename it to 2ubuntu1. Now if dipankar wants to add debdiff for another bug
[21:44] <neeraj> what he should do to avoid conflict. I hope you get my question.
[21:45] <neeraj> *rename it to 2ubuntu*2*
[22:51] <neeraj> lfaraone, I think I have got my answer by going through this link  http://en.wikipedia.org/wiki/Concurrent_Versions_System#Features Second paragraph says we will need to change our old debdiff if someones else patch accepted first.
[22:55] <manusheel> neeraj: Neat.