[02:54] <dfarning> good morning
[03:14] <dipankar> dfarning, hello.
[03:14] <dipankar> lfaraone, you around?
[03:14] <dfarning> dipankar, hello
[03:15] <dipankar> dfarning, how was your day?
[03:16] <dfarning> dipankar, It was good, and your night?
[03:17] <dipankar> dfarning, terrible.. Could sleep properly :( Feeling really weird right now
[03:17] <dipankar> *Couldn't
[03:18] <dfarning> dipankar, argg that sucks:(
[03:19] <dfarning> will you be around today?
[03:19] <dipankar> dfarning, yeah sure :)
[03:19] <dfarning> dipankar, What do you have planned?
[03:20] <dipankar> dfarning, I tried updating a package sugar-memorize last night. Some doubts that I wanted to ask
[03:21] <dipankar> dfarning, The wget -P <download-link> was not working,
[03:21] <dipankar> removing -P did.
[03:22] <dfarning> dipankar, what does the P flag do?  I'm scanning the man page
[03:24] <dipankar> -P,  --directory-prefix=PREFIX  save files to PREFIX/...
[03:24] <dipankar> dfarning, ^^
[03:24] <dfarning> dipankar, ok found it -P is prefix
[03:25] <dipankar> dfarning, but what does prefix mean hear?
[03:25] <dipankar> *hear -> here
[03:26] <dfarning> dipankar, I think that it will tell wget where to put the download.  The default is . which means the current dir.
[03:27] <dfarning> i think if you use the -P flag you have to give a valid local directory
[03:28] <dipankar> dfarning, ok.. I guess I am comfortable with 'wget <download-link>' right now :)
[03:29] <dfarning> dipankar, yep 99% of the time that is what you will use
[03:29] <dipankar> dfarning, I did not do the 'git-push' as I don't have an account yet for upload.
[03:30] <dfarning> dipankar, a very handy flag for wget is -c   is means continue.  If a download fails partway though you can just restart it where it left off.
[03:31] <dfarning> dipankar, do you know how to make a patch with git?
[03:32] <dipankar> dfarning, lfaraone showed me using 3.0(quilte=) in which I simply added a patch file to the folder debian/patch/
[03:32] <dipankar> and also in the series file
[03:34] <dfarning> ok what I am talking about is the command git-diff.  It allows you to change your recent changes, in a git repository, into a patch file.
[03:34] <dipankar> ok..
[03:35] <dfarning> dipankar, http://learn.github.com/p/diff.html is a good reference.
[03:35] <dfarning> dipankar, can you try to make a diff and send it to me?
[03:36] <dipankar> dfarning, ok.. I might be a bit slow today. :(
[03:36] <dfarning> dipankar, np.
[03:52] <dipankar> dfarning, Ok.. Here are some problems
[03:54] <dipankar> dfarning, 1. 'git status' gives the output : commit message + another line :# Untracked files:
[03:54] <dipankar> #   (use "git add <file>..." to include in what will be committed)
[03:54] <dipankar> #
[03:54] <dipankar> #	sugar-memorize-activity_33.orig.tar.bz2
[03:56] <dfarning> what this is telling you is that the last thing you did is drop the .bz2 file into the package and did not commit it yet.
[03:56] <dfarning> dipankar, is that what you intended?
[03:57] <dipankar> dfarning, I ran 'git diff' no output came. But I then ran 'git diff --cached', then I got the following output : diff --git a/NEWS b/NEWS
[03:57] <dipankar> index e2d6a52..90e830d 100644
[03:57] <dipankar> --- a/NEWS
[03:57] <dipankar> +++ b/NEWS
[03:57] <dipankar> @@ -1,6 +1,5 @@
[03:57] <dipankar> -28
[03:57] <dipankar> -
[03:57] <dipankar> -27
[03:57] <dipankar> +33
[03:57] <dipankar> +* Trial by Dipankar Patro.
[03:57] <dipankar>  
[03:58] <dipankar>  26
[03:58] <dipankar>  
[03:58] <dipankar> dfarning, I guess I haven't added the .orig tarball yet
[04:00] <dfarning> yes, the term you are look for is commit.  with git you can do a bunch of edits to the repository.  Then when you are happy with your changes you must commit them.
[04:01] <lfaraone> dipankar: hi.
[04:02] <dipankar> lfaraone, welcome back.
[04:02] <dfarning> dipankar, I like to keep the cheet sheet at http://github.com/guides/git-cheat-sheet handy
[04:02] <dipankar> dfarning, I meant that  I did not do the command 'git add <.orig tarball> ' only :)
[04:03] <dipankar> lfaraone, we are discussing git repo..
[04:04] <lfaraone> dipankar: cool.
[04:05] <lfaraone> dipankar: what you meant to say earlier is "3.0 (quilt)". It's a version of Debian package source that uses the quilt patch system to manage patches. As we talked about earlier, 3.0 (quilt) is compatible with the sort of patches generated by git.
[04:06] <lfaraone> dipankar: how would you figure this could be useful?
[04:08] <dipankar> lfaraone, I guess, I don't have to make a .patch file.. I will just change the files as per requirements
[04:08] <dipankar> run git diff
[04:09] <lfaraone> dipankar: that's one use of it.
[04:09] <dipankar> *after adding them through 'git add'
[04:09] <lfaraone> dipankar: large software projects use git to track changes to their files.
[04:09] <lfaraone> dipankar: each change is recorded as a commit.
[04:09] <dipankar> lfaraone, ohk..
[04:09] <lfaraone> dipankar: so, if a version of sugar was released, and a bug was found...
[04:10] <lfaraone> dipankar: .. and the bug was fixed in a git commit, you could look at the commit to see what changed.
[04:10] <lfaraone> dipankar: that commit may be used as a patch against a released version we're packaging, as we did earlier.
[04:11] <dipankar> lfaraone, ok..
[04:11] <lfaraone> dipankar: does that make sense?
[04:12] <dipankar> lfaraone, yes.. so tracking is git's specialty
[04:13] <lfaraone> dipankar: and we understand how that could be useful to us, when we've got several people working on a package.
[04:13] <lfaraone> dipankar: they can each work on changes, committing to their local branches until they get something worth publishing, and then push it up. if changes have been made on the remote repository, they can be merged in before the push.
[04:14] <dipankar> lfaraone, ok..
[04:15] <dipankar> lfaraone, so we have to manually search for changes before pushing? or it will be done automatically?
[04:16] <lfaraone> dipankar: well, if you push and there are remote changes, it'll tell you :)
[04:16] <dipankar> lfaraone, thats great.
[04:17] <lfaraone> dipankar: http://progit.org/book/ch3-0.html explains how this works.
[04:17] <dipankar> lfaraone, I ran 'git diff'.. but no output came
[04:18] <lfaraone> dipankar: probably because you didn't make any changes since your last commit.
[04:18] <lfaraone> dipankar: if you want to get the changes between commits, read up on the syntax for git-diff.
[04:18] <lfaraone> ("man git-diff")
[04:19] <dipankar> lfaraone, But I did change a file. And I get o/p in 'git diff --cached'
[04:20] <lfaraone> dipankar: okay. you then added it, right?
[04:20] <lfaraone> dipankar: look at git-diff's manpage, and read through the first three examples.
[04:20] <dipankar> lfaraone, yes
[04:20] <dipankar> ok
[04:21] <lfaraone> dipankar: so, what's the difference between git-diff with or without --cache?
[04:21] <lfaraone> *cached
[04:23] <dipankar> lfaraone, git-diff is used for changes about to be staged (before adding)
[04:23] <dipankar> lfaraone, git-diff --cached is used for changes staged but before committing
[04:24] <lfaraone> dipankar: okay. so you understand why --cached worked before when using git-diff without it did not?
[04:24] <dipankar> lfaraone, yes. Because I added the NEWS file before
[04:24] <lfaraone> graet.
[04:25] <dipankar> so git-diff didnot work
[04:25] <dipankar> :)
[04:25] <dipankar> BTW lfaraone, How do I generate a diff file that can be used for patch?
[04:25] <dipankar> lfaraone, Like the one we used for patching previously.
[04:26] <lfaraone> dipankar: I believe the diffs generated by git can be used, no?
[04:28] <dipankar> lfaraone, sorry, have put my question in a wrong way. It is 'how do i generate a patch file?'
[04:28] <dipankar> lfaraone, yes that can be used..
[04:28] <lfaraone> dipankar: well, when you run git-diff, you get something like this, right? http://sprunge.us/HRci (albiet with different content)
[04:29] <lfaraone> dipankar: doesn't that look similar to the other patch file we looked at?
[04:29] <lfaraone> dipankar: if you take the output of git-diff, and put it in a file in the right location, you're golden.
[04:29] <dipankar> lfaraone, got it. :).
[04:30] <dipankar> lfaraone, the command can be : git diff > abc.patch
[04:30] <lfaraone> dipankar: exactly.
[04:31] <dipankar> lfaraone, when committing, we already have changed our source file.. So I guess we don't have to patch again
[04:32] <lfaraone> dipankar: yes. keep in mind, however, that we don't like to make changes to the source file directly when we're doing Debian packaging.
[04:32] <lfaraone> dipankar: since direct changes are difficult to audit and hard to migrate when we rebase on a new upstream version. (the changes get lost)
[04:33] <dipankar> lfaraone, so how do I work that out?
[04:34] <dipankar> Like without changing the source, but still making corrections required..
[04:34] <lfaraone> dipankar: well, one way to do it is to make changes to a file, do git-diff, save the patch, and revert your changes. that's time consuming.
[04:34] <dipankar> ok..
[04:35] <lfaraone> dipankar: instead, there's a tool called quilt which handles a deal of that for you. quilt is what dpkg-source is using internally to edit patches.
[04:35] <lfaraone> dipankar: I highly recommend you read http://pkg-perl.alioth.debian.org/howto/quilt.html to understand how quilt works, but we'll get to that later.
[04:35] <lfaraone> dipankar: in the near-term, I have a short task for you.
[04:36] <dipankar> lfaraone, sure
[04:36] <lfaraone> dipankar: on http://git.debian.org/ , you'll find there's a repository called sugar-terminal-activity.git in collab-maint.
[04:37] <lfaraone> dipankar: are your SSH keys properly set up with alioth.debian.org?
[04:37] <dipankar> no..
[04:37] <dipankar> I haven't done that yet.
[04:38] <lfaraone> dipankar: okay. since git.debian.org uses alioth for authentication, you'll need to add youyr SSH keys.
[04:38] <dipankar> lfaraone, ok..
[04:39] <dipankar> lfaraone, I am at the sugar-terminal-activity
[04:39] <dipankar> page
[04:40] <lfaraone> dipankar: then, I'd like you to clone the sugar-terminal-activity.git repository using the "git+ssh" url listed on the page you're seeing now. Edit the debian/control.in file and update the description of the package using similar text to what is used in the description of http://git.debian.org/?p=collab-maint/sugar-calculate-activity.git;a=blob;f=debian/control.in;h=ae9a2b9989f80377c248ca774c869e0f052d7242;hb=dc85b18722eaac7f0457597a6a90b83
[04:41] <lfaraone> dipankar: commit your change to the local repository using a descriptive commit message, then push your changes up.
[04:41] <lfaraone> dipankar: let me know if/when you get stuck.
[04:41] <dipankar> lfaraone, it might take sometime..
[04:42] <lfaraone> dipankar: no worries, I'll be going to sleep in a few hours, we can talk about it in the morning :)
[04:42] <lfaraone> *going to sleep in a few minutes for several hours
[04:42] <dipankar> lfaraone, ok.. Its nearing 0000 hrs there :)
[04:42] <lfaraone> yep.
[04:43] <dipankar> but I will definitely complete it by the time you wake up..
[04:43] <dipankar> lfaraone, about the ssh key. They are to be added on the alioth site. right?
[04:44] <lfaraone> dipankar: Yes. See http://wiki.debian.org/Alioth/SSH for a description of how alioth's SSH services work.
[04:44] <dfarning> lfaraone, dipankar nice job and a good learning task for dipankar to acomplish
[04:45] <dipankar> dfarning, :).. Like you said lfaraone is a really good teacher.
[04:45] <lfaraone> dfarning: it was jonas' idea a while ago, I haven't gotten around to updating the GettingStartedGuide to talk about it yet.
[04:45] <lfaraone> dfarning: so I can only take some credit :)
[04:46]  * lfaraone will brb in 12.
[04:47] <dfarning> dipankar, so it looks like you are set for a couple of hour:)
[04:47] <dipankar> dfarning, yup..
[04:48] <dipankar> dfarning, btw the sugar-emulator fix is still not working on my machine :P
[04:49] <dipankar> dfarning, the one with the /usr/share/applications/sugar.desktop
[04:49] <dfarning> dipankar, let's worry about that after you have gotten the correct packaging method down.  Then we can use that bug as a first 'real' application of what you are learning.
[04:50] <dipankar> dfarning, great :)
[04:55] <dfarning> kandarpk, that is is good.
[04:55] <dfarning> what are you going to work on today?
[04:56] <kandarpk> those bugs that I reported yesterday
[04:56] <kandarpk> Vijit has send some help
[04:56] <dfarning> kandarpk, the ones in debian?
[04:57] <kandarpk> yes
[04:57] <kandarpk> dfarning, would you like to recommend anything else that I should do ?
[04:58] <lfaraone> kandarpk: by the way, I hope you didn't take my email as a reproach.
[04:58] <lfaraone> kandarpk: I apologieze if I came across as critical.
[04:59] <dfarning> kandarpk, that sounds good.  when you come up with a fix for one of them, will you let me know.  I'll help you work through the debian bugtracker.
[04:59] <kandarpk> lfaraone, It was good advice
[04:59] <dfarning> lfaraone, or if you are going to be here a while can you explain the debian bug tracker to kandarpk?
[05:00] <kandarpk> dfarning, sure
[05:00] <lfaraone> dfarning: I'll be off in hopefully five minutes.
[05:01] <lfaraone> kandarpk: basically, before reporting a bug, it's usually a good idea to discuss the issue via IRC with others to ensure that the bug you report is really a bug.
[05:01] <lfaraone> kandarpk: and when you finally do, it's important to identify three key components.
[05:03] <lfaraone> kandarpk: detailed on http://homepages.tesco.net/~J.deBoynePollard/FGA/problem-report-standard-litany.html
[05:03] <lfaraone> kandarpk: what you did, what happened, why that isn't what you expected.
[05:04] <kandarpk> hmmm
[05:04] <kandarpk> lfaraone, missed most of them in my mail
[05:04] <lfaraone> kandarpk: bonus is if you're able to provide a patch, or something that shows that the behavior is bad. like, "this used to work but doens't now" ( a regression ), or "the docs say it does this but in reality it doesn't" ( a bug in the docs, the code, or both )
[05:05] <lfaraone> kandarpk: no worries, most people do the first few times.
[05:05] <kandarpk> Ok.
[05:06] <lfaraone> anyway, I'm off. I'm sure dfarning will not steer you wrong.
[05:06] <lfaraone> dipankar: good luck on your quest. let me know if you encounter any gremlins.
[05:07] <dipankar> lfaraone, whats the password??
[05:07] <dipankar> :P
[05:07] <dipankar> it is not accepting mine..
[05:07] <lfaraone> dipankar: it's asking for your alioth password.
[05:07] <lfaraone> dipankar: keep in mind you have to specify your user name.
[05:07] <lfaraone> (since I doubt your local user name is dipankar-guest)
[05:07] <dipankar> lfaraone, in git clone too?
[05:08] <lfaraone> dipankar: well, you're cloning via SSH.
[05:08] <dfarning> kandarpk, ping me when you are ready to create create a bug report/patch submission and we can go over it together.
[05:09] <dipankar> lfaraone, ohk.. that means the syntax should be : git clone <user-name>@git+ssh...??
[05:09] <kandarpk> dfarning: is it really a bug, then ?
[05:09] <lfaraone> dipankar: either explicitly specify it (like your-user-name-goes-here@git.debian.org) or use the tips on http://wiki.debian.org/Alioth/SSH
[05:09] <lfaraone> dipankar: git+ssh://username@git.debian.org/etc
[05:09] <dfarning> kandarpk, which issue?
[05:09] <kandarpk> or can it be the default behaviour in sugar ?
[05:10] <kandarpk> to restart sugar-emulator
[05:10] <kandarpk> after clicking on restart now
[05:10] <dipankar> lfaraone, ohk.. I guess I have to go through the wiki site once again...
[05:10] <kandarpk> *restart manually
[05:11] <dfarning> kandarpk, hmm how about creating a draft bug report with the information luke suggested.  and we can discuss the issues in the context of the report.
[05:11]  * lfaraone is seriously sleeping now.
[05:12] <dfarning> good bug reports take pratice.
[05:14] <kandarpk> dfarning, am I required a file a report on bug tracker ?
[05:16] <dfarning> kandarpk, no just write a draft bug report at http://openetherpad.org/49lCAfLuoN then we can go over it together.
[05:16] <kandarpk> Ok.
[05:29] <kandarpk> dfarning, around ?
[05:29] <dfarning> yes
[05:30] <kandarpk> dfarning, I've drafted the report
[05:30] <kandarpk> is it ok ?
[05:30] <dfarning> looking
[06:08] <ankurkhurana> hello dfarning ,
[06:09] <dfarning> ankurkhurana, goodmorning. how are you?
[06:09] <ankurkhurana> i am fine :) ,
[06:10] <ankurkhurana> dfarning: i installed 10.04 and 10.10 on virtual box under windows
[06:10] <dfarning> ankurkhurana, how do they work?
[06:10] <ankurkhurana> i was having problem using dual boot system, so i did that.Primarily i have updated everything, but i was seking help how to import my pgp keys
[06:11] <ankurkhurana> they work fine, some more fine tuning needed and they will be as good as old
[06:12] <dfarning> ankurkhurana, the easiest way I have found to move stuff around between vms is ssh
[06:12] <dfarning> ankurkhurana, do you have an account on the build vm?
[06:12] <ankurkhurana> dfarning: I have imported my old pgp key to my new vm system through password and encryption manager, should i do anything else as well?
[06:12] <ankurkhurana> yes i have access to vm
[06:13] <ankurkhurana> i will generate my public keys and post it to authorized_keys, but i was confused regarding format.
[06:13] <dfarning> ok, you are asking a different question than I was answering:(
[06:14] <ankurkhurana> that too was my question ,which i was going to ask after this:)
[06:14] <dfarning> I don't know how to move keys around I only have one gpg key on my primary desktop.
[06:16] <dfarning> ankurkhurana, with reguard to moving files around in general I like to 'scp' to a remote server and scp them back to the other machine
[06:17] <ankurkhurana> dfarning: okay, i will try to do some more tweaking,in btw i wanted to know should i only post my ssh public key to authorized_keys or is there anything else needed.?
[06:17] <ankurkhurana> in vm
[06:18] <ankurkhurana> *remote vm
[06:18] <dfarning> ankurkhurana, that should be it.
[06:20] <dfarning> kandarpk, can you copy the bug report we were working on to a google doc and start working on the next one?
[06:20] <kandarpk> sure
[06:20] <kandarpk> only the report part ?
[06:21] <dfarning> kandarpk, yes, lets start with the report. then we can add what ever else is needed.
[06:22] <kandarpk> ok.
[06:23] <kandarpk> dfarning, should I report back on the mailing list ?
[06:24] <dfarning> kandarpk, lets wait until we have a bug report we are happy with and then file it in the debian bug tracker.
[06:24] <kandarpk> Ok.
[06:24] <kandarpk> Thanks
[06:25] <dfarning> kandarpk, your welcome.
[06:27] <dfarning> kandarpk, ankurkhurana  I am getting sleepy so I will go to bed. I will try to be back in 5.5 to 6 hours
[06:27] <kandarpk> dfarning, Good night
[06:27] <ankurkhurana> dfarning:  good night :)
[06:27] <dfarning> Thanks for sticking with on this I know your are learning at lot of new stuff and process.
[06:28] <kandarpk> dfarning, you are a great mentor to have
[06:29] <dfarning> FWIW, manu has assigned me some readings so I can learn how to speak the QA language that shops like yours use:)
[06:29] <dfarning> Im learning too:)
[06:33] <ankurkhurana> kandarpk:  are you aware of the process of uploading packages of 10.04 to 10.10 ppa
[06:33] <ankurkhurana> ?
[06:34] <kandarpk> ankurkhurana, no.
[06:34] <ankurkhurana> okay
[12:15] <dfarning> good morning Manusheel
[12:16] <Manusheel> dfarning: Good morning David.
[13:37] <dipankar> dfarning, goodmorning.
[13:38] <dipankar> lfaraone, you up? goodmorning
[13:39] <lfaraone> dipankar: how can you tell?
[13:39] <lfaraone> dipankar: I'm just going through some email, then off to breakfast.
[13:39] <lfaraone> dipankar: what can I help you with?
[13:40] <dipankar> lfaraone, I pushed the changes that you wanted me to.
[13:40] <dipankar> lfaraone, you have your breakfast then we will continue on git. :)
[13:49] <dfarning> dipankar, good morning
[13:49] <dipankar> dfarning, how are you?
[13:51] <dfarning> dipankar, I am doing well and you.
[13:51] <dipankar> dfarning, I am doing great. :)
[13:52] <dfarning> dipankar, how did the packaging go last night?
[13:52] <dipankar> dfarning, I have pushed the changes that Luke told me to do. Luke will be verifying it (He is having his breakfast)
[13:55] <dfarning> dipankar, that is great.
[13:55] <dipankar> dfarning, I hope I have done it correctly :)
[13:56] <dfarning> dipankar, if not lfaraone will help you get it straight.
[13:56] <dipankar> dfarning, Sure!
[13:57] <dipankar> dfarning, I was trying the neighbourhood view on sugar today.
[13:57] <dipankar> dfarning, It is weird that I couldn't find any user in my neighbourhood unlike before.
[13:58] <dipankar> dfarning, Earlier I could find many sugar users there. Does this happen with you?
[13:58] <dfarning> dipankar, I have to run for a few minutes.  I'll be back as soon as I can
[13:59] <lfaraone> dipankar: looks good, give me a second.
[13:59] <dipankar> lfaraone, no problem. Take your time
[14:05] <lfaraone> dipankar: okay, only one thing: all lines in control should be wrapped at 72 characters. I did that for you, and pushed up. You should be able to pull down the changes via something like "git pull origin master"
[14:07] <lfaraone> dipankar: now, look in the debian/ folder for the package. there should be two similarly named files, one "debian/control" and one "debian/control.in". What is the difference between these two?
[14:08] <dipankar> lfaraone, brb in 5
[14:14] <dipankar> lfaraone, control.in has cdbs format
[14:15] <dipankar> lfaraone, control.in also has git repo ino
[14:15] <dipankar> *f/ino/info
[14:15] <lfaraone> dipankar: correct on both, but the second is just because we haven't regenerated debian/control yet.
[14:16] <dipankar> lfaraone, ok..
[14:16] <lfaraone> dipankar: basically, CDBS has some magic where it can automatically determine some of the packages your package build-depends on.
[14:16] <lfaraone> dipankar: to do that, you create a debian/control.in file where you  include a substitution line, "@cdbs@", that gets replaced when you run a special command.
[14:18] <lfaraone> dipankar: the special (and rather unobvious, admittedly) command to regenerate debian/control fron debian/control.in is "DEB_MAINTAINER_MODE=1 fakeroot debian/rules clean"
[14:19] <lfaraone> dipankar: after you make changes to debian/control.in (and commit them!), regenerate debian/control and commit that separately. (this way we can differentiate between stuff you did manually and stuff done by a regeneration script)
[14:19] <lfaraone> dipankar: so, pull my changes if you haven't already, regenerate debian/control fron debian/control.in, commit them, and push it up.
[14:20] <dipankar> lfaraone, that was a long!...
[14:21] <lfaraone> dipankar: huh?
[14:22] <dipankar> lfaraone, I pulled your changes..
[14:22] <lfaraone> dipankar: okay,  was there a problem?
[14:23] <dipankar> lfaraone, nope, now I have to regenerate debian/control from debian/control?
[14:24] <lfaraone> dipankar: from debian/control.in, yes.
[14:24] <lfaraone> dipankar: if you like, run git-diff before you commit the result to see what regenerating did.
[14:25] <ankurkhurana> lfaraone,  can you help me as well as of now ? if you are not too busy
[14:26] <lfaraone> ankurkhurana: sure. by the way, in the future, don't bother asking, just say your question and one of us will help you when we're free.
[14:27] <ankurkhurana> lfaraone,  I have to upload sugar packages for 10.10 . what would be the right steps for starters
[14:28] <ankurkhurana> Ii have a test vm for maverick
[14:28] <ankurkhurana> what i was thinking that we ned to change my dput configuration ,and istead of lucid
[14:28] <lfaraone> ankurkhurana: what sort of sugar packages? activities? core packages?
[14:28] <lfaraone> ankurkhurana: okay, so your question is how you upload packages directly to maverick in a PPA?
[14:29] <ankurkhurana> i should write maverick
[14:29] <ankurkhurana> yes
[14:29] <lfaraone> ankurkhurana: that sounds reasonable.
[14:29] <dipankar> lfaraone, why not copy package to maverick series?
[14:29] <ankurkhurana> Is the ppa for maverick is automatically created in launchpad? i searched on net
[14:29] <ankurkhurana> but was not able to find suitable answer.
[14:30] <ankurkhurana> also can i upload directly from 10.04 or should i upload from 10.10 environment?
[14:31] <lfaraone> ankurkhurana: there is no need to create one, the same PPA can contain lucid, maverick, karmic, intrepid, etc packages.
[14:31] <lfaraone> dipankar: well, you could, but you usually have to rebuild the source for changes since Lucid.
[14:31] <dipankar> lfaraone, makes sense..
[14:32] <dipankar> lfaraone, btw I ran git-diff
[14:32] <lfaraone> okay, and did you see what you expected?
[14:32] <ankurkhurana> but i was thinking of downloading the packages and then re upload , is that a good idea?
[14:32] <ankurkhurana> and i will have to change lucid to maverick in change log as well i suppose in top line
[14:33] <ankurkhurana> ?
[14:33] <lfaraone> ankurkhurana: you can. you'll just have to change the version number so that the PPA will accept it.
[14:33] <lfaraone> ankurkhurana: you should, but it's not required if you override in dput.cf. I recommend it, though.
[14:33] <lfaraone> for clarity's sake.
[14:35] <dipankar> lfaraone, got the difference b/w the control.in files
[14:35] <ankurkhurana> lfaraone,  for how much time you will be around ?
[14:35] <lfaraone> dipankar: okay. commit your changes and push them up so I can take a look at them.
[14:35] <lfaraone> ankurkhurana: til about noonish EST. it's 9:30 right now.
[14:38] <ankurkhurana> lfaraone,  while i do my work i was wondering ubuntu series name is named as per the alphabetical order ? last one was karmic kola -> lucid lynx ->now maverick meerkat ?
[14:39] <lfaraone> ankurkhurana: well, there has to be an order of some sort, right? :)
[14:39] <lfaraone> ankurkhurana: and that way if I put "+maverick" at the end of a version number, it'll trump "+lucid" :D
[14:39] <ankurkhurana> :)
[14:41] <dipankar> lfaraone, done
[14:42] <lfaraone> dipankar: great.
[14:42] <lfaraone> dipankar: you can see all the changes made to the branch via the webui at http://git.debian.org/?p=collab-maint/sugar-terminal-activity.git
[14:43] <dipankar> lfaraone, was there only :)
[14:44] <lfaraone> dipankar: okay. go to the shortlog link on that page. do all the changes I made make sense?
[14:45] <dipankar> lfaraone, I guess I forgot to add the 'debian/control.in' file too
[14:45] <dfarning> \
[14:45] <lfaraone> dipankar: well, you didn't make any changes to debian/control.in, so it's not a problem.
[14:45] <ankurkhurana> lfaraone, it says No host for sugarteam-maverick found in config
[14:45] <ankurkhurana> http://paste.ubuntu.com/457842/
[14:46] <ankurkhurana> ^^ log file of proceedings
[14:46] <lfaraone> ankurkhurana: okay.
[14:46] <lfaraone> dipankar, ankurkhurana, for future use, can you both do "sudo apt-get install curl" on your systems?
[14:46] <ankurkhurana> ofcourse
[14:47] <ankurkhurana> already installed
[14:47] <dipankar> 'curl' for?
[14:47] <ankurkhurana> dipankar, man curl
[14:48] <ankurkhurana> but what will be the exact use?
[14:48] <dipankar> already installed.. must be done at start only..
[14:48] <lfaraone> ankurkhurana: run "cat ~/.dput.cf | curl -F 'sprunge=<-' http://sprunge.us" and give me the resulting URL.
[14:50] <ankurkhurana> lfaraone,  http://sprunge.us/LFbK
[14:50] <dipankar> lfaraone, aah.. got it..
[14:51] <lfaraone> ankurkhurana: cool. the point of that command was to pipe the output of cat to curl, which sends it to sprunge.us. Sprunge.us is a command-line pastebin :)
[14:51] <dipankar> lfaraone, nice
[14:51] <ankurkhurana> lfaraone,  i think i forgot to change upper field
[14:51] <lfaraone> ankurkhurana: yeah.
[14:52] <ankurkhurana> lfaraone, package uploaded and that curl thing is very useful :). waiting for package confirmation
[14:54] <dipankar> ankurkhurana, which field did you change '[sugar-lucid]'?
[14:54] <ankurkhurana> yes
[14:54] <ankurkhurana> i changes it before in input line
[14:54] <dipankar> lfaraone, Ok the site is really helpful..
[14:55] <lfaraone> dipankar: the first field is just the name, by the way. it doens't really do anything,y ou could call it "fadjiasdasd-magic-gnus" for all dput cares :)
[14:55] <ankurkhurana> but forgot to change it in the top one.Now let us see. dipankar  , to prevent sugar from crashing at start, which package did we change?
[14:55] <lfaraone> dipankar: now, I'd like you to create a new git repository in a new folder.
[14:55] <ankurkhurana> lfaraone, but it only worked after i changed it sugarteam-maverick
[14:55] <ankurkhurana> else it was giving error
[14:55] <lfaraone> ankurkhurana: that's becasue you said "dput sugarteam-maverick ..."
[14:56] <lfaraone> ankurkhurana: dput does not care what it's named, but you have to use the same name on the command line as you do in the file. we only use "sugarteam-RELEASE" so that it's easy to understand.
[14:56] <dipankar> lfaraone, :) now i got what was ankur's error
[14:56] <lfaraone> ankurkhurana: with the file as yo u had it before, you could have said "dput sugarteam-lucid" and it would have uplaoded to maverick per your wishes in the file :)
[14:57] <dipankar> ankurkhurana, s-p-s package for sugar-start-up
[14:57] <dipankar> *crash
[14:57] <lfaraone> dipankar: okay, in a new directory, run "apt-get source sugar-logviewer-activity".
[14:57] <dipankar> lfaraone, in a minute
[14:58] <lfaraone> dipankar: we're going to have you convert an activity packaged only in Ubuntu to git repository ready for a release.
[14:58] <ankurkhurana> oh, that means what the name of dput is ,the same is to be given in command
[14:58] <lfaraone> ankurkhurana: yes.
[14:59] <ankurkhurana> lfaraone,  The package was accepted , in what time i should try to check it in 10.10? just after it gets build in ppa?
[14:59] <lfaraone> ankurkhurana: sure.
[15:01] <dipankar> lfaraone, done
[15:02] <lfaraone> dipankar: okay, read the first section (until "importing a new upstream version") of http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.EXISTING
[15:03] <dipankar> lfaraone, ok..
[15:03] <lfaraone> dipankar: this describes how to  import an existing Debian/Ubuntu package into a git repository.
[15:04] <lfaraone> dipankar: what is the command you would  use to import sugar-logviewer-activity?
[15:04] <ankurkhurana> lfaraone, will you mind looking at ppa ,as i have just uploaded sugar-artwork , and i was proceeding with others , in case if there is any change needed as such.
[15:04] <ankurkhurana> https://launchpad.net/~sugarteam/+archive/ppa/+packages
[15:04] <lfaraone> ankurkhurana: okay, what do you want me to verify?
[15:05] <ankurkhurana> hmmm , if there is anything out of line which generally should not be there, well not much as such.
[15:06] <lfaraone> ankurkhurana: in your changelog entry, you said "New upstream release for Maverick Meerkat". An "upstream release" is a release from Sugar Labs. Typically, you only have them when you're changing the upstream version part and providing a new upstream tarball. That didn't happen here.
[15:06] <lfaraone> ankurkhurana: What you probably  meant was "Package rebuilt for Maverick Meerkat", I think.
[15:07] <dfarning> 0/=
[15:07] <dfarning> ";
[15:07] <lfaraone> dfarning: having trouble?
[15:07] <ankurkhurana> lfaraone, then should i upload them again?
[15:07] <lfaraone> ankurkhurana: no, just keep this in mind for the future.
[15:07] <ankurkhurana> i just uploaded s-p-s as well :(
[15:07] <ankurkhurana> lfaraone,  will bear that in mind for future .
[15:08] <lfaraone> ankurkhurana: also, keep in mind you might want to use a version number that reflects that you didn't make any additional changes to the package. Since you used 0.88.1-1ubuntu2, if you wanted to upload to Lucid you'd have to make it 0.88.1-1ubuntu3 for lucid. you see how this is unsustainable?
[15:09] <lfaraone> ankurkhurana: ideally, if you're doing a "no-change-rebuild", you should just add "+lucid" or "+maverick" to the end, or something like tha.
[15:10] <ankurkhurana> do u mean 1ubuntu1+maverick
[15:10] <ankurkhurana> like that
[15:10] <ankurkhurana> ?
[15:11] <lfaraone>  ankurkhurana sure.
[15:11] <ankurkhurana> lfaraone, i will send you a change log this time before i upload, just to make sure i dont do any other mistake.
[15:14] <lfaraone> dipankar: hi, did you get my last message?
[15:14] <dipankar> lfaraone, got d/c
[15:15] <lfaraone> dipankar: no worries. "10:04  lfaraone$ dipankar: what is the command you would  use to import sugar-logviewer-activity?"
[15:15] <dipankar> lfaraone, <dipankar> lfaraone, just a confusion.. can't the 'debcheckout' be used here too?
[15:16] <lfaraone> dipankar: try it.
[15:18] <ankurkhurana> lfaraone, please see this http://paste.ubuntu.com/457851/
[15:19] <lfaraone> ankurkhurana: sure. Neeraj shouldn't have done "0.88.1-1" before as the NUV, but we're stuck with it so what you did is good.
[15:19] <dipankar> lfaraone, :) failed. no repo found..
[15:20] <lfaraone> dipankar: yep. debcheckout looks at those "Vcs-**" fields that you saw earlier in debian/control.
[15:20] <dipankar> ok...
[15:20] <lfaraone> dipankar: if the package doesn't have them (in this case because sugar-logviewer-activity is not in a VCS system), then it won't work :)
[15:20] <ankurkhurana> lfaraone,  then i guess i will be uploading it as it is.
[15:20] <lfaraone> ankurkhurana: yes, what you did is good.
[15:21] <lfaraone> dipankar: as part  of our task, we'll fix that.
[15:21] <dipankar> lfaraone, ok..
[15:21] <lfaraone> dipankar: so you read the page I linked you, right?
[15:22] <lfaraone> dipankar: adding a bit to what they say, "If you want to be able to exactly recreate the original tarball (orig.tar.gz) from Git you should also specify the --pristine-tar option. This is recommended."
[15:22] <lfaraone> dipankar: I go further: we always do this. (until we tell git to do it for us, but we'll get ot that later)
[15:23] <dipankar> lfaraone, confused :(
[15:23] <lfaraone> dipankar: okay. do you understand what the dsc is?
[15:24] <dipankar> lfaraone, Yes.. it describes the source package
[15:25] <lfaraone> dipankar: cool. so, git-buildpackage has a command "git-import-dsc". What does that do?
[15:27] <dipankar> lfaraone, it creates a new git repo with the existing package source..
[15:27] <ankurkhurana> lfaraone, dipankar  http://paste.ubuntu.com/457853/
[15:27] <ankurkhurana> any pointers?
[15:27] <lfaraone> dipankar: yep. it puts the upstream source in a separate branch, along with the  info required to generate the original tarball, if you use --pristine-tar
[15:28] <ankurkhurana> ^^ the link is to content of mail i got for rejection of package.
[15:28] <dipankar> ankurkhurana, you have to sign manually first using the debsign
[15:28] <lfaraone> dipankar: --pristine-tar makes our life easier. we love --pristine-tar. we use it like a lucky charm, to ward off broken tarballs :P
[15:28] <dipankar> commans
[15:29] <dipankar> command
[15:29] <ankurkhurana> i used dch -i, so it signed automatically, when i built packagte.Also i have uploaded s-p-s package and artwork package using same method
[15:30] <dipankar> lfaraone, ohk... Thats why git-buildpackage didn't require us find the original tarball ourselves
[15:30] <dipankar> :)
[15:30] <lfaraone> dipankar: I'm exaggerating here, of course. but you get th epoint.
[15:30] <dipankar> ankurkhurana, try this site : http://ubuntusci.meraka.org.za/wiki/PPAIntro
[15:31] <dipankar> ankurkhurana, I never had this problem AFAIR
[15:31] <lfaraone> ankurkhurana: what was the exact command you used to dput? If you just do "dput something.changes" you'll upload directly to the main ubuntu archive, which will reject your upload since you're not an Ubuntu Developer :)
[15:32] <ankurkhurana> oh, got my mistake. silly one from my side.
[15:34] <dipankar> lfaraone, so I use the command git-import-dsc or apt-get source?
[15:37] <dipankar> lfaraone, ?
[15:40] <lfaraone> hold on, sorry, on the phone.
[15:41] <dipankar> lfaraone, no problem.
[15:43] <lfaraone> dipankar: well, when you do apt-get source apt downloads the dsc, orig, etc and unpacks it.
[15:43] <lfaraone> dipankar: you can remove the unpacked directory, since we're not going to use it.
[15:43] <lfaraone> dipankar: but we can use git-import-dsc on the resulting dsc and orig tarball etc to create a git repository out of the old package version.
[15:44] <lfaraone> dipankar: like "git-import-dsc --pristine-tar path/to/package.dsc"
[15:44] <ankurkhurana> lfaraone,  power off, will meet you as soon as it come back
[15:44] <dipankar> lfaraone, ok..
[15:45] <ankurkhurana> was on back up now, will go after uploading this package
[15:45] <lfaraone> dipankar: aside: when you end your sentence with ".." or "...", I take that as a "uh, okay, that doesn't really make sense, can you explain more?". Is that  interpretation accurate?
[15:46] <ankurkhurana> lfaraone, no
[15:46] <ankurkhurana> it means nothing, just symbolic to continue the conversation , dipankar , am i right
[15:47] <lfaraone> okay, just checking.
[15:47] <ankurkhurana> ?
[15:47] <dipankar> lfaraone, nope. My ".." or "..." means 'ok, I got it. now I can continue'
[15:47] <dipankar> ankur got that right :)
[15:48] <dipankar> lfaraone, I will try to use less '..' or '...'
[15:48] <lfaraone> dipankar: it's not important, I was just confused.
[15:48] <Neeraj> lfaraone, good morning :)
[15:49] <lfaraone> hello Neeraj
[15:49] <dipankar> lfaraone, its just a chat habit here. :) When I don't get your point, I will directly ask for it :)
[15:49] <dipankar> Hey Neeraj, welcome back
[15:49] <lfaraone> dipankar: great. so, import the dsc. the command should automatically create a new git repository for you underneath your current directory.
[15:49] <Neeraj> As you I have been assigned for packaging activity.. dfarning asked to me start wtih calculate activity.. can u help me in getting started
[15:49] <Neeraj> hi dipankar
[15:50] <Neeraj> lfaraone,Till now  I have just read sugar/gettingstarted guide on debian wiki..
[15:51] <lfaraone> Neeraj: okay.
[15:51] <lfaraone> dfarning: according to http://packages.debian.org/sid/sugar-calculate-activity , s-c-a is already packaged, no?
[15:51] <dipankar> lfaraone, done with impoting
[15:51] <dipankar> *importing
[15:51] <dfarning> lfaraone, Neeraj is going to be the activity expert for seeta.  Would it be possiable for him to spend the next couple of days working with dipankar to package activites?
[15:52] <lfaraone> dfarning: sure.
[15:53] <lfaraone> Neeraj: get the source for sugar-memorize-activity using "apt-get source PACKAGE_NAME" and import it into the git repository as I explained above to dipankar , if you would.
[15:53] <lfaraone> dipankar: so you now have a folder sugar-logviewer-activity.
[15:53] <Neeraj> lfaraone, ok, doing that
[15:54] <dfarning> lfaraone, I have lost track of which activites need attention.  I have been focused on what skill we need to learn.
[15:54] <lfaraone> dipankar: so, now edit debian/rules.
[15:55] <dfarning> Neeraj, please correct me if I ask you to do something which has already been done:)
[15:55] <lfaraone> dipankar: we want it to look something like http://git.debian.org/?p=collab-maint/sugar-terminal-activity.git;a=blob;f=debian/rules;h=fd04db13856a54e6412948d5bfb46d811a35a378;hb=HEAD , minus the VTE stuff on lines 17 and 16.
[15:55] <lfaraone> * 17 / 18
[15:55] <ankurkhurana> dfarning, good morning
[15:55] <lfaraone> dipankar: and change sugar-terminal-activity to meet what you think it should read.
[15:56] <lfaraone> dipankar: then commit your changes to rules with a descriptive commit message.
[15:56] <dfarning> ankurkhurana, good morning.
[15:58] <ankurkhurana> dfarning, , i was uploading packages for 10.10 ,and that task would soon be completed , so what what i am supposed to do next ?
[15:58] <dipankar> lfaraone, this is weird, There is only a debian folder and log.activity file. This is a bit confusing
[16:01] <lfaraone> dipankar: ugh. this package was done oddly.
[16:01] <lfaraone> dipankar: so this will be an exercise in doing a package from scratch, then.
[16:02] <lfaraone> dipankar: keep your old sugar-logviewer-activity folder around, we'll reference it later.
[16:02] <lfaraone> dipankar: in the mean time, download the latest version of Log from http://download.sugarlabs.org/sources/sucrose/fructose/Log/
[16:02] <ankurkhurana> dipankar,  am i connected ?
[16:02] <dipankar> ankurkhurana, yup..
[16:02] <dipankar> mtnl! :P
[16:03] <dfarning> ankurkhurana, how do they work?
[16:03] <lfaraone> dipankar: then create a new git repository, and use "git-import-orig -u UPSTREAM_VERSION PATH_TO_UPSTREAM_TARBALL.tar.bz2" inside your new repository
[16:03] <dipankar> lfaraone, Now I am really confused. Let me get this: I am editing debian/rules right now for sugar-logviewer-activity using the site you have told
[16:04] <ankurkhurana> they were not built yet so i haven't checked them, next thing on list :)
[16:04] <dipankar> lfaraone, after that? sorry, I completely lost track.
[16:05] <lfaraone> dipankar: okay, just ignore what I said earlier, I was thinking of how to proceed out load.
[16:05] <lfaraone> *loud
[16:05] <lfaraone> dipankar: so you edited debian/rules, and you've committed your changes?
[16:06] <dfarning> ankurkhurana, ok then how about installing a debian test system. I belive that Neeraj has experience with this.
[16:07] <dipankar> lfaraone, committing..
[16:07] <ankurkhurana> dfarning,  sounds good. Also is launchpad server down? can you check with that , it is not opening :(
[16:08] <dfarning> ankurkhurana, I think so.
[16:08] <lfaraone> ankurkhurana: try http://downforeveryoneorjustme.com/ :)
[16:08] <Neeraj> dfarning, kandarpk installed debain test system.. I will try to do the same tonight
[16:09] <dipankar> lfaraone, done
[16:09] <lfaraone> dipankar: now, we need to create a remote repository on alioth so we have somewhere to put your changes.
[16:10] <dfarning> ankurkhurana, Neeraj yes, please do.  Our goal is for everyone to have a ubuntu 10.04 working envirnment, a 10.10 test envirnment and a debian test envirnment.
[16:10] <lfaraone> dipankar: so ssh into git.debian.org, and follow the steps for setup-repository at http://wiki.debian.org/Alioth/Git#CollabMaintproject
[16:10] <kandarpk> Neeraj, the process in the documentation I sent you
[16:10] <dipankar> lfaraone, That mean this package is not in debian packages? We have to do it now?
[16:10] <kandarpk> might be a bit different for netinstall cd
[16:10] <ankurkhurana> so i think me and neeraj will set up a debian test environment , tonight
[16:11] <kandarpk> mentioned in it
[16:11] <lfaraone> dipankar: well, puttting it on alioth.debian.org doesn't put it "in debian", we'll do that when we're finished at the end.
[16:11] <lfaraone> dipankar: right now we're just putting the git repo on alioth so others can see our work.
[16:11] <dipankar> lfaraone, ok..
[16:12] <kandarpk> Neeraj, please download CD-1 if you are following the documentation
[16:13] <ankurkhurana> launchpad is up again :)
[16:13] <Neeraj> kandarpk,ok
[16:17] <lfaraone> dipankar: were you able to create the repository
[16:17] <lfaraone> ?
[16:18] <ankurkhurana> lfaraone,  i will have to download whole 100mb file of sugar activities to upload again? any other way out?
[16:18] <lfaraone> ankurkhurana: well, I don't know what you're trying to do.
[16:19] <dfarning> ok, I am going to log out and work on a work plan for the next couple of days.
[16:19] <ankurkhurana> well i am trying to download the source file fo sugar-activites and then upload it again to maverick ppa
[16:19] <dipankar> lfaraone, a good description of logviewer activity ? :)
[16:19] <Neeraj> lfaraone, dipankar  I have imported the orig file in git repository.. now what should I do
[16:19] <lfaraone> dipankar: for alioth, we usually just say "Packaging for sugar-logviewer-activity" or something.
[16:19] <lfaraone> dipankar: those descriptions are pretty meaningless :)
[16:20] <lfaraone> Neeraj: do you have an alioth account?
[16:20] <Neeraj> lfaraone,  yes.. while importing I didn't used pristine tar cmd
[16:20] <lfaraone> Neeraj: okay. you should probably remove and recreate the repository using the pristine tar falg.
[16:21] <lfaraone> flag
[16:21] <ankurkhurana> kandarpk,  i have not received any documentation regarding debian test system :(, can you send it to me again
[16:21] <Neeraj> k.. doing so
[16:21] <kandarpk> Neeraj
[16:21] <kandarpk> plz edit the iso cd location in it
[16:21] <dipankar> lfaraone, done: Made a new repo for sugar-logviewer :)
[16:22] <ankurkhurana> I am going for dinner, will be take some time :).
[16:23] <ankurkhurana> lfaraone,  I was asking that i have to upload sugar-activities for maverick , do i need to download them or is there any other way out.
[16:23] <lfaraone> ankurkhurana: nope.
[16:24] <Neeraj> lfaraone, done
[16:24] <dipankar> lfaraone, what do i do next?
[16:24] <lfaraone> dipankar: okay. so add the remote git location to your local repository and push up to it. use "git remote add origin PATH_TO_REMOTE_GIT_REPO" (origin here is a name, you could call it hot-forking-action for all git cares), then "git push --all origin" to push all local refs to origin.
[16:25] <ankurkhurana> lfaraone, nope is for what ?
[16:25] <lfaraone> dipankar: can you guess that the PATH_TO_REMOTE_GIT_REPO is?
[16:25] <dipankar> ankurkhurana, you have to download them :)
[16:25] <lfaraone> ankurkhurana: you are trapped in a maze of twisty passages, all alike. there is no way out.
[16:26] <ankurkhurana> lfaraone,  clever example :) , dipankar  thanks
[16:26] <dipankar> lfaraone, is it 'git+ssh://git.debian.org/git/collab-maint/sugar-logviewer-activity.git'?
[16:27] <lfaraone> dipankar: looks shiny to me.
[16:27] <ankurkhurana> i am off for dinner
[16:27] <ankurkhurana> :)
[16:27] <dipankar> lfaraone, so i need to add this repo to my local one?
[16:27] <dipankar> ankurkhurana, ~njoy!
[16:27] <lfaraone> dipankar: yep. git-remote is your friend, with regards to that.
[16:28] <lfaraone> dipankar: basically, it lets you track a remote repository from your local one.
[16:28] <lfaraone> dipankar: so add the remote repository to your local, and push up.
[16:28] <dipankar> lfaraone, ok, the _tracking_
[16:32] <dipankar> lfaraone, error: fatal: '/git/collab-maint/sugar-logviewer-activity.git' does not appear to be a git repository
[16:32] <dipankar> fatal: The remote end hung up unexpectedly
[16:34] <dipankar> lfaraone, I think we have to wait for sometime before the git repo is actually online
[16:34] <Neeraj> lfaraone, I have completed importing using pristine cmd..
[16:37] <lfaraone> possibly
[16:40] <lfaraone> Neeraj: are you a member of collab-maint and debian-olpc?
[16:41] <Neeraj> yes
[16:42] <Neeraj> I am member of both.
[16:43] <lfaraone> dipankar: try again.
[16:44] <lfaraone> Neeraj: okay. ssh into git.debian.org and create a repository for your package as dipankar did.
[16:45] <dipankar> lfaraone, Nopes. Still the same: Please check the command: git push git+ssh://git.debian.org/git/collab-maint/sugar-logviewer-activity.git
[16:45] <dipankar> lfaraone, I am out for dinner..
[16:45] <lfaraone> dipankar: okay, have fun.
[16:46] <lfaraone> dipankar: does "git push origin --all" work? :)
[16:46] <dipankar> lfaraone, :P I guess I was trying with wrong command
[16:47] <lfaraone> dipankar: well, that command sounds like it'll work, but try the one I provided.
[16:47] <dipankar> lfaraone, same result :(
[16:47] <dipankar> lfaraone, I guess we have to wait.
[16:48] <lfaraone> dipankar: well, that's not what the alioth people I'm talking to say...
[16:48] <lfaraone> dipankar: uh, you mispelled "activity" on alioth.
[16:48] <dipankar> lfaraone, brb in 15
[16:48] <lfaraone> you created /git/collab-maint/sugar-logviewer-acitvity.git
[16:48] <dipankar> yyup
[16:49] <lfaraone> dipankar: acitivity != activity :)
[16:49] <lfaraone> dipankar: okay. I've renamed the repo. Try one last time :)
[17:05] <dipankar> everyone, back
[17:05] <Neeraj> lfaraone, I added my ssh pub key on my alioth a/c.. Now ssh git.debian.org is giving Connection time out Error
[17:06] <lfaraone> Neeraj: okay. see http://wiki.debian.org/Alioth/SSH#I.27munabletoConnectviaSSH.2C...
[17:06] <manusheel> dipankar: Good to see you back.
[17:07] <dipankar> lfaraone, http://paste.ubuntu.com/457890/
[17:07] <dipankar> manusheel, hello Sir :)
[17:07] <manusheel> dipankar: Hi Dipankar.
[17:07] <manusheel> dipankar: How are things coming along?
[17:08] <lfaraone> dipankar: lol. you seriously called it hot-forking-action? that made my day.
[17:08] <dipankar> manusheel sir, Luke is guiding in an excellent way. We now have a git repository for sugar-logviewer-activity.
[17:09] <dipankar> lfaraone, I wanted to have some fun :P
[17:09] <manusheel> dipankar: Great. Glad to hear.
[17:09] <lfaraone> dipankar: so you can now see the repository at http://git.debian.org/?p=collab-maint/sugar-logviewer-activity.git;a=summary
[17:10] <dipankar> lfaraone, got it.
[17:10] <lfaraone> dipankar: so now when you look at debian/rules, is there anything there that looks like it might need to be changed since you copied the text over from sugar-terminal-activity into sugar-logviewer-activity?
[17:11] <dipankar> lfaraone, who is Jani Monoses?
[17:11] <lfaraone> dipankar: https://launchpad.net/~jani
[17:11] <lfaraone> dipankar: the original person who packaged a bunch of sugar stuff, then lost time to continue working on it, if i recall correctly.
[17:12] <dipankar> lfaraone, ohk.
[17:12] <dipankar> lfaraone, let me check the rules file
[17:13] <lfaraone> with regards to debian/rules, there's one thing that jumps out at me. let me know what you find.
[17:14] <dipankar> lfaraone, line no. 6
[17:14] <dipankar> lfaraone, it is having DEB_PYTHON_SUGAR_PACKAGES = sugar-terminal-activity
[17:14] <lfaraone> dipankar: yeah. change that to what you think it should read.
[17:15] <dipankar> lfaraone, rest I guess is fine
[17:15] <lfaraone> dipankar: yep.
[17:15] <dipankar> lfaraone, shall I add it now?
[17:15] <lfaraone> dipankar: yep.
[17:17] <dipankar> lfaraone, done
[17:19] <lfaraone> dipankar: okay. now do steps 1, 2 of http://build-common.alioth.debian.org/cdbs-doc.html#id2562500 , commit your changes, then do step 4 using the DEB_MAINTANER_MODE command I provided earlier, and commit.
[17:19] <lfaraone> dipankar: so we can use automagic dependency handling.
[17:26] <Neeraj> lfaraone, ok.. my connection port was blocked by firewall... I am finally able to log into alioth
[17:27] <kandarpk> dfarning, hi
[17:27] <dfarning> kandarpk, hello
[17:27] <lfaraone> okay.
[17:28] <dipankar> lfaraone, is this how the control.in file should look like : http://paste.ubuntu.com/457900/?
[17:28] <kandarpk> dfarning, tried looking for some information on those bugs
[17:28] <kandarpk> couldn't find much
[17:29] <kandarpk> dfarning, how do I approach ?
[17:29] <dipankar> lfaraone, oops, made some mistake. Let me read through the web page once again
[17:30] <dfarning> kandarpk, will you be around in the morning?
[17:31] <kandarpk> I wont be on my PC then
[17:31] <dfarning> I am babysitting my sisters kids and can't have a focused conversation:)
[17:31] <kandarpk> Ok.
[17:32] <kandarpk> dfarning, suggest something that I should be doing ..
[17:32] <kandarpk> will ask you in the morning my doubts then
[17:35] <dipankar> lfaraone, ?
[17:35] <lfaraone> dipankar: yep?
[17:35] <dipankar> lfaraone, was the control.in file okay?
[17:36] <dipankar> lfaraone, here : http://paste.ubuntu.com/457900/?
[17:37] <lfaraone> dipankar: sure.
[17:38] <dipankar> lfaraone, shall I commit the changes then?
[17:39] <lfaraone> dipankar: go ahead. undoing a commit if you break something is trivial.
[17:42] <lfaraone> dipankar: anyway, I'm off to lunch. I'll mail you some thoughts on things to do by your tomorrow.
[17:43] <dipankar> lfaraone, made mistake I guess.
[17:43] <dipankar> lfaraone, I would like to continue tomorrow morning.
[17:44] <dipankar> lfaraone, sure.
[17:44] <lfaraone> dipankar: of course. i'll just go through the packaging and make some comments on things that need fixing before it's done./
[17:44] <lfaraone> oops.
[17:47] <neeraj_> lfaraone, ping me whenever you come back after having lunch.. :)
[17:50] <ankurkhurana> neeraj see the hello package in ppa
[17:50] <ankurkhurana> it seems different
[17:50] <ankurkhurana> while i try you too please take a look into it
[17:50] <ankurkhurana> neeraj,
[17:50] <ankurkhurana> wil you?
[17:51] <neeraj> wait
[17:51] <neeraj> hello package?
[17:51] <ankurkhurana> yes
[18:37] <manusheel> lfaraone: Luke, around?
[19:45] <dfarning> kandarpk, are you around?
[19:45] <kandarpk> dfarning, hi
[19:46] <dfarning> kandarpk, sorry I had to leaves do fast. I was babysitting my sisters 5 kids and one of them spilled a pitcher of milk:(
[19:47] <kandarpk> :(
[19:47] <kandarpk> its ok
[19:47] <dfarning> kandarpk, do have time to look at the bugs/bug reports or are you working on something else
[19:48] <kandarpk> I tried to
[19:49] <kandarpk> but could find much help
[19:49] <kandarpk> *couldn't
[19:50] <kandarpk> dfarning, Where should I look for it ?
[19:52] <dfarning> ok let's take a step back.  Last night we looked at the 'restart now' error.  What is your next possiable bug?
[19:53] <dfarning> kandarpk, Let't turn it into a bug report at http://openetherpad.org/0OCNClgARq
[19:54] <kandarpk> reading activity does not start
[19:55] <dfarning> hmmm ok before we file a bug on that one let's check the version number in debian and on activities.sugarlabs.org.
[19:56] <kandarpk> wait
[19:56] <dfarning> that way we might just request an update
[19:56] <kandarpk> I'll log into debian
[19:59] <kandarpk> dfarning, the version of read activity is
[20:00] <kandarpk> 78-4
[20:00] <kandarpk> 0.86
[20:01] <dfarning> kandarpk, did you find the version on ASLO
[20:02] <kandarpk> no
[20:02] <dfarning> kandarpk, http://activities.sugarlabs.org/en-US/sugar/addon/4028
[20:03] <kandarpk> its 86 there
[20:04] <dfarning> since there is a more recent version in aslo let's file a request to update in the debain bug tracker.
[20:05] <kandarpk> the version installed on my system too is 0.86
[20:05] <dfarning> kandarpk, we can just forget about the bug not starting problem until we are working with an upto date package.
[20:08] <kandarpk> dfarning, what should I be looking for ?
[20:10] <dfarning> kandarpk, what do you mean?
[20:11] <kandarpk> the version number in synaptic is written as 78-4
[20:12] <kandarpk> while the name of the package is sugar-read-activity-0.86
[20:14] <dfarning> ok that is a bit confusion at first.  the versions of sugar are .84 .86, and .88
[20:15] <kandarpk> so, what does 78-4 stand for ?
[20:15] <dfarning> jonas tries to to keep all of them in sync. as such for allmost every sugar package the name in debian is *-.8*
[20:16] <dfarning> the 78-4 refers to the actual version of read contained in  sugar-read-activity-0.86
[20:16] <kandarpk> Ok.
[20:17] <dfarning> but then when we look in aslo we see that the most recent version of read is 86. which is newer than 78-4.
[20:18] <kandarpk> Ok.
[20:19] <kandarpk> dfarning, how do I update it ?
[20:19] <kandarpk> *sugar-read
[20:20] <dfarning> kandarpk, this is something that you will have to learn from dipankar in the next couple of days:)
[20:21] <kandarpk> does it involve using git ?
[20:21] <dfarning> kandarpk, luke tought dipankar.  I think that dipankar will be teaching neeraj tomorrow.  and then together they will teach you.
[20:22] <kandarpk> Ok.
[20:22] <dfarning> kandarpk, yes, from now on we will be doing all of our packaing in git.  and then maintaining branches for debian, ubuntu 10.04, and 10.10
[20:23] <kandarpk> what should I be doing till then ?
[20:23] <dfarning> kandarpk, I don't understand git well enough to teach it:(
[20:23] <kandarpk> no problems
[20:24] <dfarning> do you have another possiable bug to report.
[20:24] <kandarpk> selecting language
[20:24] <kandarpk> does not result into anything
[20:24] <kandarpk> except for the appearance of cross and tick
[20:25] <kandarpk> on top right side
[20:25] <dfarning> ok let's look at that. I think that might be a hard one.. IIRC the sugar translations are handled differently than the debian/ubuntu translations.
[20:26] <kandarpk> that means installing language packs under debian wont effect sugar-language ?
[20:28] <dfarning> kandarpk, let's ask alsroot on sugar.  Can you start drafting the question at http://openetherpad.org/0OCNClgARq ?
[20:28] <kandarpk> sure
[20:31] <manusheel> kandarpk, dfarning: Great.
[20:31] <manusheel> kandarpk: Once we are done with bug no.s #1, 3 and 5, Kandarp, we should look at #2 and 4.
[20:32] <dfarning> kandarpk, lets just start with an informal question to alsroot telling him we are doing and if he has advice on how to move forward.
[20:33] <dfarning> manusheel, thanks  kandarpk is learning the fine art of commicating with on open source community.
[20:33] <dfarning> s/on/an/
[20:34] <manusheel> dfarning: Great. Glad to hear. That is a very important skill set.
[20:36] <kandarpk> dfarning, I have written it as in a bug report
[20:36] <kandarpk> looks ok ?
[20:38] <dfarning> kandarpk, sorry, I got called into a meeting.
[20:38] <dfarning> back in a few. while we wait can you start looking at the next issue
[20:39] <kandarpk> dfarning, wont be able to wait for long
[20:40] <kandarpk> its 1:00 AM here
[20:40] <dfarning> ok lets talk tomorrow.
[20:41] <kandarpk> ok.
[20:41] <kandarpk> i'll be ready for your feedback
[20:41] <kandarpk> on the report