[03:26]  * lfaraone waves.
[03:37] <neeraj> hi lfaraone
[03:37] <neeraj> I have pushed the changes for record activity
[03:38] <neeraj> for write activity I have to create new repository on collab-main.. right?
[03:42] <lfaraone> neeraj: unless there's one already, es.
[12:52] <dfarning> good morning Manusheel
[12:52] <Manusheel> dfarning: Good morning David.
[12:52] <Manusheel> How was your flight?
[12:53] <Manusheel> dfarning: Hope you had a comfortable journey.
[12:53] <dfarning> Manusheel, I am spending an additional day traveling.... I forgot to get a visa.  So I need to stop at the embassy this morning:(
[12:54] <dfarning> opps.
[12:54] <Manusheel> dfarning: That is unfortunate. Hope you get Visa on time.
[12:54] <Manusheel> dfarning: What type of Visa are you traveling on to PY?
[12:55] <dfarning> Manusheel, yes, it is just a matter of stopping in an getting a signature.
[12:55] <Manusheel> dfarning: Glad to hear.
[12:56] <Manusheel> dfarning: Wish to inform you that the new developers have started picking up speed.
[12:56] <dfarning> Manusheel, I think there is just one type.  If you pay your $40 dollars you get a stamp in you passport.
[12:57] <Manusheel> dfarning: Ok. That is interesting. Getting PY visa seems simple.
[13:00] <dfarning> Manusheel,  I just read Ishan's report.
[13:00] <Manusheel> dfarning: Great. Please let me know your feedback on it.
[13:02] <dfarning> Manusheel, seems the core concepts were understood.
[13:03] <Manusheel> dfarning: Yes. I wish to get the developers started on understanding the code in a day or two. Also, we would need a couple of simple assignments to understand the collaboration aspect from a code perspective.
[13:04] <Manusheel> dfarning: Looking forward to your memo on collaboration and network management.
[13:05] <dfarning> Manusheel, after reviewing the resources.  The next step seems to be working through the code in the presence service.
[13:06] <Manusheel> dfarning: Yes. We need to define the steps for the same. On the same note, Kandarp will be packaging presence service package today.
[13:07] <dfarning> Manusheel, all other resources are very vague or incomplete.
[13:08] <Manusheel> dfarning: Can you send me a memo on all such incomplete areas and resources. I'll ask Morgan and Robert McQueen to help us arrive at a fine aggregation on them. We'll also have one of our team members document the resources with their help. In any case, we'll be touching base with them on Sugar API documentation for adding description on sugar.presence classes and variables.
[13:09] <dfarning> Manusheel, at this point I would start going through the code path Sugar uses to establish a telepathy connection.
[13:11] <Manusheel> dfarning: Sure. That is a good starting point for us. Will communicate it with the team.
[13:11] <Manusheel> dfarning:  Can you please register Ishan's ssh public key at Launchpad?
[13:11] <dfarning> In terms of what is missing.... I think the next most useful learning tool would be a would be a code walk through on how telepathy connections are established.
[13:12] <Manusheel> He will be working on packaging at launchpad today.
[13:12] <Manusheel> dfarning: Absolutely. We'll first hack through the how the telepathy connections are established at our end. Develop a workflow document, and ask Tomeu to audit this for us.
[13:13] <Manusheel> dfarning: Using this technique, we'll have a very good understanding of things, and also well defined idea on what we know, and what is vague/missing.
[13:15] <dfarning> Manusheel, yes I think a lot of collaboration errors can be track to the connection setup process.
[13:15] <Manusheel> dfarning: Yes, absolutely.
[13:16] <Manusheel> dfarning: This is indeed a very important starting step for us.
[13:17] <dfarning> Manusheel, wrt Ishan's ssh key. if he goes to his user page on launchpad.net there are links to register his gpg and ssh keys.
[13:18] <Manusheel> dfarning: Ok. I thought it required your approval. It is administered system.
[13:19] <Manusheel> dfarning: Will be back in 10 minutes.
[13:25] <dfarning> Manusheel, you mentioned that you were looking for Ideas for learning objects.... Are you looking for Ideas for useful demos objects that demonstrate educonn.js or something else?
[13:32] <Manusheel> dfarning: I am looking at more use case scenarios for demonstrating educonn.js.
[13:33] <Manusheel> dfarning: The two use case scenarios that you e-mailed me - multiplication drill and puzzles will be completed with testing by this week.
[13:33] <Manusheel> Wish to create a roadmap and design for more use case scenarios for the learning objects.
[13:35] <dfarning> ok, they just called my flight.  I try to come up with demo objects.
[13:37] <Manusheel> dfarning: Thank you.
[13:37] <Manusheel> Talk to you soon. Have a safe flight.
[13:38] <dfarning> Over the last couple of weeks, I have been help my second grade niece with phonics and sound recognition.  It would be really cool:).... but it would be rather audio intensive:(
[13:38] <dfarning> bye
[13:38] <dfarning> bye
[14:54] <Manusheel> kandarpk:
[14:54] <Manusheel> Hi Kandarp.
[14:54] <Manusheel> Around?
[14:55] <kandarpk> Manusheel sir: yes sir
[14:55] <Manusheel> kandarpk: We should start going through the code path Sugar uses to establish a telepathy connection, in reference to David's latest e-mail.
[14:56] <Manusheel> We'll first hack through the how the telepathy connections are established at our end. Develop a workflow document, and ask Tomeu to audit this for us.
[14:56] <Manusheel> how the*
[14:57] <Manusheel> kandarpk: A code walk through on how telepathy connections are established will be most useful at this juncture.
[14:57] <kandarpk> Manusheel sir: Ok, sure.
[14:57] <kandarpk> that will be very interesting
[14:57] <Manusheel> kandarpk: Yes, indeed.  Lot of collaboration errors can be track using the connection setup process.
[14:58] <Manusheel> kandarpk: Let us divide our time on 3 tasks today - presence service and sugar packaging; code walk through and inserting doc strings in Sugar API docs.
[14:59] <kandarpk> Manusheel sir: how do I access the code ?
[14:59] <kandarpk> ssh seeta@140.186.70.115
[14:59] <kandarpk> Manusheel sir: using ^^ ?
[14:59] <Manusheel> kandarpk: Please try this.
[15:00] <Manusheel> Let me know if it is working.
[15:00] <Manusheel> kandarpk: Will ask Bernie for help if this does not work.
[15:00] <kandarpk> Ok.
[15:01] <kandarpk> Manusheel sir: Permission denied (publickey).
[15:01] <Manusheel> kandarpk: We might be incorrect on our steps too. In that case, please drop me an e-mail.
[15:01] <Manusheel> I'll be back in an hour or so. Attending a meeting with content developers.
[15:02] <kandarpk> Manusheel sir: Ok
[15:02] <lfaraone> morning.
[15:02] <Manusheel> lfaraone: Good morning.
[15:03] <kandarpk> lfaraone: Good morning :)
[15:03] <Manusheel> lfaraone: Will you be able on Skype sometime today?
[15:04] <lfaraone> Manusheel: If you want. Personally, I prefer IRC, since it's low bandwidth and not dependent on synchronous communication.
[15:05] <Manusheel> lfaraone: Ok, sure. We'll talk on IRC. Will touch base with you soon.
[15:05] <Manusheel> Going for a meeting. Will be back.
[15:06] <Manusheel> kandarpk: Let us start with packaging first.
[15:06] <kandarpk> Manusheel sir: Ok.
[15:06] <kandarpk> *switching to debian.
[15:06] <Manusheel> lfaraone: Dipankar has been ill, and is under medication. Wish to inform you that he'll unavailable today.
[15:07] <Manusheel> kandarpk: Sure.
[15:07] <Manusheel> Please ask
[15:07] <lfaraone> Manusheel: okay. hope he feels btter.
[15:07] <Manusheel> questions if required.
[15:07] <Manusheel> lfaraone: I hope too. I have asked him to take complete rest. He was terribly unwell last night.
[15:08] <Manusheel> lfaraone: Talk to you soon. Going for the meeting.
[15:12] <kandarpk> lfaraone: around ?
[15:13] <lfaraone> kandarpk: yes.
[15:15] <kandarpk> lfaraone: http://paste.ubuntu.com/466484/
[15:15] <kandarpk> I've followed these steps
[15:16] <kandarpk> lfaraone: now, if I change 0.88 to 0.90 and try to build the package
[15:16] <kandarpk> I get :
[15:16] <kandarpk>  fatal: Path 'sugar-0.90_0.89.1.orig.tar.bz2.delta' does not exist in 'refs/heads/pristine-tar'
[15:17] <lfaraone> kandarpk: before you imported you should have changed the package name.
[15:18] <kandarpk> lfaraone: damn !
[15:18] <kandarpk> lfaraone: the import command will remain the same ?
[15:18] <lfaraone> kandarpk: I believe so.
[15:19] <kandarpk> it has version number in it.
[15:19] <lfaraone> kandarpk: well, the tarball should start with "sugar-0.90"
[15:20] <kandarpk> lfaraone: I'll need to rename it first ?
[15:35]  * ishan is away
[15:41]  * ishan is back
[15:43] <kandarpk> lfaraone: Jonas updated the git repo for sugar 90 min ago.
[16:01] <lfaraone> kandarpk: ?
[16:01] <kandarpk> lfaraone: packaging of sugar isn't required now.
[16:02] <lfaraone> kandarpk: ah, right. like I said, he's got that handled :)
[16:02] <kandarpk> lfaraone: just "git clone+git-buildpackage --git-ignore-new" will build the .deb
[16:02] <kandarpk> lfaraone: yup, he works hard :)
[16:03] <kandarpk> lfaraone: I am late by just 1 day.
[16:03] <kandarpk> lfaraone: and these are two different commands ^^
[16:32] <lfaraone> neeraj: I'm looking at your commit history for record.
[16:33] <lfaraone> neeraj: In c3c72dd2f3cb3f6e916f5895f5a81c382901131c, you "Modified debian/changelog file" according to the git log. That commit doesn't tell me anything about the changes you actually made.
[16:33] <lfaraone> neeraj: and you don't need to commit when you just build the package, as you did in b2456ff1dd97a2a9a54cee6dd732f4aa9244b0d9
[16:34] <lfaraone> neeraj: you can see how this gets confusing, 3f0e6295750aace64174e81871d4ec16984bd673 and a65da631118b3d97dce420fb0eff203d6453b95d both are "correction  in debian/copyright file", but I still have no idea what changes were made unless I look at the diff itself.
[16:35] <lfaraone> neeraj: the commit message in teh git log should tell me what you actually did, not what you did it to. "Used © consistantly, included license text in copyright file" and 'Removed extra ""s from copyright' would have been better messages for those commits.
[16:55] <kandarpk> lfaraone: is sugar-presence-service present on git.sugarlabs.org ?
[17:00] <lfaraone> kandarpk: Probably.
[17:11] <lfaraone> neeraj: you omitted aleskey's copyright of "port/" in record ,afaict.
[17:12] <lfaraone> alsroot: what happened to sugar-port, anyway?
[17:13] <alsroot> lfaraone: it is part of polyol, partly recoded in Vala, partly as a part of polyol pythin binding -- but anyway it is not ready to use
[17:18] <lfaraone> alsroot: mk. it's in record, but it's marked obsolete on the wikie.
[17:20] <alsroot> lfaraone: yup it is obsolete, better to leave bundled-to-record sugar-port as is
[17:31] <lfaraone> kandarpk, ping.
[17:31] <kandarpk> lfaraone: yes
[17:32] <lfaraone> kandarpk: what do they have you working on right now?
[17:33] <kandarpk> lfaraone: had to understand packaging sugar and presence service
[17:33] <kandarpk> lfaraone: do you have anything else for me ?
[17:36] <lfaraone> kandarpk: did you have an idea about fixing jigsawpuzzle and sliderpuzzle in Lucid?
[17:37] <kandarpk> lfaraone: I haven't tried that, but can help if you think I may be able to
[17:37] <lfaraone> kandarpk: oops, nevermind, was confused.
[17:38] <kandarpk> lfaraone: np
[18:28] <kandarpk> lfaraone: around ?
[18:34] <lfaraone> kandarpk: yessir.
[18:35] <lfaraone> kandarpk: so far, all of the activities you've packaged and submitted have been approved. good job1
[18:35] <lfaraone> *!
[18:35] <kandarpk> lfaraone: can you please help me in finding upstream repo of presence service
[18:35] <kandarpk> lfaraone: thanks sir :)
[18:38] <lfaraone> kandarpk: well, you can find the download location easily. get the source of the current sugar-presence-service-0.88 package, and look in the debian/watch folder.
[18:39] <lfaraone> kandarpk: git repo, not suure
[18:40] <kandarpk> lfaraone: how can I update tags ?
[18:40] <lfaraone> kandarpk: what do you mean?
[18:40] <kandarpk> lfaraone: git repo is required for it, right ?
[18:40] <kandarpk> git fetch --tags upstream-repo
[18:42] <kandarpk> I understand that it is used to fetch the changes in upstream git into our repo.
[18:42] <kandarpk> lfaraone: plz correct me if I am wrong
[18:46] <lfaraone> kandarpk: yes.
[18:46] <manusheel> lfaraone: I think Kandarp is looking at the source of sugar presence service.
[18:46] <manusheel> Is it at git.sugarlabs.org?
[18:46] <manusheel> I think that is Kandarp's question.
[18:46] <lfaraone> manusheel: yes.
[18:46] <kandarpk> manusheel sir, lfaraone: the tarball is available
[18:46] <lfaraone> manusheel: probably, but i'm not sure where.
[18:47] <manusheel> lfaraone: Can we find this together now?
[18:47] <manusheel> We'll face the same issue for sugar-datastore too.
[18:47] <lfaraone> kandarpk: ask on the mailing list. Jonas will say "The answer is ANSWER. And by the way, I'd rather have you guys working on activities and not on core sugar for now, like I said eearlier. "
[18:48] <manusheel> lfaraone: Absolutely. But, we can work on sugar-datastore and sugar-presence, right?
[18:48] <lfaraone> manusheel: that's core, afaict.
[18:48] <manusheel> lfaraone: Ok, then lets do one thing now. We should sync the activities with Ubuntu downstream.
[18:49] <lfaraone> manusheel: okay, have the sync requests filed then.
[18:49] <manusheel> lfaraone and kandarpk: Let us take this assignment now. Sure, Luke.
[18:50] <manusheel> kandarpk: Let us start with an activity assigned to you. Which one did you find most simple and most difficult to package?
[18:50] <kandarpk> manusheel sir: steps followed were the same.
[18:51] <manusheel> kandarpk: Yes, but the number of issues faced were different, right?
[18:52] <kandarpk> manusheel sir: except for tagging the date, commit ID, there wasn't much difference.
[18:52] <manusheel> kandarpk: Ok, great. Which activity would you like to sync with Ubuntu downstream?
[18:52] <manusheel> Let us start with one of the activities now.
[18:53] <kandarpk> manusheel sir: memorize. because I love playing it :)
[18:53] <kandarpk> others might like it too
[18:54] <manusheel> kandarpk: Ok, great. Let us file the sync request for it now.
[18:54] <manusheel> kandarpk: Memorize is cool indeed :-)
[18:54] <manusheel> Was developed by Muriel in 2007.
[18:54] <manusheel> He used to sit next to me at One Cambridge Center back then :-)
[18:54] <kandarpk> Ok.
[18:55] <kandarpk> manusheel sir: Great.
[18:55] <manusheel> He returned to Brazil after 5-6 months in Cambridge.
[18:55] <lfaraone> manusheel: we can't really file a sync request unless the package was accepted into Debian, and we're waiting on Jonas to do that..
[18:56] <manusheel> lfaraone: Ok. In the meantime, what all other activities around packaging can our team concentrate upon?
[18:56] <manusheel> Pointers.
[18:57] <lfaraone> manusheel: well, since the apckage is already in ubuntu, you can upload a new version of the package into Ubuntu, but we might as well wait for it to be in Debian and sync it from there. Whichever you prefer.
[18:59] <manusheel> lfaraone: Syncing approach would be preferable. However, since we are not sure about how much time Jonas takes on approving our work, let us package in Ubuntu natively. kandarpk, are we aware about the steps for the same?
[18:59] <kandarpk> manusheel sir: No idea about it.
[19:00] <manusheel> lfaraone: Can you point Kandarp to resources on packaging in Ubuntu? He has been focused on Debian packaging right from the beginning.
[19:00] <manusheel> That would be a good assignment for our team too.
[19:01] <kandarpk> manusheel sir, lfaraone: and it will be a nice change for me
[19:01] <manusheel> kandarpk: Sure :-)
[19:03] <manusheel> lfaraone: Around?
[19:04] <lfaraone> manusheel: for a little while.
[19:05] <manusheel> lfaraone: Can you point us to a good resource on packaging Memorize in Ubuntu (without following the syncing approach from Debian)?
[19:07] <lfaraone> manusheel: well, the steps are straightforward:
[19:09] <lfaraone> Take existing packaging from Alioth. Copy over changelog from previous verison of package in Ubuntu. Add new changelog entry that has the same version as the one we are using right now in debian, with the "-1" replaced with "-0ubuntu1", and a change log entry of "New upstream version". Use "update-maintainer" to change the maintainer of the package from Debian OLPC. File a bug in launchpad "Please update FOO to VERSION.", attaching the diff.
[19:10] <manusheel> lfaraone: Neat. Thank you so much.
[19:12] <kandarpk> lfaraone: how is the diff tarball(?) generated ?
[19:12] <lfaraone> kandarpk: when you 'git-buildpackage -S' or 'debuild -S' (when not using git), it is created.
[19:12] <lfaraone> kandarpk: diff.gz is if you're not using 3.0 quilt, debian.tar.gz is when you are.
[19:12] <kandarpk> lfaraone: Oh yes. thanks
[19:12] <lfaraone> (IIRC)
[19:13] <kandarpk> lfaraone: so I should make all the changes and just run "debuild -S" ?
[19:13] <kandarpk> thats it ?
[19:14] <manusheel_> lfaraone: My apologies. The internet connection got disrupted at my place.
[19:14] <lfaraone> kandarpk: then upload the resulting diff / debian.tar.gz to a launchpad bug report.
[19:14] <manusheel_> lfaraone: Thank you for sharing the steps.
[19:15] <lfaraone> kandarpk: if you file the bug in Launchpad before doing the other steps, add "(LP: #BUGNUMBER)" so that the package management software automatically closes the bug when your package is sponsored.
[19:15] <lfaraone> kandarpk: * add ... to the changelog so that...
[19:15] <kandarpk> lfaraone: sure.
[19:16] <kandarpk> lfaraone: and the bug report is similar to the one we filed for debian ?
[19:17] <kandarpk> *looking for it at launchpad
[19:20] <lfaraone> kandarpk: let me get you an exmaple.
[19:23] <lfaraone> kandarpk: https://launchpad.net/bugs/358433 's one by ~morgs.
[19:24] <lfaraone> kandarpk: granted, that one didn't get sponsored, but he followd proceedure properly ;)
[19:24] <kandarpk> lfaraone: thanks.
[19:25]  * lfaraone is out. 
[19:25] <lfaraone> kandarpk: let me know if you have trouble, subscribe me to the result.
[19:25] <kandarpk> lfaraone: filing a report now.
[19:26] <kandarpk> lfaraone: oh, need to have a diff first !
[19:29] <kandarpk> manusheel_ sir: https://bugs.launchpad.net/ubuntu/+source/sugar-memorize-activity/+bug/512605
[19:30] <kandarpk> manusheel_ sir: David had requested for removal of memorize
[19:30] <manusheel_> kandarpk: Let me check.
[19:31] <manusheel_> kandarpk: Will have a word with David. Actually, the bug is a request from David to make sure someone picks up the maintainership :-)
[19:31] <manusheel_> It seems like that.
[19:31] <kandarpk> manusheel_ sir: Ok.
[19:31] <manusheel_> kandarpk: The activity needs maintainership. Will have a word with Sugar Labs oversight board about it.
[19:32] <manusheel_> kandarpk: Let us try read activity then.
[19:32] <manusheel_> Or, some other activity, in the meantime, whose steps we can get it reviewed by Luke now.
[19:33] <kandarpk> manusheel_ sir: read didn't work properly
[19:34] <kandarpk> manusheel_ sir: poll activity can be synced but it had a lessons option which didn't work.
[19:34] <manusheel_> kandarpk: Can we package an activity right now?
[19:34] <manusheel_> kandarpk: Can you send me a list on what all activities didn't work, and the issues that we faced.
[19:35] <manusheel_> kandarpk: I need to get these issues under dev asap.
[19:35] <kandarpk> manusheel_ sir: Ok.
[19:38] <manusheel_> kandarpk: Which activity can we package now?
[19:39] <kandarpk> manusheel_ sir: Poll is the best choice, if not memorize
[19:40] <manusheel_> kandarpk: Ok.
[19:40] <manusheel_> Let us go ahead with it now.
[19:41] <kandarpk> manusheel_ sir: Ok :(
[19:44] <manusheel_> kandarpk: interesting remark - :-(
[19:45] <manusheel_> what happened?
[19:45] <manusheel_> Are you finding things challenging?
[19:46] <kandarpk> manusheel_ sir: It will get a bit late.
[19:47] <kandarpk> manusheel_ sir: anyways, where do I look for the package for ubuntu ?
[19:47] <manusheel_> kandarpk: Kandarp, you can take this activity tomorrow too.
[19:47] <manusheel_> Good question. Let us ask Luke or Neeraj on it.
[19:48] <kandarpk> op_amp: Hi, around ?
[19:49] <manusheel_> kandarpk: We can ask Luke, if Neeraj is not around.
[19:50] <manusheel_> kandarpk: Kindly send me an e-mail on asking for the access of source files for sugar api documentation.
[19:50] <kandarpk> manusheel_ sir: lfaraone seems to be not there ( marked away ).
[19:51] <manusheel_> kandarpk: Will talk to Bernie once I see him around.
[19:51] <manusheel_> kandarpk: Ok, in that case, let us take the packaging activity tomorrow.
[19:52] <lfaraone> kandarpk: back.
[19:52] <kandarpk> lfaraone: great
[19:53] <kandarpk> lfaraone: where do I look for the Ubuntu package ?
[19:59] <lfaraone> kandarpk: I'm not sure what you mean.
[19:59] <lfaraone> kandarpk: you're basing your work off the package in git, right? you don't *need* a debdiff :)
[20:00] <kandarpk> lfaraone: you asked to copy the changelog file from previous version of the package for ubuntu
[20:01] <kandarpk> lfaraone: how do I do that ?
[20:10] <lfaraone> kandarpk: oh, right.
[20:11] <lfaraone> kandarpk: go to the package page in launchpad: https://launchpad.net/ubuntu/+source/sugar-memorize-activity/
[20:11] <kandarpk> lfaraone: thanks.
[20:12] <lfaraone> kandarpk: then download the latest verison of the package's dsc file using dget.
[20:12] <lfaraone> kandarpk: that'll get you the most recent version of the package source, which has the debian/changelog from Ubuntu.,
[20:24] <kandarpk> lfaraone: there is one problem.
[20:24] <kandarpk> lfaraone: I named the activity as poll ( it  was named as poll on a.sl.o ), nut it is named as pollbuilder in ubuntu package
[20:27] <lfaraone> kandarpk: let me see.
[20:37] <kandarpk> lfaraone: I should leave now.
[20:38] <lfaraone> kandarpk: okay.
[20:38] <kandarpk> lfaraone: please see what should be done.
[20:39] <kandarpk> manusheel sir: I should leave now, will carry forward tomorrow
[20:39] <manusheel> kandarpk: Sure..
[20:40] <manusheel> Good night Kandarp.
[20:40] <manusheel> lfaraone: I am around.
[20:40] <kandarpk> manusheel sir, lfaraone: good night.
[20:40] <manusheel> Let us discuss what should be the name of the poll project - poll builder or poll.
[20:41] <manusheel> kandarpk: Take good rest. Good night.
[20:42] <kandarpk> sources :
[20:42] <kandarpk> http://activities.sugarlabs.org/en-US/sugar/addon/4074
[20:42] <lfaraone> kandarpk: just rename the package to sugar-pollbuilder-activity when we build for ubuntu, we'll use the proper name when we sync.
[20:42] <kandarpk> https://launchpad.net/ubuntu/+source/sugar-pollbuilder-activity
[20:42] <kandarpk> lfaraone: ok.
[20:42] <lfaraone> kandarpk: "source tarball" is either the upstream git repo or a released tarball.
[20:44] <manusheel> lfaraone: Thanks for the pointer.
[20:44] <kandarpk> lfaraone: I think I should have used "links" instead of sources there ^^
[20:44] <kandarpk> lfaraone: did I understand what you wanted to say ?
[20:46] <kandarpk> lfaraone:  Use "update-maintainer" to change the maintainer of the package from Debian OLPC.
[20:46] <kandarpk> update-maintainer ?
[20:49] <lfaraone> kandarpk: "update-maintainer" is a command.
[20:50] <kandarpk> lfaraone: not recognised
[20:50] <lfaraone> kandarpk: it automatically changs the maintainer of a package from whatever-the-current-maintainer-is to "Ubuntu Development <SOME_EMAIL@lists.ubuntu.com>"
[20:50] <lfaraone> kandarpk: do you have ubuntu-dev-tools installed?
[20:51] <kandarpk> lfaraone: installing
[21:02] <kandarpk> lfaraone: done
[21:03] <kandarpk> lfaraone: should I mail you some files for verification ?
[21:03] <lfaraone> kandarpk: well, if you post it to the bug report Ill be able to review it there and approv eit it its' good, if you mail direct then we ahve another step to go through.
[21:05] <kandarpk> lfaraone: Ok, but I have used LP: #BUG_NUMBER in changelog
[21:05] <kandarpk> when do I change that ?
[21:07] <lfaraone> kandarpk: you file the bug report, change the BUG_NUMBER in changelog to the number you get after filing the report, then ost the diff.gz / debian.tar.gz to the bug.
[21:07] <kandarpk> lfaraone: Ok
[21:14] <kandarpk> lfaraone: I need to upload source.changes ?
[21:19] <kandarpk> lfaraone, manusheel sir: bug report filed here :
[21:19] <kandarpk> https://bugs.launchpad.net/ubuntu/+source/sugar-pollbuilder-activity/+bug/607949
[21:20] <manusheel> kandarpk: Let me have a look.
[21:21] <lfaraone> kandarpk: uh, there was no debian.tar.gz?
[21:21] <manusheel> kandarpk: Looks fine to me.
[21:21] <manusheel> kandarpk: Yes.
[21:21] <lfaraone> kandarpk: did you get a warning about missing an orig.tar.gz when you built the package?
[21:21] <kandarpk> manusheel: yes sir.
[21:21] <kandarpk> the orig was of version 17
[21:21] <manusheel> debian.tar.gz file is missing.
[21:22] <kandarpk> Ok.
[21:23] <lfaraone> kandarpk: all that is needed is the debian.tar.gz created by building the package.
[21:24] <manusheel> kandarpk: Let us try to fix this.
[21:24] <kandarpk> manusheel sir: shall I rename the orig file ?
[21:25] <neeraj> Hi lfaraone,
[21:25] <neeraj> I will make sure from next time that I give appropriate information about changes in commit
[21:25] <neeraj> *commit message
[21:26] <manusheel> kandarpk: Yes, I think we should rename the file.
[21:26] <manusheel> The orig file.
[21:26] <kandarpk> manusheel sir, lfaraone: dpkg-source: error: unrepresentable changes to source
[21:27] <manusheel> kandarpk: Ok. Interesting. This means our changes cannot be reflected to the source.
[21:27] <manusheel> lfaraone: Any workaround on it?
[21:28] <lfaraone> kandarpk: what is the change it talks about?
[21:28] <lfaraone> neeraj: no worries, just FYI
[21:31] <kandarpk> lfaraone, manusheel sir: http://paste.ubuntu.com/466652/
[21:32] <neeraj> lfaraone, for sugar-write-activity, I still have few doubts.. First I have to change the rules file and control.in acco to For sugar-record-activity
[21:32] <neeraj> If it works in 0.86 and above, for example, restore your debian/rules
[21:32] <neeraj> file to it's original state. Change "DEB_PYTHON_SUGAR_PACKAGES" adding
[21:32] <neeraj> "-0.86" to the end. Change the binary package name in debian/control.in
[21:32] <neeraj> adding "-0.86" to the end.
[21:32]  * lfaraone will be right back.
[21:33] <manusheel> kandarpk: Thanks Kandarp. Having a quick study.
[21:34] <neeraj> Now apart from these changes do I need to change anything else? Also I will push these in sugar-write-activity.git.. right?
[21:34] <lfaraone> neeraj: yes. just the binary package name will change.
[21:34] <neeraj> lfaraone, Ok.. thanks.. making required changes now..
[21:36] <kandarpk> lfaraone, manusheel sir: I must leave now.
[21:36] <kandarpk> need to get up at 6
[21:37] <lfaraone> kandarpk: okay, understandable.
[21:37] <manusheel> kandarpk: Sure, Kandarp.
[21:37] <manusheel> Good night.
[21:37] <kandarpk> manusheel sir, lfaraone : Thanks.
[21:37] <kandarpk> good night
[21:38] <manusheel> lfaraone: Did you get a chance to look at the logs posted by Kandarp?
[21:38] <lfaraone> manusheel: yes, I'll send him an email tomorrow.
[21:38] <manusheel> lfaraone: Thanks Luke.
[22:02] <lfaraone> manusheel: done.
[22:05] <neeraj> lfaraone, in local git repo, how to change the commit message after committing once?
[22:06] <lfaraone> neeraj: you can change the most recent commit message (before you've pushed up) using "git commit --amend"
[22:06] <lfaraone> neeraj: "man git-commit" and search for "amend" for more.
[22:07] <neeraj> lfaraone, thanks :)
[22:07] <neeraj> also wish if u could tell me copyright year for port/*
[22:07] <lfaraone> neeraj: let's go with "2009"
[22:08] <lfaraone> neeraj: isn't it like 2am over there? :)
[22:10] <neeraj> lfaraone, yeah but I have slept for 4hrs.. 9pm -1am :).
[22:12] <neeraj> lfaraone, If u have to go somewhere then please provide me some link for tutorial that I can read in free time :)
[22:13] <neeraj> s/for/for any tut/documentation that will help us in future in completing our task :)
[22:13] <lfaraone> neeraj: I do.
[22:14] <lfaraone> neeraj: read http://www.debian.org/doc/maint-guide/ and http://www.debian.org/doc/debian-policy/ if you're looking for something dry to put you to sleep :)
[22:14]  * lfaraone is out to dinner. 
[22:22] <manusheel> lfaraone: Thank you.
[22:31] <bernie> manusheel: ping?
[22:31] <manusheel> bernie: Hi Bernie.
[22:31] <manusheel> Just send you an e-mail.
[22:31] <manusheel> bernie: We need to insert docstrings in the sugar sources. This is in reference to Sugar API documentation.
[22:32] <manusheel> Could you please have a look, and see if we have the access to the server.
[22:34] <bernie> manusheel: which server?
[22:34] <bernie> manusheel: ok I'll read your email.
[22:35] <bernie> manusheel: that machine is buildslave-ubuntu-lucid-64bit.sugarlabs.org.
[22:35] <manusheel> bernie: Ok, it seems like it is the incorrect machine. Thoughts?
[22:35] <bernie> manusheel: there's no seeta user
[22:36] <bernie> manusheel: I'm not root, but I can see users:
[22:36] <bernie> manusheel: ah sorry, there _is_ a seeta user too
[22:36] <manusheel> bernie: David has set up the sources. We need to insert docstrings to test the documentation for api.sugarlabs.org/sphinx.
[22:36] <manusheel> bernie: Great.
[22:36] <manusheel> Glad to hear.
[22:36] <manusheel> bernie: Not sure, why we are unable to access the server.
[22:37] <manusheel> bernie: We need to add description - classes, variables, methods for the modules and sub modules.
[22:37] <manusheel> That can be done by inserting docstrings.
[22:38] <manusheel> At required places, which will carry the description of the fields.
[22:38] <bernie> manusheel: ok I've hacked the box. now I do have root :-)
[22:38] <manusheel> bernie: Hacker :-)
[22:38] <manusheel> bernie: Can you please check why we are unable to ssh to the server.
[22:38] <manusheel> Should i send you Kandarp's ssh keys again?
[22:39] <manusheel> Will that help?
[22:43] <manusheel> bernie: around?
[22:43] <bernie> manusheel: the key for seeta@buildslave-ubuntu-lucid-64bit.sugarlabs.org is chirag@chirag-desktop
[22:43] <bernie> manusheel: what ssh key are you using to log in?
[22:44] <bernie> manusheel: also, perhaps this is not how it was designed to work. there are accounts for each person... so maybe one should login with his own user and _then_ become user seeta with sudo or su.
[22:44] <manusheel> bernie: Did you see a user name Kandarp?
[22:44] <bernie> manusheel: a lot of users have root access on this machine
[22:45] <bernie> manusheel: yes, kandarp.seeta
[22:45] <manusheel> Should he use ssh kandarp@140....
[22:45] <bernie> manusheel: who is "it"?
[22:45] <manusheel> Ok, thank you.
[22:45] <manusheel> bernie: kandarp.seeta is the team member inserting the doc strings.
[22:45] <bernie> manusheel: don't use the IP, use the hostname.... so if we shuffle VMs around it will keep working
[22:46] <manusheel> bernie: Ok, thank you for the pointer. So ssh kandarp.seeta@buildslave-ubuntu-lucid-64bit.sugarlabs.org
[22:46] <manusheel> will work, right.
[22:47] <manusheel> bernie: That was indeed a very important pointer. Yes, if IPs are shuffled, we would be in a mess.
[23:44] <neeraj> lfaraone, ping