[02:19] <c2tarun> I was trying to pack bluedevil, I didn't understand one thing. What is the differece b/w building a package via debuild and pbuilder-dist?
[02:21] <kklimonda> c2tarun: debuild builds the package on your system, pbuilder creates a chroot in which the package is built.
[02:23] <c2tarun> kklimonda: how can i put my package into REVU for reviewing?
[02:23] <kklimonda> !revu
[02:24] <kklimonda> c2tarun: ^
[02:24] <c2tarun> kklimonda: I was actually reading that page only :) its written there two motu members have to comment it. Can't we get it commented here on IRC?
[02:25] <micahg> c2tarun: comment in this case means advocate and they have to be able to examine the package
[02:27] <c2tarun> micahg: ok, and a line 'dpkg-buildpackage -S -sa -rfakeroot' I think this command will create .change file and I have on change file with me inside natty_results folder. Are they the same?
[02:27] <micahg> c2tarun: no, you need a source upload
[02:28] <micahg> err, that should be the right command though...
[02:28]  * micahg uses debuild -S --sa
[02:28] <micahg> oops, 1 dash
[02:29] <c2tarun> micahg: I used that already before running pbuilder, now running it again will make any difference?
[02:29] <micahg> c2tarun: you don't run it again, you need to upload the source_changes file to revu when you think it's ready
[02:32] <c2tarun> micahg: ok, and I am also trying a application directly from its source code, its a new one 'schedio'. I think I dont have source_chages file with me, all I have is schedio_2.0.0-0ubuntu1_i386.changes file
[02:32] <micahg> c2tarun: that's a binary changes file
[02:32] <micahg> err, that's a build record...
[02:33] <c2tarun> micahg: if that's a build rlsecord
[02:33] <c2tarun> sorry
[02:33] <c2tarun> micahg: if that's a build record then what is last_operation.log?
[02:33] <micahg> err, not a build record, it's a binary changes file :)
[02:34]  * micahg was right the first time
[02:34] <micahg> c2tarun: Ubuntu only accepts source uploads
[02:34] <c2tarun> micahg: ok i got the source.changes file, its not in natty_results but the folder containing the orig tarball :)
[02:34] <micahg> c2tarun: it'll be in the same folder as the .dsc file
[02:35] <c2tarun> micahg: one last thing, I am not sure that the developer supplied us with any documentation for man pages, how can I check?
[02:36] <micahg> c2tarun: I don't know the various pre-man documentation forms yet
[02:36] <c2tarun> micahg: you don't know or I am wrong, there are no man documents before packaging?
[02:37] <micahg> c2tarun: upstream can provide various documentation that can be turned into a manpage or they can provide their own man page, I don't know all the details yet
[02:37] <micahg> c2tarun: https://wiki.ubuntu.com/PackagingGuide/Complete#Man%20Pages
[02:38] <c2tarun> micahg: what if someone uploaded the source.changes file without proper man pages?
[02:38] <micahg> c2tarun: it'll probably be commented on
[02:38] <c2tarun> micahg: ok, thanks :)
[02:40] <micahg> c2tarun: here's the Debian policy manual on man pages, Ubuntu's a little more lenient, http://www.debian.org/doc/debian-policy/ch-docs.html#s12.1
[02:46] <c2tarun> micahg: ubuntu is linient in a way that missing man pages is not considered a bug :)? After reading the packaging documentation I found no .pod files or .bz2 in whole source code? What should I do, build the package and test it on myself first or right away report to the upstream that man pages are missing?
[02:53] <c2tarun> ping
[02:55] <micahg> c2tarun: you could write a manpage also :)
[02:56] <c2tarun> micahg: I never used that application, :( anyway i'll ask upstream for man pages and delay my upload till they supply me the man pages :)
[02:57] <micahg> c2tarun: you can get the rest of it reviewed in the mean time
[02:57] <c2tarun> micahg: grt :) so I should just upload the source.changes file?
[02:58] <micahg> c2tarun: well, you dput the source.changes file and that uploades the source
[02:58] <c2tarun> micahg: Ok, i'll do it :)
[03:01] <c2tarun> micahg: I uploaded it but couldn't find it on revuwire.com
[03:01] <c2tarun> micahg: sorry revu.ubuntuwire.com
[03:01] <micahg> c2tarun: did you get an e-mail?
[03:02] <c2tarun> micahg: not yet
[03:03] <micahg> ah, it's there now
[03:04] <micahg> http://revu.ubuntuwire.com/p/schedio
[03:05] <micahg> c2tarun: why do you have a debian collab-maint git repo listed?
[03:05] <c2tarun> micahg: its from the developer side, I didn't removed it.
[03:06] <micahg> c2tarun: what do you mean, didn't you create debian/control?
[03:06]  * micahg will comment later on it
[03:07] <c2tarun> micahg: I did, but still dh_make filled some fields by default, so i thought that it may be from the developer :(
[03:07] <micahg> c2tarun: no, dh_make creates a basic template, you're supposed to make sure what it did was sane and change whatever is necessary
[03:08] <c2tarun> micahg: ok, so my first error, I'll surely remove it in my next upload with man documentation. Any other error?
[03:08] <micahg> c2tarun: take a look at revu, it shows the lintian errors, also check the README.* files in debian/
[03:10] <c2tarun> micahg: ok watch file is missing. but I don't understand the error about maintainer field?
[03:10] <micahg> c2tarun: you need to run update-maintainer
[03:12] <c2tarun> micahg: ok, done. but sir I need some documentation or guidance for watch files, I never used them before.
[03:13] <micahg> c2tarun: https://wiki.ubuntu.com/PackagingGuide/Complete#Creating%20and%20Using%20a%20debian/watch%20File
[03:13] <micahg> c2tarun: you might want to bookmark that wiki page :)
[03:14] <c2tarun> micahg: sure sir, I already corrected the other two errors, one is of collab-maint git repo and other is of maintainer name and sir do u think I should remove both the README files?
[03:15] <c2tarun> micahg: sure I just read those two file and removed it :)
[03:16] <micahg> c2tarun: idk, BTW, I've never packaged anything from scratch :), it's generally a good idea to fix any lintian errors in new packages, so if lintian doesn't warn about a lack of a README, you're usually ok
[03:49] <guspur> good day
[03:49] <guspur> assalamualaikum
[04:35] <c2tarun> I am getting this error in watch file http://paste.ubuntu.com/561749/   this is my watch file http://paste.ubuntu.com/561750/
[04:36] <c2tarun> error is when I am uscaning the watch file
[04:59] <LaserJock> hi all, how goes it?
[05:01] <RAOF> c2tarun: You probably want to use uscan's html-scraping mode; see gnome-do's watch file for an example of doing that with Launchpad.
[05:01] <RAOF> Hey LaserJock.  What's up?
[05:02] <LaserJock> not a lot, thought I'd see how things were going in MOTU world
[05:06] <LaserJock> RAOF: how have you been?
[05:07] <RAOF> Pretty good.
[05:07] <LaserJock> you working for Canonical?
[05:07] <RAOF> Yeah!  On X.
[05:07] <RAOF> 'Tis fun.
[05:08] <RAOF> There's not so much motu-ing for me, though.  I accidentally let my membership lapse.
[05:08] <c2tarun> RAOF: can u please tell me where i can get that watch file?
[05:08] <LaserJock> uh oh :-)
[05:08] <RAOF> c2tarun: “apt-get source gnome-do; less gnome-do*/debian/watch” :)
[05:09] <RAOF> I'll get it back, with interest, by going for core-dev :)
[05:11] <LaserJock> how's Natty shaping up?
[05:12] <LaserJock> I saw Alpha 2 is almost out
[05:12] <c2tarun> RAOF: actually I am sorry to say but I dont know how to make watch files. Can u please help a bit.
[05:12] <LaserJock> but haven't been around development for so long I have no idea how it's progressing
[05:12] <RAOF> c2tarun: “man uscan” gives a pretty good overview of the contents of a watch file, and you should be able to cargo-cult from the gnome-do watchfile :)
[05:13] <RAOF> LaserJock: Natty's wandering along quite nicely.  Unity's still got some pretty big rough edges, though.
[05:13] <LaserJock> but the basics seem solid?
[05:13] <LaserJock> you know, like X ;-)
[05:14] <RAOF> As long as you don't want a proprietary driver, yeah :)
[08:31] <dholbach> good morning
[08:32] <al-maisan> Good morning dholbach :)
[08:33] <dholbach> hey al-maisan
[08:48] <geser> good morning
[08:49] <dholbach> hi geser
[14:31] <AnAnt> Hello
[14:44] <AnAnt> is alpha2 expected to be released today ?
[14:50] <micahg> AnAnt: it's scheduled to be
[14:50] <AnAnt> micahg: so I shouldn't upload today to natty ?
[14:51] <AnAnt> or it won't make a difference ?
[14:53] <micahg> AnAnt: well, only stuff that's not on any images or build-deps for any images, until the alpha 2 release announcement is made
[14:54] <AnAnt> micahg: so, universe is fine
[14:54] <micahg> AnAnt: no
[14:54] <AnAnt> ?
[14:54] <micahg> mythbuntu and xubuntu are both seeded from universe
[14:54] <AnAnt> ah, ok
[14:54] <micahg> AnAnt: so, you have to check each app to see if it's in a seed
[14:55] <AnAnt> micahg: how's that ?
[14:57] <micahg> AnAnt: apt-cache show pkgname, if there's a task at the bottom, it's in an image, I've been meaning to write a script that checks all the binaries in a src package
[14:58] <AnAnt> micahg: that works on maverick too ?
[14:58] <micahg> AnAnt: no, tasks might have changed for natty
[14:58] <AnAnt> ok
[15:18] <micahg> AnAnt: archive open :)
[15:18] <AnAnt> great
[16:10] <micahg> cyphermox: I'll get to your evolution-rss proposal today, I didn't get a good answer, but if the patch works, I'll take it :)
[16:11] <cyphermox> micahg, ah, okay
[16:20] <geser> micahg: do you know if there is an replacement for the xul-ext-notify firefox addon? I found it pretty nice to get a desktop notification when a download was finished. It seems to have vanished completely (the homepage link is 404).
[16:24] <micahg> geser: is that arch specific?
[16:37] <geser> don't know, how can I check it?
[16:38] <micahg> geser: you can try installing the version from addons.mozilla.org
[16:38] <micahg> it'll give you an error if it's arch specific and you're on amd64
[16:41] <geser> micahg: the problem is that I can't find it on addons.mozilla.org anymore (and the Homepage link on PTS for that packages doesn't work either).
[16:42] <geser> So I'm looking for an replacement for it.
[16:43] <geser> perhaps I ask bdrung about upstream status of it when he is here (he's listed as uploader for the Debian package)
[16:46] <Rhonda>  xul-ext-notify | 1.5.4-4build1  | ubuntu/maverick/universe | all
[16:46] <Rhonda> Hmm, seems to be removed/blocked from natty?
[16:46] <Rhonda> Because it's in Debian squeeze and sid.
[16:47] <Rhonda> geser: You could pull it from Debian directly?
[16:47] <geser> Rhonda: I could try but I doubt it will work without changes with Firefox 4.0beta
[16:47] <Rhonda> But yes, bdrung should know more, he's listed in Uploaders.
[16:47] <cjwatson> it was removed due to https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/FirefoxNewSupportModel
[16:48] <cjwatson> I imagine, anyway
[16:48] <cjwatson> yeah
[16:50] <geser> most of the addons I used, I've install over addons.mozilla.org again (or their homepages for a version for 4.0beta)
[16:50] <geser> but this last one, I'm still missing and as far as I can tell upstream vanished
[17:13] <micahg> geser: well, if upstream vanished, we don't want it in the archive anyways, but bdrung can upload a version to the xul-ext PPA
[17:14] <micahg> geser: I think chrisccoulson was going to do something with that eventually
[17:15] <chrisccoulson> do something with?
[17:16] <micahg> chrisccoulson: notify-osd (notify-extension seems to have vanished upstream)
[17:16] <chrisccoulson> oh, i wasn't going to do anything with that ;)
[17:16] <chrisccoulson> i might do something for download notification, but it won't be using that extension
[17:17] <chrisccoulson> that's an ugly hack that calls dbus-send ;)
[17:17] <micahg> chrisccoulson: I meant with notify-osd in general, not that extension as I remember you saying what you just said about it :)
[22:09] <bcurtiswx> StevenK, can I please get https://launchpad.net/ubuntu/+source/folks/0.3.4-0ubuntu1 taken care of, since I don't request these typicaly.. thats called "newed" right?
[22:17] <Rhonda> huhm, I have a strange problem, can't seem to create a cowbuilder chroot: sudo nice ionice -c3 cowbuilder --create --basepath ./natty --distribution natty --mirror http://at.archive.ubuntu.com/ubuntu/
[22:18] <Rhonda> And it gives me this error in the end: E: Package 'cowdancer' has no installation candidate
[22:18] <Rhonda> But cowdancer actually _is_ available in natty?
[22:18] <Rhonda> Same with lucid and maverick, I'm currently a bit puzzled.
[22:19] <micahg> Rhonda: maybe try in a chroot to see if it has an install failure
[22:19]  * micahg has to run, bbiab
[22:19] <bcurtiswx> micahg, thx for the link earlier
[22:20] <StevenK> bcurtiswx: They're in the NEW queue, yes. I'm just about to ACCEPT them.
[22:20] <Rhonda> micahg: I am currently trying to *create* the chroot. :(
[22:21] <StevenK> bcurtiswx: And done.
[22:21]  * micahg tries to install cowdancer in a chroot
[22:21] <bcurtiswx> StevenK, so requesting in the future I ask for someone to accept them?
[22:22] <bcurtiswx> StevenK, and very much thanks :)
[22:22] <StevenK> bcurtiswx: Usually just ping someone who is around and say "<source> is in <source|binary> NEW, could you look at it, please?"
[22:23] <micahg> Rhonda: http://pastebin.ubuntu.com/562242/
[22:23] <bcurtiswx> StevenK, OK, thanks :)
[22:25] <Rhonda> micahg: wtf?
[22:25] <micahg> Rhonda: could be my chroot, idk
[22:25] <Rhonda> micahg: I tried it for natty, lucid and maverick, neither worked.
[22:27] <micahg> hmm
[22:39] <ari-tczew> ScottK: ping
[22:40] <ScottK> ari-tczew: Pong, but I'm about to leave.
[22:40] <ari-tczew> ScottK: could you build one package on armel?
[22:40] <ScottK> ari-tczew: Give me a link to the .dsc and I can probably do it later tonight.
[22:41] <ari-tczew> ScottK: dget http://ftp.de.debian.org/debian/pool/main/libv/libv8/libv8_2.5.9.9-2.dsc
[22:41] <ari-tczew> ScottK: if you could save buildlog would be nice, thanks!
[23:45] <ScottK> ari-tczew: Started.
[23:46] <ari-tczew> ScottK: OK.