[00:01] jtatum, have you created a deb package for python project ? [00:01] jtatum, I'm planing to create Ubuntu 9.04 package for LDTPv2 [00:02] nagappan: It's pretty simple if there is a working setup.py. [00:02] jtatum, not sure, how to create the diff.gz [00:02] jtatum, awesome :) [00:02] * nagappan listening jtatum [00:02] {} [00:02] nagappan: just a sec, let me power on that vm [00:02] jtatum, sure [00:04] nagappan: did you already setup the debian dir? [00:04] jtatum, nope [00:04] jtatum, http://cgit.freedesktop.org/ldtp/ldtp2/ [00:07] nagappan: ok, pulling it down [00:09] jtatum, ok [00:12] 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] jtatum, sure [00:15] * nagappan doing now [00:15] jtatum, mago not available on Ubuntu 9.04 I think ? [00:16] nagappan: ah, you're right. that's ok, we can just pastebin everything [00:16] jtatum, :) [00:16] 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] 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] jtatum, sure [00:17] jtatum, done [00:17] jtatum, next [00:17] {} [00:18] nagappan: a couple of lines to throw in .bashrc - export DEBEMAIL="naggapan@gmail.com" [00:18] export DEBFULLNAME="Naggapan" [00:18] jtatum, sure [00:19] 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] jtatum, http://download.opensuse.org/repositories/home:/anagappan/ [00:20] 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] jtatum, ok [00:20] that's interesting though, not familiar with the opensuse builder [00:21] ok. your source dir should be named something like ldtpv2-0.99.whatever [00:21] package-version [00:21] jtatum, I grabbed ldtp dsc from Debian and uploaded to there and it build the package for me [00:21] neat [00:21] jtatum, sure [00:21] * nagappan renaming the folder [00:23] jtatum, done [00:23] inside that directory, run dch --create --package ldtpv2 -v 0.99.whatever --distribution jaunty [00:24] jtatum, sure [00:24] 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] :) thank you command-not-found for catching my mistake :) [00:28] jtatum, :) [00:28] nagappan: should have debian/changelog after running dch. next, debian/control. http://pastebin.com/m4ee4fbac <- mago's control file [00:29] jtatum, yes, it has created the file debian/changelog [00:29] 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] 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] for now you probably want Depends: ${misc:Depends}, ${python:Depends} [00:31] remove line 14 [00:33] jtatum, I want to remove ldtpv1 if its installed [00:33] jtatum, guess conflict [00:33] jtatum, is the tag ? [00:33] yes. also your binary package (line 11) should probably be python-ldtpv2 [00:33] to stay consistent with other py libs [00:34] jtatum, sure [00:36] debian/rules - http://pastebin.com/mc0748d6 [00:36] jtatum, control file created [00:36] jtatum, let me create rules now [00:37] jtatum, we don't have man page for now [00:37] 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] right, remove that line [00:37] jtatum, can I ignore this ? [00:37] jtatum, ok [00:38] jtatum, done [00:38] echo 7 > debian/compat [00:39] launchpad.net is up now !!! [00:39] * nagappan creating compact file [00:39] echo 2 > debian/pycompat [00:39] jtatum, done, both the files [00:40] one more file, copyright. checking to see if it's required. [00:40] jtatum, sure [00:42] easier to just create I guess. debian/copyright: http://pastebin.com/m764af635 [00:42] (didn't paste the whole GPL) [00:44] I forgot an important step. the orig tar file. mv the debian directory somewhere outside your source directory. [00:44] we need to create a .tar.gz that includes only your source, not the debian dir [00:45] 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] the packaging tools are dash and underscore sensitive :) [00:46] they'll magically detect this orig file and use it to create the changes file [00:49] nagappan: ^^ [00:49] jtatum, sure, just saw the above message [00:50] jtatum, we have LGPL [00:50] jtatum, will get it from LDTPv1 [00:50] that's fine :) [00:53] jtatum, created copyright file [00:53] nagappan: ok [00:55] jtatum, I have the source file created using python setup.py sdist, is that okay ? [00:55] jtatum, now whats the next step ? [00:56] nagappan: that should be OK. did you create the .orig.tar.gz ? [00:59] jtatum, just rename that file should be good ? [00:59] jtatum, which was created by python setup.py sdist ? [00:59] i would suggest creating a new one. [01:00] you want to capture your ldtpv2-whatever dir as it is now, including any .git or whatever directories might be in it [01:00] jtatum, nope, sdist doesn't create them [01:00] that is a problem [01:00] jtatum, what ever we have mentioned in MAINFEST, it will create [01:00] 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] jtatum, ah ! ok [01:02] jtatum, I have created the tar.gz [01:02] jtatum, tar the complete folder [01:02] ok. move the debian dir back in, change into the dir and run debuild -S -sa [01:02] jtatum, sure [01:04] curious to hear what errors if any come up :) [01:04] jtatum, I get http://pastebin.com/d4290ccbc [01:04] lintian is invoked against your package as well [01:05] nagappan: ah, need apt-get install cdbs [01:05] * nagappan installing cdbs as suggested by jtatum :) [01:06] 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] jtatum, http://pastebin.com/d6f9206cc I get different error [01:09] pastebin debian/control, please? [01:09] i think this is probably dir naming, nagappan [01:10] jtatum, http://pastebin.com/d1c59467b [01:10] jtatum, ah ! ok [01:10] directory should be ldtpv2-2.0.1 [01:10] Source: should be ldtpv2 [01:10] jtatum, let me change it now [01:10] oh - sorry [01:10] ldtp2 [01:10] source: and directory name should agree [01:11] also don't forget to rename .orig.tar.gz [01:12] jtatum, changing the folder to ldtp2 or ldtpv2 doesn't help [01:13] jtatum, getting same error message [01:13] what's folder name? [01:13] jtatum, ldtpv2, also tried ldtp2 [01:13] the exact folder name is ldtp2? [01:13] should be ldtp2-2.0.1 [01:13] jtatum, ah ! ok [01:13] tar file should be ldtp2_2.0.1.orig.tar.gz [01:14] first line of debian/control should be Source: ldtp2 [01:14] (leave Package: line as is) [01:16] jtatum, now a diff error, the above one passed [01:17] jtatum, gpg: skipped "Nagappan ": secret key not available [01:17] gpg: [stdin]: clearsign failed: secret key not available [01:17] debsign: gpg error occurred! Aborting.... [01:17] debuild: fatal error at line 1250: [01:17] do you have a gpg key? [01:17] jtatum, I need to have my gpg pub keys ? [01:17] jtatum, yes :) [01:17] you need your pivate key actually :) [01:17] jtatum, will copy it to my development box [01:19] jtatum, I have already id_rsa and id_rsa.pub in my ~/.ssh folder [01:20] those are ssh keys, not gpg [01:21] jtatum, ah ! my bad, let me get my gpg now [01:22] 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] jtatum, I have this http://pgp.mit.edu:11371/pks/lookup?search=nagappan&op=index [01:22] jtatum, created 2005, forgot about it :) as it was too long [01:23] nagappan: that's your public key :) guess your private key is lost [01:23] no worries. try -us -uc [01:23] jtatum, sure [01:23] can always rebuild and sign it later [01:24] so that should generate the .dsc and .changes, which you'll feed to your builder. hopefully it builds :) [01:25] jtatum, sure, thanks :) [01:26] nagappan: np :) heading home, afk a bit [01:26] jtatum, sure [01:26] jtatum, I get this [01:26] E: ldtp2 source: missing-build-dependency cdbs [01:26] W: ldtp2 source: unknown-field-in-dsc original-maintainer [01:26] jtatum, will add cdbs [01:26] nagappan: from your builder? [01:27] jtatum, from this debuild -S -sa -us -uc [01:27] nagappan: hm... ah. yes, cdbs needs to be one of the build-depends [01:29] jtatum, ok, fixed most of the warnings [01:29] nagappan: great! the original maintainer can be ignored or removed from control, it's not necessary for a private package [01:29] jtatum, ok [01:30] 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] rmcbride, sure, thanks :) [01:31] nagappan: I'm going to leave my browser spinning for a bit and then I'll restart it and tretry the attach [01:32] rmcbride, sure, thanks :) [01:32] jtatum, thanks for guiding this layman :) [01:33] 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] nagappan: no problem :) my pleasure :) [01:33] jtatum, sure [01:47] 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] just saw your comment once my browser started talking again [01:48] 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] nagappan: AH! OK [01:49] nagappan: I'm going to be out the rest of the night. I was able to get the apport-cli log attached. [01:49] 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] rmcbride, cool, thanks :) [01:50] nagappan: any time :) [02:06] nagappan, how's the package look? :) [02:10] jtatum, oops, I haven't looked at it yet, got into diff work, will look now [02:10] jtatum, sorry [02:14] lol, nagappan, no worries :) [06:44] good morning all! [08:37] Morning all [08:44] mornin brotha [08:44] from nz [08:57] whereisdarran: evening then [09:15] thanks brotha [09:15] how you doin davmor2 === asac_ is now known as asac [09:15] whereisdarran: sound as a pound you? [09:16] hangin in there [09:16] been under the weather since monday [09:16] but trying to get back on top [11:40] popey, ping [12:00] ara: try popey again now :) [12:00] popey, hello :) [12:01] 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] davmor2: stalker [12:37] ara: pong [12:38] 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] popey, it works now :) [12:38] :) [12:45] popey: not my fault that we are signed up on most of each others accounts :) === yofel_ is now known as yofel [13:07] fader|away: alternates are bust still cjwatson has uploaded a fix can you let cr3 know please :) [14:40] cr3: alternates are still bust dude [14:40] cr3: morning by the way :) [14:41] davmor2: thanks for the heads up, but desktops are fine? [14:42] cr3: seem to be although today's iso your network tests may fail in live cd mode [14:42] I haven't gotten any desktop results either, which seems to indicate there might be a problem there as well [14:43] cr3: live desktop's nm is just spiralling apparently there is a new version uploaded already [14:44] 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] 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] popey, ping [16:10] ara: lo [16:11] popey, can you have a look? http://people.canonical.com/~ara/temp/iso-tracker.avi [16:11] popey, if you approve, feel free to upload it to screencast.u.c [16:11] popey, thanks [16:11] ara: btw, you might like to mention in your indicator-applet README that the test depends on python-indicator [16:12] err, make that python-indicate [16:12] \o/ awesome! [16:12] ara: no, thank _you_ [16:13] cr3, OK. I will, thanks for telling me that [16:13] cr3, btw, notify-osd tests are failing because the need the images to compare with [16:14] cr3, maybe that's why they were appearing as faling? [16:14] ara: possible, I'll blacklist those as well then [16:15] cr3, why?? [16:15] 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] ara: if you have the spare cycles to implement this, let me know and we could work together on this [16:16] 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] 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] 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] 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] ara: cool, that doesn't need to run in certification then, why not a kvm instance on your machine overnight? [16:21] cr3, no, thanks ;-) [16:22] 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] ara: or, we have a vmware esx server in the datacenter, how about there? [16:25] cr3, I think all of those posibilities should be discussed with marjo first, don't you think? [16:26] 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] 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] cr3, what I am suggesting is that maybe marjo WANTS to run it in the datacenter, as part of the certification tests [16:41] 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] ara: however, karmic is pretty full right now, so I suspect this will have to be a karmic+1 thing [16:42] cr3, indeed :) [17:06] hey everyone wazzup? [17:07] davmor3: nothing just chilling with a bud [18:18] http://screencasts.ubuntu.com/2009/09/24/Ubuntu_Testing_-_ISO_Tracker \o/ [18:21] popey: \o/ [18:22] :) [18:26] * jpds \o/'s myself. [18:26] himself* [18:37] * davmor2 joins the belated mexican wave \o/ [19:11] hello everybody...what is to be tested next monday? [19:22] StefanAO: what do you mean? which milestone release is to be tested? [19:41] i am new to this...i thought there would be some feature to test [19:43] 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] 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] oh wait, you joined after popey pasted. here's the URL: http://screencasts.ubuntu.com/2009/09/24/Ubuntu_Testing_-_ISO_Tracker [19:44] this is a nice screencast that tells you everything you need to know to prepare for ISO testing [20:33] 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] If I'm building a new computer, should I run an install with 9.04 before trying out one of the alphas? [23:26] probably [23:26] if you want to know that your hardware is ok [23:26] probably best to run stomething stable first [23:26] yeah that sounds wise I'll run a basic install then try the alpha [23:29] * popey hugs jpds