[01:13] <postalchris1> Anybody free to look at http://revu.ubuntuwire.com/details.py?package=cvc3 ?
[01:20] <ScottK> postalchris1: You've got a typo in debian/copyright.  There's an incorrect GPL reference at the end.
[01:21] <maxb> postalchris1: I haven't managed to do a full re-review, but I still disagree with the weird version clause that I comment on
[01:21] <maxb> *commented
[01:21] <maxb> I don't think it accomplishes what it claims to
[01:21] <postalchris1> maxb: That's is possible
[01:23] <postalchris1> maxb: I failed to Google the source of the, because "(<< ${binary:Version}.1~)" looks like it has search operators in it, and I don't know how to escape them.
[01:24] <ScottK> postalchris1: Are you in contact with upstream for this package?
[01:24] <postalchris1> ScottK: Good catch. Looking up the proper boilerplate now...
[01:24] <postalchris1> ScottK: Upstream is my academic advisor. So yes.
[01:25] <ScottK> postalchris1: The license is technically Free by our terms, but I would not recommend this go in the Ubuntu archive with the current license.  Others may have a different view.
[01:25] <ScottK> The requirement to get permission to modify or rename is technically acceptable, but very difficult to deal with.
[01:26] <ScottK> Consider what happens if someone discovers a security issue and he is on vacation?
[01:26] <maxb> The packaging of a CVS snapshot from a CVS repository that is not publically accessible also is.... remarkable
[01:26] <ScottK> postalchris1: I would ask you to encourage him to use a less restrictive license.
[01:27] <ScottK> That's another interesting issue.
[01:27] <ScottK> It's not a legal problem though.
[01:28] <postalchris1> ScottK: We're working on relicensing, but who knows when it will go through...
[01:28] <ScottK> With the current license I don't think the package is maintainable.
[01:29] <postalchris1> maxb: You know what? I'm dumb. We publish daily snapshots at http://www.cs.nyu.edu/~barrett/cvc3-latest/
[01:29] <ScottK> correction:  With the current license and name it's not maintainable.
[01:33] <ScottK> postalchris1: Basically if you're Firefox you can, just barely, get away with must have permission to modify without renaming as it's technically DFSG Free, but it's sufficiently onerous that I don't think we want to deal with it.
[01:36] <postalchris1> ScottK: That makes sense. It's unfortunate. We have the intention to relicense *and* the firm assurance of all parties involved that Clause 3 wouldn't be invoked in the case of routine maintenance.
[01:38] <ScottK> postalchris1: Could they publish some kind of addendum or exception and add it to the source tree?
[01:38] <postalchris1> ScottK: Not sure what you mean.
[01:39] <ScottK> If there was something in the upstream source that said 'normal maintenance is ok', perhaps we could call that good enough.
[01:40] <postalchris1> ScottK: I'm sure I could swing that. Seems pretty weak, legally, though.
[01:41] <ScottK> postalchris1: My thought is if that 'firm assurance' could be reduced to writing in the tarball, then maybe it's good enough.
[01:41] <ScottK> The thing is it's DFSG Free and legal for the archive as it is, just very uncomfortable.
[01:41] <ScottK> So I'm trying to reduce that uncomfort.
[01:44] <postalchris1> ScottK: Cool. I'll look into it.
[07:13] <dholbach> good morning
[07:17] <iulian> Morning dholbach.
[07:18] <dholbach> hi iulian
[07:39] <quadrispro> hi guys
[07:49] <didrocks> good morning o/
[07:49] <dholbach> hey di
[07:49] <dholbach> didrocks :)
[07:49] <didrocks> Hi dholbach :)
[08:49] <geser> good morning
[08:52] <mok0> morning geser
[09:17] <pochu> would a kde3->kde4 port be considered bugfix or new feature (in terms of FF)?
[09:17] <pochu> package is minirok
[09:28] <geser> I'd consider it as both: bugfix and new feature (but I'm not from ~motu-release so you can ignore me :)
[09:53] <dolanor> I have a question about encoding
[09:54] <dolanor> I've got a tar.gz with every file in it in iso-8859-15 encoding ... With french accent éèàâ, etc
[09:55] <dolanor> does it cause a problem ? May I "patch" the source to get everything in utf8 with iconv ?
[09:55] <liw> it shouldn't cause a problem, but you could still talk upstream into converting to utf8
[09:56] <dolanor> okay
[09:56] <dolanor> because i have added some manpages totally in utf8... the fact that some files are in utf8 and others in iso-8859-15 doesn't cause any problem too ?
[09:57] <liw> as long as your editor can deal with it, it should be fine
[10:38] <dolanor> liw: btw, is there a utility to give encoding of a text file ?
[10:39] <geser> try file
[10:43] <liw> dolanor, not fully reliably; moreutils has isutf8 to see if it is syntactically valid utf8, file makes some guesses, but on the whole, you have to look at the file in various encodings and decide which is most likely
[10:44] <dolanor> ok
[10:45] <mok0> I just had to clean up a major mess caused by schroot's use of logical lvm volumes.  Anyone else has experiences with that?
[10:55] <quadrispro> hi mok0, I've followed your suggestions -> http://revu.ubuntuwire.com/p/mandvd
[10:57] <quadrispro> I've uploaded the package now
[11:09] <mok0> quadrispro: good
[11:11] <mok0> quadrispro: I need to test-drive my sbuilder after messing with the lvm's, might as well use mandvd as an example
[11:12] <quadrispro> ok ;)
[11:12] <mok0> yay it works
[11:13] <quadrispro> yeah :)
[11:16] <Laney> mok0: If you want jeuclid in Ubuntu you better upload it yourself - it might not get into Debian in time. (I think it was you that wanted it)
[11:16] <mok0> Laney: we still have a week :-P
[11:16] <Laney> hmm
[11:16] <Laney> I dunno, it's cutting it fine
[11:16] <mok0> Too close for comfort, huh?
[11:16] <Laney> but it might start moving after lenny releases
[11:17] <Laney> up to you
[11:17] <mok0> k
[11:21] <ScottK> mok0: I've got the package that's #2 in the Debian New queue among the packages not obviously on long term hold and it's been there for at least a couple of weeks.  With a release is two days, I seriously doubt New is going to be on ftp-masters TODO before our FF.
[11:21] <mok0> ScottK, you're probably right
[11:21] <mok0> I'll take a look at jeuclid then. Laney, have you tried building it?
[11:22] <ScottK> Worst case is there's an additional sync, which is not a big deal.
[11:22] <Laney> mok0: No, I'm not interested in it. I just thought you were so I let you know
[11:22] <mok0> ScottK, can we ask the archive admins to sync from the NEW queue?
[11:22] <Laney> no, it's opaque
[11:22] <ScottK> No.  New isn't publically accessible.
[11:22] <Laney> You can't get at the files
[11:22] <mok0> Huh?
[11:23] <ScottK> Their theory is they don't know if it's distributable until after it's reviewed.
[11:23] <ScottK> So they want to make sure it isn't being distributed.
[11:23] <mok0> d'Oh
[11:23] <mok0> uhm, I seem to remember it was in a ppa somewhere
[11:24] <Laney> It's maintained by debian science team, so they probably have it in svn
[11:24] <ScottK> Generally one can fish the packaging out of a VCS somewhere or worst case mail the maintainer and construct and equivalent package.
[11:24] <ScottK> mok0 probably even knows where that one is.
[11:24] <mok0> So, I should probably send it to revu
[11:24] <ScottK> ;-)
[11:24] <mok0> Yes I think so
[11:25] <ScottK> If you upload it in your name it's not strictly required.
[11:25] <ScottK> Last I checked anyway ....
[11:25] <Laney> mok0: Do your own review, and take the DD uploading as the other one
[11:25] <slytherin> Koon: did you pickup libjcip-annotations-java directly frmo new queue?
[11:25] <Laney> unless you want to seek further input
[11:26] <mok0> Laney: It's java right?
[11:26] <mok0> I don't know much about java
[11:26] <Laney> yeah
[11:27] <directhex> Laney, RAOF went into hiding without sorting sublib :(
[11:27] <Laney> psh
[11:27] <Laney> wait until tomorrow (hopefully)
[11:28] <Laney> or else sebner should be around
[11:30] <quadrispro> mok0: if you would see the buildlog -> http://home.alessiotreglia.com/jaunty/result/mandvd_2.5-4-0ubuntu1/mandvd_2.5-4-0ubuntu1.buildlog
[11:30] <mok0> quadrispro: thx
[11:32] <mok0> quadrispro: you should document in debian/changelog that you have authored a manpage
[11:32] <mok0> I know there's some confusion about this so I write it here
[11:33] <quadrispro> mok0: ah ok, I'm workin on it now
[11:33] <mok0> Also .desktop file
[11:33] <mok0> Anything that is user visible in the package, that you add, should be documented in debian/changelog
[11:34] <quadrispro> ok
[11:34] <quadrispro> so, manpage and .desktop files...
[11:34] <quadrispro> ok
[11:34] <mok0> quadrispro: :-) yes
[11:35] <mok0> I am rehashing it in the channel in the hope that the misunderstanding can go away
[11:36] <mok0> It'a policy §4.4
[11:36] <quadrispro> mok0: upstream provides a .desktop file, but it needs to be fixed. What solution could be better? Add a new .desktop or fix that shipped with the original tarball?
[11:37] <mok0> quadrispro: err, well, since there's no patch system used in the package, it's perhaps a bit much just to fix a .desktop entry
[11:38] <mok0> quadrispro: When the new source package format comes into use, there's an implicit patch system, that will help a lot
[11:39] <quadrispro> mok0: yeah, I think it's not good introduce a patch system only for a .desktop file, then I will fix mandvd.desktop
[11:40] <mok0> quadrispro: ok, perhaps send the corrected file upstream
[11:40] <quadrispro> of course
[11:41] <mok0> ScottK, I'll make you a sweet deal: if you review some of my advocated packages in revu, I'll review/upload the plasma_widget ones B-)
[11:42]  * ScottK looks
[11:43] <mok0> ScottK, there are two libraries that have dependents stuck in the pipeline
[11:43] <ScottK> mok0: OK, but it may be Saturday before I have time.
[11:43] <mok0> ScottK, NP
[11:44] <mok0> Has anyone looked at my mock-up revu site?
[11:46] <quadrispro> mok0: new package uploaded to REVU
[11:46] <mok0> quadrispro: super
[11:46] <quadrispro> :)
[11:53] <quadrispro> mok0: don't hate me :) http://revu.ubuntuwire.com/p/nfoview
[11:53]  * mok0 is confused... is it REVU day :-P
[11:54] <ScottK> Should start in about 6 minutes, right?
[11:54] <mok0> Heh
[11:54] <mok0> yes
[11:56] <quadrispro> mok0: that package is very simple, and I think it's ready really
[11:56] <quadrispro> :)
[11:56]  * mok0 is looking
[11:57] <mok0> Hm, never heard of nfo format before now
[11:58] <mok0> quadrispro: tsk tsk not lintian clean
[11:59]  * quadrispro nooooo
[11:59] <quadrispro> it's true :(
[11:59] <mok0> heh
[11:59] <quadrispro> working on it
[12:00] <mok0> don't upload yet there might be more
[12:00] <quadrispro> mok0: all the fans of emule/bittorent services know well .NFO files :)
[12:00] <quadrispro> mok0: ok
[12:01] <mok0> Ah, perhaps my son knows about it
[12:01] <quadrispro> maybe :)
[12:01] <quadrispro> mok0: http://en.wikipedia.org/wiki/.nfo
[12:02] <mok0> quadrispro: I'm gonna use that for my next personal homepage :-)
[12:03] <mok0> quadrispro: the "retro" look
[12:03] <quadrispro> yeah, it's very "cool" :D
[12:06]  * mok0 wonders why the .desktop "Encoding" statement is deprecated...
[12:06] <mok0> Seems rather sensible /me thinks
[12:07] <mok0> quadrispro: for you next package, use this:  http://wiki.debian.org/Proposals/CopyrightFormat
[12:08] <quadrispro> ah good
[12:08] <mok0> quadrispro:  Take a look at http://packages.debian.org/changelogs/pool/main/g/git-cola/current/copyright for an example.
[12:11] <quadrispro> mok0: I could try to apply now that format
[12:12] <quadrispro> * template
[12:12] <mok0> quadrispro: just curious, why didn't you choose a cdbs rules file?
[12:12] <mok0> quadrispro: great
[12:12] <quadrispro> mok0: mmm I don't know why, I prefer to use setup.py...
[12:13] <mok0> quadrispro: so does cdbs
[12:13] <quadrispro> in fact
[12:13] <quadrispro> ok, i'll use cdbs and apply that template :)
[12:14] <mok0> quadrispro: http://pastebin.com/f64a2d3ca
[12:14] <quadrispro> ok
[12:15] <mok0> quadrispro: ... and you don't need to tussle with reviewers about debian/rules :-)
[12:15] <quadrispro> lol :)
[12:15] <quadrispro> ok
[12:16] <mok0> quadrispro: your rules file was fine though, no problems
[12:21] <quadrispro> mok0: http://paste.ubuntu.com/117226/
[12:22] <mok0> quadrispro: yes, but remember the format is like debian/control. You need " ." to specify a line-break
[12:22] <mok0> quadrispro: (at lines 13 and 18)
[12:23] <mok0> quadrispro: that makes it RFC822 format, and it can be read by the standard tools
[12:23] <quadrispro> ah ok
[12:23] <mok0> quadrispro: so, perhaps someone will write a nice "copyright-viewer"
[12:24] <quadrispro> mok0: http://paste.ubuntu.com/117228/
[12:25] <mok0> quadrispro: TBH, I am unsure if it is correct
[12:25] <mok0> quadrispro: AFAIC, the text will only be wrapped correctly if it starts in column 2
[12:26] <quadrispro> you're right
[12:26] <mok0> quadrispro: ... and if it is indented 2 spaces or more, it will not be wrapped
[12:26] <mok0> I am?
[12:26] <mok0> :)
[12:26] <quadrispro> eh
[12:26] <quadrispro> :D
[12:26] <quadrispro> I'm doing a lot things at the same time
[12:27] <mok0> OK, I am going to lunch, see you later
[12:27] <quadrispro> ;) bye
[12:28] <Koon> slytherin: I had to merge it to fix a default-jdk/gcj mismatch. It's published now. libjboss-cache2-java can now build too.
[12:39] <quadrispro> mok0: I've uploaded nfoview to REVU, I didn't change copyright/rules because a lot of lintian warnings
[12:39] <quadrispro> see you later, I'm going to lunch
[12:45] <slytherin> Koon: I had seen that problem. I was planning to log bug in Debian.
[12:45] <Koon> slytherin: I'll push it back there. Though I'm not sure they are affected by it
[12:46] <slytherin> Koon: They are not. But the problem in my opinion is that when you specify default-jdk as build dep you should use default-java as java_home
[12:46] <Koon> slytherin: definitely.
[12:47] <Koon> note that for libhibernate3-java I'll fix it the other way around. Doesn't build with openJDK so it requires gcj ;)
[12:47] <Koon> slytherin: bug 328391 if you want to follow that story
[12:47] <slytherin> Koon: right.
[12:48] <Koon> i'll push that one as soon as libjboss-cache2-java clears binary NEW
[12:49] <slytherin> Koon: meanwhile if you are not too busy, can you please file movetouniverse bugs for remaining jboss/hibernate related packages?
[12:50] <Koon> slytherin: will do if I can enjoy some free time. Unfortunately it's been 10 days that I rush, not sure I can do that before FF
[12:51] <slytherin> Koon: Ok. If you don't do it by weekend I will take care of it.
[12:56] <geser> slytherin, Koon: for moving libhibernate3-java to universe see also my last comment in bug 252318
[12:56] <geser> (yes, the bug should be retitled)
[12:56] <slytherin> geser: and also we should add 'also affects' for oscache, libhibernate3-java
[12:57] <Koon> geser: interesting. I missed that. Thx !
[13:06] <dolanor> I've reuploaded new version of hexdiff, a tool to visualize the hexadecimal differences between 2 files (http://revu.ubuntuwire.com/details.py?package=hexdiff). If it could get some REVU before the 19th :p
[13:18] <mok0> quadrispro: lazy huh? ;-)
[13:22] <mok0> quadrispro: I don't like the way you are fixing the .desktop entry
[13:27] <quadrispro> mok0: I've uploaded new version (using cdbs)
[13:28] <mok0> quadrispro: you need to put some dependencies in control, did you do that?
[13:28] <quadrispro> http://home.alessiotreglia.com/jaunty/result/nfoview_1.2.1-0ubuntu1/
[13:28] <quadrispro> mmm
[13:29] <quadrispro> it needs python-gtk2 and python-glade2
[13:29] <mok0> binary-install/nfoview::
[13:29] <mok0> 	dh_desktop -pnfoview
[13:29] <mok0> quadrispro: huh?
[13:29] <mok0> you need to depend on cdbs and python
[13:30] <quadrispro> mok0: eh, the package build-depends on cdbs and python...
[13:30] <quadrispro> mok0: dh_desktop is necessary, otherwise it doesn't update the MIME cache
[13:31] <mok0> quadrispro: right, so you can add a rule binary-install/nfoview:: that calls it
[13:32] <mok0> quadrispro: http://pastebin.com/f7e14efad
[13:32] <quadrispro> done
[13:32] <quadrispro> dputting to revu
[13:32] <mok0> quadrispro: and in copyright, after the GPL license text, add the following:
[13:33] <mok0> X-Comment: On Debian GNU/Linux systems, the complete text of the GNU
[13:33] <mok0>  General Public License can be found in /usr/share/common-licenses/GPL-3
[13:33] <mok0> oops
[13:33] <mok0> 2 lines
[13:33] <quadrispro> there's "On Debian systems, the complete text of the GNU General\nPublic License can be found in `/usr/share/common-licenses/GPL-3'.
[13:33] <quadrispro> isn't it right?
[13:33] <mok0> yes. there is?
[13:34] <quadrispro> yes
[13:34] <quadrispro> mok0: http://revu.ubuntuwire.com/revu1-incoming/nfoview-0902121433/nfoview-1.2.1/debian/rules
[13:34] <quadrispro> and http://revu.ubuntuwire.com/revu1-incoming/nfoview-0902121433/nfoview-1.2.1/debian/copyright
[13:34] <mok0> quadrispro: I was talking about the other copyright file you made
[13:35] <quadrispro> ah ok ok
[13:35] <mok0> http://pastebin.com/f3b4f627
[13:35] <quadrispro> mok0: but I've tried to make the copyright file according with that new template, but lintian gaves me a lot of warnings :(
[13:35] <mok0> quadrispro:  ^
[13:35] <quadrispro> gave *
[13:36] <mok0> quadrispro: I just tried building with the above file, it gives no warnings
[13:36] <quadrispro> oh ok :) thanks
[13:36] <mok0> quadrispro: I was wondering about your message before lunch
[13:36] <mok0> quadrispro: so I tried it
[13:37] <soren> quadrispro: The call to dh_desktop is there automatically if you include the gnome cdbs class.
[13:37] <quadrispro> ah good
[13:37] <mok0> soren: yeah but we're not building a gnome app, so why add the builddepens?
[13:38] <soren> Ah, sorry, I thought it was a gnome-ish thing. What's it for, then?
[13:38] <mok0> s/ns/nds
[13:38] <mok0> soren: just a python program
[13:39] <mok0> soren: with a python-gtk2 gui
[13:39] <soren> mok0: the gnome class is in cdbs itself.
[13:39] <mok0> soren: ah, ok
[13:39] <mok0> :)
[13:39] <mok0> soren: I stand corrected and humble
[13:40] <soren> :)
[13:42] <quadrispro> I've started to build with calling gnome class
[13:42] <quadrispro> mok0: uploading to REVU again
[13:43] <quadrispro> mok0: done
[13:43] <quadrispro> soren: thanks!
[13:43] <soren> sure
[13:43] <mok0> quadrispro: is it there already?
[13:44] <quadrispro> eh, no
[13:45] <quadrispro> mok0: REVU's showing it
[13:45] <mok0> quadrispro: k
[13:49] <mok0> quadrispro: FAILED [dpkg-buildpackage died]
[13:49] <quadrispro> =-O
[13:49] <quadrispro> http://home.alessiotreglia.com/jaunty/result/nfoview_1.2.1-0ubuntu1/nfoview_1.2.1-0ubuntu1.buildlog
[13:50] <mok0> quadrispro: can't explain that, but the gnome think pulls in some autoconf checks that I think you don't want
[13:50] <mok0> s/think/thing
[13:51] <mok0> quadrispro: let me go back to your penultimate upload
[13:52] <quadrispro> ok
[13:52] <quadrispro> sure
[13:53] <mok0> quadrispro: your upload from 12 Feb 2009 14:39 builds perfectly
[13:54] <quadrispro> mok0: ok, is it necessary anohter upload?
[13:54] <mok0> quadrispro: unfortunately, yes
[13:54] <mok0> quadrispro: you should not have listened to soren ;-)
[13:55] <quadrispro> preparing another upload.... uff! :)
[13:55] <soren> mok0: build log?
[13:55] <quadrispro> soren: http://home.alessiotreglia.com/jaunty/result/nfoview_1.2.1-0ubuntu1/nfoview_1.2.1-0ubuntu1.buildlog
[13:55] <mok0> soren: I can pastebin some of it
[13:55] <soren> ...from the failed build.
[13:56] <quadrispro> ah sorry :D
[13:57] <mok0> soren http://pastebin.com/f729544d
[13:57] <mok0> soren: it wants to do some autotools fun
[13:57] <soren> where's the configure script?
[13:57] <mok0> soren: there isn't any
[13:58] <soren> Ah.
[13:58] <mok0> soren: It probably assumes there is one because it thinks its a gnome project
[13:59] <mok0> soren: in any case, the extra binary-install:: rule works perfectly :-)
[13:59] <soren> Right.
[14:00] <mok0> In fact the dh_desktop thing is the subject of a flamewar on a bug in BTS
[14:01] <mok0> 439717
[14:01] <mok0> ubottu, can you please give me a BTS link?
[14:02] <mok0> ubottu: oh, I forgot
[14:02] <quadrispro> mok0: uploaded
[14:05] <mok0> quadrispro: +1
[14:05] <quadrispro> thank you mok0
[14:05] <dolanor> I've reuploaded new version of hexdiff, a tool to visualize the hexadecimal differences between 2 files (http://revu.ubuntuwire.com/details.py?package=hexdiff). If it could get some REVU before the 19th :p
[14:05] <mok0> quadrispro: now go fix some bugs
[14:06] <quadrispro> yes :D
[14:06] <mok0> No more new package from you  ;-)
[14:07] <quadrispro> ok ok. I will work hard only on bugufixes :)
[14:07] <mok0> hehe
[14:08] <mok0> dolanor: I'll give it to you straight: there is no COPYING file giving us the permission to distribute the source tree. Without it, we can't distribute :-(
[14:08] <mok0> dolanor: :'( rather
[14:10] <mok0> dolanor: can you contact upstream?
[14:15] <dolanor> mok0: i'm in direct contact with him ^^
[14:15] <mok0> dolanor: cool
[14:15] <dolanor> mok0: I'll do the patch myself and give it to him
[14:16] <mok0> dolanor: errrr, ok, but you can't patch a license file into Ubunut
[14:16] <mok0> Ubuntu
[14:16] <dolanor> mok0: He hasn't time to reupload the new version, but when I'll harrass him to upload the new version on his site, I think he can take time for this :)
[14:16] <mok0> dolanor: good
[14:17] <dolanor> no no, I take the orig.tar.gz, increment the version, add a COPYING, and base my ubuntu package on it :)
[14:17] <dolanor> and mail the new tar.gz to upstream
[14:17] <dolanor> I always ask him first
[14:17] <mok0> dolanor: sounds reasonable :-)
[14:18] <dolanor> so a COPYING file is missing in the root oif the archive ?
[14:18] <dolanor> is there any COPYING sample for a really simple source package ? :)
[14:28] <mok0> dolanor: if you look in the file fileinfo.c, there's a URL to the license text
[14:29] <mok0>  http://sam.zoy.org/projects/COPYING.WTFPL
[14:29] <mok0> dolanor: ... so you need to change debian/copyright accordingly
[14:30] <mok0> I guess WTFPL is DFSG compliant
[14:50] <mok0> Hi RainCT, how did your exam go?
[14:52] <dolanor> mok0: do I put COPYING into the debian/doc ?
[14:52] <mok0> dolanor: no, it will be installed automatically when dh_installdocs is called
[14:53] <dolanor> ok
[14:53] <mok0> dolanor: as long as it's called COPYING
[14:57] <dolanor> mok0: and, for the debian/copyright, Do i have to put that the packaging is under GPL ?
[14:57] <pmjdebruijn> probably yes
[14:57] <mok0> dolanor: it's up to you
[14:58] <mok0> dolanor: either that or the same license as the software
[15:00] <dolanor> mok0: So I must precise it in the copyright : upstream is wtfpl and packaging is gpl ?
[15:00] <dolanor> with copy of each license in it
[15:01] <mok0> dolanor: yes, if you use the new copyright format, you just need a section for Files: debian/* with your license details
[15:06] <bddebian> Heya gang
[15:10] <dolanor> mok0: didn't find the new copyright format, do you have any links ?
[15:10] <mok0> !copyright
[15:11] <mok0> http://wiki.debian.org/Proposals/CopyrightFormat
[15:14] <dolanor> thank you, modifying the stuff :) I didn't see your remarks on revu :o
[15:14] <mok0> dolanor: ah :-)
[15:15] <mok0> dolanor: I always put them there even when doing IRC reviews
[15:15] <slytherin> slomo: is there any plan to sync/merge libdvdread/libdvdnav from Debian experimental?
[15:18] <mok0> dolanor: you don't have fixes for all of my comments
[15:22] <slytherin> does anyone know what speeds up the boot time, is it building most of the things as modules or building everything 'build-in'?
[15:22] <mok0> slytherin: I don't think it makes a lot of difference
[15:23] <mok0> slytherin: most of the boot time is starting services
[15:23] <mok0> slytherin: ... and the fact they are started serially
[15:24] <slytherin> mok0: I have built a custom kernel. And now I plan to tweak it to remove unnecessary parts.
[15:24] <mok0> slytherin: I've tried that several times. Never could get it to work right :-P
[15:25] <mok0> slytherin: now I just use ubuntus generic kernel
[15:27] <slytherin> mok0: what problems did you face?
[15:27] <mok0> slytherin: ah, can't remember, it was several years ago
[15:27] <mok0> slytherin: kernel panic was one of them
[15:29] <superm1> jdong, siretart wgrant_ can one of you merge  lp:~andreas-wenning/vlc/ubuntu into ~motumedia/vlc/ubuntu?  I was going to upload andreas merge (builds fine and solves the bug), but then i realized i cant merge into ~motumedia (What's that team for, shouldn't ubuntu-dev own it?)
[15:34] <geser> slytherin: last time I did my own kernels (all needed modules built-in), I had to either still use an initramfs (because of the UUIDs) or use the /dev/sdXY in the grub menu
[15:35] <slytherin> geser: I have just started to play with it, so can't really say I understand all the things involved. Anyway, will do the experimenting at home now.
[15:38] <superm1> dtchen, too about vlc^
[15:38] <geser> slytherin: I used to build my own kernels in the past. The only real benefit was a smaller kernel deb. And you need keep track of kernel updates yourself.
[15:40] <dolanor> mok0: I'm not sure about which keys to press to get a minus instead of hyphen ...
[15:40] <mok0> dolanor: just press - on your keyboard, but prefix it with backslash in the file, like so: \-v
[15:41] <mok0> dolanor: it's because in nroff, - means hyphen and \- means minus
[15:42] <mok0> dolanor: when typeset on the screen, you can't tell the difference, but when rendered for a printing device, you can
[15:43] <dolanor> mok0: ok, thanks :)
[15:47] <henrik-hw0> does feature-freeze apply to packages in the advocation queue?
[15:47] <ScottK> It has to be uploaded to Ubuntu by Feature Freeze.
[16:04] <mok0> Where can I find the script that does the merging on DaD?
[16:06] <dolanor> mok0: the Copyright review seems very cool :) I hope it will facilitate the revuing :)
[16:07] <iulian> mok0: http://dad.dunnewind.net/grab-merge.sh?
[16:07] <mok0> iulian: errhm not that, the script that generates what grab-merge fetches
[16:07] <Laney> mok0: launchpad.net/dad
[16:07] <iulian> Ah
[16:07] <mok0> Laney: hah, but of course! Thanks!
[16:08]  * mok0 kicks self
[16:08] <Laney> looks like a massive bash script
[16:08]  * Laney dies /o\
[16:20] <chrismurf> Would a MOTU mind reviewing http://revu.ubuntuwire.com/p/pyproj?  It's a python wrapper for PROJ.4 (a map projections library).  I've already corrected some initial problems found by fabrice_sp__.
[17:01] <siretart> superm1: you're right, that branch should probably be in ~ubuntu-dev. feel free to push the merge there!
[17:03] <mok0> chrismurf: pyproj reviewed...
[17:03] <chrismurf> mok0, thank you
[17:03] <mok0> chrismurf: you're welcome :-)
[17:04] <chrismurf> the debian/watch I basically copied
[17:04] <chrismurf> Is there actual documentation on that someplace?
[17:04] <chrismurf> a manpage or anything?
[17:04] <mok0> chrismurf: intersting...
[17:04] <chrismurf> google is frustratingly useless
[17:04] <mok0> man uscan
[17:04] <chrismurf> ah - thank you
[17:04] <mok0> chrismurf: oh, yes, google for watch :-)
[17:04] <chrismurf> ah!  wonderful
[17:05] <mok0> chrismurf: the man page has bad practice in the examples, though
[17:05] <chrismurf> lol - fantastic
[17:05] <mok0> chrismurf: it mentions (.*) which can give problems
[17:05] <chrismurf> ok
[17:05] <mok0> chrismurf: it's better to do what you are doing
[17:06] <mok0> chrismurf: then you make sure it is fetching a revision number like 1.2.3
[17:07] <chrismurf> makes sense
[17:08] <mok0> chrismurf: anyway I'll keep an eye on pyproj and +1 it
[17:08] <chrismurf> thanks - making those changes now
[17:10] <chrismurf> one more random question -- how do I setup gpg/debuild to use the correct signing key by default?  I have to specify -k* each time
[17:11] <chrismurf> mok0, you suggest replacing pyversions with XS-Python-Version, but python-distutils says that XS-Python-Version is deprecated and suggests doing the opposite?
[17:12] <mok0> chrismurf: you have a url for that?
[17:12] <chrismurf> well, it throws a warning on compile
[17:12] <chrismurf> and reading : http://wiki.debian.org/DebianPython/NewPolicy
[17:12] <chrismurf> "For that you should create debian/pyversions" under Using python-support
[17:13] <chrismurf> might be something they've gone back and forth on
[17:14] <mok0> I can't see that in the debianpython document?
[17:15] <mok0> The addition of the XS-Python-Version/XB-Python-Version fields is required.
[17:15] <chrismurf> #3 under "Using python-support"
[17:15] <mok0> The addition of the XS-Python-Version/XB-Python-Version fields is appreciated.
[17:15] <DktrKranz> chrismurf: to avoid -k, edit /etc/devscripts.conf,  DEBSIGN_KEYID
[17:15] <mok0> appreciated?
[17:15] <chrismurf> DktrKranz, thanks
[17:15] <chrismurf> mok0, interesting
[17:16] <chrismurf> and confusing
[17:16] <mok0> chrismurf: appreciated != deprecated
[17:16] <chrismurf> in the top section, under "Using python-support"
[17:16] <chrismurf> not the notes for packaging with private modules
[17:17] <chrismurf> I see where you're pulling from further down too though
[17:17] <chrismurf> which is confusing
[17:17] <DktrKranz> chrismurf: you're welcome
[17:17] <chrismurf> but then when I compile, python-distutils issues the following: http://pastebin.ca/1334955
[17:18]  * mok0 looks
[17:18] <mok0> pysupport... hm
[17:19] <mok0> chrismurf: pysupport is deprecated :-)
[17:19] <chrismurf> haha - I thought pysupport >> pycentral, n'est pas?
[17:19] <jcfp> chrismurf: iirc, python-support uses debian/pyversions, and if that's missing falls back to XS-...; that other python helper uses only the XS-Python-Version thing.
[17:19] <chrismurf> jcfp, thanks - good to know
[17:19] <mok0> jcfp: yes that's right
[17:19] <chrismurf> is pycentral a better way to go for the future/
[17:20] <mok0> chrismurf: I've heard people say so
[17:20] <chrismurf> fair enough - I'll bear that in mind next time
[17:20] <chrismurf> for now -- include both and ignore the warning?  Include just one?
[17:21] <mok0> chrismurf: but both work and are supported
[17:21] <mok0> chrismurf: hm, it seems what you've done is legal for pysupport...
[17:22] <chrismurf> fair enough - thanks for the education though
[17:22] <mok0> chrismurf: I like it better when you can see stuff like that in debian/control, instead of having to browser any number of files to get that info
[17:23] <dolanor> mok0: http://revu.ubuntuwire.com/p/hexdiff
[17:23] <chrismurf> mok0 That makes sense; should I just do both?  Having the info in two places doesn't seem great either
[17:23] <dolanor> I think it may be good
[17:23] <mok0> chrismurf: no it will get out of sync
[17:23] <dolanor> My lintian is oldish ... I'm developing from my server on 8/04
[17:23] <dolanor> 8.04
[17:24] <mok0> dolanor: don't worry, my lintian is brand new :-)
[17:24] <chrismurf> mok0, alright- I'll probably leave it as is then, and chock that up as a -1 for pysupport
[17:24] <mok0> chrismurf: alright
[17:25] <mok0> dolanor: "changed the watch file to work" :-)
[17:25] <RainCT> (lintian on REVU is also the latest version)
[17:25] <mok0> RainCT: yes, but unfortunately it only checks the source package
[17:26] <ScottK> dolanor: Newer lintian (along with other updated tools) can be found in hardy-backports if you haven't checked.
[17:28] <dolanor> ScottK: ok, but I think i'll use the base.tar.gz from pbuilder and chroot into it. I don't wanna backports version on my public server ;)
[17:28] <chrismurf> mok0, updated
[17:29] <dolanor> mok0: yes, because, right now, only a hexdiff.tar.gz exists. but upstream will upload my new version with hexdiff-x.y.z.tar.gz
[17:29] <ScottK> dolanor: Just selectively update from -backports, don't accept everything.
[17:33] <mok0> Hm, I wonder if there's a policy against foul language in licenses....
[17:34] <mok0> dolanor: wrt to the new copyright format, it is exactly the same as for debian/control. The long passage of the licenses should be indented 1 space, and with ' .' representing empty lines
[17:34] <dolanor> ScottK: I have to use pin in apt, no ? Or do you have a command-line to safe-upgrade without using backports?
[17:35] <mok0> dolanor: just download the lintian .deb and install it
[17:35] <dolanor> okay
[17:35] <ScottK> That'll work.
[17:36] <ScottK> More generally, I add the repo to sources.list, apt-get update. apt-get upgrade (but say no when asked to confirm) and then pick the list of packages I want, apt-get install the list, then then comment it out in sources.list.
[17:36] <ScottK> For just lintian, grab the .deb as mok0 says.
[17:37] <mok0> ScottK, that kind of defeats the whole purpose of apt, don't you think?
[17:37] <ScottK> Yep.
[17:38] <ScottK> mok0: Hopefully we have a change for Jaunty that'll make it safe to leave enabled.
[17:38] <mok0> Hm, I haven't met any problems with backports yet
[17:39] <ScottK> I haven't in some time.
[17:39] <ScottK> I find on servers it's quite safe as I'm generally the only one approving serverish backports and I'm careful.
[17:40] <ScottK> We went through a period where some archive admins felt they could just backport at will without going through the backports team and some stuff did get broken.
[17:50] <dolanor> mok0: updated :)
[17:50] <mok0> dolanor: ah, but I have more comments :-)
[17:51] <dolanor> damn, missed them ^^
[17:51] <dolanor> I 'll look at it
[17:51] <mok0> dolanor: still working on them
[17:51] <dolanor> mok0: ok, then i'll come back home :)
[17:55] <mok0> dolanor: ok comments are there, take a look
[17:55] <genii> Hi. Trying to compile arora (webkit/qt based web browser. debian/control states maintainer is ubuntu-motu. Getting this error: http://paste.ubuntu.com/117356/
[17:56] <slomo> slytherin: no idea
[18:00] <slytherin> genii: how are you compiling the package?
[18:02] <genii> slytherin: The git pull provides a builddeb.sh file, contents of which are this: http://paste.ubuntu.com/117359/
[18:02] <ScottK> genii: That just means you tried to sign the package.  If you need to sign the package use -k to tell it what key to use, if not, use -us -uc so stuff doesn't get signed.
[18:03] <ScottK> genii: Then you aren't trying to compile something that we are the maintainer of.
[18:03] <ScottK> Nothing maintained by this group is on github.
[18:04] <genii> ScottK: dpkg-buildpackage -D -b -uc -us         seems to be the flags
[18:04] <genii> Sorry, slytherin ^
[18:04] <ScottK> Yes.
[18:04] <genii> ScottK: Interesting. I wonder why the control file lists here as maintainers.
[18:05] <ScottK> That's what you would want, but really you should ask someone on github for help if that's where it's coming from.
[18:05] <ScottK> genii: Probably someone took an Ubuntu package, put it on github, and modified it.
[18:05] <ScottK> We can't control that, but it's really nothing to do with us.
[18:08] <genii> ScottK: Do you know if there is a freenode github channel? I'll go bother them there if so :)
[18:08] <ScottK> No idea.  Sorry.
[18:08] <genii> OK, thanks
[18:08] <ScottK> genii: Why not try with the actual Ubuntu package?
[18:08] <slytherin> does anyone have any idea what is this file urlclassifier3.sqlite in firefox profile?
[18:09] <ScottK> slytherin: I'd suggest #ubuntu-mozillateam.
[18:09] <genii> ScottK: There seems no package for it yet that I can find
[18:09] <ScottK> genii: What package?
[18:10] <genii> ScottK: arora ...it's a qt based web browser. http://arora-browser.org/ is the homepage if more info is needed
[18:11] <ScottK> Right, you said that.
[18:12] <ScottK> genii: Exists in Intrepid and Jaunty: https://launchpad.net/ubuntu/+source/arora
[18:12] <ScottK> genii: If you are interested in getting it on Hardy, we have a backports process.
[18:12] <ScottK> !backports > genii
[18:13] <genii> ScottK: Ah, OK, explains why this 8.04 box can't find it :) . I'll try build from 8.10 sources or so
[18:14] <genii> ScottK: Thanks again.
[18:17] <surfaz> Anybody could look this?
[18:17] <surfaz> https://bugs.launchpad.net/ubuntu/+source/amule/+bug/328321
[18:46] <Vest84> Hello guys. would a MOTU be so kind as to review my project? http://revu.ubuntuwire.com/details.py?package=gnome-quod m? please...
[18:49]  * mok0 looks
[18:50] <Vest84> o-o-o... thanks in forward
[19:15] <dolanor> back
[19:15] <dolanor> mok0: I think i've corrected every things you've commented. To correct the lintian, I preferred correcting in the upstream version and create a new upstream version ;)
[19:16] <dolanor> http://revu.ubuntuwire.com/p/hexdiff
[19:16] <mok0> dolanor: ah ok, well I guess you are upstreams proxy
[19:16] <mok0> dolanor: will take a look later
[19:19] <mok0> Q: What is the best thing about reviewing?
[19:24] <mok0> A: You get to type "less rules" a lot of times :-P
[19:24] <tgm4883> Come one, come all, step right up and Revu http://revu.ubuntuwire.com/p/mythnettv
[19:24] <mok0> tgm4883: what is it?
[19:25] <tgm4883> it's a program for mythtv that downloads online shows from places like revision 3 and puts them in your recording list
[19:25] <mok0> tgm4883: you in contact with anyone from Ubuntu Studio?
[19:26] <tgm4883> no
[19:26] <tgm4883> should I be?
[19:26] <tgm4883> This is more of a mythbuntu type app
[19:26] <mok0> tgm4883: or mythbuntu... they might be interested in an app like that
[19:26] <tgm4883> ah yea, i'm a mythbuntu dev.
[19:26] <mok0> tgm4883: I can review the packaging
[19:27] <tgm4883> superm1 was suppose to revu this a few days ago, but we overwork him ;)
[19:27] <mok0> tgm4883: ah ok
[19:27] <mok0> heh
[19:28] <tgm4883> i've corrected all the lintian warnings, you may want to take a look at the debian/watch file as I wasn't entirely sure how to handle that but believe it to be ok
[19:28] <mok0> tgm4883: ok wil ldo
[19:29] <superm1> tgm4883, yeah yeah.  okay how about now i've finally got all the other stuff in order for mythbuntu-default-settings, xfce, mplayer, mythtv, transcode, libmjpegtools, the seeds and ubiquity i think i will finally have time to look at that revu
[19:29] <tgm4883> yay :)
[19:29] <superm1> tgm4883, yesterday was a long night trying to track down the fixes for all that other stuff....
[19:29] <mok0> superm1: wait a sec I am revuing it atm
[19:30] <superm1> mok0, okay, i love being revu'er #2 anyway, so much easier :)
[19:30] <tgm4883> superm1, well if you think tracking down bugs is more important than revuing this I suppose that is ok
[19:30] <mok0> superm1: heh, well there are lots of other packages you can amuse yourself with :-)
[19:31] <tgm4883> I also have mythnettv-gui which is the gui frontend for that app, if you guys want to revu the packaging for that too
[19:31] <tgm4883> http://revu.ubuntuwire.com/p/mythnettv-gui
[19:31] <tgm4883> but no rush, there is always tomarrow too ;)
[19:34] <Vest84> mok0: thank you for your review... I'm going to work on it :)
[19:34] <mok0> Vest84: cool
[20:17] <mok0> tgm4883: you have a bunch of myth* packages sitting in the "needs-work" section...
[20:18] <tgm4883> ah yes, hopefully I will be tackling those shortly
[20:18] <tgm4883> its all the mythstream ones right?
[20:18] <mok0> tgm4883: yep
[20:18] <directhex> RAOF hasn't crawled out of bed yet has he? seems not
[20:23] <mok0> ScottK, how is it possible to get mail when a package is uploaded to the archive
[20:23] <mok0> ?
[20:24] <ScottK> mok0: About what?
[20:24] <ScottK> ENOCONTEXT
[20:24] <mok0> When a new package enters the archive
[20:24] <ScottK> You mean any package?
[20:24] <mok0> Yes, a package from revu
[20:25] <ScottK> You could probably scrape that from -changes.
[20:25] <mok0> ScottK, I want to explore your idea of automatically archiving packages
[20:25] <ScottK> You'd need to just look for ones that claimed they were New.
[20:25] <mok0> ScottK, ok, I just need to get the info stream somewhere
[20:27] <ScottK> Subcribe to either jaunty-changes or the ubuntu-nl RSS feed.
[20:27] <mok0> ScottK, ah there's a feed, I was hoping that
[21:23] <jreinhardt> Hi. I packaged a tex package, and lintian tells me:
[21:23] <jreinhardt> E: pgfplots source: missing-build-dependency-for-dh_-command dh_installtex=tex-common
[21:23] <jreinhardt> But tex common is in the Depends list:
[21:23] <jreinhardt> Depends: ${shlibs:Depends}, ${misc:Depends}, pgf (>=2.00), tex-common
[21:23] <jreinhardt> And the package is building fine in pbuilder.
[21:23] <jreinhardt> What shall I do?
[21:24] <directhex> built-depends != depends
[21:24] <directhex> dh_ commands are run at build time, i.e. build-depends
[21:28] <jreinhardt> ok
[21:28] <jreinhardt> thank you
[21:37] <chrismurf> mok0, you there?
[21:39] <superm1> ScottK, can you take a look at something on the sponsorship queue?  i was helping clean up some of the arts transition and there is a kde bit in there i don't want to upload without someone in that pod agreeing: http://launchpadlibrarian.net/21903091/basket_1.0.2-5ubuntu1.debdiff
[21:39] <superm1> (bug 320915)
[21:40] <ScottK> superm1: Since it's awen's debdiff, you can be confident in the KDE stuff.
[21:40] <ScottK> It looks correct to me too.
[21:40] <superm1> ScottK, okay i'll sponsor after i verify it builds then
[21:40] <ScottK> Great.  Thanks.
[22:49] <DktrKranz> RAOF, do you plan to upgrade gnome-do{,-plugins} for gnome-sharp2 transition (bug #314516)?
[22:50] <RAOF> DktrKranz: Yes, but I was planning to fix that by uploading 0.8
[22:50] <RAOF> Which is pretty much ready.  I should probably claim that bug.
[22:50] <DktrKranz> RAOF, really a good news! I look forward to see new 0.8 :)
[23:05] <chrismurf> I asked a question on debian-mentors about packaging, and they're now trying to convince me to work with the DPMT to start with because then the package will get "pulled in" to ubuntu anyway.  I have no interest in politics or flames, but can somebody explain to a complete packaging newbie why that's a reasonable or bad idea?
[23:05] <chrismurf> I'm just trying to get a first package accepted, and growing confused
[23:07] <Laney> why did you ask on debian-mentors if you don't want it in Debian?
[23:07] <chrismurf> because debian-mentors is advertised as a place to ask questions about packaging
[23:07] <chrismurf> this (to my knowledge) is not
[23:07] <Laney> it is
[23:07] <chrismurf> I was attempting to stay on-topic
[23:07] <chrismurf> rather than bombard with questions about dh_install
[23:08] <RAOF> To be fair to debian-mentors, we'd like you to contribute to Debian, too :)
[23:08] <chrismurf> I'd love to
[23:08] <Laney> and to answer your question, we automatically get all new packages in sid at the beginning of every release cycle
[23:08] <chrismurf> I'd love to contribute to both
[23:08] <Laney> so getting it into Debian helps more people
[23:08] <chrismurf> but for now, I'm having a hard enough time contributing to one ;-)
[23:08] <Laney> and you're likely to get more specialist help in their python team
[23:08] <chrismurf> (nothing against MOTU/Ubuntu, just learning packaging)
[23:08] <Laney> contributing to Debian is contributing to Ubuntu
[23:09] <directhex> contributing to debian is contributing to freedom and world peace!
[23:09] <chrismurf> haha
[23:09] <Laney> also that <3
[23:09] <RAOF> You might find #ubuntu-motu a bit more welcoming than debian-mentors; feel free to ask packaging questions here.
[23:09] <chrismurf> okay - mok0 suggested I split out some data from http://revu.ubuntuwire.com/p/pyproj into a new package
[23:10] <pochu> chrismurf: you can ask Python packaging questions in #debian-python on OFTC
[23:10] <Laney> chrismurf: tbh, if you want it in Debian then you'd be best getting reviews for them
[23:10] <directhex> chrismurf, one source package can produce many, even hundreds, of binary packages
[23:10] <chrismurf> It's about 150kB of data once compressed, which doesn't seem like a big deal, but regardless I can't figure out how to do it while using python-support
[23:10] <chrismurf> yeah - the guy in debian-mentors is suggesting I go there
[23:10] <pochu> but I don't think asking on debian-mentors is okay if you're not targetting Debian
[23:10] <Laney> from*
[23:10] <chrismurf> so maybe targetting debian-python is the way to go?
[23:11] <chrismurf> they've been friendly so far :-)
[23:11] <pochu> that would be like asking MOTUs to review something on REVU that is for a private repository or some downstream
[23:11] <pochu> chrismurf: that's good, yes
[23:11] <pochu> chrismurf: I maintain several packages there that are in Ubuntu too
[23:11] <pochu> several people here do
[23:11]  * Laney cuddles Debian
[23:11] <directhex> i do!
[23:11] <pochu> directhex: liar!
[23:12] <chrismurf> so - there's not really any reason to contribute a python module direct to ubuntu then?  Isn't it always better to just go to debian and let it get sucked down?
[23:12] <pochu> directhex: (liar as in you don't in DPMT ;))
[23:12] <chrismurf> I realize that sounds flameish- I'm just confused
[23:12] <directhex> pochu, it's troo! i'm not officially a DD or DM or core-dev or MOTU, i'm merely a shadowy puppeteer
[23:13] <pochu> directhex: but you don't maintain Python modules... do you? :)
[23:13] <directhex> pochu, and i don't touch python nonsense. well, ironpython...
[23:13] <pochu> heh
[23:13] <directhex> ooh, i should package ironclad
[23:13] <RAOF> chrismurf: You can do both; maintaining a package in Ubuntu and Debian simultaneously works fine, and sometimes you'll need Ubuntu-specific patches.
[23:13] <directhex> which in theory allows ironpython to use cpython libraries
[23:13] <pochu> chrismurf: it's your choice, but maintaining it in Debian is a reasonable option
[23:14]  * pochu heads to bed, 'night everyone
[23:16]  * chrismurf is so confused
[23:17] <chrismurf> gnight pochu
[23:19] <RAOF> chrismurf: You can choose either, or both.  Maintianing it only in Debian is fine, and will benefit Ubuntu.  Maintaning it in Ubuntu is also OK, but it would be better to push to Debian as well.  Maintaining it primarily for Ubuntu, but pushing it up to Debian, is what I do for much of my stuff.
[23:20] <chrismurf> okay - that makes sense.  What's the timelag?  Should I pursue both in order to try and make jaunty?
[23:20] <chrismurf> or will that just make for headaches later?
[23:20] <RAOF> Jaunty's feature-freeze in in a couple of days; it makes sense to push for that first.
[23:20] <directhex> jaunty you'll need to hurry hurry
[23:21] <RAOF> Once it's in Jaunty, you can push to Debian.
[23:22] <RAOF> Then for jaunty+1 you can just sync from the Debian package, and maintain it primarily there.  You get free Ubuntu updates until Debian Import Freeze, after which you file manual sync bugs.
[23:38] <mrooney> Where can I examine the Jaunty upload queue?
[23:38] <StevenK> In Launchpad
[23:38] <StevenK> http://launchpad.net/ubuntu/jaunty/+queue
[23:58] <mrooney> StevenK: thanks!
[23:59] <mrooney> there is so much to learn, apparently my package has been automatically split up into an i86 translations tar.gz as well?