[01:25] <sven777> would a MOTU be so kind as to review my package? Thanks in advance! http://revu.ubuntuwire.com/details.py?package=lmalinux
[02:11] <jsmidt> How do you convert a patch, my.patch, into a format dpatch will understand?
[02:29] <ScottK> jsmidt: Use dpatch-edit-patch.  See it's man page.
[02:29] <ScottK> it's/its
[02:33] <jsmidt> ScottK, thanks
[03:19] <ScottK> txwikinger: Would you please update ichthux-meta to drop arts.  We're trying to get it removed from Jaunty: https://wiki.kubuntu.org/RemoveArts
[03:19] <ScottK> Please mark on the wiki page when you've done it.
[03:19] <txwikinger> ScottK: ok.. will do
[03:20] <ScottK> Thanks
[03:20] <txwikinger> np
[04:10] <chrismurf> I just started trying to package a new package today for Universe - is Jaunty still worth targeting? Is it possible to add new packages to Jaunty?
[04:11] <nhandler> chrismurf: New packages can still be added. But Feature Freeze is coming up soon. So if you want to get it into Jaunty, you might want to get it finished and uploaded to REVU asap
[04:13] <chrismurf> nhandler, thank you -- first package, so I will do what I can -- just wondering if I should try and target Jaunty or go +1
[04:15] <nhandler> chrismurf: You can try and target Jaunty. Worst case scenario is that you have to change one word in your changelog for Jaunty+1
[04:15] <chrismurf> Fair enough :-)
[04:16] <nhandler> chrismurf: You could also upload it to your PPA until the Jaunty+1 repositories open up
[04:16] <chrismurf> done for intrepid ;-)
[05:09] <chrismurf> Can somebody recommend an MIT licensed package to use as a reference for 'debian/copyright'?  All examples seem to be GPL/GPL.
[05:09] <chrismurf> better yet, a way to use apt-cache or otherwise to find such a package :-)
[05:53] <chrismurf> Anybody up for reviewing a first package?  It's a python library for doing geographical projections, pyproj.  http://revu.ubuntuwire.com/p/pyproj
[06:33] <dholbach> good morning
[06:34] <chrismurf> good morning
[06:35] <dholbach> hi chrismurf, hi iulian
[06:35] <iulian> Morning dholbach.
[06:35] <fabrice_sp> Hiya dholbach !
[06:35] <dholbach> hi fabrice_sp
[06:35] <fabrice_sp> Morning iulian
[06:35] <iulian> Hey fabrice_sp.
[06:36] <dholbach> how's life, guys? :)
[06:38] <fabrice_sp> dholbach, as usual (even if a bit colder than usual, with snow some days ago in Madrid :-) )
[06:38] <chrismurf> life's good - just got my first package into REVU, getting towards bedtime, and had a pleasant weekend :-)
[06:38] <dholbach> chrismurf: nice
[06:39] <dholbach> fabrice_sp: it's snowing here too right now
[06:39] <fabrice_sp> dholbach, but it's more normal, in your case, isn't it?
[06:39] <fabrice_sp> :-)
[06:39] <dholbach> I guess so :)
[06:40] <fabrice_sp> How are you doing?
[06:44] <dholbach> good good, thanks :)
[06:45] <chrismurf> If any MOTU's have an interest in reviewing said package, it'd be much appreciated : http://revu.ubuntuwire.com/p/pyproj (it's a python library for doing geographical / map projections)
[07:04] <fabrice_sp> chrismurf, please don't ask each hour for a review
[07:04] <chrismurf> fabrice_sp, I'm off to bed soon, figured I'd try one more time before crashing
[07:04] <chrismurf> apologies if I'm over exuberant, I promise not to saturate motu with "pay attention to ME" :-)
[07:05] <chrismurf> thanks for the friendly reminder
[07:05] <chrismurf> take care all, thanks for the guidance today
[07:05] <fabrice_sp> chrismurf, the more you request attention, the less you will have :-)
[07:06] <fabrice_sp> I'll try to have a look at your package this evening
[07:06] <chrismurf> OK - not what the tutorial left me thinking - I'll bear that in mind
[07:06] <fabrice_sp> (even if I'm not a MOTU)
[07:06] <chrismurf> the tutorial suggested it was beneficial to ask in MOTU
[07:07] <chrismurf> is it better to just leave it sitting in REVU?
[07:07] <chrismurf> let people get to it when they do?
[07:07] <fabrice_sp> chrismurf, yes, but no more than 2 times a day, I think
[07:07] <chrismurf> okay, well I've used my two ;-)
[07:07] <fabrice_sp> lol
[07:07] <chrismurf> thanks - take care
[07:07] <fabrice_sp> bye
[08:23] <didrocks> good morning
[08:25] <quadrispro> hi dholbach
[08:46] <slangasek> RainCT: hrm, why are you writing 'acked' in your own sync requests? :-)
[08:56] <iulian> slangasek: For karma? ;)
[08:57] <slangasek> heh
[09:30] <dholbach> Laney: does the new openarena need the new -data?
[09:47] <quadrispro> dholbach: have you read my messages? :)
[09:47] <dholbach> quadrispro: yes and I replied :)
[09:49] <quadrispro> dholbach: doh, my connection was lost :(
[09:49] <dholbach> just replied again
[09:50] <quadrispro> dholbach: thank you very much ;)
[09:50] <dholbach> anytime :)
[10:27] <stefanlsd> Does anyone know when debuild stopped ignoring .bzr directories?
[10:28] <soren> did you pass -i<something> to it?
[10:32] <stefanlsd> soren: i am doing -i.bzr now, but it always used to work without it. so was just wondering when it changed
[10:32] <soren> stefanlsd: How exactly were you invoking debuild before?
[10:33] <soren> keyword being: "exactly"
[10:33] <stefanlsd> soren: debuild -S -sa
[10:33] <soren> In that case, I'm clueless.
[10:33] <soren> :)
[10:34] <stefanlsd> soren: hehe. yeah. wierd. cause i've always made bzr trees of packages im working with, it always used to ignore the .bzr stuff. now it fails. shrug
[11:05] <Laney> dholbach: I don't think it needs it, but there is a sync coming up for that anyway
[11:05] <Laney> actually I can't request it until tonight, so it'd be good if you could
[11:05] <Laney> (it works fine)
[11:25] <lamothe> Hi all, if there's a package that I have in Debian but it's way old because Debian has been in freeze for a while, is it too late to ask for universe to be updated with a more recent release?
[11:27] <jpds> lamothe: Not at all, you have until the 29th.
[11:27] <mok0> lamothe: what is it
[11:27] <lamothe> mok0: jpds: me-tv.
[11:27]  * mok0 looks
[11:28] <lamothe> I've been kinda keeping experimental up to date ... but I'm not a DD ... and my uploader is AWOL.
[11:28] <rocco> wow.......this room seems bigger than I remember
[11:28] <mok0> lamothe: it's in experimental?
[11:29] <lamothe> mok0: Debian experimental.
[11:29] <mok0> rocco: this is not a room, it's achannel ;-)
[11:29] <lamothe> mok0: Did I say the wrong thing?
[11:29] <mok0> lamothe: no
[11:29] <cbx33> ahh that's better
[11:30] <cbx33> maybe it's not a room in the physical sense
[11:30] <mok0> lamothe: why do you think that?
[11:31] <lamothe> mok0: Oh, no reason, I think that you couldn't find it in experimental.  I misinterpreted your question.
[11:31] <lamothe> *though
[11:32] <mok0> lamothe: he, I found it. OK, you need to file a sync-request bug on LP, see here:
[11:32] <lamothe> You wouldn't guess but English is my first language. ;)
[11:32] <mok0> https://wiki.ubuntu.com/SyncRequestProcess
[11:32] <lamothe> mok0: Ta!
[11:32] <mok0> lamothe: Ah, well that explains it :-)
[11:33] <mok0> lamothe: plz check to see that it builds on Jaunty also
[11:33] <mok0> lamothe: because we are well past DIF
[11:34] <lamothe> mok0: Sure, without a doubt I will do that.  I think that it's always a good idea to build it on the target system.
[11:34] <mok0> lamothe: great! Thanks!
[11:34] <lamothe> But should I then use Utnubu ... is it still around.
[11:34]  * lamothe looks
[11:35] <mok0> lamothe: eeerr?
[11:35] <lamothe> http://wiki.debian.org/Utnubu
[11:35] <mok0> lamothe: your app is already in Debian
[11:36] <lamothe> mok0: I thought that Utnubu synced changes back into Debian.
[11:36] <james_w> ScottK: could you explain what you mean by "tame ezsetup"?
[11:36] <mok0> lamothe: but are there changes? I thought you just want to bring the version from Debian experimental to jaunty
[11:37] <lamothe> mok0: Oh .. yeah, I didn't think of that
[11:37] <lamothe> I just thought that I could build one for Jaunty.
[11:37] <lamothe> mok0: Either way, I'm easy.
[11:38] <mok0> lamothe: I already checked to see that there are no Ubuntu-specific changes in me-tv, so what we need to do is a straight sync. Archive admins have scripts for that
[11:38] <ScottK> james_w: Sure.  ezsetup will try and download updates from the internet if they are missing.  In my case I didn't have python-setuptools installed on my system where I was building it, so it tried to install it from cheeseshop.
[11:38] <lamothe> I'm mostly on Ubuntu nowadays and sometimes I lose my Debian uploader.
[11:39] <ScottK> james_w: Generally we patch packages to not do that.
[11:39] <james_w> ScottK: so what not add python-setuptools as a Build-Depends?
[11:39] <ScottK> No, just disable the ezsetup part.
[11:39] <mok0> lamothe: theres a cli-tool called requestsync if your'e into that sort of thing
[11:40] <ScottK> james_w: You'll see I just commented out two lines in setup.py.
[11:40] <mok0> lamothe: if you invoke that with the --lp switch it talks directly to LP
[11:40] <james_w> ScottK: yeah, I can see it, but ezsetup is about more than just downloading dependencies
[11:40] <lamothe> mok0: Wow that's pretty neat.
[11:40] <mok0> lamothe: yep :-)
[11:41] <ScottK> james_w: If it's trying to download updated packages from outside the repositories, then it's wrong.
[11:42] <james_w> ScottK: I agree.
[11:42] <mok0> lamothe: I think the default is to sync from "unstable", you have to thrown another switch to say "experimental"
[11:42] <james_w> I'm not suggesting that we let it
[11:42]  * lamothe is foofling
[11:42] <ScottK> That's what I was trying to prevent, if there's a better way, I'm quite OK with it.
[11:42] <jpds> lamothe: Add: -d experimental
[11:42] <mok0> There you go
[11:43] <mok0> jpds, the online manpage :-P
[11:43] <lamothe> jpds: Thanks ... I'm just trying to find the actual script ... not in repos?
[11:43] <jpds> lamothe: It's in the ubuntu-dev-tools package
[11:43] <freeflying> anyone try the latest alternate cd with hd-image?
[11:43] <jpds> mok0: Morning to you too :-p
[11:43] <mok0> jpds: heh
[11:44] <lamothe> jpds: Thanks again
[11:44] <mok0> I am looking at a blue sky for the first time in weeks
[11:44] <mok0> Makes me all cheery
[11:45] <lamothe> mok0: Thanks for your help also.
[11:46] <mok0> lamothe: I don't think Utnubu is active
[11:46] <mok0> lamothe: np
[11:47] <lamothe> Ok, off to find a uploader
[11:51] <Rafik_> hello. I'm trying to merge wordpress_2.7-1 from debian experimental with our 2.5.1-8ubuntu1... I'm learning yet (first merge tentative). I'm trying to view the diffs with Meld. but before that I have to apply the debian's diff first.. can any one please help me on that ?
[11:54] <Laney> Rafik_: Do you mean 11ubuntu1?
[11:54] <Laney> You should just look at the diff that was applied between -11 and -11ubuntu1 and then see which of those changes we still need
[11:54] <Laney> (also, thanks for letting me know that this was uploaded. /me runs off to update his blog)
[11:55] <Rafik_> Laney> apt-get source downloaded from intrepid-updates/universe wordpress 2.5.1-8ubuntu1.1
[11:56] <Rafik_> Laney> btw, thanks for your blog post, I was reading it :)
[12:01] <Tonio_> hi there :) someone to revu this please ? http://revu.ubuntuwire.com/p/skrooge
[12:08]  * mok0 takes a look
[12:10] <mok0> Tonio_: The shared object libraries are not meant for development work, right? In that case, we might prefer them to go into /usr/lib/scrooge
[12:11] <mok0> Tonio_: I can't yet see if it's possible to make that happen
[12:11] <Tonio_> mok0: I can ping upstream about the issue, indeed, and will make it
[12:11] <Tonio_> mok0: but I'm not ready to maintain such a patch, to be honnest :)
[12:12] <mok0> Tonio_: heh, well just a thought
[12:13] <Tonio_> mok0: and btw, it should go /usr/lib/kde4/
[12:13] <Tonio_> mok0: but you're right, upstream has to be notified on that point :)
[12:14] <mok0> Tonio_: yes I guess you're right
[12:41] <Tonio_> mok0: how's the packaging appart from that ? :)
[12:42] <mok0> Tonio_: It looks alright, I am putting the final words into the review now
[12:42] <Tonio_> mok0: super, thanks :)
[12:44] <mok0> Tonio_: OK, have fun ;-P
[12:47] <Tonio_> mok0: thanks fot the revu :)
[12:47] <Tonio_> mok0: one thing I don't understand is about the man page
[12:47] <mok0> Tonio_: np!
[12:47] <mok0> Tonio_: ok?
[12:47] <Tonio_> mok0: when was it decided that desktop apps should have a super-overdocumented man page ?
[12:48] <Tonio_> mok0: they already have docs btw and are not intended to be used the command line way ;)
[12:48] <mok0> Tonio_: at least it wasn't decided that the manpage is a formality
[12:49] <Tonio_> of course it's fine to describe all options when they are to be used that way, but writting a complete book about generic kde/qt options...
[12:49] <mok0> Tonio_: no that's not the point, you don't need to explain options, but what the program can do
[12:49] <Tonio_> hum oki :)
[12:49] <Tonio_> and about lintian, that drives me nuts :)
[12:50] <mok0> Can you use it for business? What are the principles it works on? Does it rely on a database? Webpage?
[12:50] <Tonio_> oki :)
[12:50] <mok0> What banking system does it communicate with
[12:50] <mok0> etc
[12:50] <Tonio_> everyone has different expectations, override/no-override, etc.... this is very likely to the guy revuing :)
[12:50] <Tonio_> mok0: is there is clear policy for this ?
[12:51] <mok0> Tonio_: those are things I want to know as a user, explained in a plain language
[12:51] <mok0> Tonio_: Well, I think it's up to the disgression of the MOTUs and I like to see well written man pages
[12:51] <Tonio_> mok0: well as a user, you would go in the app documentation :) but that's just a personal feeling ;)
[12:52] <mok0> Tonio_: I always check the man page
[12:52] <Tonio_> mok0: but I get your point, sure :) I just have the feeling that everyone has different expectations with packaging on revu :)
[12:53] <mok0> Tonio_: We all have our favourite horses to whiip
[12:53] <mok0> whip
[12:53] <Tonio_> mok0: sure :)
[12:53] <Tonio_> mok0: that's not personal, just that for example, when I package, I NEVER know if I have to override or not lintian warnings
[12:54] <Tonio_> cause some people like it, some don't, some expect it etc...
[12:54] <mok0> Tonio_: Sometimes lintian warnings are not relevant
[12:54] <mok0> Tonio_: but I just prefer to switch them on when the package is finished
[12:55] <Tonio_> mok0: so do I
[12:55] <mok0> Tonio_: and one of yours is not used by lintian anywat
[12:56] <Tonio_> mok0: I just get lost are packaging expectations.... changing every 2 weeks... I'm packaging for 4 years, and I'm still lost when it comes to revu :)
[12:57] <mok0> N:    Lintian discovered an unused override entry in its database. Please
[12:57] <mok0> N:    remove it from the overrides file if it is not needed anymore.
[12:57] <Tonio_> mok0: anyway, let's fix te points :)
[12:57] <mok0> Tonio_: It's obvious that you are experienced. You just have to roll with the punches
[12:57] <mok0> :-P
[12:58] <mok0> Tonio_: We have to find out if it's relevant to make a .symbols file for plugins
[12:59] <Tonio_> mok0: I have no opinion on that point to be honnest...
[12:59] <mok0> Tonio_: Yeah... it's only a recommendation so far, anyway
[12:59] <Tonio_> mok0: about debian/watch, the issue is the debian side.... sometimes working sometimes not
[13:00] <mok0> Tonio_: just use sf.net/
[13:00] <mok0> Tonio_: oh, and use ([\d.]*) instead of what you have
[13:01] <Tonio_> mok0: stupid man pages :) hehe
[13:01] <Tonio_> mok0: http://sf.net/skrooge/skrooge-([\d.]*)\.tar\.gz this way ?
[13:03] <mok0> Tonio_: yeah looks right
[13:03] <Tonio_> mok0: won't be relevant with the 403, since that's random :)
[13:03] <mok0> heh
[13:03] <Tonio_> mok0: just tried twice, one 403, and one working :)
[13:04] <mok0> Tonio_: ydrk, what a nuissance
[13:04] <mok0> Tonio_: I've never had the Debian PHP service work for me
[13:05] <Tonio_> mok0: yup, I'll ping debian if that continues all day long
[13:05] <stefanlsd> Anyone seen this ftbfs before - http://launchpadlibrarian.net/22389029/buildlog_ubuntu-jaunty-i386.gromacs_4.0.3-1_FAILEDTOBUILD.txt.gz
[13:05] <stefanlsd> essentially libtool: Version mismatch error.  This is libtool 2.2.6 Debian-2.2.6a-1ubuntu1, but the libtool: definition of this LT_INIT comes from an older release
[13:05] <Tonio_> mok0: http://pastebin.com/m7ef2029d not working
[13:06] <mok0> Tonio_: sh*t
[13:06] <Tonio_> mok0: http://pastebin.com/m618428fe works :)
[13:06] <Tonio_> mok0: just need to be patient, I'd say :)
[13:06] <mok0> Tonio_: Guess so :-/
[13:07]  * mok0 wishes Debian would get Lenny off the shelf so we could all get on with things
[13:07] <Tonio_> what I don't get is the 403.... that's an authorization issue, not an overloaded service or so...
[13:07] <mok0> For example, fix webservices that are borken
[13:07] <Tonio_> a 500 error would be more understandable
[13:09] <mok0> stefanlsd: hmm, strange
[13:10] <mok0> It's libtool acting up
[13:11] <mok0> stefanlsd: libtool issues some warnings in the beginning
[13:11] <mok0> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
[13:11] <mok0> libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am
[13:13] <stefanlsd> mok0: mm. we dont have a m4 directory. will make it and try add that stuff tho
[13:13] <mok0> stefanlsd: well, ok, wonder why it issues that statement then
[13:14] <mok0> stefanlsd: perhaps you should avoid libtoolize
[13:41] <stefanlsd> mok0: yeah. thanks. not doing that seems to "fix it".
[13:42] <mok0> stefanlsd: great
[13:42] <mok0> stefanlsd: There are some issues with libtool 2.2 and aclocal
[14:28] <sven777> would a MOTU be so kind as to review my package? Thanks in advance! http://revu.ubuntuwire.com/details.py?package=lmalinux
[14:28] <sven777> oh mok0 - thanks for advocating!
[14:29] <mok0> sven777: you're welcome
[14:37] <sven777> is revu supposed to send out emails when comments are posted?
[14:38] <sven777> nm - didn't realize you have to set the preference before emails happen
[14:38] <sven777> I thought the "subscribe" was enough to make it happen
[15:04] <slicer> Hi. I could use a bit of help with a build failure report. http://launchpadlibrarian.net/22413534/buildlog_ubuntu-jaunty-powerpc.mumble_1.1.7-1_FAILEDTOBUILD.txt.gz seems to indicate the problem is in the libqt4-opengl-dev package. The package has successfully built on lpia, and the other archs are still "needs to be built". The package did build successfully on i386, amd64 and lpia in my PPA. I don't have personal access to a PPC machine, so I can't try to
[15:05] <dholbach> nixternal: THANKS :)
[15:05] <dholbach> hey huats
[15:05] <huats> hey dholbach
[15:06] <dholbach> how's life in France? :)
[15:08] <bddebian> Heya gang
[15:08] <ScottK> slicer: Likely you need to wait until the package is built on ppc and then ask a MOTU to retry the build.
[15:10] <slicer> ScottK: Ah, so the packages I'm depending on might not be built yet? That explains a lot :)
[15:11] <ScottK> Yes
[15:11] <ScottK> I didn't actually look, but from your decscription that's what it sounds like.
[15:21] <slicer> ScottK: Hmm. Googling around and looking at other packages didn't reveal anything. I'll wait and see how the other builds go, and if they work fine, I'll request a rebuild. Thanks for your help :)
[15:30] <henrik-hw0> Hi. Need a second advocate for libmirage.
[15:38] <mok0> henrik-hw0: *sigh*
[15:38] <mok0> :-)
[15:38] <henrik-hw0> mok0: hi.
[15:42]  * henrik-hw0 attempts bribing with waffles & jam. 
[15:43] <mok0> henrik-hw0: I don't think there are any MOTUs in revuing mode present ATM
[15:52] <savvas> er.. how do we specify in the changelog the changes used in Ubuntu? Something like "* Kept Ubuntu changes:" and I start laying them out?
[15:52] <savvas> (talking about a merge)
[15:53] <Amaranth> savvas: Something like "Remaining Ubuntu changes:" and this a list under that
[15:54] <savvas> Remaining! And I was wondering about that, thanks Amaranth :)
[15:58] <savvas> I thought remaining meant the changes that had to be done, which didn't make much sense heh
[15:59] <nixternal> dholbach: no problemo!
[15:59]  * nixternal hugs #ubuntu-motu 
[16:01] <DktrKranz> mok0: re latest motu-meeting, did you have chance to obtain REVU db?
[16:01] <mok0> DktrKranz: yes I did
[16:02] <mok0> I have it now :-)
[16:02] <DktrKranz> cool!
[16:02] <mok0> DktrKranz: working on my mockup
[16:03] <DBO> does anyone know why OO.o is packages with a shell script (/usr/bin/ooffice) that simple calls soffice with the same arguments.  That is all the script does (well it also obfuscates other applications ability to identify OO.o)
[16:03] <mok0> DktrKranz: I have a few issues with the schema, however. Some relations are _very_ complicated to extract
[16:04] <mok0> DktrKranz: ... which also makes them quite slow
[16:05] <DktrKranz> mok0: do you know if mysql or postgres is required?
[16:05] <mok0> DktrKranz: postgresql
[16:05] <mok0> DktrKranz: fortunately
[16:06] <DktrKranz> for REVU yes, not for my hosting
[16:06] <DktrKranz> it only has mysql :(
[16:06] <mok0> DktrKranz: don't you have an account on spooky?
[16:06] <DktrKranz> no
[16:07] <mok0> You'll have to run a server on localhost
[16:08] <RainCT> like me ^^
[16:08] <DktrKranz> I can setup a VM for that
[16:08] <mok0> ... and me
[16:08] <DktrKranz> VM with sid...
[16:09] <RainCT> DktrKranz: You don't really need a VM for that (unless you want to imitate the setup on spooky so that the incoming uploads processing scripts work)
[16:09] <hyperair>                                   -czf codelite_$(UPSTREAM_VERSION)+dfsg.orig.tar.gz \
[16:09] <hyperair>                                   codelite-$(UPSTREAM_VERSION)+dfsg
[16:09] <hyperair>  <-- what could possibly make this end up as codelite_+dfsg.orig.tar.gz followed by codelite-1.0.2579+dfsg?!
[16:09]  * hyperair curses
[16:09] <hyperair> it's the same damn variable why doesn't it substitute the same damn value?!
[16:10] <RainCT> hyperair: calm down :P
[16:10] <mok0> hyperair: It's not our fault :-(
[16:10] <DktrKranz> RainCT: so, only apache and postgres is needed to run a REVU instance?
[16:10] <hyperair> yeah yeah it isn't.
[16:10] <mok0> hehe
[16:10]  * hyperair yells at the wall and hammers on it
[16:10] <RainCT> DktrKranz: for the web interfaces, yes
[16:10] <mok0> DktrKranz: yes
[16:10] <DktrKranz> mmmh
[16:11] <RainCT> DktrKranz: and you can configure apache and pg to only run when you start it (that's how I have it on my laptop)
[16:11] <DktrKranz> I see
[16:12] <DktrKranz> RainCT: are you able to process uploads with that instance?
[16:12] <RainCT> DktrKranz: No, but if necessary you can import them semi-manually :P.
[16:12] <DktrKranz> a feature I'd like to see is sending mails about preferred procedure to upgrade a package
[16:12] <DktrKranz> which is attaching .diff.gz to bug repotrs
[16:12] <RainCT> DktrKranz: fixing the scripts is on my TODO (actually, I've already started doing some work on them)
[16:14] <RainCT> DktrKranz: Uhm.. Like a "Hurray! You upload has been sponsored! Now don't forget to continue watching for it, and .. <instructions for fixed/upgrades here>"
[16:14] <RainCT> DktrKranz: or rather when someone uploads a package which is already in Ubuntu?
[16:15] <DktrKranz> both :)
[16:17] <DktrKranz> but REVU is designed for NEW packages, using it for already available packages is a waste of time/resources
[16:18] <RainCT> Hehe. Oaky. So the first one is blocking on detecting when a package is sponsored, and the second one is blocking on the new/upgrade detection code properly working ;)
[16:18] <DktrKranz> so, we should encourage contributors to use LP instead
[16:18] <RainCT> *Okay, even
[16:18] <chrismurf> Will a MOTU please peek at pyproj?
[16:18] <chrismurf> I'd certainly pay you homage
[16:18] <chrismurf> it's my very first .deb
[16:18] <chrismurf> but my excitement will ebb
[16:18] <chrismurf> if nobody responds to my barrage
[16:18] <DktrKranz> LP is not the right place itself, but that's it
[16:18] <RainCT> DktrKranz: I've heard of people (don't remember whom) that at some cases prefer to look at packages on REVU
[16:18] <mok0> DktrKranz: yeah, or ppa's
[16:18] <chrismurf> (http://revu.ubuntuwire.com/p/pyproj) :-)
[16:19]  * DktrKranz proposes to use mentors.debian.net
[16:19]  * RainCT proposes Debian to use REVU for mentors.debian.net *g*
[16:20] <DktrKranz> RainCT: TBH, I prefer REVU too. But we need an unique place to manage such things
[16:20] <DktrKranz> REVU for all
[16:20] <DktrKranz> REVU for NEW only
[16:21] <DktrKranz> core-devs from Canonical usually look at LP only, though
[16:22] <RainCT> Actually, making revu.ubuntuwire.com more Debian friendly (like showing DDs as such and giving them review permissions and the like) is something I've been thinking about a bit.. Not sure if anyone would make use of that, though
[16:23] <DktrKranz> well, REVU is free software, I think they could use it as well, even if I heard of some issues with mentors
[16:23] <DktrKranz> *mentors.d.n
[16:23] <mok0> REVU FTW
[16:24] <RainCT> DktrKranz: Anyway, so you want to contribute to REVU? :)
[16:24] <DktrKranz> REVU would fix a recent discussion on debian ML about using a new Debian revision to fix sponsor's comments
[16:25] <RainCT> heh, right
[16:25] <DktrKranz> RainCT: I'd like to
[16:25] <DktrKranz> this cycle I'm more code-oriented :)
[16:26] <DktrKranz> less packages, more commits
[16:26] <RainCT> (They also have that GSoC thing, though. But I've no idea what is happening with it)
[16:26] <RainCT> DktrKranz: that's good for your LP karma ;)
[16:26] <mok0> DktrKranz: we were chatting about the advantages of having the REVU source packages in bzr repo
[16:26] <DktrKranz> RainCT: I used to have > 35 million karma, I had karma stomachache :)
[16:27] <RainCT> lol
[16:27] <RainCT> DktrKranz: About wanting to contribute, that's great :). Just ask if you have any question (and if you don't know what to do just ask, too, and I'll give you something from my TODO :P).
[16:27]  * mok0 thinks as long as a source package has revision -0ubuntu* we should maintain them in bazaar
[16:28] <DktrKranz> RainCT: do you have anything stupid enough to be fixed by a dumb Ubuntu developer like me? :)
[16:28] <DktrKranz> mok0: mmmh... explain it better
[16:28] <mok0> DktrKranz: ok
[16:29] <mok0> DktrKranz: source package is sitting in a repo in LP. Uploader fixes stuff in own branch, pushes to repo
[16:29] <RainCT> DktrKranz: There is a syntax eror in your messsage. "dumb", "Ubuntu developer" and "you".. how can those concepts be related? ;P
[16:29] <mok0> DktrKranz: REVUer pulls changes evaluates, posts comment on REVU
[16:29] <mok0> DktrKranz: Reviewer can fix tiny bits and pieces if necessarty
[16:30] <DktrKranz> I think REVU itself is similar to VCS
[16:30] <mok0> DktrKranz: sometimes you feel cruel by asking for a tiny fix before advocation, e.g. spelling mistake or something
[16:30] <mok0> DktrKranz: It is
[16:31] <mok0> DktrKranz: we just need to have revu on top of bzr instead
[16:31] <mok0> DktrKranz: this is a proposal for the long term though
[16:31] <DktrKranz> if distributed-development stage5 takes place, it's not that long term :)
[16:31] <mok0> DktrKranz: I think there's a bunch of MOTUs who still does not want to work that way
[16:32] <DktrKranz> RainCT: no syntax error, it's core language now :)
[16:33] <mok0> DktrKranz: What's the current status of distrib-devel?
[16:33] <RainCT> DktrKranz: bug #172895 should be easy
[16:33] <DktrKranz> mok0: I don't know, james_w is the rockstar there.
[16:34] <mok0> DktrKranz: I can grep the mailing lists
[16:34] <RainCT> btw, does someone know which month the next UDS will be?
[16:34] <DktrKranz> RainCT: mind subscribing myself?
[16:34] <james_w> it is progressing
[16:34] <mok0> RainCT: Isn't it usually about a month or two after a release?
[16:34] <RainCT> DktrKranz: done
[16:34] <james_w> should have some more announcements soon I hope
[16:34] <mok0> james_w: exiting!
[16:35] <mok0> james_w: ... err exciting is what I wanted to say :-)
[16:35] <RainCT> mok0: yep, but I'd like to know something more exact to see how it fits my schedule :P
[16:35] <james_w> heh :-)
[16:36] <RainCT> but well, nvm
[16:37] <mok0> james_w: So, is the idea to have one "upstream" trunk, with a branch off that containing debian/ and other branches containing patches?
[16:37] <RainCT> uhm.. what's the URL of that ubuntu-nl uploads feed?
[16:37] <james_w> mok0: that's one possibility
[16:38] <james_w> mok0: the main effort at the moment is to get an "upstream" branch, then a "debian" off that, then an "ubuntu" off that
[16:38] <mok0> james_w: ah cool
[16:38] <james_w> once we have that then we can start to get more adventurous
[16:38] <mok0> james_w: what about branches originating in Ubuntu?
[16:39] <mok0> james_w: they only have the debian branch I guess
[16:39] <RainCT> james_w: Ah, I wanted to ask.. Why is the NoMoreSourcePackages spec called like that? Is it that source packages will continue existing, but being generated by bzr-buildpackage; or is there something more?
[16:39] <mok0> james_w: how do you achieve that in practise? You need a separate directory for each branch?
[16:40] <james_w> debian native packages won't have the upstream branch, ubuntu native packages will just be an ubuntu branch
[16:40] <james_w> RainCT: that's one proposal for what could happen. We're not directly working towards it right now.
[16:41] <james_w> RainCT: though some plans may make it that most Ubuntu developers never really touch source packages, they are just created by launchpad as needed
[16:41] <james_w> mok0: yeah, you currently need one directory per branch.
[16:41] <mok0> Yeah, source package are just a transport mechanism anyway
[16:42] <mok0> james_w: Hm, ok, I am used to working with git, where you check out branches in the same directory
[16:42] <mok0> james_w: so you need another level of directory to contain the branches for a project, I guess
[16:44] <james_w> mok0: that's the way most people do it
[16:44] <mok0> ok
[16:44] <james_w> there is a proposal currently for how to do the git-style branching
[16:45] <RainCT> that is, the loom stuff?
[16:45] <mok0> Another problem we have is that more and more upstream don't have regular releases, because they ask users to pull from their VSCs
[16:45] <mok0> james_w: that would be cool
[16:46] <mok0> So the whole concept of "watch" files etc. is in trouble
[16:47] <james_w> RainCT: nope, different to that, but looms allow you to simulate it in certain situations
[16:47] <hefe_bia> mok0: Thanks for uploading tomboy-blogposter!
[16:48] <james_w> mok0: they may still be useful as notification that upstream has released something, but there may be other ways to do it
[16:48] <mok0> hefe_bia: it still has to go through an archive admin
[16:48] <mok0> james_w: yes, perhaps some kind of tagging convention
[16:49] <hefe_bia> mok0: I know. Just got another package rejected a few days ago... ;)
[16:49] <mok0> hefe_bia: which one was that?
[16:49] <hefe_bia> mok0: gebabbel. But it is back in. It was an error in the copyright file.
[16:50] <mok0> hefe_bia: ah, yes, I think I uploaded it myself
[16:51] <hefe_bia> Just when it was already in the queue I read an interview about "how to not make archive admins unhappy". Right after that I spotted the error...
[17:00] <mok0> hefe_bia: It's called "Murphy's law"
[17:02] <DktrKranz> mok0: exactly "If a package could be REJECTed(tm), it's sure it will be"
[17:02] <mok0> DktrKranz: he, yeah
[17:03] <hefe_bia> ;)
[17:07] <RainCT> Uploads aren't announced on jaunty-updates@ once they passed NEW, or?
[17:07] <jpds> RainCT: They are, why?
[17:09] <chrismurf> hefe_bia, where is said interview? :-)
[17:10] <hefe_bia> chrismurf: https://wiki.ubuntu.com/MeetingLogs/devweek0809/Archives
[17:11] <RainCT> jpds: Oh, OK. I was looking on the ubuntu-nl feed and didn't see any package from REVU, but now that I look right I see that the last sponsored package is already to old to be on it
[17:11] <hefe_bia> Its with Steve Langasek
[17:11] <slangasek> hmm, not so much an interview as a presentation. :)
[17:13] <hefe_bia> slangasek: Yes right. I mixed things up ;) Anyways - an informative read...
[17:19] <james_w> the sponsors' queue is getting out of control again
[17:20] <mok0> james_w: you mean with > 180 entries?
[17:20] <james_w> yeah
[17:21] <mok0> james_w: you're right
[17:22] <iulian> We should have a UUS day.
[17:23] <mok0> iulian: good idea.
[17:23] <iulian> Instead of one REVU day, let's have a UUS one.
[17:23] <mok0> A lot of those are sync requests though
[17:23] <mok0> and aRts stuff
[17:23] <iulian> A lot of them are package upgrades.
[17:24] <mok0> iulian: like "oh, upstream has changed the name of a variable, please upgrade"
[17:26]  * mok0 wonders why "Unknown Importance" sorts first in the UUS list
[17:30] <mok0> james_w: why is bug 325076 in High status?
[17:30] <Laney> mok0: security problem
[17:31] <mok0> I se
[17:31] <mok0> e
[17:31] <james_w> mok0: I just bumped it off the -archive list, I'd agree with Laney though
[17:32] <mok0> james_w, Laney, don't you think we should ask for the bugs list to be changed to "Unknown Importance" sorts _last_ ??
[17:32] <Laney> mok0: Think of it as a "needs triage" list ;)
[17:32] <mok0> We can't do anything about them anyway
[17:32] <Laney> a lot of contributors can't change bug importance
[17:32] <mok0> They belong to other projects
[17:33] <Laney> ah, then you need to refine your search
[17:33] <mok0> Laney: this is just the default bug page of uus
[17:33] <mok0> https://bugs.edge.launchpad.net/~ubuntu-universe-sponsors/+bugs?start=0
[17:33] <Laney> I agree that it should only show bugs which affect Ubuntu packages
[17:35] <Laney> but that's an LP bug, and for now you can bookmark a custom search
[17:35] <james_w> mok0: do you know http://people.ubuntu.com/~dholbach/sponsoring/ ?
[17:36] <RainCT> DktrKranz: On bug #109289 you ask "What about change in src/main.c? You dropped it, is there a reason behind this choice?", but I don't see that it has been deleted
[17:36] <Laney> james_w: With your archive admin hat on, what do you think to pulling some packages from Debian NEW that aren't likely to make it in before FF but we want anyway?
[17:36] <mok0> james_w: ah nice! I didn't know that one
[17:36] <RainCT> DktrKranz: Actually, only the changelog is touched. Did you just post that by mistake or was there some reason for the comment?
[17:37] <maxb> I thought it was impossible to download packages in NEW?
[17:37] <Laney> yes
[17:37] <Laney> but you can get them through other means
[17:37] <james_w> Laney: they're still knitting the hat
[17:37]  * Laney fails to comprehend
[17:37] <james_w> Laney: but I think it would be appropriate to upload them if it makes sense
[17:37] <james_w> Laney: are these NEW leaf packages, or NEW libraries?
[17:38] <RainCT> DktrKranz: err wait, I can't read :P
[17:38] <Laney> one of each
[17:38] <Laney> also would they need to be REVUed?
[17:38] <james_w> Laney: probably ok
[17:39] <james_w> Laney: I'm not sure
[17:39] <Laney> moonlight because that's the kind of thing we should have and sublib because it blocks gnome-subtitles
[17:45] <james_w> wow, who wants to fix a three-digit bug?
[17:45] <james_w> bug 334
[17:50] <quadrispro> nixternal: thanks for your feedback!
[17:54] <RainCT> Someone already working on 334?
[17:55] <DktrKranz> RainCT: I'll look at that bug when I come back home
[18:08] <RainCT> james_w: I see why nobody has fixed #334..    $ ls    debian  gnupod-0.99.7.tgz
[18:10] <james_w> urgh
[18:11] <RainCT> Anyway, I'll have a go at it :)
[18:12] <james_w> \o/
[18:20] <RainCT> james_w: I guess we should also SRU this?
[18:22] <james_w> RainCT: probably appropriate, but I'm not sure it's worth it, given how long it has been broken :-)
[18:22] <RainCT> hehe
[18:30] <henrik-hw0> It's nuking time! rt28xx-linux-sta, rt2860-linux-sta and rt2870-linux-sta. i have it on good authority that there will be updated drivers in the jaunty kernel (staging area).
[18:30] <RainCT> Meh.. Already fixed in Intrepid. Now I can't upload my fix :(
[18:32]  * Laney fixes RainCT 
[18:33] <RainCT> :)
[18:35] <savvas> fix him on Friday, it's the 13th :p
[18:35] <superm1> henrik-hw0, that's good but too bad since all the packaging was in shape :)
[18:36] <Laney> woah, someone made the bash-completion for pbuilder-dist better
[18:36] <Laney> RainCT: !!! was it you?
[18:37] <henrik-hw0> superm1: it makes sense to have the drivers in kernel. in any case... libmirage needs some love. *hopeful*
[18:37] <jpds> zsh > *
[18:37] <Laney> I keep meaning to try it
[18:38] <RainCT> Laney: if "better" means recognizing *-jaunty and cowbuilder-*, then yes :)
[18:38] <Laney> jaunty, that's probably it
[18:40] <RainCT> Laney: bah, I fix the auto completion for *you* and you don't even give me a hug?   :P :P
[18:40] <Laney> First I fix you, now you expect a hug
[18:40]  * Laney cuddles RainCT
[18:40] <RainCT> heh
[18:47] <henrik-hw0> i like the "archive" feature, is it a new one?
[18:47] <RainCT> henrik-hw0: on REVU?
[18:48] <henrik-hw0> rainct: yes. used it to archive 3 now obsolete packages.
[18:49] <jpds> Can we upload new package versions, even though they have not been uploaded to Debian first?
[18:49] <RainCT> henrik-hw0: Nope, it has always been there, but I think it was only available for MOTUs until I reworked it like 1 month ago.
[18:50] <RainCT> jpds: just check how many upgraded packages with -0ubuntu1 revision there are :)
[18:50] <jpds> RainCT: Just check before someone hunts me down.
[18:51] <RainCT> jpds: oh, if someone complains kick him from #ubuntu-motu ;)
[19:05] <hyperair> supposing i'd like to submit a new upstream release to a packaged i submitted through revu (and is already in ubuntu) i just file a bug and then create a debdiff for it right?
[19:05] <hyperair> though admittedly it is kinda big
[19:06] <hyperair> and there are some files which are binary
[19:06] <ScottK> hyperair: Not a debdiff, the updated diff.gz.
[19:07] <hyperair> okay then
[19:07] <ScottK> Whoever uploads the package will fetch the tarball from upstream.
[19:07] <hyperair> it requires repacking
[19:07] <hyperair> there's a get-orig-source target so i guess it should be fine
[19:07] <ScottK> get-orig-source rules are good for this reason.
[19:07] <ScottK> Yes.
[19:08] <hyperair> ScottK: do i need to put the bug number in the changelog?
[19:09] <ScottK> Yes.
[19:09] <Laney> how does calling a get-orig-source from a diff work?
[19:09] <Vest84> hello, guys. I've got many similar messages: /var/revu/revu1-incoming/gnome-quod-0902052312/gnome-quod-0.2.2/src/statistics.h: GPL (v2 or later)    [Copyright: 2006-2009, Vlad Volodin <vest.84@gmail.com>]
[19:09] <Vest84> what's wrong with my code?
[19:10] <hyperair> Laney: you patch it onto an empty directory then call get-orig-source?
[19:10] <Laney> fair
[19:15] <hyperair> can someone try accessing http://qa.debian.org/watch/sf.php/codelite and see where it redirects to?
[19:15] <hyperair> sometimes it works, sometimes it doesn't
[19:15] <hyperair> bah
[19:15] <hyperair> uscan's messing up big time here
[19:16] <Vest84> http://heanet.dl.sourceforge.net/sourceforge/codelite/
[19:17] <ScottK> hyperair: The Debian SF redirector is not the most reliable thing in the world.
[19:17] <hyperair> ScottK: so i should avoid it?
[19:17] <ScottK> hyperair: No.  Use it, but don't worry if it's not working at the moment.
[19:17] <hyperair> alright
[19:18] <Vest84> hyperair: for me it works, I've sent you the link above
[19:18] <hyperair> Vest84: ah i see thanks
[19:18] <hyperair> right now debian's redirector is sending me to garr.dl.sourceforge.net
[19:18] <hyperair> which throws up a 403 error
[19:18] <hyperair> probably sf's fault
[19:20] <hyperair> ScottK: after i attach the diff.gz i subscribe ubuntu-universe-sponsors?
[19:20] <ScottK> hyperair: For Universe/Multiverse packages, yes.
[19:20] <hyperair> ScottK: okay then
[19:21] <hyperair> bug #327216 =p
[19:22] <directhex> hyperair, some sf mirrors are broken
[19:23] <directhex> garr is known-buggered
[19:34] <mok0> hyperair: did you manage your troubles?
[19:40] <RainCT> Vest84: The messages on the "legal" page on REVU don't necessarily say that there's something wrong.
[19:40] <RainCT> Vest84: What that page does is try to autodetect what license each of the files has (using "licensecheck")
[19:41] <nixternal> quadrispro: no problemo, good work, keep it up! :)
[19:42] <Vest84> RainCT: oh, I see. But I can't find the corrent template for GPL v3. yes, I use this license in COPYING file, but I don't know what and how should I write in *.[ch]?? files
[19:44] <RainCT> Vest84: http://paste.ubuntu.com/116166/plain/ (without the #'s)
[19:45] <Vest84> RainCT, should I write the new adress of the FSF, too?
[19:45] <Vest84> 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
[19:45] <RainCT> Vest84: no, the GPLv3 header doesn't include that address, but instead the URÑ
[19:45] <RainCT> * URL
[19:46] <hyperair> mok0: yeah i figured out it was something to do with uscan acting up on me
[19:46] <hyperair> mok0: by the way, could you sponsor #327216 for me please?
[19:46] <mok0> hyperair: good
[19:47] <hyperair> it's a new version of codelite
[19:47] <mok0> hyperair: I'll take a look later
[19:47] <hyperair> mok0: alright thanks
[19:47]  * hyperair is off to bed
[19:47] <hyperair> night
[19:47] <mok0> g'night
[20:04] <jpds> nixternal: You around/have time for a main upload?
[20:13] <nixternal> jpds: unfortunately no...at work
[20:30] <chrismurf> quadrispro, if you've got some time to review http://revu.ubuntuwire.com/p/pyproj, I'd much appreciate it.  Thanks for your help yesterday.
[20:47] <Vest> RainCT: thank you, I'll change my sources
[20:52] <fabrice_sp> chrismurf, I'm not able to build your package
[20:53] <fabrice_sp> dpkg-source: error: File ./pyproj_1.8.5-0ubuntu1.diff.gz has size 2075 instead of expected 2052
[20:53] <chrismurf> fabrice_sp, well that does seem like a negative.
[20:54] <fabrice_sp> chrismurf, I think you should build again the package (debuild -sa -S) and upload it again to revu
[20:54] <chrismurf> doing it right now
[20:57] <chrismurf> fabrice_sp, done
[20:59] <fabrice_sp> chrismurf, also, it seems the copyright is not given to the right persons: the copyright in src/PJ_aea.c is claimed by Gerald Evenden, but in debian/copyright, it appears Frank Warmerdam
[20:59] <chrismurf> Okay - Frank Warmerdam claims copyright over everything in the PROJ distribution
[20:59] <chrismurf> but he acknowledges that Gerald Evenden wrote a lot of the code
[20:59] <chrismurf> should I list both as copyright holders for src/*
[21:00] <chrismurf> or give explicit file copyrights for the ones claimed by Gerald E
[21:01] <fabrice_sp> I would say gives the copyright to the right person, but let's see if someone else answer
[21:02] <chrismurf> fabrice_sp, http://revu.ubuntuwire.com/revu1-incoming/pyproj-0902092157/pyproj-1.8.5/LICENSE_proj4
[21:02] <chrismurf> Actually, the right answer is probably to copy from the PROJ package itself
[21:02] <chrismurf> I will look at what the copyright file for that says
[21:03] <fabrice_sp> yes, but according to Franck: Essentially all work was done by Gerald Evenden
[21:03] <fabrice_sp> so Gerald's name should appear :-)
[21:03] <chrismurf> agreed :-)
[21:03] <fabrice_sp> check if src/* is is copyrigthed to Gerald
[21:04] <chrismurf> well, src/* is a static copy of a particular version of PROJ, which is a seperate library
[21:04] <chrismurf> and the debian/copyright for that library is an old-style free-flowing copyright
[21:05] <fabrice_sp> I still ahve the same problem with diff.gz size :-/
[21:05] <fabrice_sp> did you run again debuild -sa -S?
[21:05] <chrismurf> ??? I've deleted everything and did that, yeah
[21:05] <fabrice_sp> ?! I'll try to delete everything also
[21:06] <chrismurf> the .changes file lists 2052 for me, and that's the size of .diff.gz on my filesystem
[21:06] <chrismurf> both .changes and .dsc list the size as 2052
[21:08] <chrismurf> so - the real problem with the copyright is that Gerald wrote 99% of the src/* files, but in his own words: "The software was developed by the USGS and has no copyright nor license.  Do with it what you will.  :-)"
[21:08] <RainCT> good night
[21:08] <chrismurf> so I'm going to list them both as copyright holders, with an X-comment explaining.
[21:11] <fabrice_sp> chrismurf, can you try to open the one in revu? I'm getting garbage when downloading it
[21:12] <chrismurf> It's definitely 2075B on REVU ...
[21:12] <chrismurf> is there a "JUST DELETE IT" button on REVU?
[21:12] <chrismurf> seems like it's getting messed up in the transfer, or didn't replace it
[21:13] <fabrice_sp> let's wait for a REVU admin
[21:13] <fabrice_sp> and about copyright: some sources claims to be MIT like licensed, but other are 'public doamin' like
[21:13] <chrismurf> okay - I'm fixing the copyright bugs
[21:14] <jpds> What do you want deleted/archived?
[21:14] <chrismurf> I am going as close to the PROJ package as possible
[21:14] <chrismurf> jpds, could you kill pyproj please?  It seems to be corrupted, and isn't taking the .diff.gz correctly
[21:15] <jpds> chrismurf: Nothing by that name in the FTP queue.
[21:16] <jpds> Upload in  /srv/archive/revu1-incoming/pyproj-0902092157 appears to be fine.
[21:16] <chrismurf> what's the size on that file?
[21:17] <jpds> http://paste.ubuntu.com/116197/
[21:17] <jpds> chrismurf: You should be able to reupload.
[21:35] <ScottK> At least in US copyright laws, works created by the US federal government cannot be copyrighted and are public domain.
[21:36] <ScottK> Of course in many countries authors have certain 'moral' rights, so listing both the author and public domain is probably correct.
[21:37] <asac> ScottK: btw, are you on the (new) ~ubuntu-mozilla-security archive for your dapper install? or didnt i inform you about that change ;)?
[21:38] <asac> previously i did previews in ~asac
[21:38] <ScottK> asac: I don't think I am, but I'll check when I get back to my desk.
[21:38] <ScottK> asac: Thanks for mentioning it.
[21:38] <asac> thanks. there is a new build available ... we plan to roll out later. if you have a chance to run a quick test that would be awesome
[21:39] <ScottK> Should be able to do that tonight or tomorrow.
[21:39] <asac> https://edge.launchpad.net/~ubuntu-mozilla-security/+archive/ppa
[21:39] <asac> yeah. we probably will roll that tonight.
[21:39] <asac> if you dont get to it ... next time ;)
[21:39]  * ScottK is seriously considering finally upgrading that machine.
[21:41] <directhex> ScottK, workds subcontracted by the govt to private companies are not covered by that exemption. yay!
[21:41] <asac> ScottK: heh ;) ... you are my best tester ;)
[21:42] <asac> ScottK: well ... at least the only one i know how to reach ;)
[21:42] <ScottK> directhex: It depends on the terms of the contract.
[21:42] <asac> but dapper will be EOL in jun ... so well. hopefully there will be only one more round (or maybe two)
[21:42] <ScottK> directhex: In the case that the contractor owns the work it's not then a USG produced work.
[21:43] <ScottK> asac: Yes.  I do wonder though, after desktop LTS EOL, are such packages going to be removed from the archive?
[21:43] <asac> ScottK: not sure. i am leading the upstream long-term support effort somehow ... so i will try to keep 1.8 branches alive as long as possible
[21:43] <asac> at best 4 more years ;)
[21:44] <ScottK> If they aren't removed, then they'll still need 'support' of a kind.
[21:44] <asac> maybe i can still upload to dapper. will ask security team, but since i usually do most work i doubt they have any issues
[21:45] <ScottK> I'm running into problems now with my clamav backports where some rdepends upstream is dead a the package doesn't work with the current.
[21:46] <ScottK> So in extreme cases I turned the package into a transitional package to another one that was still supportable.
[21:47] <ScottK> And that was on Hardy.
[21:47] <ScottK> Now it looks like on Dapper it'll be several.
[21:49] <directhex> sounds like fun :(
[21:50] <ScottK> directhex: We got a while wiki page on it. https://wiki.ubuntu.com/MOTU/Clamav
[22:02] <chrismurf> fabrice_sp, thanks for your review and comments, I've now updated pyproj to reflect your feedback.  Take care.
[22:05] <Vest> Guys, I've uploaded my package without any errors. Can anybody of you review my project? or maybe tell me whom should I ask and possibly when (if the meeting of reviewers starts periodically)
[22:05] <asac> ScottK: you made a transition in a SRU ?
[22:06] <asac> thats interesting ;) ... except for first bumps of firefox-3.0 beta 5 to final (which were sort of transitions), I didnt feel brave enough for that yet
[22:06] <asac> i should do that for intrepid NM actually ... but well ..
[22:06] <ScottK> asac: It was a backport (so far).  The path I've been taking with major clamav updates is backports -> proposed -> security/updates.
[22:07] <ScottK> Also I've only done this for releases where clamav is in Universe.
[22:07] <asac> yeah.
[22:07] <asac> where is clamav in main?
[22:07] <asac> is that installed by default on server seeds?
[22:07] <ScottK> Intrepid and later.
[22:07] <ScottK> Yes.
[22:07] <ScottK> For the mail server task.
[22:08] <ScottK> All the GUI front ends are in Universe, but I still have to tend to them.
[22:08] <asac> back a few years when i worked a bit in universities anti-virus lab clamav was quite miserable ... especially finding new virus through heuristics (e.g. without signature)
[22:08] <asac> but i guess that has improved now
[22:08] <ScottK> We've got a major new upstream hitting in ~ one month that will break everything and so eventually I'll need to deal with 0.94 -> 0.95 in Intrepid.
[22:09] <ScottK> I think it has.
[22:09] <ScottK> It's definitely the best FOSS solution available.
[22:09] <ScottK> Essentially it's the only one.
[22:09] <asac> yeah. i dont doubt that ;)
[22:12] <lfaraone> vorian: hi, can you sponsor https://bugs.edge.launchpad.net/ubuntu/+source/sugar/+bug/327097 ?
[22:15]  * gaspa looking for a sponsor of a sync...
[22:16] <ScottK> gaspa: Just subscribe ubuntu-universe-sponsors.
[22:23] <lfaraone> ScottK: Don't syncs require ubuntu-archive?
[22:23] <ScottK> lfaraone: After approval by a MOTU.
[22:23] <ScottK> The MOTU will subscribe the archive.
[22:26] <EagleScreen> hello, i try to fix a bug in qtparted making a patch :D
[22:28] <EagleScreen> i have downloaded qtparted sources, but it has seven patches in debian/patches, and I need no know how to apply that patches to the sources before modifying it
[22:29] <EagleScreen> patch -p1 debian/patche_name.dpatch hangs
[22:29] <geser> which patch system does it use?
[22:29] <geser> ah, dpatch
[22:30] <geser> use dpatch-edit-patch
[22:32] <EagleScreen> but that is for edit a patch isn't it?
[22:34] <ScottK> EagleScreen: Read man dpatch-edit-patch
[22:34] <EagleScreen> reading man
[22:41] <EagleScreen> great tool
[22:47] <EagleScreen> i have run dpatch-edit-patch patch debian/patches/00list, now i am in the "fake" shell, but i am reading the sources, and patches does not seem to be applied
[22:48] <EagleScreen> i have to leave now, see you later, thanks
[23:20] <NCommander> ScottK, ping?
[23:36] <ScottK> NCommander: Pong
[23:37] <NCommander> ScottK, I was going to ask you to REVU a package, but I need to check some things before hand
[23:37] <ScottK> K
[23:50] <kolby> ScottK you can revu md4sum while you wait, if you like.
[23:51] <ScottK> kolby: First explain to me why we want this in the archive?
[23:51] <ScottK> From the name it sounds like the thing that came before md5sum and that's already obsolete.
[23:52] <kolby> ScottK This program creates archives for eDonkey P2P networks
[23:52] <kolby> It uses a protocol that appearantly wasn't offered in md5sum
[23:53] <huats> Tonio_: you should go to bed my friend... you need to sleep !
[23:53] <directhex> short version: edonkey sucks?
[23:53] <Tonio_> huats: je sais putain........
[23:53] <kolby> Md4sum generates or checks MD4 checksums applying the algorithm specified in RFC 1320
[23:53] <Tonio_> j'ai 38.7 de fièvre et je fais le geek.....
[23:53] <Tonio_> je suis sur le packaging de koffice la.....
[23:53] <Tonio_> huats: ca craint a ce stade la non ? :)
[23:53] <kolby> directhex: incorrect.  Nice try though.
[23:54] <huats> Tonio_: indeed :)
[23:54] <huats> Tonio_: go to bed...
[23:54] <Tonio_> huats: hehe, promises, in 6 minutes, at 1 am, I'm gonna sleep
[23:54] <huats> Tonio_: I hope...
[23:54] <Laney> kolby: md4 is broken
[23:55] <kolby> Laney: Why would you say that?
[23:55] <kolby> Laney: I packaged the program wrong?
[23:55] <Laney> No, there are collision attacks against it
[23:55] <directhex> kolby, as in "the hash is worthless, it's trivially circumvented these days"
[23:56] <Laney> although md5 is heading that way
[23:56] <kolby> It could be a tool for learning how to circumvent hashed files.
[23:56] <StevenK> md5 has already been broken, but it isn't trivial
[23:57] <kolby> A person could learn the techniques of how encryption works / breaks
[23:57] <directhex> this fast md4 collision generator i found takes ~7 seconds to generate a collision
[23:57] <kolby> I think that's a great reason/
[23:58] <kolby> directhex: what's it called?
[23:58] <directhex> http://en.wikipedia.org/wiki/MD4
[23:58] <kolby> directhex: look for an md5sum breaking tool
[23:58] <directhex> collision attacks section
[23:58] <directhex> kolby, there are some, but they take >7 seconds
[23:59] <kolby> directhex: lol.  Maybe for your pithy not-a-supercomputer.
[23:59] <directhex> kolby, wrong person to say that to.
[23:59] <Laney> MD5 is in use now, and I'm sure people will move away from it in time.
[23:59] <kolby> directhex: You have a super computer?