[00:01] <nagappan> jtatum, have you created a deb package for python project ?
[00:01] <nagappan> jtatum, I'm planing to create Ubuntu 9.04 package for LDTPv2
[00:02] <jtatum> nagappan: It's pretty simple if there is a working setup.py.
[00:02] <nagappan> jtatum, not sure, how to create the diff.gz
[00:02] <nagappan> jtatum, awesome :)
[00:02]  * nagappan listening jtatum 
[00:02] <nagappan> {}
[00:02] <jtatum> nagappan: just a sec, let me power on that vm
[00:02] <nagappan> jtatum, sure
[00:04] <jtatum> nagappan: did you already setup the debian dir?
[00:04] <nagappan> jtatum, nope
[00:04] <nagappan> jtatum, http://cgit.freedesktop.org/ldtp/ldtp2/
[00:07] <jtatum> nagappan: ok, pulling it down
[00:09] <nagappan> jtatum, ok
[00:12] <jtatum> nagappan: lol. firewall here does not allow it :) that's OK though. you need a debian dir. to bootstrap it, change to a temp directory and apt-get source mago
[00:14] <nagappan> jtatum, sure
[00:15]  * nagappan doing now
[00:15] <nagappan> jtatum, mago not available on Ubuntu 9.04 I think ?
[00:16] <jtatum> nagappan: ah, you're right. that's ok, we can just pastebin everything
[00:16] <nagappan> jtatum, :)
[00:16] <nagappan> jtatum, I actually tried and I got the error "E: Unable to find a source package for mago", then realized that ara built it only for Karmic :)
[00:16] <jtatum> nagappan: i assume you have the source for ldtp2 somewhere. in the root of that directory, create a dir named debian. we'll just add the handful of needed files.
[00:17] <nagappan> jtatum, sure
[00:17] <nagappan> jtatum, done
[00:17] <nagappan> jtatum, next
[00:17] <nagappan> {}
[00:18] <jtatum> nagappan: a couple of lines to throw in .bashrc - export DEBEMAIL="naggapan@gmail.com"
[00:18] <jtatum> export DEBFULLNAME="Naggapan"
[00:18] <nagappan> jtatum, sure
[00:19] <nagappan> jtatum, you know, actually I use openSUSE build service for building Ubuntu / Debian / SUSE / RedHat based LDTP package, so I guess I don't need this entry !?!
[00:20] <nagappan> jtatum, http://download.opensuse.org/repositories/home:/anagappan/
[00:20] <jtatum> hm. not sure. dch reads it for sure, and I think other things will as well, for instance if you are going to upload it to a PPA
[00:20] <nagappan> jtatum, ok
[00:20] <jtatum> that's interesting though, not familiar with the opensuse builder
[00:21] <jtatum> ok. your source dir should be named something like ldtpv2-0.99.whatever
[00:21] <jtatum> package-version
[00:21] <nagappan> jtatum, I grabbed ldtp dsc from Debian and uploaded to there and it build the package for me
[00:21] <jtatum> neat
[00:21] <nagappan> jtatum, sure
[00:21]  * nagappan renaming the folder
[00:23] <nagappan> jtatum, done
[00:23] <jtatum> inside that directory, run dch --create --package ldtpv2 -v 0.99.whatever --distribution jaunty
[00:24] <nagappan> jtatum, sure
[00:24] <jtatum> the changelog has kind of a prickly format. if you're happy with the single bullet, it should be ok. if you want to add more stuff, you probably want to read one of the packaging guides.
[00:24]  * nagappan installing devscripts package
[00:25] <jtatum> :) thank you command-not-found for catching my mistake :)
[00:28] <nagappan> jtatum, :)
[00:28] <jtatum> nagappan: should have debian/changelog after running dch. next, debian/control. http://pastebin.com/m4ee4fbac <- mago's control file
[00:29] <nagappan> jtatum, yes, it has created the file debian/changelog
[00:29] <jtatum> The control file describes the source package and the resulting binary package. so you'll want to s/mago/ldtpv2, remove XSBC-Original-Maintainer (this is for uploading stuff to ubuntu proper), change maintainer to you
[00:30]  * nagappan doing debian/control
[00:30] <jtatum> The depends may need some tweaking. The system detects depends from setup.py, but you can specify others here if they get missed.
[00:31] <jtatum> for now you probably want Depends: ${misc:Depends}, ${python:Depends}
[00:31] <jtatum> remove line 14
[00:33] <nagappan> jtatum, I want to remove ldtpv1 if its installed
[00:33] <nagappan> jtatum, guess conflict
[00:33] <nagappan> jtatum, is the tag ?
[00:33] <jtatum> yes. also your binary package (line 11) should probably be python-ldtpv2
[00:33] <jtatum> to stay consistent with other py libs
[00:34] <nagappan> jtatum, sure
[00:36] <jtatum> debian/rules - http://pastebin.com/mc0748d6
[00:36] <nagappan> jtatum, control file created
[00:36] <nagappan> jtatum, let me create rules now
[00:37] <nagappan> jtatum, we don't have man page for now
[00:37] <jtatum> a lot of magic happens here. cdbs automates a lot of junk. in ye olden days, this rules file would be long and complicated to behold :)
[00:37] <jtatum> right, remove that line
[00:37] <nagappan> jtatum, can I ignore this ?
[00:37] <nagappan> jtatum, ok
[00:38] <nagappan> jtatum, done
[00:38] <jtatum> echo 7 > debian/compat
[00:39] <nagappan> launchpad.net is up now !!!
[00:39]  * nagappan creating compact file
[00:39] <jtatum> echo 2 > debian/pycompat
[00:39] <nagappan> jtatum, done, both the files
[00:40] <jtatum> one more file, copyright. checking to see if it's required.
[00:40] <nagappan> jtatum, sure
[00:42] <jtatum> easier to just create I guess. debian/copyright: http://pastebin.com/m764af635
[00:42] <jtatum> (didn't paste the whole GPL)
[00:44] <jtatum> I forgot an important step. the orig tar file. mv the debian directory somewhere outside your source directory.
[00:44] <jtatum> we need to create a .tar.gz that includes only your source, not the debian dir
[00:45] <jtatum> so if the dir is ldtpv2-0.99.0. you'll want to tar -czvf ldtpv2_0.99.0.orig.tar.gz <-- note the - changes to an _ in the orig
[00:46] <jtatum> the packaging tools are dash and underscore sensitive :)
[00:46] <jtatum> they'll magically detect this orig file and use it to create the changes file
[00:49] <jtatum> nagappan: ^^
[00:49] <nagappan> jtatum, sure, just saw the above message
[00:50] <nagappan> jtatum, we have LGPL
[00:50] <nagappan> jtatum, will get it from LDTPv1
[00:50] <jtatum> that's fine :)
[00:53] <nagappan> jtatum, created copyright file
[00:53] <jtatum> nagappan: ok
[00:55] <nagappan> jtatum, I have the source file created using python setup.py sdist, is that okay ?
[00:55] <nagappan> jtatum, now whats the next step ?
[00:56] <jtatum> nagappan: that should be OK. did you create the .orig.tar.gz ?
[00:59] <nagappan> jtatum, just rename that file should be good ?
[00:59] <nagappan> jtatum, which was created by python setup.py sdist ?
[00:59] <jtatum> i would suggest creating a new one.
[01:00] <jtatum> you want to capture your ldtpv2-whatever dir as it is now, including any .git or whatever directories might be in it
[01:00] <nagappan> jtatum, nope, sdist doesn't create them
[01:00] <jtatum> that is a problem
[01:00] <nagappan> jtatum, what ever we have mentioned in MAINFEST, it will create
[01:00] <jtatum> nagappan: otherwise, when you copy the debian folder in, and run the scripts to build the .dsc and .changes file, it will create diffs for a whole bunch of junk
[01:01] <nagappan> jtatum, ah ! ok
[01:02] <nagappan> jtatum, I have created the tar.gz
[01:02] <nagappan> jtatum, tar the complete folder
[01:02] <jtatum> ok. move the debian dir back in, change into the dir and run debuild -S -sa
[01:02] <nagappan> jtatum, sure
[01:04] <jtatum> curious to hear what errors if any come up :)
[01:04] <nagappan> jtatum, I get http://pastebin.com/d4290ccbc
[01:04] <jtatum> lintian is invoked against your package as well
[01:05] <jtatum> nagappan: ah, need apt-get install cdbs
[01:05]  * nagappan installing cdbs as suggested by jtatum :)
[01:06] <jtatum> it's also going to sign all your packages. it should pull your email address from changelog and it will feed that to gpg, so if you're prompted for a keyphrase by debuild, it's for your gpg key
[01:08] <nagappan> jtatum, http://pastebin.com/d6f9206cc I get different error
[01:09] <jtatum> pastebin debian/control, please?
[01:09] <jtatum> i think this is probably dir naming, nagappan
[01:10] <nagappan> jtatum, http://pastebin.com/d1c59467b
[01:10] <nagappan> jtatum, ah ! ok
[01:10] <jtatum> directory should be ldtpv2-2.0.1
[01:10] <jtatum> Source: should be ldtpv2
[01:10] <nagappan> jtatum, let me change it now
[01:10] <jtatum> oh - sorry
[01:10] <jtatum> ldtp2
[01:10] <jtatum> source: and directory name should agree
[01:11] <jtatum> also don't forget to rename .orig.tar.gz
[01:12] <nagappan> jtatum, changing the folder to ldtp2 or ldtpv2 doesn't help
[01:13] <nagappan> jtatum, getting same error message
[01:13] <jtatum> what's folder name?
[01:13] <nagappan> jtatum, ldtpv2, also tried ldtp2
[01:13] <jtatum> the exact folder  name is ldtp2?
[01:13] <jtatum> should be ldtp2-2.0.1
[01:13] <nagappan> jtatum, ah ! ok
[01:13] <jtatum> tar file should be ldtp2_2.0.1.orig.tar.gz
[01:14] <jtatum> first line of debian/control should be Source: ldtp2
[01:14] <jtatum> (leave Package: line as is)
[01:16] <nagappan> jtatum, now a diff error, the above one passed
[01:17] <nagappan> jtatum, gpg: skipped "Nagappan <nagappan@gmail.com>": secret key not available
[01:17] <nagappan> gpg: [stdin]: clearsign failed: secret key not available
[01:17] <nagappan> debsign: gpg error occurred!  Aborting....
[01:17] <nagappan> debuild: fatal error at line 1250:
[01:17] <jtatum> do you have a gpg key?
[01:17] <nagappan> jtatum, I need to have my gpg pub keys ?
[01:17] <nagappan> jtatum, yes :)
[01:17] <jtatum> you need your pivate key actually :)
[01:17] <nagappan> jtatum, will copy it to my development box
[01:19] <nagappan> jtatum, I have already id_rsa and id_rsa.pub in my ~/.ssh folder
[01:20] <jtatum> those are ssh keys, not gpg
[01:21] <nagappan> jtatum, ah ! my bad, let me get my gpg now
[01:22] <jtatum> you can tack on a -us -uc to skip signing. your build system may or may not think that's important. it also makes a difference at install time. users can trust your gpg key after they add your repo. otherwise, they will get an error.
[01:22] <nagappan> jtatum, I have this http://pgp.mit.edu:11371/pks/lookup?search=nagappan&op=index
[01:22] <nagappan> jtatum, created 2005, forgot about it :) as it was too long
[01:23] <jtatum> nagappan: that's your public key :) guess your private key is lost
[01:23] <jtatum> no worries. try -us -uc
[01:23] <nagappan> jtatum, sure
[01:23] <jtatum> can always rebuild and sign it later
[01:24] <jtatum> so that should generate the .dsc and .changes, which you'll feed to your builder. hopefully it builds :)
[01:25] <nagappan> jtatum, sure, thanks :)
[01:26] <jtatum> nagappan: np :) heading home, afk a bit
[01:26] <nagappan> jtatum, sure
[01:26] <nagappan> jtatum, I get this
[01:26] <nagappan> E: ldtp2 source: missing-build-dependency cdbs
[01:26] <nagappan> W: ldtp2 source: unknown-field-in-dsc original-maintainer
[01:26] <nagappan> jtatum, will add cdbs
[01:26] <jtatum> nagappan: from your builder?
[01:27] <nagappan> jtatum, from this debuild -S -sa -us -uc
[01:27] <jtatum> nagappan: hm... ah. yes, cdbs needs to be one of the build-depends
[01:29] <nagappan> jtatum, ok, fixed most of the warnings
[01:29] <jtatum> nagappan: great! the original maintainer can be ignored or removed from control, it's not necessary for a private package
[01:29] <nagappan> jtatum, ok
[01:30] <rmcbride> nagappan: your bug number is 435570. I'm trying to get the log attached but firefox is not cooperating (or maybe it's the new LP drop)
[01:30] <nagappan> rmcbride, sure, thanks :)
[01:31] <rmcbride> nagappan: I'm going to leave my browser spinning for a bit and then I'll restart it and tretry the attach
[01:32] <nagappan> rmcbride, sure, thanks :)
[01:32] <nagappan> jtatum, thanks for guiding this layman :)
[01:33] <jtatum> nagappan: in case your builder gives you trouble, you may want to google pbuilder. it's a pretty great build system for debian/ubuntu which creates a full chroot, installs build depends and builds in a very clean environment, then spits out the binaries.
[01:33] <jtatum> nagappan: no problem :) my pleasure :)
[01:33] <nagappan> jtatum, sure
[01:47] <rmcbride> nagappan: Ah, either you're not behind a firewall/proxy anymore or the problem was the LP update teh whole time I guess :)
[01:48] <rmcbride> just saw your comment once my browser started talking again
[01:48] <nagappan> rmcbride, I can access the web through proxy, but apport-cli could not upload the logs, as it doesn't understand https proxy
[01:49] <rmcbride> nagappan: AH! OK
[01:49] <rmcbride> nagappan: I'm going to be out the rest of the night. I was able to get the apport-cli log attached.
[01:49] <nagappan> rmcbride, that has been fixed in karmic, but the issue here is karmic is not getting installed on this, probably I should try installing karmic on some other box and then report the issue :)
[01:50] <nagappan> rmcbride, cool, thanks :)
[01:50] <rmcbride> nagappan: any time :)
[02:06] <jtatum> nagappan, how's the package look? :)
[02:10] <nagappan> jtatum, oops, I haven't looked at it yet, got into diff work, will look now
[02:10] <nagappan> jtatum, sorry
[02:14] <jtatum> lol, nagappan, no worries :)
[06:44] <ara> good morning all!
[08:37] <davmor2> Morning all
[08:44] <whereisdarran> mornin brotha
[08:44] <whereisdarran> from nz
[08:57] <davmor2> whereisdarran: evening then
[09:15] <whereisdarran> thanks brotha
[09:15] <whereisdarran> how you doin davmor2
[09:15] <davmor2> whereisdarran: sound as a pound you?
[09:16] <whereisdarran> hangin in there
[09:16] <whereisdarran> been under the weather since monday
[09:16] <whereisdarran> but trying to get back on top
[11:40] <ara> popey, ping
[12:00] <davmor2> ara: try popey again now :)
[12:00] <ara> popey, hello :)
[12:01] <davmor2> ara: actually looking at his gmail ac it says he's not here so he must of just signed onto his facebook ac
[12:37] <popey> davmor2: stalker
[12:37] <popey> ara: pong
[12:38] <ara> popey, don't worry. I wasn't having any sound with recordmydesktop, but I asked dholbach and he gave me a script that you had given him
[12:38] <ara> popey, it works now :)
[12:38] <popey> :)
[12:45] <davmor2> popey: not my fault that we are signed up on most of each others accounts :)
[13:07] <davmor2> fader|away: alternates are bust still cjwatson has uploaded a fix can you let cr3 know please :)
[14:40] <davmor2> cr3: alternates are still bust dude
[14:40] <davmor2> cr3: morning by the way :)
[14:41] <cr3> davmor2: thanks for the heads up, but desktops are fine?
[14:42] <davmor2> cr3: seem to be although today's iso your network tests may fail in live cd mode
[14:42] <cr3> I haven't gotten any desktop results either, which seems to indicate there might be a problem there as well
[14:43] <davmor2> cr3: live desktop's nm is just spiralling apparently there is a new version uploaded already
[14:44] <davmor2> cr3: I don't know if or how that might effect you.  But if you are running the install as a pxe boot then that might be the cause the minute the desktop comes up you lose networking that would be a cause for the install to fail :)
[14:44] <cr3> davmor2: cool, and I just fixed a bug in my mago integration, so I might be able to test the new desktop image and that at the same time
[16:06] <ara> popey, ping
[16:10] <popey> ara: lo
[16:11] <ara> popey, can you have a look? http://people.canonical.com/~ara/temp/iso-tracker.avi
[16:11] <ara> popey, if you approve, feel free to upload it to screencast.u.c
[16:11] <ara> popey, thanks
[16:11] <cr3> ara: btw, you might like to mention in your indicator-applet README that the test depends on python-indicator
[16:12] <cr3> err, make that python-indicate
[16:12] <popey> \o/ awesome!
[16:12] <popey> ara: no, thank _you_
[16:13] <ara> cr3, OK. I will, thanks for telling me that
[16:13] <ara> cr3, btw, notify-osd tests are failing because the need the images to compare with
[16:14] <ara> cr3, maybe that's why they were appearing as faling?
[16:14] <cr3> ara: possible, I'll blacklist those as well then
[16:15] <ara> cr3, why??
[16:15] <cr3> ara: I have lots of machines with different resolutions, so I would need to introduce the concept of golden images on a per system basis
[16:16] <cr3> ara: if you have the spare cycles to implement this, let me know and we could work together on this
[16:16] <ara> cr3, we will need to discuss, marjo, you and I, the need of having mago tests running in all the machines. (which I think is not worth it)
[16:18] <cr3> ara: sure, if you want to work on the scheduler too, let me know. I'd like to implement something like the JESS rules engine to schedule where mago tests should run
[16:19] <cr3> ara: it would be nice for this rules engine to be able to schedule tests on multiple machines, because mago takes a rather long time to run and it will only get longer as times goes by. so, being able to balance the load across multiple machines might be worthwhile
[16:19] <ara> cr3, the number of hw related bugs mago tests could catch are so small I don't think it is worth it. I would prefer running mago tests always on the same machine. with all the needed data (like screenshots for comparison) is correct for that one
[16:20] <cr3> ara: cool, that doesn't need to run in certification then, why not a kvm instance on your machine overnight?
[16:21] <ara> cr3, no, thanks ;-)
[16:22] <cr3> ara: it could be a simple matter of: apt-get update; apt-get dist-upgrade; bzr pull mago; run mago. just do that at the end of your day and, voila, we gots daily tests :)
[16:23] <cr3> ara: or, we have a vmware esx server in the datacenter, how about there?
[16:25] <ara> cr3, I think all of those posibilities should be discussed with marjo first, don't you think?
[16:26] <cr3> ara: sure, but if you're not comfortable with the possibility of running it on your own hardware, I wouldn't even bother mentionning it to marjo
[16:28] <cr3> ara: I'd rather we consider possible possibilities together which can then be presented to marjo. so, you mentionned you just want to run it on a single machine. if that machine were running vmware esx, would that be a good solution for you?
[16:38] <ara> cr3, what I am suggesting is that maybe marjo WANTS to run it in the datacenter, as part of the certification tests
[16:41] <cr3> ara: ah, good point then, there are costs to introducing the concept of a golden image in order to run it across multiple machines or implementing the scheduler to only run on a single machine. and, marjo would be best positionned to make a decision on those costs
[16:41] <cr3> ara: however, karmic is pretty full right now, so I suspect this will have to be a karmic+1 thing
[16:42] <ara> cr3, indeed :)
[17:06] <davmor3> hey everyone wazzup?
[17:07] <davmor2> davmor3: nothing just chilling with a bud
[18:18] <popey> http://screencasts.ubuntu.com/2009/09/24/Ubuntu_Testing_-_ISO_Tracker \o/
[18:21] <jcastro> popey: \o/
[18:22] <popey> :)
[18:26]  * jpds \o/'s myself.
[18:26] <jpds> himself*
[18:37]  * davmor2 joins the belated mexican wave \o/
[19:11] <StefanAO> hello everybody...what is to be tested next monday?
[19:22] <cr3> StefanAO: what do you mean? which milestone release is to be tested?
[19:41] <StefanAO> i am new to this...i thought there would be some feature to test
[19:43] <cr3> StefanAO: there are always features to test :) since you are new to this, perhaps you might like to prepare for the beta release which will be available next week
[19:44] <cr3> StefanAO: to do so, you can have a look at the above URL pasted by popey and try testing an image or two
[19:44] <cr3> oh wait, you joined after popey pasted. here's the URL: http://screencasts.ubuntu.com/2009/09/24/Ubuntu_Testing_-_ISO_Tracker
[19:44] <cr3> this is a nice screencast that tells you everything you need to know to prepare for ISO testing
[20:33] <mikefletcher> Hi.  What time do the daily iso's get generated?  When a bug is marked 'Fix Released' does that mean the fix would be on the iso at that time?
[23:25] <FlyingBishop> If I'm building a new computer, should I run an install with 9.04 before trying out one of the alphas?
[23:26] <whereisdarran> probably
[23:26] <whereisdarran> if you want to know that your hardware is ok
[23:26] <whereisdarran> probably best to run stomething stable first
[23:26] <FlyingBishop> yeah that sounds wise I'll run a basic install then try the alpha
[23:29]  * popey hugs jpds