[00:00] <directhex> lots of manual requests, but does DIF make a difference to those?
[00:21] <Laney> directhex: no
[02:55] <ScottK> Mez: Thanks (ubuntu-backporters not expiring).
[05:47] <Kalidarn> say i'm packaging a file which is just a single .c file do i really need a configure script?
[05:48] <Kalidarn> because there's not really anything to configure
[05:48] <RAOF> Kalidarn: Why are you packaging a source file?
[05:48] <Kalidarn> well im compiling it, but it's a single binary
[05:48] <Kalidarn> that's all
[05:48] <Kalidarn> ftp://borg.uu3.net/pub/unix/mktorrent/mktorrent-0.9.9.tgz ie, that
[05:48] <Kalidarn> (new to debian packaging)
[05:49] <Kalidarn> come from archlinux pkgbuilding/gentoo ebuilds & rpm spec
[05:49] <RAOF> We don't add configure scripts, no.
[05:49] <Kalidarn> so i havn't really written a debian rules thingo before, i did read one of the documents on it
[05:49] <Kalidarn> and it indicated that you should have a configure file
[05:49] <Kalidarn> anyway
[05:49] <RAOF> That would be the common case.
[05:50] <Kalidarn> but there's nothing to configure :P
[05:50] <RAOF> You don't need a configure file.
[05:50] <Kalidarn> ah thought so
[05:50] <RAOF> Basically, all you need is a "binary" target that builds the the binary and creates the .deb.
[05:51] <Kalidarn> in that case it would be mktorrent.c
[05:51] <RAOF> You need more targets than that, but there are very few restrictions on what you do inside those targets.
[05:51] <Kalidarn> there's a makefile already created
[05:52] <Kalidarn> http://rafb.net/p/EHgIVf65.html (makefile) http://rafb.net/p/fstIZT18.html (single .c file)
[05:52] <Kalidarn> so yea
[05:52] <RAOF> debian/rules is also a makefile, which will generally call the upstream buildsystem.
[05:53] <Kalidarn> ah okay so do i put the options from that makefile
[05:53] <Kalidarn> into the debian rules file?
[05:53] <Kalidarn> ie cflags etc
[05:53] <Kalidarn> is there an example of a similar small binary that i could take a looksey at to get an idea
[05:55] <RAOF> Um...
[05:55] <RAOF> I can't think of one offhand, sorry.
[06:29] <Kalidarn> RAOF, if im doing a build dependency for it
[06:29] <Kalidarn> but i don't know what version
[06:29] <Kalidarn> Build-Depends: debhelper (>= 7) libssl-dev
[06:29] <Kalidarn> for example, do i specify one
[06:29] <Kalidarn> i think it will work with any version of libssl-dev
[06:29] <Kalidarn> doesn't have a configure file so i can't check, doesn't say anywhere either
[06:29] <persia> Kalidarn, Try unspecified first: only specify if you know a certain version is required.
[06:30] <Kalidarn> yeah but do i just say that like:
[06:30] <Kalidarn> Build-Depends: debhelper (>= 7) libssl-dev
[06:30] <Kalidarn> it complained it was not formatted correctly.
[06:30] <persia> It might benefit from a comma
[06:30] <Kalidarn> ah
[06:32] <persia> Also, unless you're using debhelper 7 features, you shouldn't force 7.
[06:32] <persia> (although using debhelper 7 features makes it *much* easier)
[06:38] <Kalidarn> it automatically did
[06:38] <Kalidarn> that was the default
[06:38] <Kalidarn> http://rafb.net/p/EHgIVf65.html (makefile) http://rafb.net/p/fstIZT18.html (single .c file)
[06:38] <Kalidarn> that was the project i was building
[06:38] <Kalidarn> i had this in my control files
[06:39] <Kalidarn> http://rafb.net/p/28SWJ687.html
[06:39] <Kalidarn> http://rafb.net/p/6Xhx3X17.html
[06:39] <Kalidarn> i think i might have messed up a slight bit :)
[06:40] <Kalidarn> i was following this guide https://wiki.ubuntu.com/PackagingGuide/Complete
[06:40] <Kalidarn> the thing is also, i don't have a configure file, its just built and then the binary is moved to the binary directory ie /usr/bin
[06:40] <persia> That's really more a debhelper 5.x guide, but many of the essentials remain the same.
[06:41] <Kalidarn> oh
[06:41] <Kalidarn> well if you can help me in the right direction ;)
[06:41] <Kalidarn> i'd be happy to learn
[06:41] <Kalidarn> seeing as im using ubuntu more now these days than other distributions :)
[06:42] <persia> I'd recommend reviewing the debhelper changelog.  Find the last version that changes something you think is important for your package, and require that version.
[06:42] <Kalidarn> yeah im not sure what version i should use
[06:42] <Kalidarn> version 7 is just the default one
[06:42] <Kalidarn> it put there
[06:43] <Kalidarn> to be honest this is a simple package
[06:43] <Kalidarn> i dont think it would use any of the newer features
[06:43] <Kalidarn> it's a simple C file, which is compiled with some simple options
[06:43] <Kalidarn> single c file goes in compiler, single binary comes out
[06:43] <persia> Well, it's worth a read of the changelog.  You might get by with 5.  I wouldn't recommend going lower than that.
[06:43] <Kalidarn> is lower usually better?
[06:45] <persia> Well, you're asserting that it cannot build unless you have at least debhelper 7.
[06:45] <Kalidarn> oh i see
[06:45] <persia> That doesn't appear to be correct.
[06:45] <Kalidarn> 7 isn't the stable one
[06:45] <persia> The idea is to be correct.
[06:45] <Kalidarn> http://packages.qa.debian.org/d/debhelper.html
[06:45] <Kalidarn> Stable   	  5.0.42
[06:45] <Kalidarn> yeah ill use that then
[06:45] <persia> 7 is perfectly stable, you're just not using those features.
[06:45] <Kalidarn> Testing   	  7.0.15
[06:45] <Kalidarn> it says is in testing
[06:45] <Kalidarn> wouldnt u use the stable version
[06:45] <persia> If you'd like to use debhelper 7, you'll find the rules file smaller: man dh to read about it.
[06:45] <Kalidarn> unless ur using the newer features
[06:45] <Kalidarn> oh
[06:45] <Kalidarn> mm i might do that then
[06:46] <Kalidarn> whats the default in intrepid ibex
[06:46] <Kalidarn> anyway
[06:46] <persia> Debian "stable" is just the name for the distribution that Debian released last time.  The "testing" distribution is expected to become "stable" in Debian real-soon-now.
[06:46] <Kalidarn> oh yeah
[06:46] <Kalidarn> thats right i forgot :)
[06:46] <persia> https://launchpad.net/ubuntu/+source/debhelper
[06:48] <Kalidarn> mm that changelog is long
[06:48] <persia> So just because a given version is in "testing" or "stable" doesn't mean anything regarding the stability of the software itself.  There's stuff in "stable" that is considerably less stable than stuff in "unstable": it's more a statement about the amount of variance one can expect in package versions than about the propensity for software to crash.
[06:48] <Kalidarn> yeah
[06:48] <Kalidarn> its just the distribution of debian its in
[06:49] <persia> Right.
[06:49] <Kalidarn> im aware of that i realize that now
[06:49] <Kalidarn> so is there an example of a rules file for version 7?
[06:49] <Kalidarn> i'd ultimately like to be using version 7... if it makes things simpler
[06:49] <persia> man dh
[06:50] <Kalidarn> ah thx
[06:51] <Kalidarn> /usr/share/doc/debhelper/examples/rules.simple
[06:51] <Kalidarn> might be of help :0
[06:52] <persia> Yes, although there's an even shorter one embedded in the man page :)
[06:52] <Kalidarn> oh okay
[06:53] <Kalidarn> what rules.tiny?
[06:53] <persia> Yes, that would be the embedded one.
[06:54] <Kalidarn> how much pkging have you done btw ;)
[06:55] <persia> I've packaged one library.
[06:57] <Kalidarn> okay so i've got this: http://rafb.net/p/46wv5q46.html
[06:58] <Kalidarn> i dont now need the make section do it
[06:58] <Kalidarn> *i
[06:58] <Kalidarn> im not passing any options to configure, because there is no configure script
[06:58]  * slytherin stares at the phrase 'real-soon-now'. :-)
[06:59] <persia> Firstly, you probably want the variable definitions above the rules.  Secondly, I suspect that dh expects there to be an upstream makefile, so you may want to start with simple rather than tiny, and rewrite much of the build rule.
[06:59] <Kalidarn> hmm
[07:00] <Kalidarn> okay then can i get it to use the upstream makefile
[07:00] <Kalidarn> im just kind of confused :P
[07:00] <persia> dh ought to try to use the upstream makefile by default.
[07:00] <Kalidarn> ah
[07:00] <persia> Since you don't have one, you'll want to rewrite the build rule to be different.
[07:02] <Kalidarn> i do have an upstream makefile
[07:06] <persia> Oh, then you're all set.  Just put the variable definitions above the %: line, and try a build.
[07:18] <iulian> Good morning.
[07:18] <NCommander> persia, how's your perl?
[07:20] <Kalidarn> i think my connection died out there
[07:21] <Kalidarn> http://rafb.net/p/6uwQgw47.html i wonder what's causing that error http://rafb.net/p/WX7cS276.html
[07:21] <StevenK> rm exits 1 if the files don't exist
[07:21] <Kalidarn> oops ignore the first link
[07:22] <Kalidarn> ah
[07:22] <Kalidarn> the makefile removes the object code
[07:22] <Kalidarn> is that alright?
[07:22] <StevenK> rm -f *.o will exit 0 even if the files don't exist
[07:23] <Kalidarn> orhmm
[07:23] <persia> -rm -f *.o
[07:23] <persia> NCommander, I can generally read it.  Why?
[07:23] <NCommander> I was wondering if you were interested in helping me modify buildd :-)
[07:24] <persia> Oh.  Not so much.
[07:24] <persia> What are you trying to get it to do?
[07:24] <NCommander> autosign and autoupload packages
[07:25] <Kalidarn> ah perfect
[07:25] <persia> I though it's not doing that was widely considered a feature.
[07:25] <Kalidarn> it seems to be working now ;)
[07:25] <NCommander> persia, not if your emulating an Ubuntu build environment :-P
[07:25] <Kalidarn> iW: mktorrent source: out-of-date-standards-version 3.7.3 (current is 3.8.0)
[07:25] <Kalidarn> :P should i update that
[07:25] <persia> Kalidarn, Policy is in the debian-policy package.  Worth a read.
[07:26] <persia> I'd recommend making your package comply with 3.8.0, and then declaring that.
[07:26] <Kalidarn> yeah
[07:26] <Kalidarn> i just changed it
[07:26] <Kalidarn> whats the clean command
[07:26] <Kalidarn> to clean the shit up
[07:27] <Kalidarn> after a debbuild
[07:27] <persia> debian/rules clean might work.
[07:27] <Kalidarn> no i mean to clean up my package directory
[07:27] <persia> You'd do better to get in the practice of running debuild -S and then using sbuild or pbuilder to build.
[07:27] <Kalidarn> ah
[07:27] <persia> Yes, `debian/rules clean` is supposed to do that.
[07:28] <persia> If it doesn't, it's a bug, but if it's your first package, it could well be buggy.
[07:28] <Kalidarn> which do u recommend
[07:28] <Kalidarn> sbuild or pbuilder
[07:29] <persia> I personally use sbuild.  Others use pbuilder.  Both are good.  qemubuilder, cowbuilder, and the like seem less popular.
[07:29] <Kalidarn> o.O
[07:29] <Kalidarn> Now signing changes and any dsc files...
[07:29] <Kalidarn>  signfile mktorrent_0.9.9-1.dsc David C <dcecchin@gmail.com>
[07:29] <Kalidarn> gpg: skipped "David C <dcecchin@gmail.com>": secret key not available
[07:29] <Kalidarn> gpg: [stdin]: clearsign failed: secret key not available
[07:29] <Kalidarn> debsign: gpg error occurred!  Aborting....
[07:29] <Kalidarn> debuild: fatal error at line 1250:
[07:29] <Kalidarn> that's a load of rubbish
[07:29] <Kalidarn> my secret key is too available
[07:29] <Kalidarn> i always sign email with it
[07:30] <persia> What's the identity on your secret key?
[07:30] <Kalidarn> F2FE93F8?
[07:31] <persia> Try `gpg --list-keys F2FE93F8`
[07:31] <Kalidarn> it's in the keyserver
[07:31] <Kalidarn> yeah it shows it
[07:31] <Kalidarn> when i have the `
[07:31] <Kalidarn> it says pub not found
[07:31] <persia> Sure, but I suspect that the identity associated with it doesn't match " David C <dcecchin@gmail.com>"
[07:31] <Kalidarn> kalidarn@sanction:~/Desktop/mktorrent/mktorrent-0.9.9/debian$ `gpg --list-keys F2FE93F8`
[07:31] <Kalidarn> bash: pub: command not found
[07:31] <Kalidarn> kalidarn@sanction:~/Desktop/mktorrent/mktorrent-0.9.9/debian$ gpg --list-keys F2FE93F8
[07:31] <Kalidarn> pub   1024D/F2FE93F8 2008-08-07
[07:31] <Kalidarn> uid                  dcecchin <dcecchin@gmail.com>
[07:31] <Kalidarn> sub   4096g/408F3186 2008-08-07
[07:31] <Kalidarn> hmm.....
[07:32] <Kalidarn> that' the email i entered
[07:32] <persia> Right.  Put your name on the key.
[07:32] <Kalidarn> David C is the name
[07:32] <persia> Both name and email have to match.
[07:32] <Kalidarn> i use on the key
[07:32] <persia> See your paste.  The name is "dcecchin" on the key.
[07:32] <Kalidarn> oh yeah
[07:32] <Kalidarn> mm
[07:32] <Kalidarn> okays
[07:33] <Kalidarn> mm no it didn't like that either
[07:33] <Kalidarn> Maintainer: dcecchin <dcecchin@gmail.com>
[07:33] <Kalidarn> i tried Maintainer: David C <dcecchin@gmail.com>
[07:33] <Kalidarn> too
[07:33] <Kalidarn> both don't work
[07:33] <Kalidarn> :P
[07:34] <persia> Maintainer doesn't matter.  It's only the last line in the changelog.
[07:34] <Kalidarn> ah
[07:34] <persia> Anyway, you want to fix your key, not the package.
[07:34] <Kalidarn> didn't change that ;)
[07:34] <NCommander> you can force what key to sign with -k*keyid*
[07:34] <Kalidarn> okay that works
[07:35] <persia> NCommander, Yes, but you *shouldn't*
[07:35] <persia> (except when sponsoring something for someone else)
[07:39] <Kalidarn> mm
[07:39] <Kalidarn> its not putting the binary anywhere
[07:39] <Kalidarn> it compiled it i obviously have to have something in my rules file
[07:39] <Kalidarn> to tell it
[07:39] <persia> That's the install rule.  By default, it just calls make install.
[07:40] <Kalidarn> to put ~/Desktop/mktorrent/mktorrent-0.9.9/mktorrent in /usr/bin
[07:40] <Kalidarn> oh it didn't ;P
[07:40] <persia> Try putting something in debian/${package}.install
[07:40] <Kalidarn> #!/usr/bin/make -f
[07:40] <Kalidarn> %:
[07:40] <Kalidarn>         dh $@
[07:40] <Kalidarn> that's all that's in my rule file
[07:40] <Kalidarn> that is probably why
[07:40] <persia> No.
[07:40] <persia> That's correct.
[07:41] <Kalidarn> oh
[07:41] <persia> Check what your makefile does with make install
[07:41] <Kalidarn> nothing
[07:41] <persia> Right, then add a line to debian/${package}.install
[07:41] <persia> man dh_install for the format
[07:41] <Kalidarn> http://rafb.net/p/JucbQb25.html
[07:47] <Kalidarn> $ cat /home/kalidarn/Desktop/mktorrent/mktorrent-0.9.9/debian/mktorrent.install
[07:47] <Kalidarn> usr/bin
[07:48] <persia> You probably want something like mktorrent usr/bin
[07:48] <Kalidarn> hmm that doesnt seem right im guessing here from what i read in dh_install
[07:48] <Kalidarn> ah
[07:48] <Kalidarn> thats the format
[07:48] <Kalidarn> the name of the ile
[07:48] <Kalidarn> file
[07:48] <Kalidarn> space
[07:48] <Kalidarn> then location
[07:49] <Kalidarn>        Suppose your package’s upstream Makefile installs a binary, a man page, and a library into appropriate subdirectories of debian/tmp.
[07:49] <Kalidarn>        You want to put the library into package libfoo, and the rest into package foo. Your rules file will run "dh_install
[07:49] <Kalidarn>        --sourcedir=debian/tmp". Make debian/foo.install contain:
[07:49] <Kalidarn>          usr/bin
[07:49] <Kalidarn>          usr/share/man/man1
[07:51] <Kalidarn> usr/bin/
[07:51] <Kalidarn> usr/bin/mktorrent
[07:51] <Kalidarn> perfect
[07:51] <Kalidarn> included files
[07:51] <Kalidarn> ;) so there we go
[07:51] <Kalidarn> woot
[07:51] <Kalidarn> my first deb file
[07:51] <Kalidarn> ;) thankyou
[07:51] <Kalidarn> for your help
[07:51] <Kalidarn> now i'll have to practice making lots more ;)
[07:52] <Kalidarn> also i built that with debuild
[07:52] <Kalidarn> it built an i386 one
[07:52] <Kalidarn> how do i make it build a x64 one too
[07:52] <Kalidarn> or amd64 rather
[07:53] <Kalidarn> my control file says 'any' for architecture btw
[08:01] <Kalidarn> RAOF how do i build for another architecture
[08:01] <Kalidarn> it keeps building for i386 :) i want to build an amd64 version too
[08:01] <Kalidarn> or do i actually need that arch to do it
[08:03] <Hobbsee> you need that arch, usually
[08:04] <Kalidarn> mmm someone in debian said it's possible to cross compile
[08:04] <Kalidarn> ;)
[08:04] <slytherin> Kalidarn: are you doing cross compilation?
[08:04] <Hobbsee> it is possible to cross-compile, yes.
[08:04] <Kalidarn> yeah
[08:04] <Kalidarn> im on an i386 box, ive built myself a i386 binary that works nicely i want to make an amd64 one too
[08:05] <Kalidarn> i didn't notice anything about cross compiling in the build doc
[08:10] <Kalidarn> http://www.omgili.com/mailinglist/debian-user/lists/debian/org/4915B8F67080000gmailcom.html
[08:10] <Kalidarn> this gives me the impression i can only build i386 from a amd64 processor
[08:10] <Kalidarn> but not the other way around
[08:11] <RAOF> Kalidarn: That's generally correct, yes.
[08:11] <Kalidarn> damn it i don't have a 64 processor with ubuntu on it :P
[08:12] <Kalidarn> suppose i can put the source pkg up somewhere
[08:12] <Kalidarn> how does ubuntu deal with user contributed packages
[08:12] <Kalidarn> in archlinux we had AUR
[08:12] <RAOF> I believe it _is_ possible to cross-compile, too; I'm just not familiar with it at all.
[08:12] <RAOF> AUR?
[08:12] <Kalidarn> ArchLinux User Repository
[08:12] <Kalidarn> its basically a place where users who made binaries and stuff
[08:12] <Kalidarn> could upload
[08:13] <Kalidarn> for other users
[08:13] <RAOF> Hm.  We don't have something like that.
[08:13] <RAOF> Not officially, at least.
[08:13] <Kalidarn> mm
[08:13] <Kalidarn> that sucks :P
[08:13] <Hobbsee> ppa?
[08:13] <Kalidarn> im just wondering where i can dump my files :P
[08:13] <Kalidarn> yeah i thought ppa was a user thing
[08:13] <RAOF> You can use a PPA on launchpad to bulid a repository built for i386, x86-64, lpia.
[08:14] <Kalidarn> that sounds like what i want
[08:14] <RAOF> Yeah.
[08:28] <huats> morning !
[09:10] <Kalidarn> with ppa
[09:10] <Kalidarn> u know how they have a special version scheme
[09:10] <Kalidarn> Here, the tilde knocks the precedence of the package down to below whatever is in front of it. So, for now, this package counts as being a higher version number than myapp_1.0-1 but when Ubuntu releases myapp_1.0-2 that will supersede your PPA version.
[09:10] <Kalidarn> where do i edit that in my control
[09:10] <Kalidarn> and changelog
[09:11] <Kalidarn> because i had mktorrent (0.9.9-1) intrepid; urgency=low
[09:12] <Kalidarn> oh hang on
[09:12] <Kalidarn> i think the ~ppa
[09:12] <Kalidarn> is only needed if its being made of an official package
[09:12] <Kalidarn> but in this case its not
[09:12] <Kalidarn> the package hasn't been even put into the main repositories
[09:15] <Kalidarn> hmm
[09:15] <Kalidarn> says it uploaded
[09:15] <Kalidarn> Successfully uploaded packages.
[09:15] <Kalidarn> yet i dont see any
[09:15] <Kalidarn> :(
[09:25] <soren> Uploading is almost always succesful. Whether the upload is accepted or not is determined afterwards.
[09:25] <soren> kirkland: ^
[09:25] <soren> kirkland: Sorry, not you :)
[09:25] <soren> Kalidarn: ^^
[09:25] <soren> Kalidarn: You should receive an e-mail with info about your upload
[09:26] <Kalidarn> woot
[09:26] <Kalidarn> nevermind
[09:26] <Kalidarn> i did something silly
[09:26] <Kalidarn> its now successful
[09:26] <Kalidarn> i upped a binary
[09:27] <Kalidarn> not the source
[09:27] <Kalidarn> its compiling
[09:27] <Kalidarn> yay!
[09:27] <Kalidarn> Still building amd64 lpia i386
[09:27] <Kalidarn> Publishing details
[09:27] <Kalidarn> Changelog
[09:27] <Kalidarn> mktorrent (0.9.9-1) intrepid; urgency=low
[09:27] <Kalidarn>   * mktorrent package i386 package for intrepid ibex.
[09:27] <Kalidarn>   * stable release
[09:27] <Kalidarn>  -- dcecchin <dcecchin@gmail.com>   Fri, 26 Dec 2008 15:30:19 +1030
[09:27] <Kalidarn> Builds
[09:27] <Kalidarn>     * [NEEDSBUILD] amd64
[09:27] <Kalidarn>     * [BUILDING] i386
[09:27] <Kalidarn>     * [NEEDSBUILD] lpia
[09:27] <Kalidarn> Download files from Librarian
[09:27] <Kalidarn>     * mktorrent_0.9.9-1.dsc (751 bytes)
[09:27] <Kalidarn>     * mktorrent_0.9.9-1.tar.gz (6.7 KiB)
[09:27] <Kalidarn> oops
[09:27] <Kalidarn> silly thing highlighted a lot of text invisibly.
[09:27] <Kalidarn> "Still building amd64 lpia i386"
[09:27] <Kalidarn> is what i meant to paste
[09:29] <Kalidarn> wootage
[09:29] <Kalidarn> soren, https://launchpad.net/~dcecchin/+archive
[09:29] <Kalidarn> ppa rocks
[09:29] <persia> You really do want to fix your name on your key though
[09:30] <Kalidarn> oh,
[09:30] <Kalidarn> what should it be
[09:30] <persia> Your actual name.
[09:30] <Kalidarn> ah yeah
[09:30] <Kalidarn> hmm
[09:30] <Kalidarn> i'd need to remake my keys though
[09:30] <Kalidarn> wouldn't i
[09:30] <persia> No, just update the key, self-sign the change, and publish the update
[09:31] <Kalidarn> mmm how might i go about doing that easily?
[09:31] <persia> Use seahorse
[09:31] <Kalidarn> ah
[09:31] <Kalidarn> thats good i can do it with that ;)
[09:32] <persia> Just don't add a comment.  The comment needs to do in the changelogs, and that's rarely what you want.
[09:32] <Kalidarn> alrighty in seahorse how do i do it :P
[09:32] <Kalidarn> Names and Signatures?
[09:32] <Kalidarn> im guessing i add a name and delete the one that's there
[09:32] <persia> Right.
[09:32] <persia> Then self-sign it.
[09:33] <persia> (highlight the identity, and click sign)
[09:34] <Kalidarn> okay done
[09:34] <persia> One warning though: signatures apply to identities: if you have a lot of signatures already on that identity, just do the add, rather than the add ' delete.
[09:34] <persia> OK.  Sign the new identity, and upload the key.
[09:34] <Kalidarn> nah
[09:34] <Kalidarn> i only had one
[09:35] <Kalidarn> i do Deactivated keys?
[09:36] <persia> Hrm? Probably not.
[09:37] <Kalidarn> trying to work out how to delete it
[09:37] <persia> You didn't create a new key, did you?
[09:37] <Kalidarn> no
[09:37] <Kalidarn> i didnt
[09:37] <Kalidarn> its the same key
[09:37] <persia> OK.
[09:37] <Kalidarn> same fingerprint
[09:37] <persia> So, You used "Add Name" to add the new identity, right?  In the Names and Signatures tab?
[09:38] <Kalidarn> yep
[09:38] <Kalidarn> and now it says my full name next to the email
[09:38] <persia> Now, select the new identity, and click Sign
[09:38] <Kalidarn> yep i said "Very Carefully"
[09:39] <persia> Then, if you don't mind losing the signatures, select the old identity, and click Delete
[09:39] <Kalidarn> and self signed it
[09:39] <Kalidarn> yep
[09:39] <Kalidarn> i did that
[09:39] <Kalidarn> so the only identity there is my full name and my email
[09:39] <persia> Great.  Now, close that window, and go back to the main interface.
[09:39] <persia> Select your key from My Personal Keys
[09:40] <persia> Then choose Sync and Publish keys from the Remote menu
[09:40] <Kalidarn> ya
[09:40] <Kalidarn> ah
[09:40] <Kalidarn> mm sync is greyed out :P
[09:40] <Kalidarn> pgp.mit is where i originally submitted it
[09:40] <persia> click "key servers" and select a key server
[09:40] <Kalidarn> ya so i then can sync it there
[09:41] <persia> You probably have to change the preference at the bottom.
[09:41] <Kalidarn> yep
[09:41] <Kalidarn> okay all done
[09:41] <persia> Now, wait a few hours, and check your key from one of the online repos.
[09:41] <persia> And in the future, you can put your name in the changelog (as is intended)
[09:42] <Kalidarn> ah okay
[09:42] <Kalidarn> ill delete those packages
[09:42] <Kalidarn> then
[09:42] <persia> No need.  Someone else needs to sign them to upload anyway.
[09:42] <persia> Just next time you make a change, you can put the correct information in the changelog.
[09:42] <Kalidarn> yeah well nobody knows they are there
[09:42] <Kalidarn> cept me ;)
[09:42] <Kalidarn> so i can delete them
[09:43] <persia> Well, you can't really completely delete them, but you can at least make them hard to get.
[09:43] <Kalidarn> oh :P
[09:44] <persia> Also, there will be a record that you uploaded that version, so you'd need a new changelog entry and a new version to upload again anyway.
[09:44] <persia> No point to deleting them, really.
[09:44] <Kalidarn> ah okay
[09:44] <Kalidarn> yeah
[09:45] <Kalidarn> so ill have to bump it to a -2
[09:45] <persia> Or just leave it until someone reviews it, and you need to change things.
[09:46] <persia> Anyway, in future, I'll recommend versioning it as -0ppaX where X goes from 1 up.
[09:46] <Kalidarn> ah okay
[09:46] <persia> That way, users would be upgraded to -0ubuntu1 if it ends up in the repos.
[09:46] <Kalidarn> fair enough
[09:46] <Kalidarn> okay
[09:46] <persia> Or to -1 if it ends up in repos that use that revision coding scheme
[09:46] <Kalidarn> mktorrent (0.9.9-2) intrepid; urgency=low
[09:47] <Kalidarn> is what i had so ill make it mktorrent (0.9.9-2~ppa1) intrepid; urgency=low
[09:48] <persia> You can't.  -2~ppa is lower than -2
[09:48] <Kalidarn> oh hang on ;P
[09:48] <Kalidarn> yeah so it's mktorrent(0.9.9~ppa1)
[09:48] <Kalidarn> my brain fuzzed on the syntax :P
[09:49] <persia> Again, no.
[09:49] <Kalidarn> :(
[09:49] <persia> You want 0.9.9-0ppaX
[09:49] <Kalidarn> oh yeah cos that 0 before ppa
[09:49] <Kalidarn> represents whether it came from debian or not
[09:49] <Kalidarn> doesn't it
[09:49] <persia> The hypen separates the version number from the revision number
[09:49] <persia> You want a very low revision number.
[09:49] <Kalidarn> and the ppaX represents rev number?
[09:49] <persia> No, the 0 just sorts less than 1, which is the first revision number in Debian.
[09:49] <Kalidarn> ah
[09:50] <persia> -0ppaX is nice because it also sorts lower than 0ubuntuX.
[09:50] <Kalidarn> right
[09:50] <persia> All of "0ppaX" represents the revision number.
[09:50] <Kalidarn> mktorrent (0.9.9-0ppa1) intrepid; urgency=low
[09:50] <persia> It's just a very low revision.  Same sort of reason one uses 0.0.X for early versions of software.
[09:50] <Kalidarn> is what ill set it to then
[09:51] <Kalidarn> because i scrubbed what was in there
[09:51] <persia> That would be good, except you already uploaded something higher, so you can't upload that (it remembers)
[09:51] <Kalidarn> because i had dcecchin in other parts of it so i changed that
[09:51] <Kalidarn> :(
[09:51] <Kalidarn> now my versions are all screwed up
[09:51] <persia> Indeed.  PPAs are good for distributing software, but it's not easy to recover if you mess up.
[09:52] <Kalidarn> haha can i delete my account?
[09:52] <persia> One way to work around it is to use something like 0.9.9+clean-0ppa1 as your version.
[09:52] <persia> Then, when 0.9.10 comes out, you just upload 0.9.10-0ppa1
[09:52] <Kalidarn> oh true
[09:52] <Kalidarn> i might do that :P
[09:52] <Kalidarn> and i don't think u can delete accounts
[09:53] <Kalidarn> by the looks of it
[09:53] <persia> You can, but it's non-trivial, mostly because it breaks things, like the URL you asked someone to look at that is now logged at irclogs.ubuntu.com
[09:54] <Kalidarn> oh well ;)
[09:54] <Kalidarn> as long as the name isn't reserved i might do that as i've learnt from my lesson
[09:54] <Kalidarn> and i will create the same name after anyway
[09:54] <Kalidarn> so it wouldn't break it :P
[09:54] <persia> That's non-trivial.  Ask in #launchpad, but I suspect it's poorly staffed for the next week or so.
[09:55] <Kalidarn> ah okay
[09:55] <NCommander> persia, once you delete, you can upload any version except for the last one if it has the extact same version string
[09:55] <Kalidarn> NCommander, yeah i was going to delete my account and reopen it :P
[09:55] <persia> NCommander, I was sure that got fixed so that you had to upload a version higher than the last distributed.
[09:57] <NCommander> persia, not as of last week
[09:58] <persia> NCommander, Ah.  Is there an open bug filed about that?
[09:59] <NCommander> No, cause I didn't consider it a bug :-P
[10:01] <persia> Please file it.  For a while, PPAs were trying to be both a playground and a place for real distribution.  The decision was made to support real distribution, with the side effect of breaking some of the playground stuff.  That's a bug, because even deleted, the version could exist on some users' systems.
[10:02] <Kalidarn> persia, killing accounts wouldnt kill uploads anyway
[10:02] <Kalidarn> i doubt
[10:02] <Kalidarn> :P
[10:07] <NCommander> persia, but the same is true in the real archive
[10:07] <NCommander> persia, if an upload is killed, you can upload something with a lower version than it
[10:07] <persia> NCommander, Only if it's killed before it's accepted.
[10:07] <persia> Anyway, that's just dangerous.
[10:08] <NCommander> (and that has happened in Debian)
[10:08] <persia> Yes, I know.  It's still dangerous, and shouldn't be done.
[10:10] <Kalidarn> mm so i should just wait for my new identity to propergate the keyservers and then what
[10:10] <NCommander> persia, no, once an upload is killed, dak retains no memory of it in unstable
[10:10] <persia> Kalidarn, Try uploading 0.9.9-0ppa1  I think it shouldn't work, but there may be a bug that it does.
[10:10] <NCommander> (or should I say a package is killed)
[10:10] <Kalidarn> oh okay
[10:10] <persia> NCommander, Right, but that doesn't mean it's not been distributed.
[10:11] <NCommander> Anyway, that's why epoch's exist
[10:11] <persia> Right, but an epoch is probably overkill for the current needs.
[10:11] <persia> Kalidarn, If that doesn't work, try -1ppa1 and go from there.
[10:11] <Kalidarn> okies
[10:15] <NCommander> persia, oh, I'm perfectly aware of the problem, and I know how bad it is, I'm just saying how things currently are
[10:16] <persia> NCommander, Which is why I'm arguing with you when you say "I didn't consider it a bug"
[10:16] <persia> In the current situation, if -0ppa1 can be uploaded, it will be a good thing.
[10:16] <Kalidarn> :)
[10:16] <Kalidarn> yeah
[10:17] <Kalidarn> im sorry i noobed it
[10:17]  * NCommander turns --verbose on himself
[10:17] <NCommander> I didn't consider it a bug because I didn't realize the full implications of the problem
[10:17] <NCommander> persia, :-P
[10:18] <NCommander> BTW, anyone know how to switch vim from using tabs to spaces?
[10:18] <persia> Kalidarn, No need to apologise: we all have to learn once.
[10:18]  * NCommander is hacking on dak and Ganneff hates tabs ;.;
[10:18] <persia> NCommander, That's OK.  I'm happy to share implications anytime you're short a few :)
[10:18] <NCommander> persia, feel free to shoot down my core dev application :-P
[10:18] <NCommander> although Steven already beat you to it
[10:19]  * NCommander sighs
[10:19] <NCommander> My ping times are over a second
[10:21]  * directhex pongs NCommander 
[10:26] <Kalidarn> btw persia
[10:26] <Kalidarn> my key is updated on the MIT server
[10:26] <Kalidarn> i expect it is on others
[10:26] <Kalidarn> although i think the old identity exists
[10:27] <persia> Kalidarn, Cool.
[10:28] <StevenK> NCommander: Use xemacs' python-mode
[10:28] <StevenK> NCommander: And damn it, stop calling me Steven
[10:28] <NCommander> ok StevenK
[10:29] <NCommander> (unless you perfer Steve)
[10:29] <StevenK> Which I do
[10:29] <NCommander> Sorry, I didn't realize you did.
[10:30] <StevenK> NCommander: If you can drive {x,}emacs, python-mode makes coding Python very simple. Hit tab, and it adds the correct number of spaces to go up an indent level, and if you backspace, it will go down an indent level
[10:30] <NCommander> Oooh, sounds handy
[10:30]  * NCommander uses console emacs however
[10:30] <NCommander> Just :set python-mode?
[10:30] <NCommander> wait
[10:30]  * NCommander is using vi
[10:30] <NCommander> damn it
[10:30] <StevenK> If your file ends with .py, emacs should just deal
[10:31] <Kalidarn> Uploading to dcecchin-ppa (via ftp to ppa.launchpad.net):
[10:31] <Kalidarn>   mktorrent_0.9.9-0ppa1.dsc: done.
[10:31] <Kalidarn>   mktorrent_0.9.9-0ppa1.tar.gz: done.
[10:31] <Kalidarn>   mktorrent_0.9.9-0ppa1_source.changes: done.
[10:31] <Kalidarn> Successfully uploaded packages.
[10:31] <Kalidarn> now we wait and see ;)
[10:36] <Kalidarn> man its taking ages
[10:55] <Kalidarn> odd
[10:55] <Kalidarn> persia, havn't got a email yet
[10:55] <Kalidarn> whether my commit was rejected or accepted
[11:00] <slytherin> Kalidarn: your upload log has no mention of .diff.gz
[11:01] <slytherin> Kalidarn: also there is no .orig.tar.gz
[11:01] <Kalidarn> hmm strange
[11:01] <Kalidarn> wonder why
[11:01] <Kalidarn> i used debuild -S
[11:10] <Kalidarn> bah
[11:11] <Kalidarn> persia, it doesn't seem to be building the orig files
[11:14] <Kalidarn> persia,
[11:14] <Kalidarn> that scheme
[11:14] <Kalidarn> isn't calling it orig
[11:14] <Kalidarn> mktorrent_0.9.9-0ppa1.tar.gz
[11:14] <Kalidarn> is what it's getting called
[11:14] <Kalidarn> not orig
[11:14] <Kalidarn> like it should be
[11:14] <persia> Oh, no the scheme is correct, you just also need to have the orig.tar.gz file.
[11:14] <Kalidarn> yeah it is an orig file though
[11:17] <Kalidarn> persia, if i use debuild -S
[11:17] <Kalidarn> it should build it
[11:17] <Kalidarn> properly
[11:17] <Kalidarn> This package has a Debian revision number but there does not seem to be
[11:17] <Kalidarn> an appropriate original tar file or .orig directory in the parent directory;
[11:17] <Kalidarn> (expected mktorrent_0.9.9.orig.tar.gz or mktorrent-0.9.9.orig)
[11:17] <persia> You need to construct the orig.tar.gz separately.
[11:17] <Kalidarn> it does say that though
[11:18] <persia> Put all the upstream stuff in a directory, and tar it up.  Call this mktorrent_0.9.9.orig.tar.gz
[11:18] <Kalidarn> ah
[11:18] <persia> Then put that in the directory under your build directory when you call debuild -S
[11:19] <Kalidarn> i thought the orig file was done automatically
[11:20] <slytherin> Kalidarn: usually the .orig.tar.gz file is just the upstream tarball renamed.
[11:20] <Kalidarn> AH
[11:20] <Kalidarn> okays
[11:20] <Kalidarn> i had it in there
[11:20] <Kalidarn> not renamed
[11:20] <Kalidarn> okays
[11:22] <Kalidarn> Successfully uploaded mktorrent_0.9.9-0ppa1.dsc to ppa.launchpad.net.
[11:22] <Kalidarn> Successfully uploaded mktorrent_0.9.9.orig.tar.gz to ppa.launchpad.net.
[11:22] <Kalidarn> Successfully uploaded mktorrent_0.9.9-0ppa1.diff.gz to ppa.launchpad.net.
[11:22] <Kalidarn> Successfully uploaded mktorrent_0.9.9-0ppa1_source.changes to ppa.launchpad.net
[11:22] <Kalidarn> there we go ;)
[11:24]  * Kalidarn waits for his email
[11:25] <Kalidarn> persia,
[11:25] <Kalidarn> the first time it accepted it
[11:25] <Kalidarn> without an orig file
[11:25] <Kalidarn> i just checked the email
[11:26] <Kalidarn> i think it might be that bug
[11:26] <Kalidarn> u talked about
[11:26] <Kalidarn> which is why it is ignoring me not rejecting or accepting
[11:35] <Kalidarn> i might check back in a few hours
[12:21] <handschuh> since it is revu-day, I would kindly ask to review a package: http://revu.ubuntuwire.com/details.py?package=h2database . thanks!
[13:00] <slytherin> handschuh: what is the package about?
[13:01] <handschuh> slytherin: the h2 database lib
[13:01] <handschuh> slytherin: h2database.com
[13:25] <slytherin> handschuh: free enough?
[13:27] <handschuh> slytherin: yes
[13:27] <slytherin> handschuh: can you please try compiling a package from debian for me? I want to file a sync request but don't have access to jaunty pbuilder.
[13:28] <handschuh> slytherin: sure!
[13:29] <slytherin> handschuh: http://packages.qa.debian.org/libj/libjboss-web-services-java.html use 'dget <link_to_dsc_file>' to get the source and do a simple pbuilder --build *.dsc
[13:29] <handschuh> slytherin: ok
[13:31] <nhandler> You could also use pull-debian-source to get the source ;)
[13:31] <slytherin> nhandler: didn't know that. thanks. :-D
[13:33] <nhandler> slytherin: It is in the ubuntu-dev-tools trunk bzr branch, but not in the repositories yet
[13:34] <handschuh> slytherin: it takes a few minutes
[13:55] <handschuh> slytherin: sorry for the long time it took, build was successfull
[13:56] <handschuh> slytherin: http://pastebin.ubuntu.com/93186/
[14:02] <handschuh> slytherin: does that satisfy you?
[14:07] <handschuh> slytherin: the content of the package: http://pastebin.ubuntu.com/93194/
[14:09] <slytherin> handschuh: thanks. It doesn't matter to me what the content is as long as it builts.
[14:10] <handschuh> slytherin: ok great
[14:19] <nhandler> If we are touching an old Ubuntu package that is not in debian, should we bump the debhelper Build-Depends and debian/compat if they are less than 5?
[14:20] <persia> nhandler, That would be a good idea.  Updating to current standards is also appreciated.
[14:20] <persia> In fact, if you want to do something like update to dh7 or other packaging experimentation, those packages are great candidates.
[14:21] <nhandler> persia: I thought we were only meant to use dh7 ir the package really needed it because it made it difficult to backport
[14:22] <NCommander> nhandler, that was fixed
[14:22] <persia> nhandler, That's the regular recommendation, but for the Ubuntu-local packages, if you want to experiment, go ahead, unless you think they ought be backported.
[14:22] <NCommander> nhandler, but its still recommended that you use the lowest possible dh version
[14:23] <NCommander> persia, we backported debhelper since the number of dh 7 packages kept increasing
[14:23] <persia> Oh, then it doesn't matter at all.
[14:23] <NCommander> hey DktrKranz
[14:24] <DktrKranz> hey NCommander
[14:24] <nhandler> Thanks persia and NCommander
[14:26]  * NCommander waits for REVU's source code to check out
[14:26] <DktrKranz> NCommander, is REVU broken sorting "updated packages"? I see packages already in the archives into "New packages" section.
[14:26] <NCommander> I need its legal checker
[14:26]  * NCommander ughs
[14:26] <NCommander> Quite possibly
[14:27] <persia> Isn't that just licensecheck?
[14:27] <NCommander> I'm on dialup ATM, so I can't really check
[14:27] <NCommander> (REVU's source is taking forever to checkout)
[14:27] <NCommander> Well
[14:27] <NCommander> I just learned something ;-)
[14:27] <nhandler> NCommander: If you just want to look at the code, wouldn't it be faster to use the web interface on LP?
[14:27] <Kalidarn> mmm
[14:27] <Kalidarn> this is annoying its still not giving me any email
[14:28] <Kalidarn> of whether it accepted or rejected my upload
[14:28] <Kalidarn> although it says it uploaded successfully.
[14:28] <nhandler> Kalidarn: Where did you upload to?
[14:28] <Kalidarn> my ppa
[14:28] <Kalidarn> i made a boo boo the first time
[14:28] <Kalidarn> with the naming
[14:28] <Kalidarn> and it accepted it
[14:28] <Kalidarn> so i tried fixing it
[14:28] <Kalidarn> now i can't do anything
[14:28]  * NCommander works on dropping licensecheck into dak.
[14:28] <Kalidarn> nobody knows about my ppa it'd be nice if some kind admin could scrub it
[14:29] <persia> Kalidarn, ppa admins are in #launchpad
[14:29] <Kalidarn> yar
[14:30] <AnAnt> Hello, why isn't gnome-python-extras sync'ed/merged from Debian ?
[14:31] <persia> AnAnt, Have you checked for a merge or sync bug?
[14:31] <NCommander> We're past DIF AnAnt
[14:31] <AnAnt> in Ubuntu it is 2.19.1-0ubuntu13, while in Debian it is 2.19.1-3
[14:32] <AnAnt> NCommander: I know, I'm wondering why the import wasn't done
[14:32] <persia> AnAnt, Might be different orig.tar.gz files that mean it's hard to sync.
[14:32] <AnAnt> I see
[14:33] <AnAnt> persia: no, I didn't check for a merge/sync bug
[14:38] <persia> AnAnt, Well, that's the first place to check.  If there's no bug, then it's maybe worth looking at the last changelog entry in Ubuntu: if that doesn't include the fixes from the latest Debian upload, then if you feel it should be merged, prepare a candidate.
[14:40] <Kalidarn> what timezone are most of the canoical people around
[14:40] <Kalidarn> *canonical
[14:42] <nhandler> NCommander: Do you have a list of the current REVU admins? The wiki page is out of date
[14:43] <NCommander> nhandler, ~revu-admins on Launchpad
[14:43] <nhandler> Thanks
[14:43] <persia> Kalidarn, All timezones, really.  This is just a bad week.
[14:43] <Kalidarn> fair enough :)
[15:21] <pmjdebruijn> https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/309684
[15:21] <pmjdebruijn> anybody a clue if there a chance that will gets synced on time?
[15:21] <persia> pmjdebruijn, How do you mean "in time"?
[15:22] <pmjdebruijn> isn't the sync window closing today or tomorrow?
[15:22] <pmjdebruijn> well "in time", for Jaunty...
[15:22] <persia> autosync is closing.  Manual sync continues as long as is required.
[15:22] <pmjdebruijn> ok, good :)
[16:01] <handschuh> may i kindly ask for a review of http://revu.ubuntuwire.com/details.py?package=h2database (java h2 database engine lib)? Thanks in advance
[16:25] <slytherin> is anyone facing problem filing syncrequest with requestsync --lp?
[16:26] <persia> There were reports earlier of it filing 5 or 6 bugs rather than one.
[16:27] <slytherin> I am getting this error - Maybe there is no product 'libjboss-web-services-java' in the distribution 'ubuntu'
[16:27] <slytherin> persia: damn, it indeed files 5 bugs in my case even though I for the error
[16:27] <persia> What does rmadison tell you?
[16:28] <persia> Yeah.  Either fix it, or file the bugs manually.
[16:29] <slytherin> persia: I am now marking the bugs duplicate.
[16:36] <loic-m> Is today a REVU day?
[16:36] <nhandler> Yes loic-m
[16:36] <nhandler> Every Friday is a REVU day
[16:37] <loic-m> Oh, every Friday. I though it was less often
[16:38] <Adri2000> slytherin: bug #311289 - my advice is 'do not use --lp, and trust email rather than python-launchpad-bugs magic' :p
[16:38] <slytherin> Adri2000: The email setup never worked for me before. But I will try again.
[16:38] <nhandler> loic-m: Nope. Every Friday. On REVU, in the top right, it will also display the date of the next REVU day
[16:39] <loic-m> nhandler, thanks
[16:40] <Adri2000> slytherin: if it doesn't work, check that you can connect to fiordland.ubuntu.com on port 25
[16:41] <slytherin> Adri2000: connect as in ssh?
[16:41] <Adri2000> no, telnet fiordland.ubuntu.com 25
[16:42] <Adri2000> it should say 220 fiordland.canonical.com ESMTP Postfix (Ubuntu)
[16:42] <NCommander> what's fiordland?
[16:42] <loic-m> Can somebody review ecm package at http://revu.ubuntuwire.com/details.py?package=ecm ?
[16:43] <Adri2000> NCommander: the default smtp server used by requestsync
[16:43] <Adri2000> [4~[4~[4~[4~[4~[4~[4~[4~[4~
[16:43] <Adri2000> err, sorry
[16:43] <slytherin> Adri2000: I can connect. I will check if it works next time I file a sync request.
[16:54] <jpds> Adri2000: No idea where the 5 bugs filed problem came from... but then again I never use the --lp flag.
[16:55] <slytherin> jpds: I never had problem with --lp till today.
[16:55] <jpds> slytherin: Odd..
[16:55] <slytherin> so probably it is something wrong in LP side
[17:03] <jpds> NCommander: fiordland is where the @ubuntu, etc mail goes through.
[17:42] <slytherin> Do I need to add command dh_installchangelog in debian/rules for upstream changelog to get installed?
[18:00] <ScottK-palm> cody-somerville or NCommander: Would you please arrange to have somone test the proposed backport in Bug 310061 under Xubuntu.  I'd like to make sure we don't break anyone.
[18:00] <NCommander> ScottK-palm, er, wasn't the last time this was tried, things went very very badly?
[18:02] <ScottK-palm> NCommander: That was Intrepid - Hardy and was a bit diifferent.
[18:02]  * NCommander winces
[18:02] <NCommander> but flashplugin-nonfree is a transitional package in jaunty
[18:02] <NCommander> or it will be soon
[18:03] <ScottK-palm> NCommander: That is why I'm asking for testing on i386 and amd64 using all 3 major DE.
[18:03] <NCommander> I'm not running intrepid, and cody is running Hardy ...
[18:03] <NCommander> Your best bet would be asking knome, who hangs out in #xubuntu-devel, he runs intrepid
[18:03] <ScottK-palm> OK.  Surely someone is.
[18:04] <ScottK-palm> NCommander: I'm on the road with limited internet.  Would you, please?
[18:04] <NCommander> I'll poke him for you, but ATM, I can't downgrade
[18:05] <ScottK-palm> Sounds good.  Thanks.
[18:06] <ScottK-palm> NCommander: Do you still have a KDE upload needing sponsorship?
[18:06] <NCommander> Not at the moment
[18:06] <NCommander> I can't download source packages ATM
[18:07] <ScottK-palm> OK.  Off for now then.
[18:07] <directhex> looks like yesterday's wiffle problems are driver-specific. wifey's laptop connected fine to father in law's wifi under intrepid
[19:25] <leonel> sebner: what's to do for the  cherokee 0.11.6 merge ??
[19:26] <sebner> leonel: nothing, it's a sync O_o
[19:26] <leonel> sebner: this for bug 311598
[19:26] <leonel> sebner: ok so just wait ?
[19:26] <sebner> leonel: yep, I already subscribed ubuntu-archive so you don't have to wait for sponsorship (I'm MOTU)
[19:27] <leonel> sebner: great
[19:27] <sebner> leonel: np
[21:55] <loic-m> I'm trying to learn a bit more about packaging by reviewing some packages on REVU, and I'd like to know if they're all supposed to build ok with debuild -S -uc -us
[21:56] <loic-m> Because a few I tried don't
[21:57] <Adri2000> that should build the source package indeed
[21:58] <loic-m> So if they don't, how can i check it's not my setup?
[21:59] <LaserJock> loic-m: if you pastebin the error we can have a look
[22:00] <loic-m> It's a simple error - all packaes around cdemu have a line that pose problems : include /usr/share/quilt/quilt.make
[22:01] <LaserJock> loic-m: apt-get install quilt then
[22:03] <loic-m> LaserJock: thanks. I thought it should have been handled by the package dependencies
[22:03] <loic-m> LaserJock: http://pastebin.com/d25517163
[22:04] <LaserJock> loic-m: quilt should be in the build dependencies
[22:04] <LaserJock> loic-m: but there aren't really source package build dependencies
[22:04] <LaserJock> generally though if you have dpatch, debhelper, cdbs, and quilt installed you'll not run into many problems
[22:05] <loic-m> LaserJock: so the repositories and PPA all have quilt installed?
[22:05] <LaserJock> loic-m: no
[22:06] <LaserJock> loic-m: but building a source package is different then building the binary packages
[22:06] <loic-m> LaserJock: ok, now I understand
[22:07] <loic-m> LaserJock: so as long as pbuilder is ok afterwards, this kind of errors aren't a problem
[22:07] <loic-m> LaserJock: thanks
[22:08] <Laney> loic-m: To build a source package, dpkg-buildpackage runs the clean target of the debian/rules file
[22:08] <Laney> so you have to have installed anything that's run there