[00:00] <cyberix> dget -x http://com/file.dsc
[00:01] <Kmos> crimsun: i'll try it =) thanks for the tip
[00:02] <crimsun> cyberix: you could just backport devscripts from edgy.
[00:02] <cyberix> Already got it done by looking at the script
[00:02] <cyberix> Thanks anyway
[00:03] <StevenK> crimsun: Did you see my upload of libsdl?
[00:05] <crimsun> StevenK: noted, yes.
[00:05] <crimsun> I closed the associated bug yesterday.
[00:06] <StevenK> Great.
[00:06] <crimsun> thanks, BTW!
[00:08] <StevenK> No problem, any time. :-)
[00:09] <imbrandon> ScottK: not sure if the key still needed syncing or not , so i'm running it now to be sure
[00:09] <imbrandon> ( just fyi )
[00:10] <imbrandon> moins crimsun StevenK and all
[00:10] <crimsun> 'lo imbrandon
[00:11] <imbrandon> TheMuso: i got an "broken" xbox -given- to me today , that i fixed by sodering the points and reflashing the TSOP , so soonish ( when i get time after work durring the week ) we'll have a "dev" xbox
[00:11] <imbrandon> :)
[00:13] <bddebian> And for what? :-)
[00:13] <imbrandon> bddebian: the port of ubuntu to the xbox we;re working on :)
[00:13] <StevenK> Hey imbrandon
[00:13] <imbrandon> port , not deriv
[00:13] <imbrandon> :)
[00:14] <bddebian> imbrandon: Again, for what? :-)
[00:14] <imbrandon> bddebian: a $69 USD 733mhx workstation :)
[00:14] <imbrandon> or similar
[00:14] <crimsun> oh, only to take over bddebian's house.  Nothing more.
[00:16] <imbrandon> bddebian: we figured if the ps3 can get a cd rolled ( unsupported of course ) we can roll one for the xbox with only a few ( about 15 ) patches to the kernel and X ( both of witch will eventualy be upstream upstream )
[00:16] <imbrandon> which*
[00:16] <bddebian> :-)
[00:16] <bddebian> crimsun: No xboxen in this house :-)
[00:17] <imbrandon> so really for minial work we can support the xbox, and the only other distro that does this is xebian ( debian deriv ) and its 2.4 kernel based
[00:17] <crimsun> bddebian: no no, it's like X10, but you won't even see/hear it coming
[00:18] <bddebian> crimsun: Ah :)
[00:18] <imbrandon> support == installing and questions awnserd on the forums etc etc etc when possible, you know, not canonical ( other than possible hosting the cd's on cdimage.u.c )
[00:18] <psicus78> hi!
[00:18] <martoss> have fun guys... cu
[00:19] <imbrandon> sides , theres something satisfying about installing linux/ubuntu on a MS product :)
[00:19] <psicus78> Is this the place where to ask to re-sync the REVU uploaders keyring? :)
[00:19] <imbrandon> psicus78: i have one in progress, one moment
[00:20] <imbrandon> ahh infact it JUST finished
[00:21] <psicus78> it's ok
[00:44] <psicus78> .
[00:48] <crimsun> (yes?)
[00:49] <TheMuso> imbrandon: Cool. Did you by chance see my message about apt-mirror?
[00:56] <LaserJock> anybody around who is familiar with SbuildLVMHowto?
[00:57] <soren> Sort of.
[00:57] <soren> As in: I'm sort of around, and I'm sort of familiar with that howto :)
[00:59] <soren> LaserJock: ^^
[01:00] <LaserJock> do you need to have already set up LVM before running the script?
[01:00] <Fujitsu> LaserJock: It's not going to create the LVM partitions for you.
[01:00] <Fujitsu> That would be more than mildly dangerous.
[01:01] <LaserJock> that's what I was thinking
[01:01] <LaserJock> but there wasn't any instructions or links
[01:01] <Fujitsu> So yes, you need to have a VG set up.
[01:01] <LaserJock> but down on the bottom under "Previous Instructions" there was some
[01:02] <Fujitsu> 'It assumes a passing understanding of LVM, and having an available VG to work with.'
[01:02] <LaserJock> oh ...
[01:02] <LaserJock> darn ;-)
[01:03] <imbrandon> TheMuso: nope , i dont think so
[01:03] <imbrandon> was it on irc ?
[01:03] <LaserJock> and do you really need 5GB per chroot?!
[01:03] <Fujitsu> LaserJock: Not really.
[01:04] <Fujitsu> I use 3 normally.
[01:04] <Fujitsu> OOo will want more, but you'd be silly to try to touch OOo.
[01:05] <LaserJock> # Allocate the "golden" chroot LV
[01:05] <LaserJock> sudo lvcreate -n "$CHROOT_LV" -L 5G "$VG"
[01:05] <LaserJock> I think if I run the script it's gonna give me 5GB
[01:05] <Fujitsu> Modify the script, then :)
[01:06] <Fujitsu> Note that there's no point having an initial chroot that's smaller than the snapshots.
[01:07] <TheMuso> imbrandon: Yes.
[01:07] <TheMuso> imbrandon: One sec, I'll see if I can dig it up.
[01:07] <imbrandon> TheMuso: then no , sorry i dident get it
[01:07] <imbrandon> ok
[01:07] <LaserJock> hmm, I just don't know how much space this is all gonna take
[01:07] <LaserJock> I have a 12GB partition
[01:08] <LaserJock> how much do I have to account for?
[01:08] <Fujitsu> Oh dear.
[01:08] <TheMuso> imbrandon: I seem to be having a problem with apt-mirror. The error I get is: http://www.pastebin.ca/841988  My mirror.list file is: http://www.pastebin.ca/841990
[01:08] <Fujitsu> Where did you get a 12GB disk?
[01:08]  * imbrandon looks
[01:08] <LaserJock> Fujitsu: no, 12GB partition for sbuild/LVM
[01:08] <Fujitsu> Ah, so your system isn't on LVM?
[01:08] <LaserJock> heck no
[01:09] <LaserJock> I dislike LVM
[01:09] <Fujitsu> Why not?
[01:09] <Fujitsu> Why?
[01:09] <LaserJock> it eats things
[01:09] <Fujitsu> Never done so for me.
[01:09] <LaserJock> or rather my ability to control it causes me great pain ;-)
[01:09] <LaserJock> *inability
[01:09] <LaserJock> I just kept losing partitions and things
[01:09] <Fujitsu> Heh.
[01:10] <LaserJock> I fell much better in general with have a nice big ext3 /
[01:10]  * TheMuso doesn't think he'll touch luks encryption for a while at least, after having his laptop battery die, and the whole root filesystem going caboom.
[01:10] <imbrandon> TheMuso: it seems to ( rightfully , i cant seem to get it manualy either )  getting a 404 on http://mirror.internode.on.net/pub2/ubuntu/ubuntu//dists/gutsy/multiverse/source/Sources.gz
[01:11] <Vorian> i am getting a 404 error too
[01:11] <Fujitsu> TheMuso: I have been running LVM on LUKS on my laptop for several months now.
[01:11] <TheMuso> imbrandon: change pub2 to pub
[01:11] <Fujitsu> (and yes, the battery has died a couple of times, without ill effect)
[01:11] <TheMuso> pub2 is for internode customers only
[01:11] <TheMuso> so /pub/ubuntu/ubuntu works
[01:11] <TheMuso> s/works/should work/
[01:11] <imbrandon> right that works
[01:12] <TheMuso> imbrandon: Note that this is apt-mirror from svn
[01:12] <TheMuso> Well I tried my config file with s/pub2/pub/ and got the same result.
[01:13] <LaserJock> Fujitsu: my pbuilders (5 different ones) only take up 400MB, are you telling me that'd take up 25GB with sbuild/LVM?
[01:14] <TheMuso> Fujitsu: Hrm interesting.
[01:14] <Fujitsu> I'm sure there must be a way to avoid that, but I haven't found it yet.
[01:14] <TheMuso> Funny how one experience like mine burns you.
[01:14] <Fujitsu> TheMuso: I had to hard-reset it a couple of times a day for weeks too, while X was being dodgy in early Hardy.
[01:14] <TheMuso> Fujitsu: Right.
[01:15] <TheMuso> Good afternoon Hobbsee.
[01:15] <imbrandon> right, svn should be stableized ( just not tarred, 1.4.6 is whats current svn )
[01:15] <imbrandon> hum, try to change your mirror.list to s/pub2/pub/ and see if it works
[01:15] <imbrandon> ( not a full run, once it gets past the preceed indexes is fine to tell if its gonna work )
[01:15] <imbrandon> something strange might be going on with http headers or something, but it just uses normal wget
[01:15] <imbrandon> do you use a http proxy or anything ?
[01:15] <Fujitsu> O_o
[01:15] <Fujitsu> imbrandon can type quickly.
[01:15] <imbrandon> also it would be nice for internode to redirect non internode customers to pub/ :)
[01:15]  * Hobbsee waves
[01:16] <TheMuso> imbrandon: not afaik. If so, its transparent, but I doubt it since I'm within internode's network.
[01:16] <imbrandon> heya Hobbsee
[01:16] <imbrandon> hrm
[01:16] <Fujitsu> LaserJock: Ideally, one should be able to create a snapshot of an LVM volume, and grow the snapshot of the volume. But I don't think LVM can do that at the moment.
[01:16] <imbrandon> Fujitsu: ??
[01:16] <imbrandon> heh
[01:16] <TheMuso> imbrandon: I'm running it again now.
[01:17] <imbrandon> TheMuso: ok
[01:17] <Fujitsu> imbrandon: 5 of your messages appeared at the same time.
[01:17] <imbrandon> if it fails again, try to just normaly run wget
[01:17]  * Fujitsu heads to lunch.
[01:17] <imbrandon> Fujitsu: ahh , i must have lagged
[01:17] <LaserJock> Fujitsu: so what's the advantage of sbuild/lvm again .... :-)
[01:18] <imbrandon> TheMuso: if it fails again , try to just run wget on the file it fails on , to soo if its a possible problem with wget and that mirror
[01:18] <imbrandon> s/soo/see
[01:18] <TheMuso> imbrandon: Yeah will do.
[01:18] <Vorian> i am getting this error http://paste.ubuntu-nl.org/51031/
[01:19] <imbrandon> on your box, or a chroot, or pbuilder
[01:20] <Vorian> pbuilder
[01:20] <Vorian> sorry
[01:20] <imbrandon> run "sudo pbuilder update" ( where pbuilder == how you normaly call pbuilder , e.g. pbuilder-dist hardy or pbuilder-hardy or pbuilder
[01:20] <imbrandon> )
[01:21] <Vorian> alrighty
[01:21] <Vorian> :)
[01:22] <imbrandon> :)
[01:23] <Vorian> imbrandon: that did the trick :)
[01:23] <Vorian> how often should pbuilder be updated?
[01:24] <LaserJock> I do it once a day that I'm working
[01:24] <TheMuso> Yeah once a day is good. I update my sbuild chroots once a day.
[01:24] <imbrandon> Vorian: i do it once a day or so, but it really depends on how new the packages in the archive you need are, its the equiv of running "apt-get update" localy
[01:24] <Vorian> that makes sense
[01:34] <TheMuso> c
[01:34] <TheMuso> ugh
[01:34]  * TheMuso thinsk this keyboard needs replacing
[01:35] <LaserJock> well, I guess since I wiped out my 12GB partition I should at least give this sbuild thing a go
[01:35] <cyberix> What does "Depends: ${shlibs:Depends}" actually do?
[01:36] <nenolod> cyberix, replaces Depends: with all of the depends it detects during dh_makeshlibs
[01:36] <LaserJock> replaces ${shlibs:Depends} specifically
[01:37] <nenolod> there's also ${misc:Depends} which you should add, but it's not yet used
[01:39] <TheMuso> imbrandon: One problem with apt-mirror is that it fails if a file can't be retrieved, however the way my mirror.list file is set up, its asking apt-mirror to check for paths that may not be there now, but could be there when packages get updated in the future. Any ideas?
[01:39] <TheMuso> SO for example, gutsy-updates/multiverse/debian-installer may not exist now, but if a package that places content in that dir gets updated in gutsy-updates, that path will exist.
[01:39] <LaserJock> nenolod: it is used
[01:40] <LaserJock> nenolod: misc:Depends is used by debhelper to insert and additional dependencies that come from the dh_*
[01:40] <TheMuso> So far, I'm thinking of going back to debmirror.
[01:42] <cyberix> LaserJock: So which one should I prefer?
[01:42] <LaserJock> cyberix: prefer?
[01:43] <cyberix> ${misc:Depends} is ok for dh_makeshlibs too as it falls into dh_*
[01:43] <cyberix> So should I always use ${misc:Depends} then?
[01:43] <LaserJock> no, no
[01:43] <cyberix> instead of ${shlibs:Depends}.
[01:43] <LaserJock> they are different things
[01:43] <cyberix> ok
[01:44] <LaserJock> let me try to find an example
[01:45] <nenolod> LaserJock, it is now? well, that's good.
[01:45] <LaserJock> nenolod: has been as long as I've been around I think
[01:46] <nenolod> LaserJock, dpkg-buildpackage was warning about it being an unrecognised subst a few months ago
[01:46] <LaserJock> yes, that is correct
[01:47] <nenolod> which lead me to believe it wasn't used yet ;)
[01:47] <LaserJock> it's used for debhelper, not dpkg
[01:48] <LaserJock> I think dh_gconf may be an example for misc:Depends
[01:48] <cyberix> Oh. It is used only by some dh_*
[01:48] <LaserJock> basically, some dh_* scripts need additional dependencies
[01:49] <LaserJock> I think there are some more
[01:49] <StevenK> ${shlibs:Depends} is for shared library dependancies, ${misc:Depends} is used for example, by debconf
[01:49] <StevenK> dh_installdebconf will put debconf into ${misc:Depends}
[01:49] <StevenK> dh_installdefoma same sort of thing
[01:51] <imbrandon> is there an easy way in bash to make all files in a dir have a lowercase ext
[01:51] <imbrandon> like mass rename .TXT to .txt
[01:51] <imbrandon> s/rename/mv
[01:51] <StevenK> imbrandon: Install renameutils
[01:51] <imbrandon> k
[01:52] <StevenK> imbrandon: Run 'qmv -f do' which drops you into vi with a filename on each line
[01:52] <StevenK> Other than that:
[01:52] <imbrandon> killer, thanks
[01:53] <StevenK> for i in * ; do j=$(echo $i | tr 'A-Z' 'a-z') ; mv "$i" "$j" ; done
[01:54] <Fujitsu>  /win 48
[01:54] <Fujitsu> Bah.
[01:54] <imbrandon> cool, thanks StevenK
[01:55] <imbrandon> btw it must use the default editor , because it was s/vi{,m}/nano
[01:55] <imbrandon> :)
[01:55] <StevenK> It probably calls sensible-editor
[01:55] <StevenK> Actually, nano shouldn't be in that list. :-P
[01:55]  * Fujitsu agrees with StevenK
[01:56] <imbrandon> hahah
[01:56]  * StevenK high fives Fujitsu
[01:56] <imbrandon> that for loop will do the whole filename wont it ?
[01:56] <StevenK> It ought to
[01:57] <minghua> How is nano not sensible?
[01:57] <StevenK> If it doesn't, use qmv
[01:57] <StevenK> minghua: In many ways
[01:58] <Hobbsee> no delete line
[01:58] <imbrandon> ^K
[01:58] <minghua> StevenK: Okay, I'm not arguing.  But the best hacker I know in real life uses nano.
[02:03] <cyberix> I'm looking after first advocate for my package malbolge. I've fixed all problems that have been brought up. http://revu.tauware.de/details.py?package=malbolge
[02:25] <Chipzz> minghua: it's just seriously underpowered/underfeatured
[02:27] <justin_> is this the development team channel?
[02:30] <pwnguin> for Universe
[02:30] <LaserJock> hmm, sbuild wants to install exim4 :/
[02:32] <RAOF> LaserJock: You don't already have a mta?
[02:40] <LaserJock> RAOF: no
[02:40] <LaserJock> I don't like having mta's if I don't need them
[02:40] <RAOF> Well, sbuild will want to email you the buildlogs.
[02:41] <LaserJock> but I don't want it to :-)
[02:41] <lifeless> you don't need an mta
[02:41] <lifeless> you can just have local delivery
[02:41] <LaserJock> seems odd that it'd be a dep and not a Recommends
[03:00] <LaserJock> hmm, is there an easy way to see what provides m-t-a?
[03:06] <blueyed> LaserJock: aptitude search "~Pm-t-a"
[03:07] <LaserJock> I just found synaptic has it :-)
[03:07]  * RAOF wanders through the monodevelop 0.18 dependency stack
[03:11] <jdong> hola everyone
[03:11] <jdong> I'm alive... I think :)
[03:12] <jdong> upgrading my macbook to Hardy at the moment for kicks
[03:12] <TheMuso> jdong: Heh have fun watching everything break.
[03:12] <LaserJock> oh my ;-)
[03:12] <TheMuso> :)
[03:12] <jdong> TheMuso: ooh what's scheduled to break?
[03:12] <jdong> other than the stuff I have scheduled ready to break :D
[03:12] <TheMuso> jdong: I don't know.
[03:13]  * jdong tries to play a quicktime mp4
[03:13] <jdong> look at that, it still works
[03:13] <jdong> well... can't have that happening!
[03:13] <RAOF> jdong: Thanks for reminding me.  Wavpack playback has broken; I need to file that bug :)
[03:13] <jdong> lol
[03:13] <jdong> are we under any freezes yet or soon?
[03:14] <RAOF> Alpha 3 freeze is either now or soon.
[03:15]  * jdong takes a look at that libmp4v2 stuff that he left off on...
[03:26] <jdong> grumble I hate circular dependencies
[03:26] <bddebian> aye...
[03:26] <bddebian> fuuuuuuuuuuck
[03:27] <jdong> would anyone cry if at this point I upload a new faac that may break AAC encoding in mencoder, avidemux, and/or gst-plugins-bad-multiverse till I upload rebuilds of those? :)
[03:27]  * bddebian wouldn't
[03:27] <jdong> nobody likes aac anyway right ;-)
[03:28] <bddebian> I have been working on building newpki-client with wx2.6 for over a week now and there's all kinds of shit in my diff... :'-(
[03:28] <RAOF> If you can get that all done by the alpha 3 freeze tomorrow... :)
[03:29] <jdong> lol well I'll wait for alpha3 to finish then, meanwhile I'll just re-test this build order locally... again.
[03:30] <jdong> I'm not sure I trust these tomboy notes dated on the 17th of december
[03:33] <minghua> I though universe/multiverse wouldn't be affected by alpha freezes?
[03:33] <minghua> thought*
[03:34] <RAOF> Oh, yeah.  We had this discussion before, didn't we.
[03:35]  * TheMuso won't be using hardy full-time till around the last alpha/beta.
[03:35] <TheMuso> Universe/multiverse will be free rain as usual.
[03:37] <somerville32> Does anybody know if bazaar has already been proposed for backport?
[03:39] <bddebian> persia: You about?
[03:40] <ScottK2> somerville32: Look for a bug in gutsy-backports
[03:41] <bddebian> Anyone have a clue how I get rid of cruft from a diff that I don't even know how it got there?  In almost every file I touched I'm getting the complete copyright statement re-generated
[03:46] <Fujitsu> bddebian: You look for the script that is regenerating it.
[03:47] <bddebian> Hmm, I think it's because the files were in MS-DOS format so had extra CR on them :_(
[03:51] <Mattva01> why do I get this error from soyuz ? i don't quite understand it :dpkg-genchanges: failure: cannot read files list file: No such file or directory
[03:51] <jdong> GRR fscking....
[03:52] <somerville32> bddebian, You can user filterdiff
[03:53] <jdong> yay lovely, that's why... libmp4v2 is removed from the archive
[03:53] <somerville32> bddebian, or if the cruft is isolated, you can just remove it from the patch manually
[03:53] <ion_> Could i get a second advocation for http://revu.tauware.de/details.py?package=hardware-connected (a program that checks whether given hardware is connected to the system, nice for scripting)? Thanks
[03:55] <jdong> LucidFox: hey sup?
[04:00] <jdong> oooooh shiny new x264!
[04:00] <jdong> must upload crack!
[04:01] <bddebian> somerville32: Unfortunately I don't know what showed up :-(
[04:01] <bddebian> Isn't there some utility to strip carraige returns from files?
[04:01] <somerville32> bddebian, Can you pastebin your diff?
[04:02] <bddebian> It would be HUGE :-)
[04:05] <cyberix> Help to increase the amount of public domain in Ubuntu. Review my package malbolge, now! Right here on R-E-V-U. http://revu.tauware.de/details.py?package=malbolge
[04:06] <cyberix> Enough syrup in my speech?
[04:07] <Fujitsu> Public domain isn't always good.
[04:07] <bddebian> Aha, dos2unix saves the day!!
[04:07] <LucidFox> jdong> I was wondering about mpeg4ip
[04:07] <jdong> LucidFox: uploaded 7 seconds ago
[04:08] <LucidFox> Ooh.
[04:08] <LucidFox> Awesome.
[04:08] <jdong> :)
[04:09] <jdong> now I'm wrangling faac then going to queue rebuilds of the libmp4v2-0 dep chain
[04:10] <cyberix> Fujitsu: The software  or  the "license" (or lack of it)
[04:14] <LucidFox> cyberix> I think it's better to add a disclaimer for legislatures with no concept of public domain
[04:14] <LucidFox> like Wikipedia does
[04:15] <LucidFox> "
[04:15] <LucidFox> I, the copyright holder of this work, hereby release it into the public domain. This applies worldwide.
[04:15] <LucidFox> In case this is not legally possible,
[04:15] <LucidFox> I grant any entity the right to use this work for any purpose, without any conditions, unless such conditions are required by law.
[04:15] <LucidFox> "
[04:16] <cyberix> But I'm not the copyright holder of all the stuff in the package.
[04:16] <LucidFox> Ah. Sorry then.
[04:20] <cyberix> And using multiple licenses would be far too complicated.
[04:21] <cyberix> Of course I might have the right to "relicense" it because it is public domain.
[04:21] <cyberix> But then again I'd ask a US citizen to do that.
[04:21] <cyberix> And then again the spirit is what matter most.
[04:22] <LucidFox> cyberix> You don't need to.
[04:22] <cyberix> I'm way too technical to work with these concepts anyway.
[04:22] <LucidFox> And now we'll have to wait until mpeg4ip passes NEW... *sigh*
[04:24] <jdong> LucidFox: yep :)
[04:24] <jdong> LucidFox: then I got another mpeg4ip I need to upload after the first one and faac build.
[04:25] <jdong> LucidFox: had a circular uninstallable chain, the mpeg4ip I uploaded is crippled faac-less, which frankly I don't think all but 3 people on the planet care.
[04:25] <jdong> lol but oh well I keep everyone happy ;-)
[04:25]  * cyberix found speed-game (currently in revu) to be lots of fun.
[04:27] <LucidFox> On the plus side, it will finally be possible to get rid of gtkpod-aac patches.
[04:28] <jdong> LucidFox: yep, that's what I'm currently removing :)
[04:29] <LucidFox> In 0.99.12, I hope? ;)
[04:29] <jdong> LucidFox: did debian release the new one?
[04:29] <jdong> ep I see it
[04:30] <jdong> grumble well merge time :)
[04:30] <jdong> LucidFox: you wanna do it? :D
[04:30] <jdong> I feel like catching up on some sleep tonight ;-)
[04:31] <LucidFox> Well, I have already uploaded an interdiff for 0.99.12, so I might as well remove the patches
[04:33] <jdong> LucidFox: ah, awesome, looks like you've got that under control then
[04:33] <Vorian> jdong!
[04:33] <jdong> looks like just exfalso needs rebuilding then
[04:33] <jdong> Vorian!
[04:33] <Vorian> welcome back
[04:34] <jdong> thanks, doing laundry tonight and got bored
[04:34] <jdong> otherwise I was ENJOYING my VACATION....
[04:34]  * Fujitsu sends jdong away again.
[04:34] <bddebian> heh
[04:35] <jdong> ok, looks like I've hit a dead end for the night, time to wait for FTBFS-mail :D
[04:35] <jdong> oh wait libx264 is asking to be broken
[04:54] <jdong> ok, x264 is all happy now
[04:54] <jdong> snoozing time
[04:56] <Fujitsu> Night jdong.
[04:57] <jdong> night Fujitsu
[05:12] <LaserJock> I don't suppose I could interest anybody in some grub recovery help?
[05:12] <LaserJock> I'm trying to reinstall grub by chrooting off the LiveCD
[05:12] <LaserJock> but grub-install is not working
[05:12] <Fujitsu> What is the problem?
[05:12] <Fujitsu> !doesn't work
[05:12] <ubotu> Doesn't work is a strong statement. Does it sit on the couch all day? Does it want more money? Is it on IRC all the time? Please be specific! Examples of what doesn't work tend to help too.
[05:13] <Fujitsu> I love that factoid.
[05:13]  * StevenK too
[05:13] <LaserJock> root@ubuntu:/# grub-install /dev/sda
[05:13] <LaserJock> Could not find device for /boot: Not found or not a block device.
[05:13] <bddebian> hehe, that's funny
[05:13] <Fujitsu> Have you bind-mounted /proc, /dev inside the chroot?
[05:13] <LaserJock> Fujitsu: yep
[05:14] <LaserJock> I can go to /boot and I see it in /dev
[05:14] <StevenK> What about /sys?
[05:14] <LaserJock> I didn't bindmount /sys
[05:14] <Fujitsu> I haven't historically needed /sys, I don't think, but you never know.
[05:14] <LaserJock> I've never had to do that  before
[05:14] <StevenK> I'm not quite sure how grub-install enumerates devices
[05:14] <Fujitsu> Neither.
[05:15] <LaserJock> no go
[05:15] <LaserJock> can I tell it manually?
[05:15] <StevenK> strace it?
[05:15] <Fujitsu> Hmmm.
[05:15] <Fujitsu> You might need to ask it to regenerate its maps.
[05:16] <Fujitsu> Have you moved drives/partitions around?
[05:16] <LaserJock> just tried that
[05:16] <LaserJock> Fujitsu: nope
[05:16] <StevenK> Remove /boot/grub/device.map ?
[05:16] <StevenK> I think that's what it's called.
[05:17] <LaserJock> nada
[05:17] <LaserJock> grr, my wife needs some files :/
[05:18] <LaserJock> stupid sbuild
[05:18] <Fujitsu> sbuild doesn't eat boot records.
[05:18] <Fujitsu> Neither does mk-sbuild-lv.
[05:18] <StevenK> Carbon unit problem?
[05:23] <LaserJock> Fujitsu: no, but the partition I wiped to do it had my previous grub install
[05:23] <LaserJock> ok, so in grub running find /boot/grub/stage1 says it can't find the file
[05:26] <LaserJock> man, I'd really hate to have to re-install this laptop :(
[05:28] <Fujitsu> Er, why would you consider reinstalling?
[05:28] <Fujitsu> Does /boot contain the appropriate GRUB files?
[05:28] <LaserJock> yep
[05:29] <LaserJock> Fujitsu: well, I can't boot
[05:29] <LaserJock> I'm getting off what I need for now via LiveCD
[05:29] <Fujitsu> What was on the partition? Just the boot sector?
[05:30] <LaserJock> I have a separate partition for /boot
[05:31] <Fujitsu> You copied all the stuff from there to /boot on your root partition before obliterating it?
[05:31] <LaserJock> no, I didn't obliterate /boot
[05:32] <LaserJock> I had an openSUSE install on another partition
[05:32] <LaserJock> and of course it installed it's grub
[05:32] <LaserJock> so today I wiped that out
[05:32] <LaserJock> I think I may have just gotten it
[05:32] <LaserJock> I started up grub itself
[05:32] <LaserJock> and ran:
[05:32] <LaserJock> root (hd0,2)
[05:32] <LaserJock> setup (hd0)
[05:33] <LaserJock> and it said it worked
[05:33] <Fujitsu> Aha, good.
[05:33] <LaserJock> ok, rebooting
[05:33]  * Fujitsu shakes his head in dismay.
[05:34] <Fujitsu> One probably shouldn't consider reinstalling because the bootloader is broken.
[05:34] <ant1> man-di: hello, how's the icedtea package ?
[05:44] <ant1> man-di: I got bad news, I just installed icedtea-java7-jre on my system, when I attemped to run JOSM, it crashed
[05:47] <ant1> Hello, I was building one of my packages under hardy amd64 using pbuilder, and I got this: http://pastebin.com/m461bd24
[05:51] <jscinoz> hey persia
[05:52] <jscinoz> you mentioned on my package that "15) uscan --report-status reports no matching files, which is often an indication that the watch file doesn’t work properly." i just ran it again, it returns up-to date for me... can you try it again?
[05:56] <jscinoz> where can i find the information on the policy change in debian/menu in hardy?
[05:59] <LucidFox> jscinoz> sudo apt-get install menu
[05:59] <LucidFox> :)
[05:59] <LucidFox> the Hardy version, of course
[05:59] <jscinoz> how would i get the hardy version rather than the gutsy version (im assuming it'll ge the one for the dist im currently on)
[06:00] <LucidFox> Well, you can download the source package
[06:00] <LucidFox> https://launchpad.net/ubuntu/+source/menu/2.1.36
[06:02] <jscinoz> thanks
[06:03] <ant1> Hello, I was building one of my packages under hardy amd64 using pbuilder, and I got this: http://pastebin.com/m461bd24 , can anyone help on this ? I'm pretty sure that there's nothing wrong with the package because Debian has an amd64 binary for it
[06:03] <mattva01> sorry about all the Soyuz questions,but is there a way to find the build log of your project if it never shows up (it publishes, but never comes up with a deb package )
[06:04] <ant1> actually Ubuntu too has and amd64 binary for it
[06:04] <ant1> http://packages.ubuntu.com/hardy/misc/acon
[06:05] <Fujitsu> mattva01: Ho long ago was it uploaded?
[06:05] <Fujitsu> *How
[06:05] <StevenK> ant1: https://edge.launchpad.net/ubuntu/+source/acon/1.0.5-4
[06:05] <jscinoz> there we go got what i needed from that, games/arcade is games/action in hardy.
[06:06] <StevenK>     * Published on 2007-10-24
[06:06] <mattva01> about 45 minutes ago , but it shows it as published , but with no build failed or success log
[06:06] <Fujitsu> mattva01: Wait a while. The builds probably won't have been created yet.
[06:07] <ant1> StevenK: so why I can't build it ?
[06:08] <Fujitsu> mattva01: You should be watching https://launchpad.net/people/+me/+archive/+builds?build_state=all
[06:08] <ion_> ant1: You probably should find the package that contains the missing file and investigate why it hasn’t been installed.
[06:12] <jscinoz> hey guys, im creating a package of the game urbanterror which contains non-gpl code but allowed to distribute, i need to make it display a prompt to allow the user to review the license and accept or decline it, i've seen this done in the sun-java packages but i cannot figure out how its done from that source package. how would i accomplish this?
[06:12] <ant1> jscinoz: use debconf
[06:13] <jscinoz> thakns
[06:19] <jscinoz> ant1, the short description line in debian/templates should be limited to 80 characters correct?
[06:19] <mattva01> what does this even mean? dpkg-genchanges: failure: cannot read files list file: No such file or directory
[06:24] <Amaranth> ugh, i hate it when people abuse nominations
[06:24] <Amaranth> we're not even half way though the hardy cycle and people are already nonimating bugs to be fixed in hardy
[06:24] <Amaranth> uh, duh?
[06:26] <ant1> jscinoz: not sure
[06:27] <ant1> jscinoz: dunno about that
[06:28] <jscinoz> hmm
[06:32] <ant1> man-di: hmmm, it didn't work with sun java either, I think it's a problem under AMD64 arch.
[06:38] <jscinoz> argh the documentation on debconf is confusion
[06:38] <jscinoz> confusing*
[06:39] <jscinoz> you wouldnt think it so hard to simply display some text and a true/false prompt, continue installation if true and exit if false.
[06:40] <StevenK> Can someone remember a package that does something different on say amd64?
[06:40]  * StevenK can't remember the magical dpkg-architecture runes in debian/rules
[06:41] <ant1> jscinoz: http://64.233.183.104/search?q=cache:0uKuMO_uzYIJ:www.fifi.org/doc/debconf-doc/tutorial.html+debconf+tutorial+fifi&hl=en&ct=clnk&cd=1&ie=UTF-8
[06:42] <jscinoz> thats the one im looking at
[06:42] <jscinoz> ive got the templates file
[06:42] <jscinoz> cant figure out how im supposed to call it
[06:42] <jscinoz> in debian/config?
[06:43] <ant1> jscinoz: debian/config is for dh_input mostly
[06:43] <ant1> jscinoz: postinst is for dh_get
[06:43] <ant1> db_* sorry
[06:43] <jscinoz> well it has to be shown and the license accepted *before* the package is installed
[06:43] <jscinoz> so i assumed config would be a good place
[06:43] <ant1> jscinoz: the preinst
[06:43] <ant1> jscinoz: then preinst maybe ?
[06:45] <jscinoz> hmm alright..
[06:45] <jscinoz> is there any way to test it works without compiling the package and such?
[06:46] <ant1> dunno
[06:57] <dholbach> good morning
[06:59] <ant1> dholbach: hello
[07:00] <dholbach> hey ant1
[07:00] <dholbach> how are you doing?
[07:01] <TheMuso> Hey dholbach!
[07:01] <ant1> dholbach: I'm fine thanks,  can you review this package: http://revu.tauware.de/details.py?package=ubuntume-themes , one of the themes is based on a theme you worked on (Human theme)
[07:01] <dholbach> heya TheMuso
[07:01] <ant1> dholbach: particularly I'd hope you check the copyright file
[07:02] <dholbach> ant1: not right now - I'm just catching up with myriads of emails - if you'd drop me an email with the link I'd do it later on and not forget it
[07:02] <ant1> k
[07:02] <psicus78> Hi!  Is this the place where to ask to re-sync the REVU uploaders keyring? :)
[07:03] <dholbach> thanks ant1
[07:06] <ant1> np
[07:09] <Fujitsu> psicus78: It is.
[07:11] <psicus78> thanks
[07:12] <Fujitsu> You would like it synced, then?
[07:13] <jscinoz> is this script valid for calling debconf to ask a boolean question and continue package installation if true, and cancel installation if false? http://pastebin.ubuntu-nl.org/51060/
[07:17] <jscinoz> alright...
[07:17] <psicus78> Fujitsu: it looks like already synced, I just tried to get my password and it worked, thanks!
[07:18] <slangasek> jscinoz: no, "exit" doesn't cause the maintainer script to return an error
[07:18] <jscinoz> if i want a debconf script to present a boolean question, and cancel package installation if the result is False, can i do this straight from debian/rules (in the install-indep section)
[07:18] <jscinoz> ugh
[07:18] <jscinoz> this is confusing
[07:19] <ant1> dholbach: can I ask a review for another couple of artwork packages too ?
[07:19] <dholbach> ant1: just add the links to that email
[07:19] <ant1> dholbach: ok, thanks
[07:22] <ant1> how can I use dpkg to search for which package provides the file X ?
[07:23] <StevenK> dpkg -S
[07:24] <ant1> StevenK: aha, the file posix_types_64.h is provided by linux-headers-2.6.24-2-generic, does linux-headers package get installed in pbuilder's base.tgz ?
[07:26] <ant1> hmmm, could that be a bug that posix_types_64.h is provided by linux-headers-2.6.24-2-generic and NOT linux-libc-dev ?
[07:27] <ant1> wierd, it is provided by linux-libc-dev
[07:30] <ant1> ok, I think I found the problem
[07:30] <ant1> posix_types_64.h is in /usr/include/asm
[07:31] <jscinoz> slangasek, what about "exit 2"
[07:35] <jscinoz> slangasek, i've updated my script, would this work: http://pastebin.ubuntu-nl.org/51064/
[07:35] <ant1> can someone confirm this with me, I think there's a problem with asm/posix_types.h that comes with hardy
[07:36] <ant1> in hardy it has #include "posix_types_64.h"
[07:36] <StevenK> Why are you including asm/posix_types.h at all? It's a kernel header.
[07:36] <ant1> in gutsy it was #include <asm-x86_64/posix_types.h>
[07:36] <ant1> StevenK: I am including linux/kd.h
[07:37] <ant1> StevenK: which in turn includes linux/posix_types.ht
[07:37] <ant1> StevenK: which in turn includes linux/posix_types.h
[07:37] <ant1> StevenK: and the last one includes asm/posix_types.h
[07:37] <StevenK> It changed because the kernel in Hardy is 2.6.24, which pulled i386 and x86_64 into one arch.
[07:37] <ant1> StevenK: here's the compile error: http://pastebin.com/m461bd24
[07:38] <ant1> StevenK: yes, but should the new asm/posix_types.h read something like:
[07:38] <ant1> #include <asm/posix_types_64.h> , instead of #include "posix_types_64.h" ?
[07:39] <StevenK> Maybe your source should I changed to include -I/usr/include/asm
[07:40] <ant1> StevenK: I wonder how acon got compiled on Ubuntu's hardy ?
[07:42] <ant1> StevenK: isn't this -I/usr/include/asm a bad workaround ?
[07:44] <StevenK> I'm not sure.
[07:51] <jscinoz> persia are you here?
[08:01] <slangasek> jscinoz: yes, that looks like it should work as you describe
[08:12] <LucidFox> Aren't packages that automatically update debian/control forbidden?
[08:15] <dholbach> LucidFox: no - the pkg-gnome team for example makes use of debian/control.in a lot
[08:15] <dholbach> but they just update the maintainer automatically in there
[08:19] <dholbach> congratulations pochu! :-)
[08:27]  * StevenK twitches, getting used to using quilt
[08:32]  * Fujitsu sews some patches onto StevenK.
[08:33]  * StevenK doesn't need patching
[08:35]  * Fujitsu shrugs, and continues patching.
[08:35] <huats> moring dear MOTUs
[08:35] <Fujitsu> Hi huats.
[08:36] <huats> Hi Fujitsu
[08:37] <jscinoz> slangasek thanks
[08:38] <jscinoz> where should i call it from?
[08:39] <slangasek> jscinoz: typically you would do that in a package preinst, if it's some kind of license that the user has to agree t
[08:39] <slangasek> o
[08:43] <slytherin> is anyone planning to update classpath packages? Or should I file a sync bug?
[08:47] <jscinoz> slangasek, are preisnt scripts automatically executed if they have the right name? or do they need to be executed from debian/rules?
[08:50] <chazco> Hi... does anyone know how I can set the default application for a mime type without using defaults.list?
[08:52] <amarillion> jscinoz, afaik it just depends on the name of the script
[08:52] <amarillion> you don't need to run them from debian/rules
[08:53] <amarillion> debian/rules is run at package build time, the preinst & postinst etc at package install time
[08:54] <jscinoz_> what is the preinst called by?
[08:54] <jscinoz_> or is it run automatically if it has the right filename?
[08:56] <amarillion> It's run automatically
[08:56] <amarillion> by dpkg
[08:56] <amarillion> It needs to be executable too, of course
[09:04] <chazco> Is it resonable to have echo "application/tmd.textmaker=tm.desktop" >> /usr/share/applications/defaults.list inside the postinst script?
[09:05] <amarillion> won't that lead to a lot of cruft when you upgrade the package?
[09:06] <amarillion> maybe you can grep defaults.list first to see if that line is already present
[09:06] <chazco> The trouble is I cant think of any other way to do it... one of the rm scripts has some sed magic to remove it
[09:08] <chazco> It seems odd since everything else I've needed to do is done with .desktop's and an .xml, which seems like a clean way to do it... then this (KDE appears to use another .desktop so avoids the issue, but i'm after Gnome as well)
[09:09] <amarillion> Yeah, i see. It might work but it seems like there should be a better way
[09:09] <chazco> Thats what I was thinking (i'm new to this so may be missing something)
[09:11] <Ng> I have a comment on my REVU upload that the .desktop doesn't validate in Hardy, something about "Encoding=UTF-8" being wrong - where can I find out what it should be, and if at all possible, validate it myself?
[09:11] <chazco> I've got /usr/share/applications/tm.desktop (a menu entry), /usr/share/icons/... for the icons, /usr/share/mime/packages/tm.xml to define the mime type, /usr/share/mimelnk/applications/tmd.desktop (for KDE file assosiations)... now i'm stuck :D
[09:16] <chazco> Judging by the gnome documentation it seems like defaults.list must be modified though, so cant see any other way to do than in postinst
[09:16] <jussi01> Hi all, could someone point me to a tutorial for making a debdiff?
[09:18] <ChrisGibbs> gday all
[09:21] <chazco> Anyone know the correct way to set a default application for a mimetype in Gnome?
[09:25] <geser> good morning
[09:44] <warp10> persia: may I request the merge for sympa?
[10:35] <persia> warp10: Go ahead.
[10:36] <persia> jussi01: https://wiki.ubuntu.com/MOTU/Contributing
[10:36] <persia> chazco: look into dh_installmime
[10:36] <warp10> persia: Ok. I'll take care of sending that patch to Debian too
[10:36]  * persia thanks those who answered previous questions
[10:36] <persia> warp10: Thanks.
[10:37] <persia> warp10: Wait, isn't that a python 2.4 -> python 2.5 change?  Debian likely doesn't want it.
[10:38] <warp10> persia: mmm... no. It's about verifying /var/run/sympa on startup.
[10:38] <persia> warp10: Ah.  Then Debian likely does want it.  Thanks :)
[10:38] <warp10> :)
[10:42]  * amarillion is learning dpatch
[10:43] <amarillion> Somehow I keep getting unwanted changes in my patches after dpatch-edit-patch
[10:43] <amarillion> and then I have to go through a lot of trouble to get it clean again
[10:43] <jpatrick> amarillion: my personal preference is simple-patchsys
[10:43] <persia> amarillion: Are you running build inside dpatch-edit-patch?
[10:44] <amarillion> persia, yes, how else to test the changes?
[10:44] <persia> jpatrick: No comments, only works for CDBS, and doesn't allow selective enablement of patches (but I agree).
[10:44] <persia> amarillion: Exit dpatch-edit-patch.  Do your testing.  dpatch-edit-patch the patch again, etc.
[10:45] <amarillion> ah right
[11:07] <DaveMorris> if a source release produces 5 shared libraries, which depend on each other quite heavily.  Should I separate them into separate packages or just 1 package
[11:08] <persia> DaveMorris: It's generally advised to separate them early, so you can avoid the pain of separating them later (in case a client only uses some of the features), but there are exceptions in the archive.
[11:08] <geser> DaveMorris: can each be used without the others?
[11:09] <DaveMorris> ok atm I have libs a, b, c, d, e.
[11:09] <DaveMorris> a is useless on it's own.  b depends on a. c/d/e all depend on a,b but are independent of each other
[11:09] <Kmos> dholbach: welcome back =)
[11:10] <dholbach> hi Kmos :)
[11:11] <TheMuso> dholbach: Oh lovely. Seems that LP is somewhat late in changing that wordpress bug you just closed. :p
[11:11] <persia> DaveMorris: In that case, I'd suggest at least splitting into four packages (a,b), c, d, and e.
[11:11] <DaveMorris> and 4 dev packages ?
[11:12] <persia> DaveMorris: Err.  Right.  Eight.  Sorry.
[11:12] <dholbach> TheMuso: was there a LP: #xxxxx in the changelog?
[11:13] <DaveMorris> thanks, whilst I'm here.  My small package http://revu.tauware.de/details.py?package=libserial is looking for a revu.
[11:13] <TheMuso> dholbach: Yes. Soyuz even indicated as such with the launchpad-bugs-fixed field in changes
[11:13] <dholbach> TheMuso: weird
[11:13] <TheMuso> Indeed.
[11:25] <liri> could someone check if daloradius-0.9.5-1 uploaded successfully to revu?
[11:26] <liri> ahh nevermind, I see it now
[11:26] <TheMuso> c
[11:26] <TheMuso> ugh wrong tab
[11:47] <dannioni> Hello, hope you don't mind answering a question. https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/177615 states that a new version of flightgear has been released and that no debian package exists. We are currently at 0.9.10-2ubuntu2 should the new version number be 1.0.0-0ubuntu1 ?
[11:47] <ubotu> Launchpad bug 177615 in flightgear "New upstream version: 1.00" [Wishlist,Confirmed]
[11:48] <dannioni> I'm new to this packaging stuff, as you might have guessed, but keen to learn.
[11:50] <persia> dannioni: 1.0.0-0ubuntu1 would indeed be the correct version for a first upload to hardy.  However debian has 1.0.0-1, so you might do better to test that, and consider either a sync or a 1.0.0-1ubuntu1 for a merge.
[11:51] <imbrandon> dannioni: possibly, more likely 1.00 vs 1.0.0 if the bug title is correct
[11:51] <imbrandon> e.g. 1.00-0ubuntu1
[11:51] <persia> imbrandon: It's 1.0.0-1 in Debian, so we really want 1.0.0-$revision
[11:51] <imbrandon> ahh he said it wasent in debian
[11:52]  * persia is paranoid, and doesn't trust anyone :)
[11:52] <dannioni> rather the bug report in debian said there was no package
[11:52] <imbrandon> dannioni: did you look?
[11:52] <dannioni> no, just at the bug report :P
[11:53] <imbrandon> ahh, well persia is correct on all accounts here, personaly if its 1.00 upstream then imho debian botched the version number, but its not a big deal nor something that should be fixed at this point
[11:53] <imbrandon> base the merge or sync on 1.0.0-1 :)
[11:55] <dannioni> great, thank for the help
[11:59] <persia> dannioni: When testing, please be sure to also look at simgear and fgfs-base, as these packages are all fairly tightly integrated.
[12:00] <persia> Oops. fgfs-atlas too.
[12:07] <asac> RAOF: hey! about miro ... would like to talk about moving miro to xul 1.9 ... just ping me when avail
[12:07] <amarillion> Ah I see. games should be chown root:games with chmod g+s so they can write to /var/games.
[12:07] <amarillion> Is there a way to do that in debian/rules, or do I need a postinst script for that?
[12:09] <persia> amarillion: You need to do it in postinst
[12:09] <amarillion> ok
[12:10] <RAOF> asac: Hi!
[12:11] <RAOF> asac: I've tried the PPA miro, and it seems fine to me.
[12:23] <mruiz> hi all
[12:23] <jpatrick> hi mruiz
[12:24] <RAOF> We don't want to preserve PPA entries in the Ubuntu changelogs, do we.
[12:25] <RAOF> s/./?/
[12:25] <dannioni> persia: will do
[12:25] <dannioni> flightgear depends on them, right?
[12:25] <Hobbsee> RAOF: not unless there's a really good reason to, no
[12:25] <RAOF> Hobbsee: Thanks, just checking.
[12:26] <sladen> Removing information from changelogs seems excessive
[12:26] <RAOF> Is anyone looking into the new monodevelop packages in Debian?
[12:26] <jscinoz__> persia!
[12:26] <sladen> perhaps it can be "zipped up", like a new upstream version pull-in from DEbian
[12:27] <jscinoz> hey guys, ive got a script in debian/preinst am i correct to assume this is automatically called pre-installation?
[12:27] <persia> sladen: We drop ~ppa revisions because as Ubuntu, we consider that all part of the preparation process.  Similarly, Debian drops all Ubuntu changelogs when importing, as a part of the preparation process.
[12:28] <persia> jscinoz: http://women.debian.org/wiki/English/MaintainerScripts has all the secrets of how and when for maintainer scripts.
[12:28]  * RAOF checks out this new link he hasn't read before
[12:30] <chazco> Can anyone point me in the direction of a package which creates a totally new mimetype, registers a default open application for it as well as icons etc and works on KDE and Gnome? I'm not having much luck currently writing my own deb to do this for an app...
[12:36] <chazco> I'll leave KDE users out for now then, at least it works for Gnome
[12:38] <persia> chazco: Does dh_installmime not do it for you?
[12:39] <chazco> I'm doing most of it manually currently...
[12:39] <persia> Oh, and you'll also need the .desktop file for the MIME type, and dh_desktop
[12:39] <jscinoz> thank you persia
[12:39] <chazco> But ive found very little documentation which helps with this
[12:41] <slytherin> Please give me an advice, I filed a bug that fixes FTBFS and attached debdiff. In the meanwhile I also forwarded bug to debian where it was fixed. So do I wait for my debdiff to be accepted in Ubuntu or file a sync request? There are no other significant changes in Debian
[12:41] <Hobbsee> slytherin: sync request.
[12:41] <Hobbsee> slytherin: saves you the effort of merging, and/or requesting the sync then
[12:43] <slytherin> Hobbsee: There were no other changes in Ubuntu. Do I still file sync request?
[12:44] <Hobbsee> slytherin: yes, as the autosync is off (and has been since debian import freeze)
[12:46] <jscinoz> persia, but is debian/preinst automatically called or does it need to be referenced somewhere
[12:46] <persia> jscinoz: dpkg calls the scripts at the times and with the arguments explained on the Debian Women wiki.
[12:48] <persia> DktrKranz: Please mention the package and the issue when mailing the BTS: there is no context in notifications.
[12:48] <Hobbsee> dholbach: ping
[12:49] <DktrKranz> persia, oh. right. It isn't in the subject or in the body. Thanks.
[12:49] <Hobbsee> dholbach: didn't the MC violate point #1 of https://wiki.ubuntu.com/CommunityCouncil/Delegation ?
[12:50]  * nenolod wonders why dholbach pinged somebody who is entirely unrelated to the audacious package on the audacious merge bug and ponders idly if he meant to do it on some other bug instead
[12:51] <Hobbsee> dholbach: and why is that the opposite to the bottom of https://wiki.ubuntu.com/MOTU/Council ?
[12:52] <jscinoz> persia, can i request you try uscan --report-status again for my two packages, i tried it a few minutes ago after seeing your comments, and it works fine for me.
[12:53] <persia> jscinoz: I don't have time to download them before I go to sleep?  I'll give it a shot when I have time again.
[12:54] <chazco> persia - Still cant get KDE to work (testing on a liveCD)... thanks anyway :)
[12:54] <persia> chazco: Where are you installing the .desktop file?
[12:54] <nenolod> also out of curiosity, would packages one maintains in debian which do not require ubuntu changes count as collateral reference should someone choose to join MOTU?
[12:55] <chazco> I've created /usr/share/applications/tm.desktop (which is a menu entry type one) and /usr/share/mimelnk/tmd.desktop which is the mimetype one
[12:55] <nenolod> isn't it mimelink, not mimelnk ?
[12:55] <nenolod> hmm, it is mimelnk
[12:55] <jscinoz> persia, i thought you'd already downloaded it since you've commentedo n the new ones
[12:55] <persia> chazco: Put the MIME .desktop in /usr/share/applications, or dh_desktop won't do the right thing.
[12:55] <nenolod> go figure.
[12:55] <persia> jscinoz: I delete after reviewing: I don't have infinite disk space :)
[12:56] <jscinoz> >_<
[12:56] <chazco> So I should have two .desktops in /usr/share/applications
[12:56] <nenolod> chazco, also, generally speaking, you can combine mime and launcher into a single .desktop
[12:56] <jscinoz> one quick thing... idk if you can answer it with out the package
[12:56] <nenolod> chazco, so probably, you only need one
[12:56] <jscinoz> "11) The manpages say they are GPLv2, but provide a reference to GPLv3. Please either narrow the reference, or change the license." I cant find any references to GPLv3 in either man page.
[12:56] <chazco> hmm, ok... will have a look
[12:57] <dholbach> Hobbsee: that's a proposal
[12:57] <dholbach> Hobbsee: it'll be discussed in the next CC meeting
[12:57] <chazco> How can you combine the two .desktops? One has a type of mimetype and one has application...?
[12:57] <Hobbsee> dholbach: which is?
[12:57]  * persia notes that one needs two .desktop files when there is one icon for the application and a different icon for the files.
[12:57] <dholbach> nenolod: I asked somebody to review the packages
[12:58] <dholbach> Hobbsee: what do you mean?
[12:58] <nenolod> dholbach, oh. ok.
[12:58] <Hobbsee> dholbach: when's the next CC meeting?
[12:58] <dholbach> Hobbsee: I proposed a few meetings times to the members, but didn't get replies yet
[12:58] <chazco> I'm getting the impression this just isnt going to work... it sounds simple but I just cant get it to go
[12:58] <dholbach> Hobbsee: we'll announce the new meeting time asap
[12:58] <nenolod> chazco, what's your .desktop ?
[12:58] <chazco> Which one? Application or mime?
[12:59] <persia> chazco: Please pastebin both of those.
[12:59] <nenolod> chazco, you really should have all of it in one file
[12:59] <chazco> Oki, one moment
[12:59] <chazco> No idea how to merge them though (really new to this)
[12:59] <persia> chazco: Also your debian/package.sharedmimeinfo file
[12:59] <chazco> Ive got what i have so far by looking at other packages
[12:59] <persia> nenolod: Only if there is only one icon.
[12:59] <chazco> persia - I dont have one of those...
[12:59] <persia> chazco: That might be why dh_installmime isn't working :)
[13:00] <nenolod> persia, hmm. afaik desktops can provide more than one mimeicon.
[13:00] <chazco> Would I be better off trying to start the mime type stuff from scratch? (trying to pastebin desktops)
[13:00] <persia> nenolod: Really?  That's different than my understanding, but would be a nice feature.  I hope you are correct.
[13:00] <nenolod> persia, i believe i have seen it before. but i could be mistaken.
[13:01] <zul> ,prmomg
[13:02] <jscinoz> Why is it bad to include the upstream changelog in /usr/share/docs/packagename/
[13:02] <chazco> persia - http://paste.ubuntu-nl.org/51079/
[13:02] <jscinoz> *confused*
[13:03] <DaveMorris> linda gives me an error about no man page for a binary I'm installing into /usr/bin  The binary is GUI only with no paramaters to be passed in, so does it need a man page?
[13:04] <jscinoz> how does one differentiate between hypens and minus in a man page.
[13:04] <imbrandon> DaveMorris: any binary in /usr/bin must have a man page
[13:04] <persia> DaveMorris: Yes it does.  The manpage might only explain what the command does, that it is a GUI app, and that it takes no arguments, but it should be there.
[13:04] <persia> jscinoz: \- vs. \(hy
[13:04] <nenolod> persia, there are several duplicates to our bug, for what it's worth. i'm going to list them now. ;)
[13:04] <jscinoz> hmm
[13:04] <persia> nenolod: Don't list them.  Just mark them dupes.
[13:05] <nenolod> persia, that'll do.
[13:05] <persia> nenolod: Anyway, unless it gets rejected upstream, it will likely be applied later.
[13:06] <jscinoz> persia, so youre saying in every argument listed in the man page i need to change -- to \-\-?
[13:06] <jscinoz> ie change --help to \-\-help
[13:07] <persia> chazco: Small notes: you don't want an absolute path for the executable, shouldn't have an extension for the icon, and Encoding is deprecated (non UTF-8 isn't supported anymore).  Other than that, looks relatively sane.
[13:08] <Ng> persia: aha, that answers one of my questions about the comments you left for my upload :)
[13:08] <chazco> Tried removing the icon extension, didnt help (but thanks)... app is relative for now because it clashes with something else i'm testing, but wont be in the final... didnt know about encoding, thanks :)
[13:08] <persia> Ng: Ah.  I thought you had an answer.  Also try lintian and desktop-file-validate from hardy to check against the latest standards.
[13:08] <guest22> Any MOTUs here willing to review package photoml (http://revu.tauware.de/details.py?package=photoml)? It's already been advocated once (the previous upload, at least), so it should be very close to being acceptable.
[13:08] <chazco> This debian/package.sharedmimeinfo file... i have an xml file in usr/share/mime/packages which looks similar to what ive seen...
[13:09] <persia> chazco: Removing the icon extension won't help, but it means that themes are supported (which is a good thing).  Please do remove it, while also trying to sort your other issue.  Also, consider debian/package.mime, which tends to be helpful.
[13:10] <chazco> I'm totally lost tbh now... it works on Gnome, but KDE doesnt do anythign (the menu entry doesnt show, file assosiations dont work). Its probably something simple since I built it by trial and error.
[13:10] <Ng> persia: you've just answered my next question with desktop-file-validate. thanks :)
[13:11] <persia> chazco: You might ask for someone to comment in #kubuntu-devel (although they may be focused on actually developing kubuntu and not have time to answer).
[13:11] <nenolod> persia, 4 duplicates ;)
[13:11] <chazco> For now i'll probably leave KDE out, its difficult to test without a KDE machine
[13:12] <persia> nenolod: Thanks for helping triage :)
[13:12] <nenolod> persia, well, it also demonstrates to sebastian that there are indeed duplicates
[13:12] <nenolod> the problem is that my bug is the only one which had a clean backtrace...
[13:13] <nenolod> i think it's related to having amd64
[13:15] <persia> nenolod: Maybe it's an SMP thing?
[13:16] <nenolod> maybe
[13:16] <chazco> So... i have a .desktop in /usr/share/applications (menu entry), an xml in /usr/share/mime/packages which defines the glob patten for the mime type, icons in usr/share/icons/gnome/scalable/mimetypes for files which match, and postinst which updates defaults.list and runs the update-* commands... does that sound correct?
[13:16] <nenolod> i finally got my memory issue worked out too
[13:16] <nenolod> turns out the motherboard's firmware is on crack and set up the memory with a ridiculous CAS timing
[13:16] <nenolod> :D
[13:16] <persia> chazco: Sounds right.  Does it work?
[13:17] <chazco> It does for gnome... most of it is reverse-engineered, so im not sure its the correct way to do it
[13:17] <nenolod> persia, that's what i'm thinking
[13:18] <persia> chazco: As long as you don't do anything especially GNOME-specific, if it doesn't work on KDE, and people want it, you'll get a bug, which might help towards a solution (or at least identify a willing tester).
[13:19] <chazco> Ok, hopefully it'll get fixed at some point
[13:19] <chazco> I was unaware of the debhelper stuff... where can I find more info, they could help...
[13:20] <persia> chazco: debhelper is typically exceedingly helpful.  There are manpages which help some, and the source is fairly readable.
[13:21] <chazco> Odd... mime wont show any man pages (tried it already)... will try to reinstall it
[13:22] <nenolod> persia, this is the best backtrace of the bug i've found. it's better than mine. http://launchpadlibrarian.net/11083488/Stacktrace.txt
[13:23] <DaveMorris> just notice that linda and lintian don't complain about a binary going into /usr/bin with a name of fcdActor even though all the other binaries are all lowercase.  Is it something I should change?
[13:23] <liri> persia: I'm not being emailed the recovery password, can you check it out please?
[13:23] <chazco> Just to be totally clear - i can safely remove Encoding=UTF-8 then?
[13:25] <imbrandon> liri: recovery password for what ?
[13:26] <imbrandon> REVU ?
[13:26] <liri> imbrandon: yeah, sorry if I wasn't clear
[13:26] <persia> liri: Have you uploaded anything?
[13:26] <imbrandon> liri: it dosent email it to you, you click recovery and follow the instructions
[13:26] <liri> imbrandon: yeah I uploaded the daloradius package and saw it on the website
[13:26] <liri> imbrandon: ahh, the documentation on the wiki is a bit unclear on that then
[13:26] <persia> nenolod: Is there a threadedstacktrace for that bug?
[13:28] <nenolod> maybe
[13:28] <nenolod> persia, http://launchpadlibrarian.net/11083489/ThreadStacktrace.txt
[13:29] <tuxmaniac> Can somone please verify and ack for the sync request in bug 181007?
[13:29] <ubotu> Launchpad bug 181007 in libitpp "[SYNC] Debian Unstable sync of libitpp 4.0.1-3 requested" [Undecided,New] https://launchpad.net/bugs/181007
[13:29] <persia> Bah.  Only shows one thread.  I was hoping to see the clearing function running ahead of the populate function.
[13:29] <nenolod> persia, that happens
[13:29] <nenolod> persia, because the populate function is asynchronous
[13:30] <persia> tuxmaniac: subscribe the sponsors queue to ask for review
[13:30] <nenolod> persia, so it's possible that the clearing function is already called, but there's another populate in the queue
[13:30] <tuxmaniac> persia, even for sync request from Debian Unstable?
[13:30] <persia> nenolod: Exactly.  That's why I was hoping for two threads in a threadstacktrace that would demonstrate the issue to actually be the one you fixed.
[13:30] <nenolod> but since priv->menu and blah blah blah
[13:30] <persia> tuxmaniac: Yep.  You need approval from a member of ~ubuntu-dev, which is what the sponsors do.
[13:30] <nenolod> gnome makes me want to headdesk repeatedly.
[13:34] <nenolod> persia, the only reason why i succeeded in fixing that bug is because i'm quite familiar with the craqery that is gtk+
[13:35] <nenolod> things like gksudo scare me, knowing just how many bugs just like that in gtk+ haven't been fixed yet
[13:35] <nenolod> :P
[13:37] <liri> persia: could you check that the package was uploaded and signed successfully?
[13:38] <chazco> I'm wondering if it could be a permissions issue now...
[13:50] <chazco> persia - You know I said it would be something simple....
[13:50] <persia> which simple thing was it?
[13:50] <chazco> Log out and back in... which is harder on the live CD :D
[13:51] <chazco> I cant believe it after all that
[13:51] <chazco> I was expecting it to be like Gnome, where it updates without restarting
[13:51] <chazco> Anyway, thanks for your time, it was really appreciated :)
[13:53] <chazco> Think i'm going to have to setup a duel-boot from now one :)
[13:57] <pkern> How do rebuild uploads work?  I upload the package sourceful with adapted build-deps and a XbuildY version number?
[13:58] <persia> pkern: -XbuildY means you only changed the changelog.  If you have to touch control, mangle the maintainer and use -XubuntuY
[14:00] <pkern> persia: Which kills autosync.  Bah.
[14:00] <pkern> persia: So if I do build uploads, the deps already need to be built and published?
[14:00] <persia> pkern: You don't want to autosync if you changed control.  That's why.
[14:01] <pkern> persia: I do want autosync if I changed control. (:
[14:01] <pkern> persia: I know what I'm doing.
[14:02] <persia> pkern: The guidelines assumes you aren't 100% sure, and should check again when hardy+1 opens.  If you're very, very, very certain, and you break the guidelines, such is life.  On the other hand, you ought set an Ubuntu maintainer for an Ubuntu variation.
[14:03] <pkern> persia: It's my package in Debian. \-:
[14:04] <pkern> persia: But ok, thanks.  So XbuildY will not prevent autosyncing?
[14:04] <Whoopie> siretart: hi, the patch from bug report 104332 is missing in the gutsy package. Can I reopen the ticket?
[14:04] <Whoopie> bug 104332
[14:04] <ubotu> Launchpad bug 104332 in rdesktop "rdesktop crashes when logging in to windows 2000 (or pressing cancel)" [High,Fix released] https://launchpad.net/bugs/104332
[14:05] <Kmos> pkern: yes
[14:06] <siretart> Whoopie: is the patch in the hard package?
[14:06] <siretart> Whoopie: re the bug: sure, but please reassign to yourself
[14:08] <Whoopie> siretart: what's a hard package?
[14:08] <man-di> Whoopie: hardy
[14:08] <siretart> hardy, right
[14:09] <Whoopie> siretart: hardy has a CVS version of rdesktop where the bug is fixed.
[14:10] <Whoopie> siretart: we could just backport it. ;)
[14:11]  * persia suggests that propagating VCS snapshots can lead to user confusion and complaints, even when bugs are fixed.  Is a new upstream coming soon?
[14:11] <Whoopie> persia: no idea, sorry
[14:11] <siretart> Whoopie: which would miss everyone not using backports. an upload to -security would be better, and requesting a backport as well for more adventureous users
[14:14] <cyberix> I'm looking after first advocate for my package malbolge. I've fixed all problems that have been brought up. http://revu.tauware.de/details.py?package=malbolge
[14:15] <Whoopie> siretart: I don't know how to add Gutsy to this bug report. It's not "project" nor "distribution/package".
[14:15] <persia> Whoopie: "Nominate..."
[14:20] <Kmos> there is a way to enable pkgbinarymangler in pbuilder ?
[14:21] <RAOF> Kmos: Yes; install it in the pbuilder environment.
[14:21] <Kmos> RAOF: ah ok =) thank you
[14:22] <RAOF> Kmos: So, you'd pbuilder login --save-changes (or whatever that switch is), then apt-get install
[14:22] <geser> and don't forget to enable it
[14:22] <Kmos> exactly
[14:22] <Kmos> geser: how to do it ?
[14:22] <Kmos> it's installed now
[14:23] <Kmos> in /etc
[14:23] <Kmos> found it =)
[14:24] <Whoopie> persia: done, but it's not the same as it's shown for the others (edgy, feisty)
[14:25] <siretart> Whoopie: I accepted your  nomination and assigned that task to you
[14:25] <Kmos> geser: thanks
[14:25] <persia> Whoopie: Moving from Nomination to confirmed needs-fixing for a given release needs confirmation from a developer.
[14:25] <Whoopie> siretart: so what is my task now? ;)
[14:25] <siretart> Whoopie: fix the bug
[14:26] <siretart> e.g. by attaching a debdiff and getting someone to review and upload it for you
[14:26] <Whoopie> siretart: ok
[14:27] <Kmos> grep: debian/control: No such file or directory
[14:27] <Kmos> /usr/bin/pkgstriptranslations: Error: not in source package directory
[14:27] <Kmos> EtienneG: pbuilder-satisfydepends failed.
[14:27] <Kmos> not EtienneG but E:
[14:29] <Whoopie> siretart: what if I want to add the patch to a debian/patches directory? any changes needed for debian/rules. because last time, I think, it got lost because it was applied "inline".
[14:30] <siretart> Whoopie: please fix the package with minimal intrusion. this mean try to keep the debdiff as small as possible
[14:35] <Kmos> geser: pbuilder gives me that error now..
[14:36] <geser> hmm
[14:37] <Kmos> i've it installed and set enable to true
[14:37] <Kmos> pbuilder updated
[14:38] <geser> I've enabled pkgstriptranslations too but pbuilder still works for me
[14:39] <Whoopie> siretart: f*, please remove gutsy, it's applied. sorry for the inconvenience.
[14:39] <Kmos> really strange
[14:39] <siretart> Whoopie: you should be able to do that yourself. please add a meaningful comment for that
[14:41] <DaveMorris> I'm still looking for someone to revu my package - http://revu.tauware.de/details.py?package=libserial  All previous comments have been adressed
[14:52] <chazco> Is glibc (>=2.2.5) a valid depend?
[14:53] <geser> no, as glibc is the source package name
[14:53] <chazco> Ah ok...
[14:54] <chazco> Trying to write a Depends line for the vague requirements of: glibc 2.2.5 or higher, X Window system with any Window Manager
[14:54] <man-di> chazco: forget about that, dh_shlibdeps will generate depends needing newer glibc anyway
[15:05] <\sh> moins
[15:05] <\sh> crimsun: what do I had to read on p.u.c. you are stepping down?
[15:26] <Legendario> hi. is anyone here from both motu and doc teams?
[15:27] <jpatrick> Legendario: I contribute to both, what's up?
[15:27] <Legendario> hi. I would like to translate the packaging guide to portuguese
[15:28] <Legendario> is there a way to do it using launchpad?
[15:32] <jpatrick> Legendario: yes, sorry, I was doing somethin
[15:32] <Legendario> it's ok
[15:32] <Legendario> so. how can i do it?
[15:33] <bluekuja> Legendario, I'm not really sure it's available for translation in LP
[15:33] <jpatrick> Legendario: the packguide is maintained at the wiki
[15:33]  * joejaxx wonders how much work it would be to package kde from scratch
[15:35] <bluekuja> hellboy195, around?
[15:37] <bddebian> Heya gang
[15:37] <joejaxx> bddebian: !
[15:37] <joejaxx> :D
[15:37] <bddebian> Hello joejaxx
[15:37] <joejaxx> anyone know how packaged the kde packages originally?
[15:37] <joejaxx> bddebian: :)
[15:38] <broonie> joejaxx: The bottom of the changelo for kdelibs says Adreas Jellinghaus
[15:38] <joejaxx> oh ok
[15:38] <joejaxx> hmm
[15:40] <geser> Hi bddebian
[15:40] <bddebian> Hi geser
[15:42] <Hattory> Legendario, the translation of the packaging guide was available with dapper: https://translations.launchpad.net/ubuntu/dapper/+source/ubuntu-docs/+pots/packagingguide/pt/+translate
[15:42] <geser> broonie: Hi, have you had time to look at the aqsis build failure? Is it a problem with aqsis or scons? (the problem was that it got caught in a loop)
[15:44] <jpatrick> Hattory: but that's Dapper :p
[15:46] <Hattory> I know... jpatrick..... just to see that it was on Launchpad
[15:47] <Hattory> :)
[15:48] <jpatrick> Hattory: must be so outdated
[15:50] <Legendario> do you guys know if the version listed on the doc.ubuntu.com as work in progress is to different from the dapper one? Hattory, do you have the link for this one?
[15:50] <pochu> dholbach: thanks a lot!
[15:51] <Kmos> pochu: greetingz :)
[15:51] <pochu> Thank you Kmos :)
[16:01] <Hattory> jpatrick, why wasn't it update anymore?
[16:02] <jpatrick> Hattory: it's moved to the wiki
[16:21] <ScottK2> pochu: Congratulations.
[16:22] <mruiz> pochu, great news! congrats ;-)
[16:23] <jdong> pochu: wow congrats, though I thought you were a MOTU for like a year :D
[16:23] <Hattory> pochu,  congrats ;)
[16:33] <pochu> Thanks ScottK2 mruiz jdong and Hattory! :)
[16:39] <tuxmaniac> hi guys. now the package builds on pbuilder hardy base. request someone to please review and comment. http://revu.tauware.de/details.py?package=alliance
[17:21] <ion_> Could i get a second advocation for http://revu.tauware.de/details.py?package=hardware-connected (a program that checks whether given hardware is connected to the system, useful for scripting)? Thanks.
[17:23] <pfein> is there anyway to tell debbuild not to sign a package?  Building a local upgrade, don't have my key on the server...
[17:25] <jdong> pochu: probably by passing in -us -uc
[17:25] <jdong> oops pfein
[17:26] <pfein> jdong: yup, thx
[17:30] <rexbron> If a piece of code is licenced under the lgpl and you compile it with --enable-gpl such that the resulting binaries are gpl, should debian/copyright reference the LGPL, GPL or both?
[17:36] <mdomsch> I'd think both
[17:38] <rexbron> Ok, i'll put in a "source licenced under" and "binaries"
[18:43] <unenough> Hi, I am trying to build the python2.5 package via "debian/rules binary" inside the source, but its running all of the regression tests, and that takes _ages_
[18:43] <unenough> any way to disable the regression tests?
[18:44] <azeem> unenough: export DEB_BUILD_OPTIONS=nocheck
[18:44] <azeem> will still run the benchmarks, though
[18:45] <slangasek> ScottK2: were you following up with the Debian maintainer about bug #154730 as requested by seb128?
[18:45] <ubotu> Launchpad bug 154730 in secvpn "Please remove secvpn source and binary from Hardy" [Wishlist,Incomplete] https://launchpad.net/bugs/154730
[18:46] <unenough> azeem, Thanks!
[18:46] <unenough> azeem, any way to cancel the benchmarks too?
[18:46] <azeem> dunno
[18:47] <azeem> look inside debian/rules, comment it out if it's a seperate command
[18:48] <unenough> K, I'll hope for now that the benchmarks are not as long as the regression tests
[18:51] <ScottK> slangasek: It's on my "list", but I haven't actually done it yet.
[18:52] <slangasek> ScottK: ok
[18:58] <bddebian> slangasek: newpki-client builds now, I think that just leaves ctsim with wx2.4?
[18:59] <slangasek> I dunno, I haven't been following the progress
[19:05] <bddebian> Well you're fired :)
[19:06] <bddebian> I'd work on the vflib stuff if I really understood the issue :(
[19:11] <ScottK> bddebian: When has that ever stopped you before? ;-)
[19:13] <bddebian> ScottK: Never, but thanks for pointing that out :-)
[19:14] <DaveMorris> my cdbs rules file has 1 big target which is independent (doc from doxygen) of the other targets.  Is there anyway to have it run in a separate thread from the rest of cdbs, thus making use of dual core systems?
[19:15] <ScottK> No.
[19:15] <DaveMorris> shame
[19:15] <ScottK> There is work in progress on parallel builds in Debian, but nothing production ready yet.
[19:15] <DaveMorris> would save me around an hr
[19:16] <ScottK> If you look in (I think it was) the debian-devel mail list archives for parallel build, there was a recent thread on the topic.
[19:16] <Kmos> The package libfontbox-java in hardy shouldn't be in multiverse? it needs checkstyle package that's in multiverse
[19:16] <Kmos> ?
[19:17] <man-di> the question is: why is checkstyle in universe when its in main for Debian
[19:17] <man-di> multiverse I mean, sorry
[19:17] <Kmos> :)
[19:18] <man-di> ubuntu names...
[19:19] <Kmos> man-di: that's also a good question
[19:20] <man-di> well, checkstyle was moved from contrib to main some long time ago...
[19:21] <ScottK> And it looks like no one ever touched it in Ubuntu to move after the tarball got repacked
[19:23] <Kmos> I'll fill a bug about this to move it to universe..
[19:24] <slangasek> ScottK: well, one can certainly configure one's own package build rules to support parallel building in line with the d-d discussion, and invoke the package build accordingly on one's own system
[19:25] <slangasek> since he seems to be concerned with saving his own time, not the buildd's :)
[19:25] <ScottK> True.
[19:25] <ScottK> DaveMorris: ^^^
[19:26] <dannioni> I was talking earlier this afternoon of merging our flightgear with debians, should I do this even though we've passed DebianImportFreeze?
[19:26] <ScottK> Are there any changes in Debian's version we don't have that are worth having?
[19:27] <dannioni> I havn't gone through that yet, as I wasn't sure of what to do i wanted to check first
[19:28] <ScottK> Judgement call at this point
[19:29] <ScottK> Go mok0! (Just saw your Debian ITP for Mustang)
[19:30] <dannioni> We're at verion 9.10 and they're at 1.0. I went through the changelogs and there's a lot we're missing
[19:30] <mok0> ScottK: Heh! It's my first try
[19:30] <ScottK> dannioni: I'd go for it then.
[19:31] <mok0> ScottK: ... and part of my MOTU training...
[19:31] <ScottK> Excellent
[19:31] <dannioni> ok, thanks for the advice, needs to be done sooner or later anyways
[19:32] <ScottK> slangasek: I'm curious if you saw my perl-module post on ubuntu-devel and if you have an opinion?
[19:32] <mok0> Started using git-buildpackage today. Pretty nifty, but it has some quirks
[19:33] <emgent> hi astharot ;)
[19:33] <mok0> dpatch has the annoying habit of touching the files in debian/patches, which means git thinks they have been modified...
[19:33] <slangasek> ScottK: yes, seen; I think dropping those modules from perl-modules and making them a dep appears to be the correct course of action, but since this is apparently a MIR I'll leave it to others like pitti to dredge up any concrete objections
[19:33] <ScottK> K.  Thanks.
[19:34] <astharot> re
[19:35] <mok0> Anyone else here has experience with git-buildpackage?
[19:35] <mok0> s/has/have
[19:35] <ion_> mok0: I’m using it.
[19:35] <ScottK> mok0: I know lamont (on ubuntu-devel/server) uses Git.  Dunno if he uses that.
[19:36] <mok0> ion_: How do you handle upstream updates?
[19:36] <jharr> Hello
[19:36] <ScottK> Hello
[19:36] <mok0> ion_: Do you untar it on the upstream branch?
[19:36] <mok0> ion_: or create a new one?
[19:37] <jharr> Say I have samba-3.0.26a, which is having problems, but I want to do a quick build of 3.0.28, what's the quickest way to swap out the old .orig source for the new?
[19:37] <ion_> mok0: If upstream doesn’t use git in the first place, you should be able to use git-import-orig to import the source to a git repo. Then just merge the changes from the upstream branch to the ubuntu branch, update the packaging and use git-buildpackage as usual.
[19:37] <AnAnt> Hello
[19:38] <AnAnt> is Emmit Hikory here ?
[19:38] <AnAnt> bddebian: hide
[19:38] <ScottK> AnAnt: He goes by persia
[19:38] <AnAnt> ah, so he's persia
[19:38] <mok0> ion_: do you have to be sitting on the upstream branch, or will git-import-orig do that for you?
[19:38] <AnAnt> persia: Hello, thanks for reviewing the ubuntume artwork packages
[19:39] <ion_> mok0: Look at its man page.
[19:39] <mok0> ion_: :-)
[19:39] <AnAnt> man-di: Hello, I ran josm using icedtea jre under i386, it didn't work so well
[19:39]  * mok0 feels stupid
[19:39] <ion_> mok0: It has defaults for the upstream and packaging branches, but you can override them with e.g. a .gbp.conf in the packaging branch root.
[19:40] <LaserJock> man I love Ubuntu!
[19:40] <mok0> ion_: might as well stick to the default for now... I have no better scheme anyway
[19:41] <ion_> For instance, http://gitweb.heh.fi/?p=ion/hardware-connected.git;a=blob;f=.gbp.conf;hb=ubuntu
[19:41] <jcastro> LaserJock: glad you think so, consider sticking around and getting involved!!
[19:41] <jcastro> :p
[19:41] <slangasek> jharr: like grabbing the 3.0.28 package for hardy directly from the Ubuntu archive and rebuilding it with dpkg-buildpackage -B?
[19:41] <mok0> ion_: cool
[19:41] <mok0> ion_: I guess you can run pbuilder as well from there
[19:42] <man-di> AnAnt: file a bug report
[19:42] <AnAnt> man-di: ok
[19:42] <LaserJock> jcastro: I just got the uni VPN working with Network Manager
[19:42] <man-di> AnAnt: note that icedtea is a pre-version of what will be Java7
[19:42] <ion_> mok0: Perhaps. I haven’t checked.
[19:43] <AnAnt> man-di: btw, did you tried icedtea firefox plugin on an amd64 ubuntu ?
[19:43] <mok0> ion_: I thought gbp.conf went in .git/
[19:43] <man-di> AnAnt: no
[19:43] <ion_> mok0: Again, look at the man page. You can put it in .git if you don’t want it to go to the repository.
[19:44] <ScottK> AnAnt: man-di is a Debian user, not Ubuntu.
[19:44] <AnAnt> oh
[19:44] <man-di> well, I have Ubuntu chroots for some testing
[19:44] <AnAnt> man-di: so, you made an icedtea package for Debian this week ?
[19:44] <mok0> ion_: ok
[19:44] <man-di> yes, I work in icedtea package (which is the same as for Ubuntu)
[19:45] <cyberix> Should I use debian-maintainer field even when the package does not exist in Debian?
[19:45] <AnAnt> man-di: thanks
[19:45] <mok0> ion_: Are you in Finland?
[19:45] <AnAnt> ok, I have a question, I was asked to close a bug for initial release, is there something like ITP bug in Ubuntu ?
[19:45] <ScottK> cyberix: Yes (generally).
[19:45] <ion_> mok0: Yep.
[19:45] <ScottK> AnAnt: bug tagged 'needs-packaging'
[19:46] <mok0> ion_: Perkele! :-)
[19:46] <AnAnt> ScottK: ok,  I should file the bug against what ?
[19:46] <ScottK> Against Ubuntu
[19:46] <ScottK> i.e. No package
[19:47] <slangasek> mok0: is this how you greet all Finns?
[19:47] <AnAnt> ok
[19:47] <mok0> slangasek: I don't think so :-)
[19:48] <mok0> slangasek: It's a swearword AFAIK
[19:48]  * ScottK starts to wonder what that meant.
[19:48] <slangasek> yes, it is a swear word
[19:48] <cyberix> ScottK: Is this explained somewhere?
[19:48] <mok0> slangasek: not rude I hope
[19:48] <slangasek> so "Are you in Finland?" "yes" "perkele!" is kinda strange
[19:48] <ScottK> cyberix: I'm sure it's in wiki.ubuntu.com somewhere.  Dunno where as stuff was recently re-arranged.
[19:49] <mok0> slangasek: It's the only finnish word I know... apart from yksi kaksi kolme
[19:49] <AnAnt> ScottK: what does X licensed code mean ? it was on a comment on http://revu.tauware.de/details.py?package=usplash-theme-ubuntume
[19:50] <mok0> slangasek: are you finnish too?
[19:51] <ScottK> AnAnt: From what it says, I'd say there's a thing call the "X License" and there's code in your package licensed under it and you didn't mention it in debian/copyright.
[19:51] <ScottK> AnAnt: grep -ir copyright * is your friend.
[19:51] <slangasek> mok0: no, just a polyglot
[19:51] <mok0> slangasek: you speak finnish? I'm impressed!
[19:52] <slangasek> mok0: I only know a few key phrases in Finnish
[19:52] <AnAnt> ah, ok
[19:53] <AnAnt> can any LP user have access to LP's Vcs ?
[19:53] <bddebian> Like "where's the beer?"
[19:53] <slangasek> like "hyvää huomenta" and "vittu perkele"
[19:54] <mok0> slangasek: gonna tell us what that means?
[19:55] <slangasek> nope :)
[19:55] <mok0> Google's my friend
[19:56] <slangasek> indeed
[19:56] <LucidFox> slangasek> Thanks for moving libhiglayout-java and freecol!
[19:57] <LucidFox> You are an archive administrator, I presume?
[19:57] <slangasek> yep
[19:57] <mok0> slangasek: you are bad!
[19:57] <mok0> :-)
[19:57] <slangasek> mok0: I prefer to think of myself as "authentic"
[19:57] <LucidFox> Do you manage NEW? Because I'd like to get mpeg4ip into Hardy ASAP
[19:58] <cyberix> I should not use XSBC-Original-Maintainer?
[19:58] <slangasek> LucidFox: I do, but you'll have to wait your turn :)
[19:58] <LucidFox> ah
[19:58] <ion_> Is the NEW queue visible for the public somewhere, btw?
[19:59] <LucidFox> http://launchpad.net/ubuntu/hardy/+queue
[19:59] <ion_> Thanks
[20:00] <mok0> vittu perkele saatana!
[20:00] <slangasek> not to be confused with the Finno-Latin fusion group, "vittu perkele santana"
[20:01] <ScottK> cyberix: Generally for packages new to Ubuntu and not in Debian, put yourself in that field if you are packaging it.
[20:02] <mok0> slangasek: lol
[20:06] <LaserJock> ScottK: if you have an @ubuntu.com address
[20:11] <AnAnt> ScottK: so for packages that are not in Debian, I put myself in both Maintainer: & XSBC-Original-Maintainer: fields ?
[20:16] <LaserJock> AnAnt: no, you wouldn't need XSBC-Original-Mantainer if you're setting yourself as Maintainer
[20:17] <AnAnt> LaserJock: ok, what does that comment mean "Please use an Ubuntu maintainer. If nobody on the team is an Ubuntu member, consider applying for a mailing list for the team" on http://revu.tauware.de/details.py?package=usplash-theme-ubuntume ?
[20:18] <LaserJock> well
[20:19] <LaserJock> Maintainer requires either an @ubuntu.com address *or* an Ubuntu mailing list (ubuntu-motu for Universe)
[20:21] <slangasek> which is to say, everything should have a *@*ubuntu.com email address as the Maintainer
[20:21] <AnAnt> ok, so what should I do ?
[20:22] <LaserJock> AnAnt: do you have an @ubuntu.com email address?
[20:22] <AnAnt> put myself in Maintainer: and ubuntu-motu list in XSBC .... ?
[20:22] <AnAnt> LaserJock: nope
[20:22] <LaserJock> reverse it then
[20:22] <pochu> AnAnt: the other way round
[20:22] <LaserJock> ubuntu-motu as Maintainer and yourself as XSBC....
[20:22] <AnAnt> pochu: ok
[20:22] <pochu> AnAnt: have you considered uploading this to Debian too?
[20:23] <AnAnt> pochu: it's Ubuntu specific I think, it's artwork for a distro based on ubuntu, why put that in Debian ?
[20:24] <pochu> heh, nevermind then :-)
[20:24] <AnAnt> ok
[20:24] <AnAnt> thanks for the help guys
[20:26] <AnAnt> what's the name part of Maintainer: ?
[20:26] <AnAnt> I mean what's the name part of ubuntu-motu mailing list ?
[20:26] <jpatrick> Ubuntu MOTU Developers
[20:27] <LaserJock> https://wiki.ubuntu.com/DebianMaintainerField says Ubuntu MOTU Developers <ubuntu-motu@lists.ubuntu.com> for the field
[20:27] <AnAnt> thanks
[20:28] <AnAnt> what's FTBFS stands for ?
[20:28] <jpatrick> Fails to build from Source
[20:29] <AnAnt> ok
[20:30] <AnAnt> ok, one last thing (I hope), I'm doing a usplash theme
[20:30] <mok0> AnAnt: https://wiki.ubuntu.com/UbuntuDevelopment/Abbreviations
[20:30] <mok0> AnAnt: I keep that page open when in this channel :-)
[20:30] <AnAnt> when I look at usplash-theme-ubuntu, I find that the C file is GPL licensed, yet in debian/copyright I only find a CC license
[20:31] <AnAnt> I did the same with my usplash theme, and the reviewers didn't like that
[20:31] <wallyweek> hi all! :)
[20:32] <slangasek> AnAnt: what do you mean, "find" a CC license? it's your package, surely you're responsible for the contents of debian/copyright?
[20:32] <AnAnt> let me ask this question first, can the .c file of a usplash theme be licensed under CC ?
[20:33] <AnAnt> slangasek: I'm talking about what I saw in Ubuntu's usplash theme package, hence I did similar in the usplash theme I was packaging
[20:33] <slangasek> legally, yes; but debian/copyright needs to reflect the actual license of the package (and CC licenses aren't as good for source code as GPL, anyway)
[20:33] <wallyweek> could anyone review sdlmame? it would be nice to see it in hardy :)
[20:33] <wallyweek> http://revu.tauware.de/details.py?package=sdlmame
[20:34] <AnAnt> slangasek: well, in usplash themes, there are image files (.png) and a C file that calls them
[20:34] <AnAnt> slangasek: so I think in that case, the C source code can be considered some artwork more than it is a software
[20:37] <slangasek> AnAnt: debian/copyright still needs to reflect the actual license that the software has been placed under by the copyright holders
[20:37] <AnAnt> slangasek: ok
[20:37] <AnAnt> thanks for the help
[20:41] <bddebian> Did libwxgtk-2.4 have a wxgtk-2.4-config that libwxgtk-2.6 doesn't?
[20:47] <cyberix> Is there a Debian-Maintainer filed which is separate from XSBC-Original-Maintainer ?
[20:47] <cyberix> field
[20:48] <cyberix> Even apt uses XSBC-Original-Maintainer
[20:54] <astharot> is there some ubuntumembers administrators on launchpad?
[20:54] <astharot> I have a question about my membership
[20:58] <slangasek> bddebian: how did you put together whatever list you're using of wxgtk2.4 reverse-deps?
[20:59] <bddebian> slangasek: I've just been using what was sent on the oldlibs e-mail so far
[20:59] <bddebian> I think gnue might still be an issue too iirc
[21:00] <slangasek> bddebian: url?
[21:00] <slangasek> n/m, found it
[21:16] <wallyweek> anyone to review my package, please? http://revu.tauware.de/details.py?package=sdlmame
[21:29] <unenough> yay! Almost got a Python2.5 package that puts .pyc's in another cache directory, rather than messing the source dir, and that treats .pyc's as purely cache, does not use them as sources when the .py's not there
[21:32] <geser> unenough: don't install .pyc files in your package
[21:32] <bddebian> Grr, I can't get ctsim to even attempt to build with wx2.6 :(
[21:32] <bddebian> persia: Wake up man.. :)
[21:32] <unenough> geser, for now its just a temporary local hack for me and friends
[21:33] <unenough> geser, if it becomes more serious, there are some issues to handle, such as having a system-wide cache dir to search first
[21:33] <slangasek> bddebian: that's ok, if that's really the last package and the maintainer/upstream is being obstructionist, we can just pull wxwindows2.4 out of unstable out from under him
[21:34] <geser> unenough: why do you want to have the .pyc file inside the package?
[21:34] <bddebian> slangasek: Well persia said he got it to build, he just had the sefault issue, which may have been a similar wx-config issue
[21:40] <bddebian> And, of course, I don't know if the newpki-maintainer is going to accept my patch either
[21:43] <slangasek> bddebian: then we would have two packages that are SOL in unstable due to daft maintainers. <shrug>
[21:43] <slangasek> especially when the code has already been written to move to wx2.6, there's no reason at all for us to keep wx2.4 around
[21:43] <bddebian> You're the boss :-)
[21:46] <wallyweek> come on, is revu day! no reviewers online? ;)
[21:47] <amarillion> What does a good get-orig-source rule look like? Would something like this be ok? http://paste.ubuntu-nl.org/51135/
[21:49] <amarillion> btw, what does SOL mean?
[21:54] <wallyweek> amarillion: you should also rename the directory before recompressing and delete the .zip and the extracted directory
[21:54] <wallyweek> after building the tar.gz
[21:55] <amarillion> I though the name of the directory is ignored by all utilities
[21:58] <wallyweek> amarillion: well, to be honest, I don't know... :) the packaging guide suggest to normalize the dir name
[21:58] <amarillion> ok, I'll do it just to be safe
[21:59] <wallyweek> I also pasted my suggestion on the pastebin... didn't know I could ;)
[21:59] <amarillion> so I need to add "mv speed speed-game-1.00" and rm "speed.zip", probably "rm -r speed-game-1.00" afterwards as well
[22:00] <wallyweek> yes
[22:00] <amarillion> oh I didn't know that either. Do you get a new link for that? I don't see it yet
[22:02] <wallyweek> should be http://paste.ubuntu-nl.org/51137/
[22:02] <wallyweek> I didn't notice the link was changed
[22:03] <amarillion> Ah yes, I could have just have incremented the number twice
[22:03] <amarillion> thanks for the suggestions
[22:04] <wallyweek> you're welcome :)
[22:21] <stgraber> http://revu.ubuntuwire.com/details.py?package=libfprint is ready for a review if someone has time
[22:23] <wallyweek> and so is http://revu.tauware.de/details.py?package=sdlmame, thanks :)
[22:25] <guest22> While we're on review requests, let me add one for http://revu.tauware.de/details.py?package=photoml  It's already been advocated once (the previous upload, at least), so it should be very close to being acceptable.
[22:28] <amarillion> I just updated my package: http://revu.tauware.de/details.py?package=speed-game. All comments made yesterday have been addressed, except the license clarification because I'm still waiting for an answer from upstream
[22:28] <amarillion> And I learned everything there is to know about hiscore files in the process :)
[22:35] <persia> bddebian: Sorry.  Slow today :)  There was a wx-2.4-config, but wx-config should replace it.  ctsim worked for me in early gutsy, but segfaulted on execute.  I haven't looked since.
[22:39] <bddebian> persia: With no changes other than the build deps?
[22:40] <persia> bddebian: By memory, yes.  I appear to have removed my ctsim working directory, and as I never had a working patch, didn't generate anything for my patch archive.
[22:40] <wallyweek> persia: I would ask to nuke http://revu.tauware.de/details.py?package=shorten
[22:41] <wallyweek> as norsetto pointed out, licence is quite uncomfortable and I'd like to stop packaging it
[22:41] <persia> wallyweek: I seem to be having difficulty nuking lately.  Would archiving meet your needs?
[22:42] <wallyweek> persia: it doesn't matter to me... ehr... what's the difference, btw? ;)
[22:42] <persia> wallyweek: Archiving hides it from the default listings.  Nuking removes the package and all comments from REVU entirely.
[22:43] <persia> In case of later interest, you can recover from an archive with a new upload.
[22:43] <persia> wallyweek: shorten archived
[22:43] <amarillion> wallyweek, can that package not be included?
[22:43] <wallyweek> persia: thanks!
[22:44] <amarillion> Too bad, after all that work
[22:44] <persia> amarillion: Since the original packager no longer wishes to continue, feel free to grab it, work with upstream to resolve the licensing issues, and submit a new candidate, if you have interest in the package.
[22:45] <wallyweek> persia: licence is weird... it says it's free to decode, but permission should be asked for encoding
[22:45] <persia> wallyweek: Might be related to some of the encoding patents that are floating about. (not that I've investigated)
[22:46] <minghua> a.k.a. rar license?
[22:46] <wallyweek> persia: yes. Shorten is not a free codec, even if opensource
[22:48] <wallyweek> I could patch the source, but I feel this would not be good
[22:48] <persia> That makes sense then.  I suppose a decoder-only could be packaged, or a use-specific patent grant could be given (which would make it multiverse).  Needs coordination with upstream .
[22:49] <wallyweek> persia: unfortunately, original upstream maintainer doesn't care about original code
[22:51] <wallyweek> new releases are carried on by another guy, which has no rights to modify original code licence
[22:52] <persia> wallyweek: Right.  Needs coordination with the copyright holder / patent controller / whatever, if upstream isn't that party.  Upstream can maybe help with that (although you may not be the person who works with them to achieve the goal).
[22:52] <wallyweek> amarillion: if you find shorten useful, you can download package from my ppa https://launchpad.net/~c.falco/+archive
[22:53] <amarillion> wallyweek, oh I don't really have a personal interest, I was just reading the comments page on REVU
[22:53] <amarillion> Seeing all the comments, a fair bit of work went into it
[22:54] <wallyweek> amarillion: yes... but that was good learning anyway ;)
[22:54] <amarillion> true
[22:55] <persia> Also, it's likely that much less work for someone else, if they pick up the packaging effort.
[22:55] <wallyweek> persia: true
[22:55] <amarillion> I was reading a few comments pages on REVU. Some packages go through dozens of revisions
[22:56] <persia> This is especially true for very complex packages, with lots of upstream problems.  Most reviewers stop looking carefully when reaching some threshold of comments (for me, around 10).
[22:57] <amarillion> makes you wonder how we ever got to tens of thousands of packages that are in ubuntu now
[22:57] <wallyweek> amarillion: yes, sometimes it's quite frustrating... sdlmame has been on REVU since feb 2007
[22:57] <persia> Only about 500 came thorugh REVU.  Most are imported from Debian.
[22:58] <wallyweek> persia: good answer... I wondered the same :)
[22:58] <amarillion> true, but I understand the process for inclusion in Debian even longer
[22:58] <DaveMorris> mine has had loads of revions
[22:59]  * DaveMorris cruses OpenSG
[23:00]  * DaveMorris can't spell this evening
[23:01] <wallyweek> before going to bed, let me call once again for reviews on http://revu.tauware.de/details.py?package=sdlmame
[23:01] <wallyweek> thanks :)
[23:07] <LaserJock> anybody familiar with pbuilder-dist around?
[23:07] <LaserJock> I'm trying to create a pbuilder and I just get:
[23:07] <LaserJock> E: Type '' is not known on line 1 in the source list /etc/apt/sources.list
[23:17] <TheMuso> jdong: Have you seen this aac encoder? http://teknoraver.campuslife.it/software/mp4tools/
[23:17] <nenolod> persia, patch accepted upstream. http://bugzilla.gnome.org/show_bug.cgi?id=507605
[23:17] <ubotu> Gnome bug 507605 in recent-files "[patch] gtk_recent_files_menu_populate() does not guard properly against recursion" [Critical,Unconfirmed]
[23:17] <TheMuso> jdong: specifically aacplusenc
[23:17] <nenolod> TheMuso, that's a new one
[23:17] <TheMuso> I know
[23:17] <jdong> TheMuso: yet another mp4 encoder
[23:18] <TheMuso> Yeah I know. Does anybody know how it compares to faac?
[23:18] <jdong> TheMuso: pretty sure it uses faac?
[23:18] <nenolod> jdong, no
[23:18] <TheMuso> jdong: doesn't appear to.
[23:18] <nenolod> jdong, it uses it's own encoder
[23:18] <nenolod> TheMuso, i'll play with aacplusenc tonight
[23:18] <jdong> lemme grab the sources before opening my mouth...
[23:19] <nenolod> TheMuso, it'd be nice to have a decent aac encoder in hardy
[23:20] <wallyweek> g'night everyone! :)
[23:21] <amarillion> goodnight
[23:22] <jdong> yeah, looks interesting
[23:22] <nenolod> hmm
[23:22] <jdong> would be nice to put it too the test
[23:22] <nenolod> the ubuntu packages are incorrect
[23:22] <jdong> to*
[23:22] <nenolod> they'll have to be redone
[23:22] <jdong> nenolod: you don't say? ;-)
[23:23] <TheMuso> aacplusenc doesn't tag however
[23:23] <nenolod> (they are packaged as a native archive)
[23:23] <jdong> TheMuso: tagging is trivial via gpac/MP4Box though
[23:23] <jdong> TheMuso: I'm more interested in its encoding abilities
[23:23] <nenolod> TheMuso, that's fairly trivial
[23:23] <TheMuso> jdong: Same.
[23:23] <nenolod> if you want to tag it, you can always open it in audacious or whatever
[23:23] <TheMuso> jdong: One thing I found out is that from reading an ubuntuforums thread, it doesn't work properly on amd64.
[23:23] <nenolod> TheMuso, i can fix that
[23:24] <jdong> TheMuso: yeah I was seeing that in the makefile
[23:24] <TheMuso> http://ubuntuforums.org/showthread.php?t=628434&highlight=aac
[23:24] <nenolod> TheMuso, also passed it onto gentoo-media team, so maybe we can collaborate on it together ;)
[23:24] <jdong> TheMuso: it looks immature but promising
[23:24] <TheMuso> Cool.
[23:25] <TheMuso> jdong: In the makefile?
[23:25] <nenolod> most amd64 bugs are due to bitwidth oversight
[23:25] <nenolod> by using stdint.h, it's not a major issue
[23:25] <nenolod> :P
[23:26] <TheMuso> heh
[23:26]  * TheMuso cranks it through powerpc
[23:26] <TheMuso> compilation that is
[23:26] <nenolod> (you can also do int foo : 4; to make a 32-bit int)
[23:26] <jdong> nenolod: looks like this thing uses x86 assembly a bit... afraid it won't be that easy
[23:27] <nenolod> jdong, yuck
[23:27] <TheMuso> Great. So PowerPC is out of the question then. :)
[23:27]  * TheMuso grumbles./
[23:27] <TheMuso> Userspace apps should not use asm unless they are arch specific IMO.
[23:27] <jdong> #ifdef __LP64__
[23:27] <jdong>   if (inputInfo.nChannels > 1) {
[23:27] <jdong>     fprintf(stderr, "Stereo encoding is not supported in 64 bit builds
[23:27] <jdong> ");
[23:28] <jdong> whee!
[23:28] <jdong> lol
[23:28] <TheMuso> SOunds like the code is hackish.
[23:28] <jdong> TheMuso: well IMO media apps have the right to drop down to assembly
[23:28] <nenolod> jdong, where's the asm?
[23:28] <jdong> TheMuso: often times their hand-tuned assembly turns in 30% minimum speedi mprovements
[23:28] <TheMuso> jdong: I doubt that not, but they should get help for other arches then. IMO all arches should benefit.
[23:29] <TheMuso> I know PowerPC is dying, but many people still use it, myself included/
[23:29] <nenolod> i don't see any x86 asm
[23:30] <TheMuso> Hrm ok. It builds on PowerPC.
[23:30] <nenolod> yeah
[23:30] <TheMuso> nenolod: You're right, I don't think there is any asm specific stuff.
[23:30] <nenolod> as i said
[23:30] <jdong> nenolod: you're right no ASM
[23:30] <nenolod> "i don't see any x86 asm"
[23:30] <nenolod> well
[23:30] <jdong> nenolod: I saw the ADD/MULT/MOVE macros and got worried
[23:30] <nenolod> jdong, i'll import this into some bzr branch
[23:30] <jdong> looks like it's just some sort of hackjob profiling
[23:30] <jdong> eep.
[23:31] <nenolod> jdong, that's right. i intend to fix it.
[23:31] <nenolod> :D
[23:32] <TheMuso> nenolod: gogogogogogo
[23:32] <nenolod> also, no autoconf = wtf
[23:32] <TheMuso> Oh, and its built statically.
[23:32] <TheMuso> nenolod: Not everything needs autotools.
[23:33] <slangasek> sure it does, just not everything uses autotools ;)
[23:33] <nenolod> TheMuso, autotools would be good for this ;p
[23:33] <jdong> I'd rather not see autotools :D
[23:33] <TheMuso> Well, it would make turning those libs into shared libs easier.
[23:33] <TheMuso> :)
[23:34] <jdong> nenolod: also chase through the changelog, I saw a few cases where the author references switching from his own to some GPL'ed routines
[23:34] <jdong> nenolod: wonder if he is bundling a bunch of unneeded routines or if they'rej ust single functions
[23:35] <TheMuso> What is the Nero aac encoder like?
[23:35] <nenolod> it seems to encode stereo just fine on 64-bit
[23:35] <nenolod> although mplayer is having problems with it
[23:36] <nenolod> but mplayer has problems with SBR anyway
[23:36]  * jdong looks at mpeg4ip
[23:36] <jdong> nope still in NEW
[23:37] <TheMuso> jdong: What package is mp4box in?
[23:37] <jdong> TheMuso: gpac
[23:37] <TheMuso> oh ok
[23:37] <nenolod> hmm
[23:37] <nenolod> weird
[23:38] <nenolod> it does indeed produce crap on amd64
[23:38] <jdong> yay!
[23:38] <jdong> I'm surprised the author hasn't just passed -m32 into gcc
[23:38] <jdong> lol
[23:39] <nenolod> (crap when done with stereo. so i think it's a bitwidth bug somewhere.)
[23:39] <nenolod> i imagine sed -i s:unsigned int:uint32_t:g s:int\s:int32_t:g will do.
[23:39] <nenolod> maybe he uses sizeof
[23:40] <ScottK> LaserJock: Was it a Debian pbuilder you were making?
[23:40] <ScottK> If so, I had the same kind of problem.
[23:40] <ScottK> I just hacked stuff out of the script until it went away.
[23:40] <jdong> nenolod: unless there's hardcoded bitmasks that are different on x64
[23:42] <nenolod> jdong, maybe. we'll see.
[23:42] <jdong> :)
[23:48] <LaserJock> ScottK: no, hardy
[23:48] <LaserJock> I just rand pbuilder-dist hardy create
[23:49] <ScottK> Did you have universe enabled?  When I had the problem on Debian ones it was getting confused about extra repos and then I got that error when I removed them.
[23:54] <LaserJock> I tried it as both pbuilder-dist hardy allcomp create and pbuilder-dist hardy mainonly create I think
[23:54] <TheMuso> Ok this encoder also doesn't accept high bitrates.
[23:56] <joejaxx> anyone else having packaging issues with kde4 packages in gutsy?
[23:57] <joejaxx> i know kde4 is "beta" but packaging is packaging :P
[23:58] <LaserJock> joejaxx: where are you getting the packages?
[23:58] <joejaxx> well the ones that i did today were from backports
[23:58] <joejaxx> http://pastebin.ca/845932
[23:58] <joejaxx> looks like fun :D
[23:58] <joejaxx> does it not?
[23:58] <joejaxx> :)
[23:59] <minghua> ScottK: Is Debian affected by the "needed perl module version is higher than the one in perl-modules" problem?
[23:59] <LaserJock> joejaxx: well, seems somewhat typical :/