[05:07] <dholbach> good morning
[05:08] <nhandler> Hey dholbach
[05:08] <dholbach> hey nhandler
[05:11] <hyperair> it's afternoon here
[05:12] <hyperair> anyway hi
[05:12] <hyperair> anyone got time for a revu?
[05:12] <hyperair> (or a few)
[05:12]  * nhandler can't REVU until he gets a working Jaunty pbuilder
[05:13] <ScottK> nhandler: I made a new one yesterday on Intrepid, so I think your problem is system specific.
[05:14] <nhandler> ScottK: It might be. I just have no idea what might be causing it. And I would prefer not to do a fresh install unless absolutely needed
[05:15] <nhandler> Well, I'm heading off to bed. I need to get up early tomorrow
[05:51] <hyperair> nhandler: i've got a jaunty pbuilder script if you like
[08:21] <didrocks> morning
[08:39] <Koon> didrocks: I'll be available to help in the French "Getting Started" session tonight, at least the first hour
[08:41] <didrocks> Koon: great! thanks :)
[08:47] <directhex> i won't be home until after the whole getting started session is well underway
[08:48] <directhex> so if someone could tell people to have a jaunty chroot which can run x apps, for the mono session, that'd be grand
[09:06] <hyperair> chroot which can run X apps? how would you pull something like that off?
[09:07] <directhex> hyperair, there are guides out & about. depends how you run your chroot, really
[09:08] <directhex> e.g. a pbuilder login
[09:08] <directhex> then there are options like Xnest
[09:08] <hyperair> hmm
[09:08] <directhex> lots of guides on t'internets
[09:08] <directhex> pick one & poke it until xlogo works
[09:08] <hyperair> having a pbuilder chroot run X apps is awesome!
[09:09] <hyperair> then i don't have to start a jaunty live session to test out packages
[09:15] <hyperair> right, it never occurred to me to use Xvnc
[09:30] <ScriptRipper> hi!
[09:30] <ScriptRipper> i got ubuntu 9.04 on my beagleboard (ARM arch) running.
[09:31] <ScriptRipper> i connected a USB ethernet adapter to it, lsusb lists it also
[09:31] <ScriptRipper> how do i setup networking with that now?
[09:32] <ScriptRipper> network adapter as listed with "$ lsusb":
[09:32] <ScriptRipper> Bus 001 Device 007: ID 9710:7830 MosChip Semiconductor MCS7830 Ethernet
[09:32] <ScriptRipper> please help!
[09:34] <al-maisan> Hello there! I am trying to create a package for Apache's ActiveMQ message broker which requires a JDK to build.
[09:34] <al-maisan> There's number of JDKs .. which one should I specify in the 'Depends:' section?
[09:34] <hyperair> ScriptRipper: wrong channel.
[09:35] <ScriptRipper> hyperair: where should i go?
[09:35] <hyperair> #ubuntu+1
[09:35] <hyperair> also, post your entire question in one line, not multiple
[09:38] <Koon> al-maisan: you should build-depend on default-jdk
[09:38] <al-maisan> Koon: ah, OK, thanks for the advice!
[09:38] <Koon> al-maisan: my pleasure :)
[09:39] <Koon> al-maisan: in the same vein, you should (runtime) Depend on default-jre[-headless]
[09:39] <StevenK> al-maisan: If it requires a JDK to *build*, it should be in Build-Depends
[09:39] <al-maisan> Ah, OK, I see.
[09:39] <al-maisan> Thanks!
[09:40] <pochu> Koon: congrats for your MOTU-ship :)
[09:40] <Koon> pochu: thx ! I'm just back from my paternity leave, so I haven't had much time to try my new powers :)
[09:41] <pochu> :)
[09:43] <hyperair> =O
[09:43] <hyperair> what does it take to become a MOTU?
[09:44] <hyperair> Koon: to celebrate your MOTU-ship would you like to revu some packages? =p
[09:45] <Koon> hyperair: i'm trying to clear out my bugmail right now, so not immediately, but tell me which and I'll see what I have the time to do :)
[09:46] <hyperair> http://revu.ubuntuwire.com/details.py?package=bansheelyricsplugin, http://revu.ubuntuwire.com/details.py?package=vazaar, http://revu.ubuntuwire.com/details.py?package=sigx
[09:46] <hyperair> Koon: ^ thanks =p
[09:50]  * directhex summons a java team person
[09:51] <Koon> directhex: I may correspond to that description.
[09:53] <directhex> what's "antlr" and why does it build-depend on nant?
[09:55] <al-maisan> antlr is a parser generator
[09:56] <al-maisan> "ANTLR: ANother Tool for Language Recognition"
[09:56] <Koon> directhex: I guess it uses ant to build in its rules file ?
[09:56] <directhex> nant.
[09:56] <Koon> ah, not a typo then ;)
[09:57]  * Koon fetches the source package
[09:57] <directhex> it's one i seem to have missed from the whole mono 2.0 transition thing
[09:58] <directhex> hm, it's full of c#, it really IS a mix
[09:58] <directhex> how bizarre
[10:02] <Koon> ew.
[10:03] <Koon> it's apparently used to build csharp libs.
[10:04] <directhex> it needs transitioning
[10:04] <directhex> i have no idea how i missed its existence
[10:39] <proppy> oy
[10:50] <stefanlsd> dholbach: Is it possible that the guys doing the dev week sessions upload files they use somewhere. im going thru some stuff and there's alot of pastebin stuff...
[11:21] <dholbach> warp10: let me know when and where the interview will be posted :)
[11:23] <warp10> dholbach: of course! hopefully even today, both in english and in italian :)
[11:23] <dholbach> warp10: fantastico! :)
[11:23] <warp10> dholbach: and thank you so much!
[11:23]  * warp10 hugs dholbach
[11:23]  * dholbach hugs warp10 back
[11:23] <dholbach> no worries :)
[12:38] <foolano> if i file a bug to request sponsorship for a new upstream version, when i attach a diff.gz, should i change its status to confirmed?
[12:39] <james_w> foolano: it doesn't really matter, but yeah, go ahead and do that
[12:39] <james_w> foolano: then important thing is that the sponsors are subscribed.
[12:41] <foolano> james_w: after attaching the diff.gz, i subscribed the sponsors team. I was reading that I had to use the status to indicate if it's a sync, new upstream version...
[12:41] <james_w> where did you read that?
[12:43] <foolano> james_w: https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue Notes for contributors
[12:46] <james_w> ok
[12:46] <james_w> I for one never really pay attention to the status
[12:47] <foolano> ok :)
[12:48] <Laney> I wouldn't be surprised if some people have some fairly specific search listings set up that do check the status though
[12:48] <savvas> do motus prefer diff.gz or debdiff ?
[12:48] <Laney> Also, I didn't know about using incomplete for exceptions, interesting
[12:48] <Laney> savvas: Depends what for
[12:49] <savvas> for a patch, not a new upstream release
[12:49] <savvas> just asking to know which one makes life easier :P
[12:49] <james_w> savvas: debdiff please
[12:49] <Laney> debdiff then
[12:49] <savvas> ok :)
[12:49] <Laney> Makes it easier to review just what you changed
[13:06] <slytherin> james_w: just FYI ... I have verified that the changes to azureus launcher done in Debian work properly. So I will probably complete the merge today.
[13:07] <james_w> slytherin: great, thanks
[13:08] <slytherin> james_w: ﻿I have one question though. Azureus has auto update enabled by default, when I launch azureus first time it starts downloading latest version. This in my opinion not only security issue but also wastage of bandwidth.
[13:08] <james_w> yeah, I think it's not a good idea to have that
[13:08] <james_w> I though it was disabled
[13:08] <james_w> or maybe there was just an open bug about it
[13:09] <Laney> Don't we generally disable automatic updates?
[13:12] <broonie> Certainly anything that should be provided by the package manager ought to have it disabled.
[13:17] <slytherin> james_w: IIRC, there is a open bug for it in Debian.
[13:18] <slytherin> james_w: so I think I will have to patch the source to disable it.
[13:24] <slytherin> savvas: it depends on the type of sponsorship. if it is upstream version change then .diff.gz, if it is ubuntu revision change then debdiff
[13:25] <savvas> ok
[13:43] <mok0> azeem: I've committed a new version of gamgi to the svn repo
[13:43] <mok0> azeem: the license problems have been solved now I think
[14:06] <james_w> "printf '%%s/^hardcode_libdir_flag_spec=.*$/hardcode_libdir_flag_spec=" -D__LIBTOOL_AINT_NO_FOOL__ "/\nw\nq\n' | ed libtool"
[14:11] <ia> hello, maybe it's not right place for this question, but at #ubuntu-devel i can't find out answers. i use alpha-3 with latest updates. http://www.markshuttleworth.com/wp-content/uploads/2008/12/jaunty904_notifications_example1_web_092.swf - this notification system looks very useful, but how can view it in action? i mean, which apps and what kind of events supports such notifications? how this system names? and technical question - it's just some impove of n
[14:11] <ia> otification-daemon, or something else? and where i can find out, which api's in which languages allow to initiate such notifications? i will be very appreciate for any useful information :-)
[14:21] <slytherin> ia: I don't think that notification system is yet implemented.
[14:39] <azeem> mok0: awesome!
[14:39] <_ruben> is it just me or is it just not that clear which dependencies are problematic when using pbuilder :p
[14:39] <_ruben> (trying to backport bind 9.5 to hardy)
[14:39] <mok0> azeem: perhaps we should try another upload?
[14:39] <azeem> yeah, looking into it currently
[14:40] <mok0> azeem: cool
[14:40] <_ruben> ah .. got it .. i think
[14:40] <_ruben> The following packages have unmet dependencies: pbuilder-satisfydepends-dummy: Depends: libcap2-dev which is a virtual package.
[14:40] <slytherin> _ruben: what is exact problem? And why are you blaming pbuilder for that?
[14:40] <_ruben> slytherin: its an interoperability problem with pbuilder and my eyes really ;)
[14:40] <_ruben> pbuilder outputs a lot, kinda hiding the actual problem
[14:40] <azeem> mok0: was it gamgi-all or gamgi-src that we need?
[14:41] <mok0> azeem: errr, the watch file got the right one for me
[14:41] <azeem> k
[14:42] <slytherin> _ruben: the bind in jaunty needs libcap2-dev >= 2.11 as build depends, but intrepid has only 2.10-1. That mighte be the problem.
[14:43] <_ruben> slytherin: hardy doesnt have libcap2-dev .. that's the prob :)
[14:43] <slytherin> _ruben: oh, I thought you were backporting to intrepid
[14:45] <_ruben> ah
[14:45] <hyperair> mok0: got time for revu? =p
[14:46] <mok0> hyperair: errm, not now
[14:46] <hyperair> alright
[14:46] <AdamDH> is there any easy way to find out what dependancies a package requires?
[14:46] <AdamDH> hey
[14:47] <mok0> AdamDH: what package, one you've the source package for?
[14:47] <slytherin> AdamDH: apt-cache show packagename, check the Depends: field
[14:47] <hyperair> AdamDH: apt-cache depends packagename
[14:47] <AdamDH> a package from source one I am packaging at present
[14:48] <hyperair> for build-deps, apt-cache showsrc
[14:48] <hyperair> oh
[14:48] <slytherin> AdamDH: look into debian/control
[14:48] <mok0> dpkg-checkbuilddeps
[14:48] <hyperair> as in one that hasn't been packaged you mean?
[14:48] <AdamDH> yes as in one that has not been packaged before
[14:49] <mok0> AdamDH: is is a depends missing in debian/control?
[14:49] <hyperair> mok0: he's packaging one from source. he's making the debian/control
[14:49] <AdamDH> i am packaging from source so I am making the debian/control file
[14:49] <hyperair> AdamDH: ask the upstream author, or alternatively, look at the build system it's using. if it's autotools, look in configure.ac or configure.in
[14:49] <slytherin> ok, then probably look into any README file or configure.ac, configure.in
[14:50] <hyperair> AdamDH: look for the stuff that says PKG_CHECK_MODULE(
[14:50] <hyperair> and poke around some more if it's not complete
[14:50] <AdamDH> thanks for the help I will take a look
[14:50] <mok0> AdamDH: ... or if you can find out what file it's looking for, find the file at http://packages.ubuntu.com/ where you can search the content of packages
[14:52] <AdamDH> thanks mok0 never considered doing that, thats a faster way of finding the dependancy
[15:02] <azeem> mok0: uploaded
[15:38] <bddebian> Heya gang
[15:43] <ripps> Since launchpad is in the process of generating everybodies archives keys as we speak, how can one go about making a *-keyring package?
[15:43] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek to start in #ubuntu-classroom in 17 minutes
[15:44] <james_w> ripps: there's not a great deal of point
[15:45] <hyperair> ripps: launchpad will have signed ppas then?
[15:45] <ripps> james_w: I don't care, I'm bored and need a project to do.
[15:46] <ripps> hyperair: I couple archives already have them released. (Ex. https://edge.launchpad.net/~fta/+archive/ppa )
[15:49] <hyperair> i see. that's cool
[15:49] <hyperair> but does that mean that the private keys are held on the lp server?
[16:04] <lfaraone> Hi, a sync request I filed two weeks ago that has been ack'd by MOTU has yet to be acted upon, how much longer should it take? (bug 313773)
[16:05] <mok0> lfaraone: there are no specifications on the duration of sync requests
[16:06] <lfaraone> mok0: Ok, I'm just trying to make sure that I don't miss the freeze on this one.
[16:06] <lfaraone> (yes, I know that's months away :)
[16:07] <james_w> it may be delayed as it is a new package, I'm not sure
[16:07] <mok0> lfaraone: The archive admins will get to it in time
[16:09] <mok0> lfaraone: it's not so long ago it was ACKed
[16:09] <lfaraone> mok0: it was acked the same day I filed it, 15 days ago.
[16:11] <lfaraone> james_w: understood.
[16:11] <mok0> lfaraone: it's pretty high up the wishlist, so shouldn't take too long now
[16:12] <maxb> hyperair: Yes, it does.
[16:12] <lfaraone> mok0: kk.
[16:13] <hyperair> maxb: so they finally decided to go ahead with it despite the fact that the keys are on the server? i thought they didn't want to store private keys on the server
[16:14] <maxb> They're not storing _people's_ private keys - they're storing locally generated PPA-only private keys
[16:41] <ScottK> Right, it's the PPA archive that's signed by LP.
[17:37] <Ng> so who's going to kban hormesis? :)
[17:37] <laga> why?
[17:37] <jpds> Ng: What laga said.
[17:38] <Ng> [17:36] DCC SEND from hormesis [0.0.0.0 port 0]: startkeylogger [0B bytes] requested in channel #ubuntu-motu
[17:38] <ScottK> !ops
[17:38] <jpds> Too late.
[17:38] <ScottK> OK
[17:38] <hggdh> gone
[17:39] <Ng> (startkeylogger being a string which causes some terminally braindead windows firewalls to cut network connections to protect against botnets ;)
[17:39] <Ng> or maybe half of you *are* spambots :)
[17:49] <SherokiX> hi
[17:49] <lfaraone> Ng: oh, yeah, I'm currently a bot DDoSing http://whitehouse.gov :)
[17:51]  * hyperair hates xulrunner
[17:52] <mneptok> there is no data, only xul.
[17:55] <hyperair> whatever
[17:55] <hyperair> it's hell trying to get this damn package to LINK with xul
[17:55] <hyperair> something about libxul.so having unresolved symbols
[17:55] <hyperair> and cannot find libmozjs.so
[17:56] <hyperair> but for the love of god it's right there
[17:56] <hyperair> why can't it find
[17:56] <hyperair> @_@
[17:56] <hyperair> short of hardcoding the path into -R i don't know what to do
[18:08] <pochu> RainCT: feel free to join #ubuntu-es-dev, we have quite a few new interested contributors :)
[18:08] <pochu> dholbach: the Spanish session was great :)
[18:08]  * pochu hugs nxvl and dholbach 
[18:08] <dholbach> pochu: ROCK ON guys!
[18:08] <dholbach> :-)
[18:08] <dholbach> thanks a bunch
[18:10] <tigreton> hi
[18:11] <pochu> hello tigreton
[18:11] <hyperair> hey how do i path -rpath-link <somedir> to ld from autotools?
[18:11] <hyperair> bla_LDFLAGS doesn't seem to work T_T
[18:25] <quadrispro> RainCT: followed DktrKranz suggestions, now uck seems ready -> http://revu.ubuntuwire.com/details.py?package=uck
[18:34] <Chris`> http://revu.ubuntuwire.com/details.py?package=partitionmanager Can someone free please review my package? :)
[18:59] <ivoks> zul: i don't understand pitti's comment :)
[18:59] <ivoks> wrong channel :)
[19:03] <dholbach> didrocks, pochu: still have the session logs?
[19:03] <dholbach> can you post them to https://wiki.ubuntu.com/UbuntuDeveloperWeek ?
[19:04] <dholbach> bddebian: #ubuntu-classroom needs you :)
[19:05] <dholbach> if bddebian can't attend can somebody please assist nxvl in #ubuntu-classroom with "Working Well With Debian"? please?
[19:07] <stefanlsd> im around and can try help, not sure how i can help tho
[19:07] <ia> does exist some automate tools, which helps to search "Copyright" strings in source code tree of project for "copyright" file? if yes, how it names, and which of them ubuntu maintainers use?
[19:08] <pochu> ia: there's "licensecheck" in devscripts
[19:08] <pochu> and there's also "grep -R -i copyright *" :-)
[19:20] <didrocks> I try to use start-stop-daemon in an init script, with -m option (to create the pidfile), but it does not write the right pid (cf http://paste.ubuntu.com/107052/). So, my init script fails
[19:42] <fabrice_sp> Hi. I'd like to request the sync to upgrade of a lib from debian (bug #318658), but it breaks openmovieeditor. Should I request first the sync, and open another bug for openmovieeditor? Or my sync will be denied?
[19:51] <fabrice_sp> hmm, building openmovieeditor with the old lib also fails, so it's not because of the sync. I'll request the sync, and open the bug report for the FTBFS
[19:56] <james_w> fabrice_sp: do you plan to work on the openmovieeditor FTBFS? It's also holding up the NBSing of the old gavl soname?
[20:27] <Chris`> http://revu.ubuntuwire.com/details.py?package=partitionmanager Can someone free please review my package? :)
[20:29] <jsmidt> If I patched a bug that affects a package both in intrepid and jaunty, for which distro do I make the debdiff? Both intrepid and Jaunty?
[20:29] <james_w> jaunty
[20:30] <laga> jsmidt: for intrepid, it'll have to be an SRU. in general, you get your fix into jaunty first and then SRU it
[20:30] <jsmidt> james_w, laga thanks.
[20:43] <fabrice_sp> james_w, yes: I'll fix the wrong header
[20:43] <fabrice_sp> in openmovieeditor to take into account hte new lib
[20:43] <fabrice_sp> s/hte/the/
[20:43] <Chris`> Just outta curiosity, how many days does it normally take to get a full revu? :)
[20:54] <RainCT> Chris`: Interesting question. I can't really say (it depends on the package, how insistent you are and a lot of stuff :P).  If I'm bored some day I may write a script to calculate some average values.. :P
[20:55] <jpds> RainCT: What do you think of my splitting of the common.py script into little bits in Bazaar?
[20:55] <Chris`> How persistent should one be? :)
[20:58] <ia> if use pbuilder for building package, then all packages, which were installed as deps for building, will be removed after building. but if i login in tgz archive via "pbuilder --login" and install some packages, will they be removed after logout either?
[21:01] <Laney> ia: yes
[21:01] <Laney> (unless you use --save-after-login if you want it to save)
[21:09] <RainCT> jpds: dunno.. would we win anything with that?
[21:10] <RainCT> jpds: btw, the recursive dir creating function in common.py can probably be replaced by a os.makedirs inside a try-except
[21:11] <jpds> RainCT: No need to load a massive file for small scripts? Just the specific thing you want?
[21:11] <jpds> RainCT: Got point, I'll try that.
[21:12] <RainCT> jpds: Right now I'm not even sure what it contains, so feel free to do what yo think is the best. At the moment you're the u-d-t master ;)
[21:12] <jpds> \o/ POOWER!
[21:13] <RainCT> lol
[21:15]  * Chris` pokes RainCT 
[21:15]  * RainCT is poked by Chris` 
[21:16] <Chris`> Fancy doing a review? :D
[21:16] <RainCT> doing homework :(
[21:16] <RainCT> but I've almost finished so drop an URL and I may look at it
[21:16] <Chris`> I'll only give you the one if you're busy; http://revu.ubuntuwire.com/details.py?package=partitionmanager
[21:17] <Laney> Chris`: It's LP: #xxx, no need for Closes
[21:18] <Chris`> Laney: But for now is Closes acceptable? :)
[21:18] <Laney> not
[21:18] <RainCT> nope
[21:18] <Laney> no*
[21:18]  * Chris` quickly edits
[21:18] <RainCT> Closes means bugs.debian.org
[21:19] <Laney> Chris`: Do you need compat to be 7?
[21:19] <RainCT> (unless what you've written "Closes LP:", which would be correct but is ugly :P)
[21:20] <Chris`> Laney: It's ok as it is but I could change it if you wanted?
[21:20] <RainCT> lower versions are preferred if possible, as they allow for easy backporting
[21:20] <Laney> ^
[21:20]  * Chris` changes to 3 then ;o
[21:20] <RainCT> o_O
[21:20] <Chris`> Bad idea?
[21:20] <RainCT> 3 is obsolete :P
[21:21] <RainCT> not recommended anymore.. minimum is 4 iirc
[21:21] <Chris`> 5? ò_Ô
[21:21] <Chris`> Ah 4 then
[21:21] <Laney> Chris`: check man debhelper for what the levels do
[21:22] <Chris`> I have updated twice now, wait for the updates to appear I guess
[21:23] <Laney> I hope you checked everything was still OK with the new compat level :O
[21:23]  * Chris` is running pbuilder but wishes for the best anyway
[21:24] <RainCT> (REVU processes the uploads every 3 minutes)
[21:24] <Laney> Bah
[21:24]  * Laney bahs at debian-multimedia changelogs
[21:24] <jpds> Gotta love cron.
[21:24] <Chris`> Ok it;s up
[21:24] <RainCT> (except for PPA imports, which run every 5 minutes as nobody is using them right now anyway)
[21:25] <Laney> "New upstream version". Except lots more than that was changed >:(
[21:25] <Chris`> http://revu.ubuntuwire.com/details.py?package=partitionmanager
[21:26] <Chris`> How long does it take for me to get my packages to be auto uploaded? Do I need like a month's perfect track-record first of no errors or something?
[21:27] <fabrice_sp> Hi. Some MOTU to review a dvd authoring tool? It's dvdstyler (http://revu.ubuntuwire.com/details.py?package=dvdstyler) and already has an advocated from mok0
[21:27]  * RainCT tries to hug mook0 but doesn't find him online :P
 Just outta curiosity, how many days does it normally take to get a full revu? :)
[21:28] <Chris`> * mok0 (n=mok@563413c5.rev.stofanet.dk) has left #ubuntu-motu
[21:28]  * fabrice_sp too :-)
[21:28] <Chris`> :)
[21:28] <laga> Chris`: it needs two reviews.
[21:28] <RainCT> Ah, right. I don't read quit messages :P
[21:28] <Chris`> I was refering to mok0 leaving :)
[21:29] <jpds> from ubuntutools import lp.cookie -> SyntaxError: invalid syntax. WHY?!
[21:29] <RainCT> jpds: the dot
[21:30] <RainCT> jono: lp.cookie is file cookie from module lp
[21:30] <RainCT> which of course is not valid as you're saying it also that the module is ubuntutools
[21:30] <pochu> RainCT: jono doesn't care :P
[21:30] <RainCT> uops
[21:30] <RainCT> well, I'm sure jono also likes Python! :P
[21:31] <jpds> RainCT: OK... good point.
[22:05] <Arc> would anyone here want to advise on an XMPP client library to use for a new app intended for universe?
[22:05] <Arc> (an XMPP x.509 cert manager via gnome-keyring)
[22:11] <xnox> hello today at the classroom session about working with debian it has been referenced to use tags in the patches with a link to past ubuntu-devel discussion. Is there any more documentation about this? Is it ubuntu specific? Am I safe to include those in packages aimed to enter debia? I have a link mentioned in the session if you want it it's from 2007 though.
[22:12] <xnox> s/debia/debian
[22:14] <raof> xnox: You mean the tags from the list which was basically: (a) this should go upstream, (b) this should go to Debian, (c) this is Ubuntu specific?
[22:15] <raof> That tagging scheme is Ubuntu specific, but there'd be no harm in including it in packages for Debian (with the obvious exception that there should be no patches with the (c) tag in Debian ;))
[22:16] <raof> There's no tool (that I know of) that uses or reads those tags; they're just for the benefit of the human reader, and Debian can benefit just the same.
[22:17] <james_w> xnox: what was the link?
[22:18] <james_w> was it about http://wiki.ubuntu.com/Debian/Bugs/Usertagging ?
[22:18] <james_w> https://wiki.ubuntu.com/Debian/Usertagging I mean
[22:22] <xnox> james_w: https://lists.ubuntu.com/archives/ubuntu-devel/2007-November/024743.html
[22:22]  * xnox sorry was reading debian-legal and forgot everything
[22:23] <james_w> ah, yeah, that's the scheme raof was talking about
[22:23] <xnox> raof: Yeah I don't quite understand how to and where to put them
[22:23] <james_w> they go inside the patch, or the changelog, so it's not really something we can annotate externally
[22:23] <james_w> and perhaps shouldn't be
[22:24] <xnox> james_w: so how do I put inside the patch? A comment in the begging, debian/control style tag: value?
[22:24] <xnox> cause I have patch to add to the package
[22:26] <james_w> xnox: ah, if you're creating a patch that is perfect
[22:26] <james_w> xnox: if it's a dpatch then it can go in the dpatch comments
[22:26] <james_w> if it isn't then in the changelog
[22:26] <james_w> (if it's another patch system then it can go at the top of the file, but that's a preference thing really)
[22:29] <xnox> james_w: cool
[22:29] <xnox> james_w: Has been reading about Usertags, cool stuff
[22:30] <xnox> So..... If I contribute to debian using ubuntu-hat, can I reference that to become Ubuntu Member? =DDDDD
[22:31] <james_w> xnox: it will count towards your application
[22:32]  * xnox exciting
[22:32] <xnox> s/exciting/excited
[22:45] <Rudd-O> hey guys
[22:45] <Rudd-O> I'm looking for a packaging ninja to package an app for ubuntu
[22:46] <Rudd-O> anyone up to the task?
[22:46] <Rudd-O> (it should be really simple because the install is basically python distutils and that's it)
[22:47] <Rudd-O> the reason I ask is because I run fedora and I am looking for a volunteer to package this for me on ubuntu
[22:47] <pochu> https://wiki.ubuntu.com/PackagingGuide/Python
[22:47] <pochu> in case you or somebody else find it useful :)
[22:48] <Rudd-O> I will likely do that but the problem is that I don't run ubuntu myself, so I have no access to the packaging system
[22:48] <Rudd-O> this is what I want to get packages for:
[22:48] <Rudd-O> http://rudd-o.com/new-projects/portablelinux
[22:49] <pochu> you can file a needs-packaging bug
[22:49] <Rudd-O> ah that's the procedure?
[22:49] <Rudd-O> will do so right away
[22:50] <pochu> Rudd-O: basically report a bug here, and tag it "needs-packaging" https://edge.launchpad.net/ubuntu/+filebug
[22:50] <pochu> Rudd-O: of course add a link to the project, a description, and mention what license it has
[22:50] <pochu> that should do enough
[22:51] <pochu> but there are no warranties anybody will package it :) it's just a request
[22:53] <Rudd-O> I just did that
[22:54] <Rudd-O> done
[22:55] <Rudd-O> https://bugs.launchpad.net/ubuntu/+bug/319005
[22:57] <pochu> Rudd-O: you might want to talk to evand in #ubuntu-installer; I think he develops a similar tool for Ubuntu
[22:58] <Rudd-O> pochu: thanks for the HUP, I'm gonna talk to him now
[23:45] <porthose> Could I get a REVU of http://revu.ubuntuwire.com/details.py?package=quickplay please :)
[23:55] <maxb> porthose: You have a quickplay.py in your .orig.tar.gz, and then a near-identical quickplay with no extension in you .diff.gz