[12:17] <ajmitch> crimsun: do you know some biologists? :)
[12:17] <LaserJock> crimsun: but ... but ... they're hardly scientists at all
[12:17] <LaserJock> just a shade above social scientists :/
[12:17] <ajmitch> now be careful, LaserJock 
[12:17] <LaserJock> ;-)
[12:18] <LaserJock> well, as an undergrad I was a jack-of-all-trades
[12:18] <ajmitch> we'll forgive you
[12:18] <LaserJock> my senior research project was chasing rare hawks around the woods
[12:18] <ajmitch> such a shame you had to throw your life away on chemistry though
[12:22] <LaserJock> ajmitch: bah, whatever
[12:23] <LaserJock> I'd much rather be figuring out how the fundamental elements of the universe work together to produce everything
[12:26] <ajmitch> LaserJock: admit it, you'd rather be up to your eyeballs maintaining someone else's bitrotten code
[12:27] <LaserJock> ...
[12:44] <tezem> hi, I just found out about REVU and because I am an Arch Linux user I would like to see that this REVU system works as easy as aur.archlinux.org . Is it planned to make the upload process of new packages easier for everybody? It's hard if you have to be approved to be able to upload something.
[12:49] <LaserJock> tezem: in the future it will probably be a little bit easier
[12:49] <LaserJock> tezem: but we can't have random people/bots uploading stuff
[12:51] <ajmitch> not that the barrier or any checking is particularly robust
[12:51] <tezem> LaserJock: Why not just making it like Archlinux? Registering is all you need to do and you can put your packages into a database. People can use them for their own risk and if enough votes come together the package will be taken into a community repo.
[12:53] <LaserJock> tezem: well, to be honest, I'm not sure that we'd be very enthusaiatic about the idea
[12:53] <LaserJock> we have a pretty low barrier for somebody wanting to have their work in an official repo
[12:54] <LaserJock> all you need is to register and have a gpg key
[12:56] <tezem> yeah the gpg key idea is good but I read that I have to wait for approval to be added to some keyring or something. Thats not good
[12:56] <LaserJock> tezem: that's more or less not an issue anymore
[12:56] <LaserJock> and was just there because of some technical issues with using Launchpad for authentication
[12:57] <tezem> Ah ok then it's already the same idea as the AUR in Arch with the addition of using gpg signing, if i understood right.
[01:02] <LaserJock> tezem: probably
[01:03] <LaserJock> it's not perfect
[01:03] <LaserJock> and will probably be integrated more into Launchpad in the future
[01:36] <crimsun> LaserJock: yeah, I'm kinda partial to biology, since it was my first undergraduate major.
[01:37] <persia> crimsun: You wanted to ask me about the icon location for uqm?
[01:38] <crimsun> persia: is there a reason it's hardcoded as such? Does it reside in that same package?
[01:40] <persia> crimsun: The icon belongs to uqm-content, which is CCA-NC-SA.  I'm not convinced I have the right to copy it, convert it, and add it to uqm, which is GPL.
[01:41] <crimsun> so the Icon location is broken?
[01:42] <persia> crimsun: That seemed the best solution.  The other would be to also change uqm-content, which allows modification for distribution as part of uqm.
[01:44] <crimsun> http://creativecommons.org/licenses/by-nc-sa/2.5/  <-- ?
[01:44] <persia> crimsun: Yes.
[01:44] <crimsun> what would prevent you from copying it?
[01:44] <crimsun> the commercial clause?
[01:45] <crimsun> or rather, the noncommercial clause
[01:46] <persia> crimsun: SA requires that it be distributed under the same license.  uqm is GPL, which is a different license, and the icon ideally belongs in the same package as the menu file and .desktop.  I could also modify uqm-content to put it in /usr/share/pixmaps, if you think that is better.
[01:49] <crimsun> persia: where on http://creativecommons.org/licenses/by-nc-sa/2.5/legalcode is it stated that non-derivative works must be distributed under the same license?
[01:50] <persia> crimsun: I believe 4a applies.
[01:50] <persia> crimsun: It's not non-derivative.  I was using an icon from uqm-content.
[01:51] <crimsun> right, and since uqm-content is not a derivative work of uqm, there's no restriction on the license of the collective.
[01:51] <LaserJock> persia: why can't you put the icon from uqm-content into uqm?
[01:51] <crimsun> "The above applies to the Work as incorporated in a Collective Work, but this does not require the Collective Work apart from the Work itself to be made subject to the terms of this License."
[01:51] <LaserJock> just put it there
[01:51] <persia> LaserJock: Are you sure Ubuntu can distribute a CCA-NC-SA icon under GPL?
[01:52] <LaserJock> why would be it be under GPL?
[01:52] <crimsun> it's not under GPL.
[01:52] <persia> LaserJock: uqm is GPL
[01:52] <LaserJock> so what?
[01:52] <LaserJock> that doesn't matter
[01:52] <crimsun> see the above section I just quoted, persia 
[01:52] <LaserJock> we put mixed licensed material together all the time
[01:53] <LaserJock> you just need to say in debian/copyright what the license is for that file, etc.
[01:53] <persia> crimsun: Thanks.  I misunderstood that bit.  I'll update.
[01:54] <LaserJock> persia: are you sure that it's NC ?
[01:54] <persia> LaserJock: I thought GPL was considered OK for universe inclusion, and CC-NC-SA required multiverse (certainly debian non-free), and that a mix across those lines what not ideal.
[01:54] <LaserJock> I think that would make it undistributable in Ubuntu
[01:55] <persia> LaserJock: It says so in debian/copyright.  uqm-content is multiverse.
[01:55] <LaserJock> well, if CC-NC-SA is indeed distributable in multiverse it would just mean that uqm and uqm-content would go in Multiverse
[01:55] <LaserJock> does uqm depend on uqm-content?
[01:56] <persia> LaserJock: Yes, (and is also in multiverse).  I'll go update the licenses...
[01:56] <LaserJock> I'm suspicious that CC-NC-SA is not distributable
[01:57] <LaserJock> you might want to ask somebody like mdz about that
[01:57] <persia> LaserJock: Why?  As long as it is downloaded for free (and multiverse isn't supposed to be on CD), and not resold by downstream distributors (who should check debian/copyright before planning a CD), it should be fine.
[01:57] <LaserJock> well, that second part would be the problem
[01:58] <LaserJock> although I think I recall mdz saying that the "must be usable by all" thing didn't apply to Multiverse
[01:58] <persia> LaserJock: Do you really think Ubuntu can get in trouble if some third party downloads something from the repositories, clearly marked as Non-Commercial, and then attempts to sell it?
[01:58] <LaserJock> although I think that doesn't make much sense
[01:59] <LaserJock> persia: well, it does have ramifications
[01:59] <LaserJock> for instance, you are supposed to be able to freely distribute Ubuntu
[01:59] <LaserJock> so a commercial organization should be allowed to sell and Ubuntu derivative
[02:00] <LaserJock> but if I remember correctly mdz said that didn't apply to Multiverse, although I don't know why it shouldn't
[02:01] <lifeless> multiverse has differently licencesed software in it
[02:01] <persia> LaserJock: My understanding is that multiverse contains lots of random unsupported stuff which users might like, but which may not fit with the general licensing guidelines of Ubuntu (yet may stil be distributed).
[02:02] <LaserJock> persia: yes, so it can be closed source
[02:02] <LaserJock> but it needs to be distributable
[02:02] <LaserJock> and that's the point
[02:02] <LaserJock> is how far you take distributable
[02:02] <LaserJock> whether it just means distributable by us
[02:02] <persia> LaserJock: Distributable by the Ubuntu mirrors, not necessarily distributable by others, I think.
[02:03] <LaserJock> or distributable by any derivative
[02:03] <LaserJock> persia: well that's not the case for other components, that's what I'm saying
[02:03] <LaserJock> but I think multiverse is the lone exception
[02:03] <persia> LaserJock: That matches my understanding.
[02:04] <LaserJock> although, I don't think it's very nice to have that exception
[02:08] <LaserJock> persia: I guess that is consistent with "The onus is on you to verify your rights to use this software and comply with the licensing terms of the copyright holder."
[02:09] <LaserJock> although my understanding of Multiverse has been more "closed source by freely distributable"
[02:10] <persia> LaserJock: That's the clause.  From what I've seen, much of multiverse is non-commercial, or non-military, or, licensed under a strange license (You can do anything you want with this code, but don't bug me!), or something else.
[02:11] <LaserJock> well, I put some rather funky stuff in there myself
[02:12] <LaserJock> what I don't like about the idea of "this may or may not be redistributable" is that derivates have a hard time checking *every* package to see if they are ok in distributing it
[02:12] <LaserJock> but Multiverse is so weird anyway, and that clause is fairly clear, I can't see much of a problem
[02:13] <LaserJock> if Universe had such a clause I'd be very worried
[02:13] <persia> LaserJock: Derivatives only have to check in Multiverse, and only if they have a different distribution policy than Ubuntu.  There aren't that many packages anyway.
[02:14] <persia> It appears that Joey went to some trouble to repack to avoid CC in uqm.  I think I'll just install uqm.xpm in uqm-content, so as to avoid rewriting debian/copyright.
[02:15] <LaserJock> well, as my dad would say, "Shoot yourself"
[02:16] <LaserJock> hmm, that really doesn't come across as well on IRC ;-)
[02:16] <jdong> that's what my priest said to...... never mind
[02:51] <shawarma> I forget: What's the procedure for adding new packages to universe? Upload to revu and get approval from two other MOTU's?
[02:51] <Nafallo> yes
[02:52] <ajmitch> that's the procedure some motus follow 
[02:55] <bronson> Is there an easy way to run build-dep inside a pbuilder environment?
[02:56] <bronson> I'm building Ubuntu kernels and just installing all the deps takes a long time.
[02:56] <bronson> It would be nice if they were already inside the tarball...
[03:00] <ajmitch> you could stuff them in the base tarball with pbuilder login --save-after-login
[03:00] <ajmitch> ie, login, install, logout
[03:01] <bronson> ajmitch: that makes sense.  I'll try it.
[03:01] <bronson> Thanks.
[03:08] <shawarma> ajmitch: ...and the one we all *ought* to be following, yes?
[03:08] <shawarma> sorry for going away after asking a question, by the way. 
[03:12] <ajmitch> shawarma: considering that a large number of MOTUs are core devs as well, working on various things
[03:12] <ajmitch> so pushing *everything* through REVU becomes a bottleneck
[03:14] <ScottK> Speaking of REVU, I have two Python packages (one upstream update of an exisiting package - http://revu.tauware.de/details.py?upid=4114 and one new package -http://revu.tauware.de/details.py?upid=4115) if any MOTUs are available.
[03:27] <bddebian> Heya gang
[03:27] <persia> hi bddebian
[03:27] <bddebian> Hi persia
[03:30] <ScottK> heya bddebian!
[03:30] <bddebian> Hi ScottK
[04:07] <bddebian> Anyone ever gotten a broadcom wireless adapter to work without ndiswrapper?
[04:07] <wasabi_> Anybody planning on packaging gimmie?
[04:20] <ScottK> Heya bddebian: I see you are revuing...  I uploaded a new package today that I'd appreaciate a look at http://revu.tauware.de/details.py?upid=4115 and on the broadcom thing - I've never actually managed to get ndiswrapper or madwifi to work, I just have to find wireless cards that are supported in the kernel.
[04:21] <bddebian> I refuse to use ndiswrapper but I can't find my damn Orinico card :-(
[04:22] <ScottK> I'm currently stuck at my desktop because we are down one laptop and my wife needs to take one to work tonight.
[04:23] <ScottK> I had to swap out the hard drive so she could dual boot into Windows :-(
[04:26] <bddebian> Heh
[04:26] <bddebian> I don't have that problem since I have 10 machines in my house now :-)
[04:28] <ScottK> I'm just short functioning laptops.  Got lots of others...
[04:42] <ScottK> bddebian: Thanks.  I've another clean one for you if you're up for it: http://revu.tauware.de/details.py?upid=4114
[04:51] <bronson> ajmitch, Here's how to automate adding build-deps to a pbuild environment: http://wiki.u32.net/Dpkg/pbuilder/deps
[04:51] <bronson> You put me on the right track.
[05:02] <jdong> bddebian: thanks for your help on the x264 stuff.... I just noticed PPC failed while other arches are ok.... drats :)
[05:02] <jdong> anyone have a PPC and some time to spare?
[05:02] <bddebian> I wish I had a PPC :-(
[05:05] <jdong> googling seems to indicate it has something to do with altivec....
[05:11] <bddebian> w00t, I have wireless with this POS broadcom
[05:15] <ajmitch> congrats
[05:19] <jdong> bddebian: wrt the FTBFS, I think adding -faltivec to PPC CFLAGS will fix it
[05:20] <jdong> bddebian: that's line 166 of configure
[05:20] <jdong> apparently -maltivec is not sufficient :)
[05:22] <jdong> bddebian: actually, one sec, I'll prepare you a debdiff with a more sane fix
[05:24] <jdong> bddebian: http://paste.ubuntu-nl.org/2120/
[05:25] <jdong> voila, debdiff 
[05:32] <bddebian> jdong: It's up
[05:35] <jdong> bddebian: cool, cross our fingers :D
[05:35] <jdong> and curse PPC @ the same time :D
[05:36] <bddebian> heh
[05:39] <Mez> how do i use rsync through ssh
[05:43] <jdong> Mez: rsync -av -e ssh host1:/path host2:/path
[05:44] <Mez> worked it out
[05:44] <jdong> actually you don't even need -e ssh; it's assumed nowadays
[05:45] <Mez> jdong: whee :D now I have my apt-repo
[05:53] <bddebian> w00t Mez :)
[06:08] <bddebian> Heya Hobbsee
[06:09] <persia> hi Hobbsee
[06:09] <Hobbsee> heya bddebian, persia 
[06:10] <persia> For iceweasel/icedove dependencies, do these just get updated to firefox/thunderbird (same versions)?
[06:17] <Mez> ffs 
[06:17] <Mez> I dont think my oven works
[06:22] <ScottK> Good night - bddebian: Thanks again for the REVU.
[06:22] <Mez> anyone good at bash scripting want to help me convert this http://rafb.net/p/3E1f1116.html into a proper bash script
[06:24] <bddebian> GNight ScottK, NP
[06:27] <bddebian> Ack, me too.. Gnight gang
[06:27] <Lutin> Mez: what's the 'exists' function ? Is it just a test 'file exists' ?
[06:28] <Mez> yeah
[06:28] <Mez> I got it anyways
[06:28] <jdong> night, bddebian
[06:28] <Mez> Lutin, http://rafb.net/p/qBwLWl29.html
[06:28] <persia> Mez: http://rafb.net/p/qMlyNI65.html
[06:29] <jdong> Mez: see, exactly what I told you ;-)
[06:29] <Mez> ;)
[06:29] <jdong> only persia did it all for you ;-)
[06:30] <persia> jdong: Mez did it himself about 13 seconds before I could :)
[06:30] <Mez> jdong: as I did myself just before
[06:30] <Mez> now I just need man pages
[06:30] <jdong> oh dear lord, man pages
[06:31] <Mez> jdong: my thoughts exactly
[06:32] <Mez> jdong: it's better than trying to backport gstreamer anyways
[06:32] <Lutin> Mez: seems to be some weird logic in your script
[06:32] <Mez> Lutin... how so ?
[06:33] <jdong> Mez: yikes :)
[06:33] <Lutin> Mez: you do if [ -f ~/.nostromorc ]  ; then; else ....
[06:33] <Mez> jdong: backportingn gstreamer works
[06:33] <Lutin> if you have something esle than [ -f ~/.nostromorc ] 
[06:33] <Mez> just the thing i was backporting it for doesnt
[06:33] <Lutin> the works would already have been true
[06:33] <Lutin> erek.
[06:33] <Lutin> the first test
[06:34] <Mez> Lutin ...
[06:34] <Mez> exactly
[06:34] <Mez> BUT ...
[06:34] <Mez> the code in the else will copy the file to where it should be
[06:34] <Mez> if it doesnt exist
[06:34] <Mez> if there is nothing plugged in that matches the hardware
[06:34] <Mez> it wont copy it
[06:34] <jdong> Mez: gstreamer is still on 0.10, just point-releases right?
[06:34] <Mez> meaning it wont exist
[06:35] <jdong> Fedora backports all the point-releases as official updates
[06:35] <Mez> jdong, yeah 0.10.10 -> 0.10.11
[06:35] <jdong> yeah, I'd expect that to work
[06:35] <Mez> jdong it does
[06:35] <Mez> cept
 Argh! Something went wrong and a serious error occurred:
 Your GStreamer installation is missing a plug-in.
 gstdecodebin.c(1668): gst_decode_bin_change_state (): /timeline/playbackbin/Instrument_0/gnlcomposition0/Event_1/internal-decodebin
 It is recommended that you report this to the Jokosher developers or get help at http://www.jokosher.org/forums/
[06:35] <Mez> Lutin, check the script again ;)
[06:36] <Mez> 
[06:37] <jdong> Mez: lovely :)
[06:37] <Mez> ] =
[06:37] <Mez> ] 0000000000000
[06:37] <jdong> Mez: and on TLTS near new year's IIRC there was a informal mention of a backport request for jokosher too :D
[06:37] <Mez> ] 0000000000000
[06:37] <jdong> I was listening to the podcast and just grinned
[06:37] <Mez> TLTS?
[06:38] <Mez> apologies about the spam there
[06:40] <jdong> linux link tech show
[06:40] <jdong> missing an L because it's midnight
[06:41] <Mez> never heard of it 
[06:41] <Mez> there hasnt been one on LR and they're the developers of it
[06:42] <Mez> lol
[06:43] <jdong> jono and a bunch of british/australian/non-american accented people do it
[06:43] <jdong> lmao
[06:43] <jdong> excuse the offensive remark :)
[06:43] <LaserJock> so jokosher isn't in Main yet?
[06:44] <Mez> jdong: you sure you dont mean http://www.lugradio.org/
[06:44] <Mez> LaserJock, nope
[06:44] <Lutin> Mez: ok, I understand now ;)
[06:44] <LaserJock> anybody want to write up a MIR for jokosher?
[06:44] <jdong> Mez: yeah, that's the one
[06:45] <Mez> jdong: I didnt hear that one :P
[06:45] <Mez> I remember them saying "oh, it might get backported"
[06:45] <Mez> but thats what prompted me to do it
[06:45] <jdong> Mez: :)
[06:45] <jdong> if I was less lazy at the time I would've started messing with it too
[06:45] <Mez> lol
[06:45] <jdong> that's about as subtle as a backport request could be for me :D
[06:46] <jdong> but audio editing wasn't an itch I had to scratch
[06:46] <Mez> ooh
[06:46] <Mez> pizza
[06:46] <Mez> bugger
[06:46] <Mez> put my poven in wrong mode
[06:46] <Mez> gotta wait another 25 mins
[06:47] <jdong> GOD FSCK IT
[06:47] <jdong> http://librarian.launchpad.net/5788159/buildlog_ubuntu-feisty-powerpc.x264_1%3A0.cvs20070117-0ubuntu2_FAILEDTOBUILD.txt.gz
[06:47] <jdong> GRR
[06:48] <jdong> any altivec genies around here?
[06:48] <jdong> possible solutions: (1) nobody cares about PPC. screw it and move on blessing i386/x86_64/ia64/sparc with x264 good ness
[06:48] <jdong> (2) Reverse svn changeset that added altivec optimizations
[06:49] <jdong> which is worse?
[07:08] <Lutin> gotta leave, bye
[07:14] <ajmitch> pango is so messed up right now
[07:15] <LaserJock> so we're supposed to put down the time we voted on the wiki page?
[07:15] <ajmitch> & the mailing list
[07:15] <Hobbsee> LaserJock: yes
[07:15] <ajmitch> which I haven't done
[07:15] <ajmitch> since I'm slack & lazy
[07:15] <LaserJock> why do we need it on the mailing list too?
[07:16] <ajmitch> sunday is winning
[07:16] <LaserJock> hmm, I'm not sure what to say. Maybe I shouldn't vote
[07:17] <ajmitch> voting is your duty!
[07:17] <ajmitch> if you don't vote, the terrorists win
[07:18] <LaserJock> well, but I'm not sure I can make any of the times
[07:18] <LaserJock> hmm, I guess Monday could work though
[07:19] <ajmitch> the 1 day it won't work for me :)
[07:20] <LaserJock> what the heck is that time format?
[07:21] <Hobbsee> dunno
[07:21] <ajmitch> just stick in @SIG@
[07:22] <ajmitch> it's hardly necessary
[07:22] <ajmitch> & I think it's slightly silly
[07:22] <LaserJock> mhm
[07:22] <LaserJock> but /me doesn't want to be the one rocking the boat
[07:23] <LaserJock> oh wow
[07:24] <LaserJock> I put in UTC, and it spits it out in local time
[07:24] <LaserJock> but I think if you vote you have to add an agenda item
[07:25] <ajmitch> I did
[07:28] <LaserJock> well, I added two just to be safe
[07:28] <LaserJock> probably not interesting though
[07:32] <ajmitch> they don't have to be interesting
[07:32] <ajmitch> the meeting's not there for general entertainment
[07:36] <LaserJock> what?!?!
[07:36] <LaserJock> and here I was going to bring my tap shoes
[07:40] <persia> Tonio_: Hey.  I was looking at a merge of yakuake earlier, and heard you didn't think it should be merged.  Could you share your thoughts on that?
[07:45] <LaserJock> persia: it's a bit confusing when you confirm a sync request for u-u-s, usually that means we've acked it
[07:45] <persia> LaserJock: Sorry.  That was me trying requestsync.  Given the results, I don't think this is a good tool for non-members of ubuntu-dev.
[07:46] <LaserJock> ah, can you get it to not set that?
[07:48] <persia> LaserJock: I can, but the default is to confirm (and sub ubuntu-archive).  I changed the subscriber in my first try, but I don't like the output, as it doesn't include any rationale.  I may edit it to be useful for me, but I may also stick with hand creation.
[07:50] <LaserJock> persia: yeah, that makes sense
[07:53] <persia> LaserJock: I'm guessing that if u-u-s members don't know why it should be sync'd, it's more difficult to make an ACK decision.
[07:54] <Tonio_> persia: there is no difference on the package, no patches etc....
[07:54] <Tonio_> the only thing to what I know is packaging, but as debian one isn't cdbs based.....
[08:00] <persia> Tonio_: OK.  I understand.  Thanks for the explanation.
[08:01] <Tonio_> persia: you're welcome
[09:02] <Laser_away> ajmitch: do you think it would be possible to add the Debian apt gpg keys to tiber?
[09:06] <ajmitch> why?
[09:07] <Laser_away> well, my scripts use apt to grab Debin sources
[09:07] <Laser_away> and so my cron log and mail on tiber get full of gpg warnings
[09:08] <Laser_away> it's not a big deal, just slightly annoying
[09:08] <ajmitch> I'll see what I can do
[09:09] <dholbach> good morning
[09:12] <ajmitch> hey daniel
[09:13] <dholbach> hey andrew
[09:19] <lucas> Laser_away: if you use mdt, you probably have to add the key to your account
[09:19] <lucas> not to the root account
[09:24] <Laser_away> lucas: can I do that? I tried generic directions but they didn't work, how do I tell it what to use?
[09:25] <lucas> well, doesn't gpg --recv-key keynumber works ?
[09:25] <Laser_away> that get's the key
[09:26] <lucas> and then, mdt still complains ?
[09:26] <Laser_away> hmm, I didn't check actually
[09:26] <Laser_away> I thought I'd need apt-key add
[09:27] <lucas> ah maybe
[10:58] <\sh> moins
[10:59] <persia> \sh: Good morning.  Did you ever get boson to compile, or should I be working on something?
[11:09] <imbrandon> moins all
[11:09] <imbrandon> off to work see yall in a bit
[11:21] <Mez> anyone wanna review http://revu.tauware.de/details.py?upid=4120
[11:22] <Mez> I know theres no man pages
[11:24] <persia> Mez: You might want to add #!/bin/bash at the top of nostromo_container_script.
[11:25] <Mez> thought i had
[11:34] <persia> ls
[11:34] <fernando> moin all
[11:36] <persia> Mez: It works for me now.  I'm leaving this one installed.  Thanks.
[11:36] <Mez> persia, woo!
[11:48] <persia> Mez: http://rafb.net/p/7E8xEx51.html
[11:48] <Mez> persia - lol
[11:50] <persia> Mez: No worries.  I'm excited about this app, and prefer not to maintain local changes :)
[11:50] <Mez> ;)
[11:51] <Mez> persia, then you wont mind writing man pages ? :P
[11:51] <persia> Mez: Umm..  Well...  Perhaps not that excited.
[11:52] <Mez> darn
[11:54] <StevenK> help2man, maybe?
[11:54] <Mez> StevenK, no --help output
[11:54] <StevenK> Useful.
[11:56] <Mez> StevenK, it has a html file ;)
[11:56] <Mez> but that gives nothing away
[11:56] <Mez> and one of the scripts we wrote ourselves.
[11:57] <Mez> and a lot of it I had to hack on :(
[11:57] <Mez> persia, you'll be happy to know - upstream are happy to take on my changes
[11:57] <persia> Mez: Good.  Everyone will get a nice icon in the control centre, even other distributions.
[12:02] <StevenK> Mez: :-)
[12:02] <Mez> StevenK, ... ? what did i do now ?
[12:03] <StevenK> Mez: You stumbling into the mess in -devel. :-)
[12:03] <Mez> lol
[12:17] <Mez> persia: even more fun 
[12:17] <Mez> seems we have most of it done now
[12:21] <persia> Mez: ?
[12:21] <Mez> well we're now using dh_installudev
[12:21] <Mez> ;)
[12:21] <Amaranth> yay
[12:21] <Amaranth> instead of doing hacky things you can just call out to scripts that do hacky things in a somewhat standard way ;)
[12:22] <Mez> Amaranth, I didnt know about dh_installudev
[12:22] <Amaranth> sorry, was supposed to be funny
[12:22] <Amaranth> dh_<tab> in a terminal might be useful though :)
[12:23] <persia> Mez: man debhelper provides a nice list.  I can never remember them all, but it's a good place to check when you want to do something.
[12:24] <Mez> ssh
[12:24] <Mez> leave me alone
[12:24] <Mez> I blame Tonio_ 
[12:24] <Mez> he gave me roms
[12:24] <Mez> my heads stuck in super mario world
[12:25] <Amaranth> "Tea, back with Heather, set too trying to repair the machine, reluctantly used a floating Kubuntu CD to do the rsyncing magic & rescued mail, home-dir & dollops of data; halleluja. Call with Kay Ramme: very switched on guy."
[12:25] <Amaranth> michael meeks :)
[12:26] <Tonio_> Mez: giving roms is my internet mission ^^
[12:26] <Mez> Tonio_, ssh
[12:27] <Mez> if I could get them to work in linux would even be better
[12:38] <Mez> jdong, can you check out bug 80579
[12:38] <Ubugtu> Malone bug 80579 in edgy-backports "backport kxmame" [Undecided,Unconfirmed]  https://launchpad.net/bugs/80579
[01:30] <Amaranth> crimsun: holy crap the light on my mute button works!!! dude, you're so awesome
[01:39] <crimsun> excellent.
[02:04] <giskard> ciao *
[02:10] <Kano> hi siretart
[02:10] <Kano> siretart: i am missing h264 support in kaffeine, vlc can playback it
[02:11] <Kano> best would be multithreaded...
[02:50] <ScottK> Is there a MOTU available who would be willing to review a new Perl library - http://revu.tauware.de/details.py?upid=4113 - I've been waiting for a dependency and it hit the archives last night...
[03:03] <white> ScottK: may i friendly suggest to consider bringing them into debian (in case you want to maintain them, but it seems you are very active with perl modules) ?
[03:04] <white> ScottK: i know that the debian-perl packaging team warmly welcomes every newcomer :)
[03:04] <white> (this would of course help ubuntu as well)
[03:07] <ScottK> white: Someone else is working on getting them into Debian who is already in the Perl group. 
[03:08] <ScottK> I'm actually more of a Python person.  
[03:08] <ScottK> The two of us are working together.  He's the Perl/Debian guy and I'm the Python/Ubuntu guy.
[03:10] <ScottK> white: You wouldn't happend to know if there is an equivalent Python group in Debian would you?
[03:13] <Hobbsee> how does one force a package on which version of python to use at runtime?
[03:15] <shawarma> Hobbsee: Set #!/usr/bin/python2.4
[03:15] <Hobbsee> shawarma: where?
[03:15] <shawarma> Hobbsee: Top of the file.
[03:16] <Hobbsee> shawarma: for every file within it?
[03:16] <Hobbsee> (seeing as there are multiple .py files)
[03:16] <shawarma> Hobbsee: No, just the one you execute.
[03:17] <shawarma> Hobbsee: Ie. not all the dependant modules and such.
[03:17] <white> ScottK: http://people.debian.org/~terpstra/list/debian-python.en.html
[03:19] <Hobbsee> shawarma: hrm.  thought that was __init__.py
[03:20] <shawarma> Hobbsee: No, you're probably looking for a file in /usr/bin/
[03:20] <Hobbsee> shawarma: oh right, point
[03:21] <white> ScottK: http://alioth.debian.org/projects/python-modules/ http://alioth.debian.org/projects/pkg-python/ http://alioth.debian.org/projects/pkg-python-debian/
[03:21] <white> ScottK: these ones might be of some interest as well :)
[03:21] <ScottK> Thanks.  Looking.
[03:21] <Hobbsee> shawarma: doesnt seem to work.  oh well
[03:23] <shawarma> If anyone's in a revuing mood, please take a peek at http://revu.tauware.de/details.py?upid=4125 and http://revu.tauware.de/details.py?upid=4126
[04:15] <bddebian> Heya gang
[04:16] <crimsun> hello deity.
[04:16] <bddebian> Hi crimsun
[04:28] <ScottK> If anyone is up for REVUing, I made a list... http://spf.pastecode.com/12053
[04:36] <bddebian> ScottK: A list?? :)
[04:38] <ScottK> bddebian: I've got three packages waiting for REVU (you've already advocated one, thanks).  Rather than explain the status of the packages every time I beg for REVU here, I just made a short list.
[04:39] <bddebian> ScottK: Well my advocations are useless ;-P
[04:42] <Mez> bddebian, http://revu.tauware.de/details.py?upid=4122
[04:42] <ScottK> bddebian: I don't think so.  I do know that your not advocating comments have been helpful for me - I ended up having to make a new Feisty chroot to reproduce the build failure you got on pyspf.
[04:43] <bddebian> :-)
[04:44] <ScottK> bddebian: BTW, the charset issue you found in one of my man pages turned out to be a nul char buried in the original text I copied the information from.  I had to retype a few lines of the document to fix it....
[04:44] <bddebian> Ugh
[04:44] <ScottK> So, as I say, your reviews have been very helpful.
[04:45] <ScottK> Dunno exactly what you're in the doghouse for, but I have certainly appreciated your work.
[04:46] <bddebian> ScottK: I'm not in the doghouse, I just seem to miss a lot of nuance stuff on my reviews that others pick up :-(
[04:47] <Mez> well bddebian I'd be happy for you to look over my thing for me
[04:47] <Mez> ScottK, you a MOTU ?
[04:47] <ScottK> Mez: No, not even close.
[04:47] <Mez> ScottK, you have a lot of knowledge for a n00b
[04:47] <Mez> to be honest, I've found you very helpful quite often
[04:48] <ScottK> bddebian: Then I guess I haven't managed to hit that level of nuance in my mistakes yet.
[04:48] <Mez> when you're up for motu, poke me, I'll happily cheerlead
[04:48] <ScottK> Mez: Thanks.
[04:48] <Mez> ScottK, no probelm
[04:49] <Mez> ScottK, member yet ?>
[04:50] <ScottK> Actually, I'm not sure.  IIRC what that means, I think not.
[04:53] <Mez> ScottK, with libspf whats the huge diff with changes to libspf2-1.2.5.orig/src/libspf2/spf_dns_windns.c for ?
[04:54] <ScottK> I have no idea.  The only changes that I made for my bug fixes were in packaging.
[04:54] <Mez> ScottK, thats something that should be looked at
[04:55] <ScottK> I think I need to go back and rebuild the package for Feisty in my chroot without changing anything and see diff that with what I got.
[04:55] <ScottK> Mez: Thanks.  I have some work work I need to do now, but I'll try and attend to it later today.
[04:56] <Mez> ;)
[04:56] <Mez> just a quick poke was like
[04:56] <Mez> "wtf ??"
[05:29] <ScottK> Mez: I decided to ignore work work and look at libspf2.  I downloaded fresh libspf2 source into a new folder in my Feisty chroot, added an entry to changelog, and made no other changes.  Then I built the package with debuild -us -uc and got that same huge diff.
[05:29] <ScottK> Mez: I decided to ignore work work and look at libspf2.  I downloaded fresh libspf2 source into a new folder in my Feisty chroot, added an entry to changelog, and made no other changes.  Then I built the package with debuild -us -uc and got that same huge diff.
[05:30] <ScottK> It looks like it's been a long time since the package was built for Feisty: https://launchpad.net/+builds/+build/276787 - I wonder if some has changed in the build environment?
[05:37] <bddebian> ScottK: Are pyspf, libspf2 ready to be looked at or are you working on something?
[05:37] <ScottK> pyspf is ready.
[05:37] <ScottK> libspf2 has some weirdness.
[05:37] <ScottK> mail-spf-perl is also ready.
[05:37] <rexbron> hey
[05:37] <ScottK> hi
[05:38] <rexbron> how can I get debuild to ignore .bzr
[05:38] <rexbron> (it complains that it can not represent changes_)
[05:38] <geser> it shouldn't be there in the first place
[05:39] <rexbron> geser: could you explain more?
[05:40] <geser> you shouldn't have .bzr (or .svn) in the debian dir
[05:41] <rexbron> ok, removed it from the debian dir
[05:42] <rexbron> geser: there is .bzr in the main source dir
[05:42] <rexbron> and it still does not like that
[05:43] <geser> dpkg-source knows the option -i / -I to ignore files for the diff
[05:43] <geser> debuild uses dpkg-source so you need to figure out how to pass it
[05:44] <geser> you could also use dpkg-buildpackage instead of debuild
[05:45] <geser> how comes that you changed .bzr?
[05:47] <ScottK> bddebian: Thanks.  Since it's an existing package, is that (1 advocate) good enough to get it uploaded?
[05:47] <bddebian> ScottK: Is libnet-dns-foo-bar-baz in the archives now so mail-spf-perl will build?
[05:47] <ScottK> Yes.
[05:47] <ScottK> It built last night.
[05:47] <bddebian> OK
[05:47] <bddebian> Did I advocate something? :)
[05:47] <rexbron> geser: example line
[05:48] <ScottK> bddebian: Darn.  I missed that point.  
[05:48] <rexbron> it complains ther there is no final newline
[05:48] <ScottK> rexbron: Then add the final newline.
[05:51] <shawarma> bddebian: Hi. You've already reviewed this once: http://revu.tauware.de/details.py?upid=4126   <-- Would you mind taking a look at it again?
[05:51] <\sh> trying to fix xulrunner :)
[05:51] <bddebian> shawarma: Sure, give me a bix
[05:51] <\sh> bbl
[05:51] <bddebian> err bit
[05:57] <ScottK> Mez: I figured out the libspf2-1.2.5.orig/src/libspf2/spf_dns_windns diff with libspf2 - The original file has windows line endings.  They get converted to unix line endings and so the entire file shows up in the diff even though there are NO code changes.
[05:57] <bddebian> Egads
[05:58] <rexbron> ScottK: not sure if you are interested but debuild -i'dir' works
[05:59] <ScottK> rexbron: Thanks.  Will look into it.
[06:02] <shawarma> bddebian: Cool. There's also http://revu.tauware.de/details.py?upid=4125 
[06:02] <ScottK> rexbron: That looks like what I need.  Thanks again.
[06:04] <shawarma> bddebian: They are *very* similar.
[06:16] <ScottK> bddebian: Thanks.  On the 
[06:16] <ScottK> urgh... more typing...
[06:16] <ScottK> "W: libmail-spf-perl; Package does not have a great enough dependancy on perl." warning, I think that's because the package is written to depend on Perl 5.6 and 5.6 is ancient.
[06:17] <bddebian> Does it build with newer perl?
[06:17] <ScottK> Yes.
[06:17] <ScottK> It's 5.6 and newer.
[06:17] <bddebian> Ahh, OK
[06:17] <rexbron> this is weird
[06:18] <rexbron> the compiled binaries are not being placed in debian/tmp
[06:18] <rexbron> and they were before
[06:18] <ScottK> I imagine I could lie and say 5.8+ and get rid of the warning, but that doesn't seem right.
[06:18] <bddebian> It should be fine the way it is, I just hadn't seen that before
[06:26] <ScottK> bddebian: Thanks.
[06:26] <bddebian> ScottK: I took it back off :-(
[06:27] <ScottK> Ah, but for a good reason.
[06:27] <ScottK> I'll fix...
[06:45] <ScottK> bddebian: Fixed, thanks - http://revu.tauware.de/details.py?upid=4127 - It was a relatively pleasant escape from trying to figure out how to convince debdiff to exclude the line ending changes...
[06:56] <ScottK> bddebian: Thanks.  Any other MOTUs for http://revu.tauware.de/details.py?upid=4127
[06:57] <bronson_> Is there any way to get rid of "warning: no utmp entry available and LOGNAME not defined; using uid of process" in my pbuilds?
[06:57] <bronson_> It generates so much noise it's hard to see what else is going on in there...
[07:00] <bddebian> bronson_: Not that I've ever seen
[07:01] <bronson_> Boo.  grep -V it is then.  :)
[07:01] <bronson_> er, -v.
[07:01] <geser> shouldn't motu be set as maintainer ony for modified packages from debian?
[07:02] <LaserJock> geser: I think we don't need to worry about that right now
[07:02] <bddebian> Heya geser, LaserJock
[07:02] <LaserJock> I looks to me like they are going to automate that
[07:02] <LaserJock> at least for Main
[07:02] <geser> LaserJock: it's because ScottK set it for his package on revu
[07:03] <LaserJock> well, I think it's ok if he does it, but he certainly doesn't have to
[07:05] <LaserJock> hmm, perhaps we should put that on our agenda
[07:06] <LaserJock> the reason we are changing Maintainer is because Debian asked us to
[07:07] <LaserJock> but we should decide whether we want it in packages that are non-Debian
[07:08] <LaserJock> then put it in Debian to start with :-)
[07:08] <ScottK> I suspect that you may want to differentiate between non-Debian packages that aren't in Debian yet and ones that never will be.
[07:09] <ScottK> Sure and get it into Feisty how?
[07:09] <LaserJock> sync it
[07:09] <LaserJock> granted, right now is not the best time with the etch freeze
[07:09] <bddebian> How do we have gnumeric 1.7.6 when gnome.org says:  gnumeric-1.2.13 is the latest stable release ?
[07:09] <LaserJock> bddebian: it's unstable
[07:09] <ScottK> My current lack of a DD to work with to do that presents a problem (in addition to the whole Etch freeze problem).
[07:09] <LaserJock> bddebian: hence all my fuss over us having and unstable version of goffice
[07:10] <bddebian> LaserJock: gnome.org says latest development branch is: gnumeric-1.3.92
[07:10] <ScottK> I'm guessing I'm 6 months to a year away from Debian...
[07:10] <LaserJock> ScottK: ?
[07:10] <LaserJock> it took me 2 days
[07:10] <ScottK> LaserJock: Are you a DD or did you have a working relationship with one before?
[07:10] <LaserJock> no
[07:11] <LaserJock> neither
[07:11] <LaserJock> uh oh
[07:11] <ScottK> but that's normal for me.
[07:11] <bddebian> ScottK: Well I meant about gnumeric :)
[07:12] <zul> LaserJock has a horshoe up his tuckus
[07:12] <LaserJock> zul: I don't think so
[07:12] <ScottK> LaserJock: Thanks for the info.  Once the Etch freeze gets done, I'll work on it.
[07:12] <LaserJock> seriously though. My package was pretty simple
[07:12] <LaserJock> I had already had the "ajmitch" test
[07:13] <LaserJock> and it was approved for Universe
[07:13] <LaserJock> so I emailed debian-mentors with a RFS and a couple days later I got a reply with "looks fine, uploading"
[07:14] <LaserJock> so I think REVU is really good for getting feedback and getting your package going
[07:14] <ScottK> Cool.  Once I get things settled for Feisty here, I'll do that.
[07:14] <LaserJock> but it's not really that hard to get things into Debian so don't be afraid
[07:14] <LaserJock> ScottK: yeah, right now it could get uploaded and sit in NEW for a long time
[07:14] <bddebian> LaserJock: Do you know where the gnumeric source is coming from?
[07:15] <LaserJock> bddebian: ummm, the gnumeric site has this in the NEWS section: "December 2006: Gnumeric 1.7.6 is out. "
[07:15] <LaserJock> bddebian: I'm not sure what site you are looking at
[07:16] <LaserJock> bddebian: http://www.gnome.org/projects/gnumeric/downloads.shtml
[07:16] <LaserJock> but I really think people shouldn't be so afraid of getting their packages into Debian
[07:16] <bddebian> http://www.gnome.org/projects/gnumeric/download.shtml
[07:17] <LaserJock> bddebian: hehe, that darn "s"
[07:17] <ScottK> LaserJock: Before last month I'd never packaged anything before in my life, so this was, I think, definitely the place to start.  I've learned a lot here.
[07:17] <bddebian> LaserJock: Well that's what google came up with and it's a valid page :)
[07:18] <LaserJock> ScottK: yeah, I think it's definately better for Ubuntu users to start here and then once there packages are "cleaned up" head over to Debian
[07:18] <LaserJock> bddebian: well, Gnumeric's site doesn't link there. odd
[07:19] <ScottK> LaserJock: Speaking of which, I have stuff ready for REVU if you are available/willing? http://spf.pastecode.com/12063
[07:19] <LaserJock> hehe
[07:19] <LaserJock> I probably don't have time today
[07:20] <LaserJock> unfortunately life and work need to come before Ubuntu
[07:20] <bddebian> Since when? :)
[07:20] <LaserJock> as much as I like working with everybody here I'm trying to lower the amount of time I spend working in Ubuntu stuff
[07:21] <LaserJock> bddebian: hmm, since the boss and wife both give me a look like "What have you been doing all day then?" ;-)
[07:23] <bddebian> heh
[07:26] <fernando> hi all
[07:31] <bddebian> Hello fernando
[07:31] <fernando> hey bddebian 
[08:25] <shawarma> bddebian: You mentioned I should add the project homepage url to the control file. The closest thing to a project homepage there is is GNOME's viewsvn.. Should I add that?
[08:25] <bddebian> shawarma: It came from gnome?
[08:26] <shawarma> bddebian: Sure.
[08:27] <shawarma> bddebian: Both of them did.
[08:29] <bddebian> shawarma: From gnome.org?
[08:30] <shawarma> bddebian: Er... svn.gnome.org, yes.
[08:30] <shawarma> bddebian: It says so loud and clear in the copyright file.
[08:31] <shawarma> bddebian: Is that a problem?
[08:33] <ajmitch> morning
[08:34] <bddebian> Heya ajmitch
[08:34] <bddebian> shawarma: No, I'm just looking for a projects page on gnome.org
[08:35] <bddebian> shawarma: Maybe just use the NetworkManager project link?  http://www.gnome.org/projects/NetworkManager/ ?
[08:36] <bddebian> Or just leave it, what the hell do I know? :)
[08:37] <Nafallo> bddebian: not much ;-)
[08:38] <bddebian> Amen Nafallo :)
[08:46] <shawarma> bddebian: I'll leave it out. :-)
[08:47] <shawarma> bddebian: Sorry that I didn't check for lintian errors first. I actually thought linda was more thorough, but she didn't say anything.
[08:58] <Nafallo> shawarma: _totally_ StevenKs fault :-)
[08:59] <ajmitch> always is
[08:59] <Nafallo> :-)
[09:14] <bddebian> heh
[09:15] <ademan_> anyone packaging code::blocks?
[09:16] <Adri2000> ademan: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=304570 http://revu.tauware.de/details.py?upid=2101
[09:16] <Ubugtu> Debian bug 304570 in wnpp "ITP: codeblocks -- Code::Blocks is a free C/C++ IDE built" [Wishlist,Open]  
[09:19] <ademan_> Adri2000: so i should file a sync request?
[09:19] <LaserJock> ademan_: check if it's actually *in* Debian first
[09:19] <Adri2000> it is not
[09:20] <ademan_> oh, i thought that link suggested it was
[09:20] <Adri2000> ITP = Intend To Package
[09:20] <ademan_> well then i think, i have my first package then
[09:21] <LaserJock> ademan_: don't package it if Debian is working on it
[09:21] <ademan_> you think they are?
[09:22] <LaserJock> that's what an ITP is
[09:22] <LaserJock> although sometimes they go stale
[09:25] <Nafallo> LaserJock: baah. Ubuntu was more fun :-P
[09:25] <bddebian> Gah, I have to build all the damn tilp libraries before I could do tilp2 :-(
[09:26] <LaserJock> Nafallo: it's a pain in the butt if we duplicate packages
[09:26] <Nafallo> LaserJock: I was more one of those who filed ITPs that got stale ;-)
[09:27] <Nafallo> LaserJock: Ubuntu had those in the kernel anyway ;-)
[09:27] <LaserJock> :-)
[09:32] <ademan_> LaserJock: it seems to have gone stale
[09:33] <ademan_> last post in the first link
[09:34] <ademan_> huh, but its in revu...
[09:34] <LaserJock> ademan_: then perhaps you sould ask the Debian person if they are still working on it
[09:34] <ademan_> already sent an email :-)
[09:37] <jdong> bddebian: did you see the new x264 patch I posted last night?
[09:38] <jdong> and Nafallo, I'm beginning to understand why you guys don't like touching this media stuff :D
[09:41] <jdong> lol
[09:41] <jdong> don't we ALL love PPC and altivec?
[09:42] <Nafallo> jdong: ;-). I have been at my parents, with sucky connection and gajim to translate. sorry. will look at it as soon as I have time to spare :-).
[09:43] <jdong> Nafallo: bddebian is being my buddy with the stuff :)
[09:43] <jdong> Nafallo: the new PPC altivec optimizations seem to only compile on OSX GCC, so after a bit of frustration last night I reverted those revisions :D
[09:43] <Nafallo> jdong: ah, but he have told you he don't know anything and is a loser, right? ;-)
[09:43] <jdong> Nafallo: all I need is someone with that shiny upload button :D
[09:44] <Nafallo> hehe
[09:44] <jdong> x264 ain't too bad of a beast to deal with
[09:44] <jdong> ffmpeg.... *shudder*
[09:44] <Nafallo> jdong: anyway. what he says is very seldom true :-)
[09:44] <Nafallo> what do we have Universe Freeze?
[09:44] <jdong> Nafallo: yeah, it doesn't built in Feisty anymore
[09:45] <jdong> Nafallo: libcaca api changed :)
[09:45] <Nafallo> wee!
[09:45] <jdong> but the good news is it did compile my x264 patch portion correctly before bombing out on caca
[09:45] <jdong> so I'm in the clear :D
[09:48] <bddebian> jdong: After the one I uploaded?
[09:49] <jdong> bddebian: yeah
[09:49] <bddebian> No havent seen that yet
[09:49] <jdong> bddebian: that one failed too; it got farther but then the altivec was incompatible with linux GCC :)
[09:49] <bddebian> Nice
[09:49] <jdong> bddebian: so I just reverted the two upstream revs that added all this altivec junk :)
[09:49] <jdong> bddebian: the ppc optimizations didn't build in marillat on ppc either :)
[09:50] <bddebian> surprise surprise :)
[09:50] <jdong> but apparently fresh blood (me) has more patience :D
[09:50] <ademan_> wait when's the universe freeze?
[09:51] <ScottK> UVF is Feb 8
[09:51] <LaserJock> ademan_: it's at least the same as the ones for Main
[09:52] <ademan_> ok, so i could squeeze code::blocks in if it hasn't been already?
[09:53] <Nafallo> thanks ScottK 
[09:54] <ScottK> No problem.  There are some questions so easy that even I can answer them.
[09:55] <Nafallo> ScottK: :-)
[09:55] <ScottK> Today was, however, a cool day for me.  When I did apt-get upgrade on my Feisty chroot I got two packages and I did them both...
[09:56] <LaserJock> coolness
[09:56] <LaserJock> ademan_: for code::blocks the more important date is Feature Freeze
[09:57] <ademan_> LaserJock: when might tht be?
[09:58] <LaserJock> ademan_: https://wiki.ubuntu.com/FeistyReleaseSchedule
[09:58] <ademan_> thanks
[09:58] <ademan_> now i gotta go, class is over
[09:59] <ademan_> but i'll figure out code::blocks when i get home
[09:59] <ademan_> hopefully i'll finally get a chance to package something
[10:00] <ademan_> i've got till the 8th, sweet
[10:00] <ademan_> anyways, i'm off
[10:00] <LaserJock> oh weird, I didn't know UVF and FF were on the same day
[10:01] <Nafallo> LaserJock: that's not a coincidence IIRC :-)
[10:06] <LaserJock> nah, I swear it was early March last I looked
[10:06] <ScottK> It would've been funnier if just stuck with knowing.
[10:56] <shawarma> I have a package which is a subversion checkout. configure.in in the file has already been changed to show the next release number (current is 0.6.4, next i 0.7.0). I'd like to name it 0.7.0
[10:56] <shawarma> whoops
[10:57] <shawarma> I have a package which is a subversion checkout. configure.in in the file has already been changed to show the next release number (current is 0.6.4, next i 0.7.0). I'd like to name it 0.7.0~svn1234-0ubuntu1, but lintian says I can't do that. I've looked in the archive and e.g. lighttpd seems to use the same scheme.. How do you guys feel about it?
[10:59] <shawarma> and before you ask (or try yourself) lintian also makes a fuss about it when run on the lighttpd package.
[11:02] <bddebian> lintian will complain about the ~, I think.  I have seen some packages use +svnXXXX but I'm not sure if that is correct either?
[11:02] <shawarma> It's not the same.
[11:02] <bddebian> ?
[11:02] <bddebian> Not the same as what?
[11:03] <shawarma> dpkg --compare-versions 1234~svn123 le 1234+svn123 && echo true
[11:03] <shawarma> No, stupid example.
[11:03] <shawarma> Try this:
[11:03] <shawarma> dpkg --compare-versions 1234~svn123-1 le 1234-1 && echo true
[11:03] <shawarma> and then this:
[11:03] <shawarma> dpkg --compare-versions 1234+svn123-1 le 1234-1 && echo true
[11:04] <shawarma> The first yields true, the other is silent.
[11:04] <bddebian>  So -1+svn-0ubuntu1 ;-P
[11:04] <shawarma> So if the base version is older than the checkout, you use +.
[11:05] <shawarma> but this is the other way around. The base versio (0.7.0) is not released yet, but upstream has chosen to codename it as such.
[11:05] <bddebian> Have you checked Debian Policy?
[11:06] <shawarma> bddebian: It doesn't mention either.
[11:06] <shawarma> bddebian: it's section 5.6.12.
[11:06] <bddebian> gawd I hate libraries
[11:07] <shawarma> sorry, it *does* mention +.
[11:09] <shawarma> But that doesn't really help me. Should I just stick with the old base version?
[11:10] <geser> I guess the policy doesn't mention ~ because it can only be used after the release of etch (iirc)
[11:12] <shawarma> geser: Interesting.
[11:13] <geser> a new feature like ~ can only be used if dpkg from debian stable nows about it
[11:14] <shawarma> Well, it does know about. It can compare it other things.
[11:14] <shawarma> No change is needed in dpkg. It's only policy.
[11:15] <geser> but if the dpkg from debian stable doesn't understand ~ you get problems when upgrading packages with the old dpkg
[11:15] <geser> therefore dpkg in stable must support the feature before you can use in in unstable
[11:15] <geser> due to the long stable cycles in debian this takes a little bit longer
[11:16] <geser> ubuntu with its shorter devel cycles can start to use it sooner
[11:16] <shawarma> It *does* understand it. It treats it just like an alphanumeric character which accomplishes just what I want.
[11:17] <shawarma> So nothing will have to be changed in dpkg for it to be legal.
[11:17] <shawarma> It's only a policy change away.
[11:18] <shawarma> I'm not comfortable using it before it's allowed by policy, though.
[11:19] <geser> yes, the current dpkg understand it but not the dpkg in debian stable
[11:20] <shawarma> What does it do?
[11:22] <geser> I looked up the versions and dpkg in debian stable understands it already
[11:22] <geser> so forget what I said
[11:22] <shawarma> done.
[11:22] <shawarma> :-)
[11:22] <shawarma> I suppose it's still a violation of the policy. 
[11:23] <somerville32> gpocentek, Have you packaged thunar-volman yet?
[11:23] <_Enchained> Hi all
[11:23] <_Enchained> I've a little problem on a package
[11:24] <pochu> _Enchained: which one?
[11:24] <_Enchained> it install 2 "binaries"
[11:24] <_Enchained> and one is a sort of link to the other
[11:24] <bddebian> Anyone ever heard of tfdocgen?
[11:25] <_Enchained> a dpkg -c on the deb file returns :  -rwxr-xr-x root/root     55904 2007-01-19 23:20 ./usr/bin/OOodi AND  hrwxr-xr-x root/root         0 2007-01-19 23:20 ./usr/bin/ooodi link to ./usr/bin/OOodi
[11:25] <_Enchained> so pochu what do you think about it ?
[11:26] <_Enchained> (lintian ask me for a manpage for each binary)
[11:26] <geser> shawarma: not directly, see Debian bug #382612
[11:26] <_Enchained> but one is a link to the other...
[11:26] <pochu> _Enchained: don't know
[11:26] <geser> shawarma: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382612
[11:27] <pochu> i'm newer within packages
[11:27] <_Enchained> bddebian: what do you think about this ?
[11:27] <LaserJock> _Enchained: hmm, you could create one manpage and then maybe link the manpages in the same way
[11:27] <LaserJock> it's nice to be able to do manpage <binary name>
[11:27] <geser> shawarma: see also http://lists.debian.org/debian-devel-announce/2006/08/msg00006.html
[11:27] <_Enchained> ok and what means the "h" on the "chmod"
[11:28] <_Enchained> I know - d and l
[11:28] <_Enchained> but never seen h
[11:28] <_Enchained> (for the "file" type)
[11:29] <geser> _Enchained: have you checked the fs?
[11:30] <_Enchained> fs of what ?
[11:30] <_Enchained> the installed files ?
[11:30] <geser> yes
[11:30] <_Enchained> I don't know.. it seems to be fine
[11:32] <geser> I've never seen h as the first letter (at least I don't remember)
[11:33] <geser> but I've seen on corrupted fs to display garbage as the first letter
[11:33] <_Enchained> :/
[11:34] <jdong> bddebian: at your next convenient time, if you could apply & upload that x264 debdiff I was talking about earlier, that'd be great (https://launchpad.net/ubuntu/+source/x264/+bug/80387/comments/5)
[11:34] <Ubugtu> Malone bug 80387 in x264 "Import 20070116 snapshot" [Undecided,In progress]  
[11:34] <bddebian> jdong: I'll do it when I get home
[11:34] <bddebian> Later gang
[11:34] <jdong> bddebian: ok, enjoy :)
[11:35] <_Enchained> maybe I should upload the package as it is actually and let reviewers see how to fix that ?
[11:48] <_Enchained> I've uplaoded on revu and descripted the problem : http://revu.tauware.de/details.py?upid=4135