[12:15] <shawarma> Schitso: You can apply, yes.
[12:15] <shawarma> Schitso: For now, you can give me the bug number, then I can set it to wishlist.
[12:15] <Schitso> https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/120284
[12:15] <ubotu> Launchpad bug 120284 in rhythmbox "video podcasts show as failed downloads" [Undecided,Unconfirmed]  
[12:17] <shawarma> Schitso: Done.
[12:17] <Schitso> Thanks
[12:17] <shawarma> Schitso: Thank *you*.
[12:17] <Schitso> Should I set it to "confirmed", then?
[12:18] <shawarma> If you've verified that it's not bogus, I'd say yes.
[12:19] <mok0> ls
[12:19] <mok0> s/ls//
[12:19] <Schitso> Alright.
[12:20] <shawarma> ScottK-laptop: Thanks for all your help. You made it to top three on my "People, I should buy beer" list.
[12:20] <ScottK-laptop> Great.  You're welcome.  Thanks for contributing.
[12:21] <ScottK-laptop> shawarma: Say thanks to the people that stuck me in an all day boring meeting and gave me internet access.
[12:21] <shawarma> ScottK-laptop: It really must have been *very* boring.
[12:22] <ScottK-laptop> Yeah and my blood pressure does better when I don't pay attention to some of this stuff.
[12:24] <shawarma> ScottK-laptop: Well, I'm glad I could be of service distracting you all day. :)
[12:33] <mok0> I've made a premature upload to revu, can I zap it?
[12:33] <ajmitch> just upload a new one once this one gets accepted
[12:34] <mok0> Okay, I just want the reviewer to look at the latest upload
[12:34] <ajmitch> right, they always should anyway
[12:34] <mok0> great, thx
[12:38] <bluefoxicy> quick question
[12:39] <bluefoxicy> state "D" is in-kernel non-interruptable something right
[12:39] <bluefoxicy> which is not running
[12:42] <ScottK-laptop> bluefoxicy: Dunno, but where in MD are you?  I live in MD too.
[12:42] <bluefoxicy> FINALLY
[12:42] <bluefoxicy> it just stopped being in D and died
[12:42] <bluefoxicy> after like 5 minutes
[12:42] <bluefoxicy> scottK:  White marsh area
[12:43] <ScottK-laptop> bluefoxicy: I live in Ellicott CIty
[12:43] <bluefoxicy> scottK:  Been there.
[12:44] <bluefoxicy> I missed my turn for college and had to go down to the next exit
[12:44] <ScottK-laptop> Heh.  Which college?
[12:59] <Schitso> I need help making a patch for a bug.
[12:59] <Schitso> It's just a small change in the debian/install file
[12:59] <ScottK-laptop> OK
[01:00] <Schitso> So, how exactly would I go about it?
[01:00] <ScottK-laptop> Schitso: What bug?
[01:00] <Schitso> Should I change the diff.gz file that comes with the package?
[01:00] <Schitso> https://bugs.launchpad.net/ubuntu/+source/timemachine/+bug/120475
[01:00] <ubotu> Launchpad bug 120475 in timemachine ".desktop file wrong srouce" [Undecided,In progress]  
[01:01] <ScottK-laptop> Schitso: apt-get source the package and work from that.
[01:02] <Schitso> I did already, and I made the change, but how should I post it?
[01:02] <ScottK-laptop> Schitso: Make your change, document it in debian/changelog (dch -i is your friend).
[01:02] <ScottK-laptop> Then make a new source package (debuild -S -uc)
[01:03] <ScottK-laptop> Then debdiff the old and new packages, attach the debdiff to the bug and subscribe ubuntu-universe-sponsrs to the bug.
[01:05] <Schitso>  Bug#120475: timemachine: .desktop wrong file srouce
[01:05] <Schitso> * timemachine.desktop installed into /usr/share/app-installer/desktop
[01:05] <Schitso>     instead of /usr/share/gnome/apps/Multimedia/ 
[01:05] <ScottK-laptop> Good bye all.  Boring meeting is ending.
[01:06] <Schitso> Is that the correct way to document the change?
[01:06] <Schitso> Ah, ok.
[01:06] <pochu> Night ScottK-laptop 
[01:06] <Schitso> Bye.
[01:06] <ScottK-laptop> No.  Sorry I've got to run.  Someone else can tell you...
[01:06] <Schitso> Blast....
[01:06] <Schitso> Someone?
[01:06] <Schitso> Anyone?
[01:07] <pochu> Good night MOTUland!
[01:07] <Schitso> Not knowing what to do sucks.
[01:23] <porthose> yea I have the same problem lololo it really does suck
[01:28] <luisbg> how should I do it if I want that when the package I'm building makes a backup of a file before installing itself?
[01:38] <owh> I'm trying to fix a bug in gphpedit. I think that the problem is that a parameter being passed is defined as a gint, but expected to be a glong. There are over 300 parameters to check. I'm using dpkg-buildpackage -rfakeroot -uc -b to build the package. How do I get the compiler to tell me of these mismatches?
[01:38] <Amaranth> 2> error.log
[01:40] <owh> Amaranth: That gave me a little output, but nothing at all to do with type errors at all.
[01:41] <owh> Any flags I need to set somewhere?
[01:45] <owh> I've just tried with the -W flag, but that didn't produce any more output.
[02:05] <jussi01> can someone remind me of how to find out the package you need if your missing a certain file? (SDL.h)
[02:07] <StevenK> jussi01: apt-file search ?
[02:07] <jussi01> StevenK: thanks :D
[02:14] <mthaddon> have a question about patching a package (noob here in terms of packaging) - I've done...
[02:14] <mthaddon> apt-get source rhythmbox
[02:14] <mthaddon> cd rhythmbox-0.10.0
[02:14] <mthaddon> # patched my installation and ran dch -i
[02:14] <mthaddon> debuild -S
[02:14] <mthaddon> cd ..
[02:14] <mthaddon> I know have the files in the directory, but am not sure how to repackage them so I can install and then test that my patch worked?
[02:15] <owh> mthaddon: The way I just did that was: "dpkg-buildpackage -rfakeroot -uc -b"
[02:15] <jussi01> you can also use pbuilder for a clean room environment
[02:15] <AndyP> mthaddon: you might want to look into using pbuilder
[02:15] <mthaddon> owh: do I need to specify the dsc file, as there are two there (the original one)
[02:16] <owh> mthaddon: Dunno, I'm just playing locally.
[02:16] <mthaddon> AndyP: I have a pbuilder set up for dapper and would like to build this for feisty - I guess I could reconfigure that...
[02:17] <jussi01> mthaddon: yeah you need to specify the dsc...
[02:17] <AndyP> mthaddon: it's possible to set up more than one pbuilder for different releases etc, but you can also just tweak your /etc/pbuilderrc to look at a different release if you only want to build for one
[02:18] <mthaddon> AndyP: might have to look into that...
[02:18] <mthaddon> jussi01: thx
[02:18] <AndyP> https://wiki.ubuntu.com/PbuilderHowto
[02:20] <jussi01> could someone tell me what im missing? http://paste.ubuntu-nl.org/25636/
[02:21] <AndyP> jussi01: looks like you need to build depend on libsdl1.2-dev
[02:22] <jussi01> AndyP: thanks
[02:23] <AndyP> if you need to find out those kinds of things, "apt-file search" or packages.ubuntu.com are good places to search
[02:25] <hollero> is there any particular reason why there's a package for Eclipse but none for NetBeans?
[02:26] <jussi01> AndyP: apt-file serch didnt reveal anything.. wht did you search on?
[02:26] <AndyP> hollero: netbeans is in multiverse, i believe
[02:26] <AndyP> jussi01: i searched for SDL.h
[02:27] <AndyP> jussi01: if you've only just installed apt-file you'll need to run sudo apt-file update to build the db
[02:28] <jussi01> AndyP: hehe, thats the problem then :D
[02:28] <jussi01> wondered why it didnt work
[02:28] <AndyP> :)
[02:30] <jussi01> AndyP: can you do a quick search on SDL_image.h for me? my internet is really sslow, and its taking ages...
[02:31] <hollero> now i got it... is there any reason why it is multiverse and not universe (i thought it was completely opensource)... and why is it only in synaptic and not in add/remove?
[02:32] <AndyP> jussi01: libsdl-image1.2-dev
[02:32] <AndyP> hollero: no idea, sorry
[02:32] <jussi01> AndyP: thanks very much
[02:34] <hollero> maybe it's just a matter of creating a metafile for add/remove (i'm not an expert on this, no idea really) with a description and so on that it can be used in the easy add/remove
[02:34] <hollero> ?
[02:36] <leonel> question :  when I get the sources from a debian unstable  deb   and  I want to patch it to work with ubuntu  dpatch-edit-patch works the same  or there's something that has to be done ?
[02:36] <leonel> no I haven't done any  merge
[02:36] <leonel> just testing if that  deb works in ubuntu
[02:37] <AndyP> leonel: i'm not sure i understand your question
[02:38] <superm1> leonel, does a test build work in a gutsy pbuilder/sbuild?
[02:38] <superm1> (or have you tried)?
[02:38] <leonel> superm1:  no I haven't  I just  downloaded   dpkg-source  and dpkg-buildpackage 
[02:39] <superm1> leonel, the first thing i would do is try it in a pbuilder/sbuild env.  if things work, you're done and just need to request a sync
[02:39] <leonel> AndyP: Ubuntu works with  debian/patches    and I didn't see any  in debian's   psycopg2
[02:39] <superm1> if not, then you can create patches using dpatch-edit-patch
[02:39] <leonel> superm1: ok thanks  
[02:39] <leonel> I'll try
[02:42] <leonel> The more I learn from  this  things  the more I want to keep working on this things .. I mean  motu things 
[02:42] <leonel> :)
[02:47] <leonel> superm1: Builded  fine  with pbuilder 
[03:11] <StevenK> shawarma: Linda 0.3.25 has been uploaded to Debian. The Debian import freeze hasn't hit yet, so hopefully she'll get pulled across automagically.
[03:17] <nixternal> crimsun: when you get the chance, I have upgraded to Gutsy and my sound is severly broken...go through some steps so I can create a bug report accordingly for you
[03:18] <ajmitch> nixternal: how broken?
[03:18] <nixternal> well, broken tot he point where my speakers are blaring, unless I turn PCM all the way down
[03:18] <nixternal> volume control doesn't work at all, only pcm
[03:18] <ajmitch> fun
[03:19] <ajmitch> there was a new alsa-utils that I saw, at least
[03:19] <nixternal> I usually sit in the back of class and listen to LUGRadio, so after I upgraded here in class I decided to listen to the latest, and boom, Jono loud as hell laughing filled the class
[03:20] <jussio1> lol
[03:20] <nixternal> at least he wasn't cussing yet
[03:20] <jussio1> hehe
[03:20] <ajmitch> haha!
[03:21] <nixternal> now the teacher definitely knows I am not paying attention during class
[03:23] <nixternal> jussio1: he is hiding, he knows it is broken ;p
[03:23] <jussio1> hehe
[03:23] <nixternal> glad I didn't click on some pr0n or something, now that would have been really embarassing
[03:23] <jussio1> im trying to figure out this, its probably not alsa's fault htough...
[03:24] <jsgotangco> huh? you upgraded your system while in class?
[03:24] <nixternal> yup
[03:24] <nixternal> dude, this is ASP.NET class, I could care less about it
[03:25] <nixternal> easy A
[03:25] <jsgotangco> you must be really bored
[03:25] <jsgotangco> even if its an MS thing class I wouldn't miss the chance to learn something
[03:25] <nixternal> ASP.NET == drag and dropping, not much to learn really, everything tells you what to do
[03:25] <jussi01> hehe
[03:26] <jsgotangco> its still learning for me
[03:26] <nixternal> every now and then we get into some c#
[03:26] <nixternal> so if you know java and c++, then c# makes sense, or is supposed to make sense
[03:27] <jsgotangco> wow powerset released a screenshot and it has a porn category
[03:27] <nixternal> heh
[03:31] <jsgotangco> go spurs
[04:02] <leonel> is it  right to  have  a  pbuilder-gutsy inside a  gutsy debootstrap running in feisty ?
[04:07] <jussi01> can someone point me to a good tutorial to get vnc working?
[04:34] <TheMuso> lionel: I'd say so. I used to use dchroot with chroots, which had pbuilder set up in them.
[04:42] <leonel> TheMuso:  ok 
[04:50] <superm1> leonel, yes that should be fine
[04:51] <superm1> you just need to file a sync request bug now
[04:51] <superm1> indicate that it built fine in your pbuilder
[04:51] <superm1> and then subscribe ubuntu-universe-sponsors
[04:57] <leonel> superm1: if the package is in MoM or DaD  ??
[04:58] <superm1> regardless
[04:58] <superm1> leonel, the entire sync process is here: https://wiki.ubuntu.com/SyncRequestProcess
[04:58] <leonel> so there's no need to merge ?
[04:59] <leonel> http://merges.ubuntu.com/p/psycopg2/REPORT
[05:00] <superm1> oh I thought you had mentioned this was was a new package
[05:00] <superm1> coming from debian
[05:00] <superm1> as in not in ubuntu.
[05:00] <superm1> what is the content of our changes?
[05:00] <superm1> from debian
[05:02] <leonel> superm1: I don't  know  but let me read  that link you send  or is there for  merge request ?
[05:02] <superm1> leonel, well you can generate a debdiff between our package and debian's 
[05:03] <superm1> and see if the changes we do are necessary
[05:03] <superm1> if it looks like they are, then you need to go through a merge
[05:03] <superm1> if they can be dropped, you can file the sync request
[05:04] <leonel> superm1: great    let me do that tomorrow  since I got to go now    and  read that link you send  (  I'm learnng  here ) ...
[05:04] <leonel> superm1: thank you 
[05:04] <superm1> np leonel :)
[05:04] <superm1> leonel, there is lots of very valuable information on all the procedures at those wiki pages
[05:05] <leonel> superm1:  I'll take a look thanks
[05:12] <leonel> superm1: found this :) https://wiki.ubuntu.com/MOTU/Packages/Merging
[05:12] <leonel> superm1: I'll read  and read  and read then  do a merge or sync 
[05:12] <superm1> sounds good leonel 
[05:12] <leonel> now got to go !
[05:13] <leonel> thank you 
[05:48] <zakame> good day MOTUs
[05:53] <zakame> make that wulfware
[06:42] <zakame> xmms2 FTBFS on amd64 known upstream: http://bugs.xmms2.xmms.se/view.php?id=1607
[06:44] <zakame> perhaps disabling build of xmms2-plugin-sid would work atm?
[06:47] <sevda> sevda1990_2007@yahoo.com
[06:51] <ed1t> anybody know on status of new scala's .deb?
[06:53] <Burgundavia> ed1t: scalas dev?
[06:53] <Burgundavia> deb?
[06:54] <ed1t> yes scala2.5.1 released....ubuntu's repository has the old version 2.3
[06:55] <ajmitch> 2.5.0 sources are in universe, but failed to build
[06:56] <ed1t> is it easy to like create your own .deb ?
[06:56] <ajmitch> "GC Warning: Out of Memory!  Returning NIL!
[06:56] <ajmitch> java.lang.OutOfMemoryError
[06:56] <ajmitch>    <<No stacktrace available>>"
[06:56] <ajmitch> comforting
[06:56] <ed1t> hmmm
[06:56] <StevenK> Oh, *twitch*
[06:56] <ajmitch> StevenK awakens
[06:57] <StevenK> I've been awake for hours, so shush
[06:57] <ajmitch> but you leapt for joy at the mention of java
[06:57] <ajmitch> it shouldn't be too hard to update scala to 2.5.1, but it entirely depends on the package
[07:01] <StevenK> And if it requires more than 1Gb of RAM to build.
[07:01] <ed1t> which one?
[07:12] <StevenK> A co-worker mentions that ant has it's own limits, much like PHP.
[07:13] <ajmitch> but php should be used for everything!
[07:13] <StevenK> Oh geez.
[07:13] <StevenK> ANT_OPTS=-Xmx512M ant -f debian/simpbuild.xml dist
[07:13] <ajmitch> why don't we use php-gtk more?
[07:13] <StevenK> Evidently, 512M isn't enough anymore.
[07:15] <StevenK> But according to the co-worker, ant tries to do everything directly in memory.
[07:32] <Hobbsee> hi all
[07:34] <lifeless> harro
[07:34] <Hobbsee> :)
[07:34] <zakame> heya Hobbsee and lifeless!
[07:35] <cbx33> hey there everybody
[07:35] <zakame> yo cbx33
[07:35] <cbx33> howz it all going
[07:37] <Hobbsee> hey
[07:37] <Hobbsee> a
[07:37] <cbx33> heya Hobbsee 
[07:37] <cbx33> guys got a bit of a MOTU question
[07:37] <cbx33> hehe
[07:38] <cbx33> so...I have a piece of software, which has several "plugins"
[07:38] <cbx33> which pull in/require many python modules
[07:38] <cbx33> so I don't want to package it all up together
[07:38] <cbx33> as it'll then require lots of deps
[07:39] <cbx33> that the person will probably never ever use.  Is it acceptable to split it into seperate binary packages for the plugins?
[07:39] <lifeless> sure
[07:39] <lifeless> see opensync for instance :)
[07:39] <cbx33> if so, I currently use a makefile to do the python stuff
[07:39] <cbx33> how best I do this
[07:40] <cbx33> maybe a link to the package would help?
[07:40] <cbx33> if someone has a few minutes to look at if with me
[07:40] <lifeless> well
[07:40] <lifeless> your software build, and your packaging should be separate
[07:40] <cbx33> yes
[07:40] <lifeless> because people may want to package it for RH etc.
[07:40] <cbx33> sure
[07:40] <lifeless> so just have your package rules create the separate binary packages.
[07:41] <cbx33> that's the plan
[07:41] <cbx33> www.progbox.co.uk/vcsfrenzy
[07:42] <cbx33> https://code.launchpad.net/~petesavage/vcs-frenzy/trunk
[07:42] <cbx33> the browse code here should have it too
[07:43] <cbx33> at the moment
[07:43] <cbx33> http://codebrowse.launchpad.net/~petesavage/vcs-frenzy/trunk/annotate/petesavage%40ubuntu.com-20070601205206-xckyam97r3q4wedk?file_id=makefile-20070510150748-m3hnibdgz7gz3czl-1
[07:43] <cbx33> my makefile installs all plugins together
[07:45] <cbx33> how best to go about splitting this?
[07:51] <crimsun> nixternal: what does "severely broken" mean?
[07:52] <Hobbsee> crimsun: means he's describing his experience of vista.
[07:56] <DarkMageZ> ... vista isn't that bad. mine only went nuclear due to my attempting to get mdns on it.
[07:58] <zakame> lol
[08:02] <cbx33> heheh
[08:02] <cbx33> so any ideas on my packging problem?
[08:05] <\sh> crimsun, do you have any clue about asoundconf-gtk, especially where the orig source code can be found?
[08:06] <cbx33> hey jsgotangco 
[08:06] <jsgotangco> hi cbx33
[08:07] <jsgotangco> hi \sh welcome back :)
[08:09] <crimsun> \sh: I thought it was in Ubuntu Studio's bzr repo
[08:09] <crimsun> \sh: don't have the url handy, but apt-get source has it
[08:10] <crimsun> \sh: it's deprecated anyhow; see LP/asoundconf-ui
[08:12] <\sh> crimsun, yeah found your project...but no bzr uploads ,-)
[08:13] <\sh> crimsun, oh ... sorry...wrong there is something ,-)
[08:13] <crimsun> hmm? there are two commits to trunk.  Granted it's very, very prelim, but if you pyuic -o displayqt.py displayqt.ui, you'll see the mockup
[08:14] <\sh> crimsun, let me give it a shot and provide some code to it ,-)
[08:16] <nixternal> crimsun: only PCM controls the volume for me
[08:16] <\sh> crimsun, do you want to reuse the code from pitti (asoundconf) ?
[08:16] <crimsun> \sh: yes, it will Depends: alsa-utils
[08:16] <nixternal> my volume up/down keys works great by turning master volume up and down, however it really doesn't turn the volume up or down
[08:17] <nixternal> and I will say, the Gutsy kernel has made my audio even louder now
[08:17] <\sh> crimsun, anything against pushing this as well to opensuse or any other distro not having this fine util?
[08:17] <nixternal> having Jono laughing in the middle of class isn't all that great :)
[08:18] <crimsun> \sh: none at all, though they probably don't have asoundconf.  Be aware that the version of asoundconf is very tightly dependent on the alsa-lib version due to the parameters culled from $prefix/share/alsa/alsa.conf
[08:18] <\sh> crimsun, yepp....I wanted to port asoundconf to opensuse...(just testing this bitch of distro)
[08:19] <crimsun> it would be useful for me to draw up that spec RSN
[08:19] <crimsun> nixternal: ok, so what's severely broken about it?
[08:20] <nixternal> well, not being able to control my volume automatically makes it severly broken in my eyes..where volume doesn't do anything...having to manually control pcm
[08:20] <crimsun> nixternal: keep in mind that we're not tracking alsa-kernel hg tip, since 2.6.22 has yet to release so that I can begin the pull.
[08:21] <crimsun> err, we apparently have very different versions of "extremely broken"
[08:21] <nixternal> roger that...just wanted to talk it over with you and see how to proceed..I can live with the manual tweaking
[08:21] <crimsun> extremely broken for me is "inaudible regardless of quirk" or "locks up machine"
[08:21] <nixternal> well when jono is laughing at 100db in the middle of class, that is severly broken ;p
[08:22] <crimsun> ok, then please provide me with some useful debugging info.
[08:22] <nixternal> that is what I wanted to talk about...you know all of the funky commands to debug audio
[08:22] <crimsun> http://trilug.org/~crimsun/alsa-info.sh
[08:22] <crimsun> download it, execute it, tell me the url.
[08:24] <nixternal> http://pastebin.ca/567967
[08:24] <nixternal> brb
[08:30] <crimsun> it's not clear whether you're saying that 'Master' does nothing at all or that 'PCM' overrides 'Master'
[08:30] <nixternal> Master does nothing at all
[08:30] <nixternal> the volume slider goes up and down, but the volume doesn't change
[08:31] <crimsun> and this is a dist-upgrade?
[08:31] <nixternal> yes
[08:31] <crimsun> the state names changed
[08:31] <crimsun> nuke your /var/lib/alsa/asound.state, unload ^snd, reload snd-hda-intel
[08:32] <crimsun> oh, and if you were using any options snd-hda-intel line in /etc/modprobe.d/*, get rid of it
[08:32] <nixternal> mute doesn't work either
[08:32] <crimsun> one step at a time
[08:34] <nixternal> how do I unload & reload?
[08:34] <nixternal> modprobe?
[08:34] <StevenK> modprobe -r .... ; modprobe ...
[08:35] <nixternal> thought so
[08:35] <nixternal> there is a ton of snd, just the intel for the unload I take it?
[08:37] <crimsun> modprobe -r $(lsmod|awk '/^snd/ {print $1}')
[08:38] <StevenK> Might need to pipe the awk into tac
[08:39] <\sh> crimsun, you should use kdes i18n method and then gettext 
[08:39] <nixternal> FATAL: Module snd_hda_intel is in use.
[08:40] <crimsun> \sh: sure, go ahead, although I'd rather keep it Qt
[08:40] <shawarma> StevenK: And you've included the patch in 0.3.25? (
[08:40] <shawarma> s/(//
[08:40] <StevenK> shawarma: No, because I'd already fixed it.
[08:40] <shawarma> StevenK: Ah, ok. Great.
[08:41] <crimsun> nixternal: close any program accessing it.
[08:41] <crimsun> fuser, lsof, whatever.
[08:41] <crimsun> (and if you're using pulseaudio, you'll need to prepend sudo due to the recent sysctl.conf change)
[08:42] <crimsun> /dev/dsp* /dev/mixer* /dev/audio* /dev/snd/*
[08:42] <crimsun> being the files you want to check
[08:44] <nixternal> OK, done
[08:45] <nixternal> amarok was the bugger
[08:46] <crimsun> now, presuming the symptom is reproducible with amixer directly, I'll need your codec dumps
[08:46] <crimsun> i.e., don't use your mmkeys; use `alsamixer -c0` directly
[08:47] <nixternal> alsamixer isn't working it either
[08:48] <crimsun> meaning Master does nothing?
[08:48] <nixternal> nope
[08:48] <crimsun> ok, then you need 4 sets of pastebins.
[08:48] <crimsun> set 1 is the initial state
[08:49] <crimsun> set 2 is the state after you've increased PCM but left Master alone
[08:49] <crimsun> set 3 is the state after you've done set 2 and increased Master
[08:51] <crimsun> set 4 is the state after you've done sets 2 and 3 and decreased Master
[08:51] <crimsun> I only need /proc/asound/card0/codec* contents
[08:51] <crimsun> please file a bug against linux-source-2.6.22, assign it to the ubuntu-audio LP team, include you first pastebin URL, then attach separately each of the four codec dumps
[08:51] <nixternal> http://paste.ubuntu-nl.org/25659/
[08:51] <nixternal> ahh, roger
[08:51] <nixternal> there is only 1 codec dump
[08:51] <nixternal> codec#0
[08:52] <crimsun> each mixer element change corresponds to a nid change reflected in the codec
[08:52] <crimsun> that's why you will have 4 codec dumps
[08:53] <nixternal> gotcha
[08:54] <nixternal> crimsun: bug 119266 - does this have anything to do with me?
[08:54] <ubotu> Launchpad bug 119266 in linux-source-2.6.22 "Intel HDA Sound device doesn't work in gutsy" [Low,Fix committed]  https://launchpad.net/bugs/119266
[08:55] <crimsun> no, you two have utterly different codecs.
[08:56] <crimsun> he has a sigmatel, you have a conexant.
[09:01] <nixternal> alrighty, bug filed with all 4 dumps
[09:01] <nixternal> thank you sir
[09:03] <crimsun> thank -you-
[09:07] <nixternal> no, thank you!
[09:36] <dholbach> good morning
[12:03] <AndyP> good morning all
[12:04] <pochu> Morning :)
[12:04] <geser> Hi AndyP
[12:19] <lionel> hi AndyP
[12:21] <AndyP> hi lionel, thanks for the paintlib sync ack
[12:21] <lionel> no pb :)
[12:43] <infinito> any motu with a little time for this? http://revu.tauware.de/details.py?upid=5532
[12:45] <pochu> infinito: a small one: In debian/control, change 'More information' with 'Homepage', indented by 2 spaces, instead of one.
[12:46] <infinito> pochu: ok
[02:07] <Zic> hmm, question about existence : how it's choose to put stuff in depends *or* in recommends in ubuntu-desktop ?
[02:08] <Zic> because I can see that their is not logical answer :o
[02:08] <Zic> s/not/no/
[02:14] <xxxxx1> morrrning people
[02:14] <xxxxx1> :)
[02:18] <infinito> anyone is bored? come on! give this a little review!! http://revu.tauware.de/details.py?upid=5542
[02:18] <infinito> :)
[02:36] <xxxxx1> hello Hobbsee 
[02:46] <Hobbsee> anyone awake?
[02:46] <StevenK> Nope.
[02:46] <Hobbsee> awww
[02:46] <Hobbsee> there's supposed to be a meeting in 15, iirc.
[02:47] <StevenK> You're right. Now I remember.
[02:47] <lucas> a MOTU meeting ?
[02:47] <Hobbsee> yes
[02:49] <TheMuso> Well clamav is not exactly something I'm interested in, so planning to sleep still goes ahead.
[02:59] <StevenK> persia: I've *gasp* set up sbuild + LVM snapshots.
[03:00] <TheMuso> Ok... What does one do with a merge, if Debian has modified the orig tarball, causing its MD5 to be different, even though the orig tarball version is still the same?
[03:01] <Hobbsee> TheMuso: fakesync, or put the debian changes into the ubuntu version
[03:01] <Hobbsee> depends if it's a merge or sync
[03:01] <TheMuso> Hobbsee: Merge.
[03:01] <TheMuso> ...and how does one fakesync?
[03:01] <Hobbsee> right.  take ubuntu's, add debian's changes as applicable
[03:01] <TheMuso> I haven't had to do that as yet...
[03:02] <Hobbsee> that's effectively a fakesync
[03:02] <TheMuso> I was hoping it wouldn't come to that.
[03:02] <TheMuso> Hobbsee: Right.
[03:02] <persia> StevenK: Great news!  How does your experience compare with pbuilder?
[03:02] <Hobbsee> ie, take out any changes that ubuntu doesnt need, add debian's, add the final changelog entry, upload
[03:02] <StevenK> persia: It's ... different. And harder to debug.
[03:02] <TheMuso> Well, this will be fun. Its one of those insane source packages, that puts a tarball inside the source package dir.
[03:02] <StevenK> Yummy!
[03:02] <Hobbsee> ooh, yummy!
[03:03] <StevenK> persia: Crazy person.
[03:03] <bluekuja> persia, heya
[03:03] <bluekuja> persia, I've just made a debdiff for gpixpod issue
[03:04] <persia> bluekuja: Great!
[03:04] <bluekuja> persia, ;)
[03:04] <StevenK> TheMuso: I do a fakesync by checking that the orig's contain the same files and that the package will build with the Ubuntu orig. Make sure the .dsc references the Ubuntu orig, generate a changes file and upload it.
[03:05] <TheMuso> StevenK: Right.
[03:06] <TheMuso> persia: Good idea.
[03:06] <persia> TheMuso: Why?
[03:06] <persia> (about embedded tarballs)
[03:07] <TheMuso> persia: Because they make things like this just that bit more difficult to work around.
[03:07] <TheMuso> And its just weird.
[03:07] <Hobbsee> TheMuso: just make sure you dont miss.
[03:07] <TheMuso> Yeah I know.
[03:07] <persia> TheMuso: Ah.  When torcs used to do that, I liked it because the patches were very easy to manage, but I can see the counter-argument as well.
[03:08] <bmm> zakame: you online? Could you elaborate on your comment on http://revu.tauware.de/details.py?upid=5511 and would you advocate if I change the changelog entry?
[03:15] <StevenK> Hrm. When does the meeting start?
[03:16] <geser> StevenK: 15 min ago officially
[03:16] <persia> StevenK: It started 15 minutes ago, but it's not moving every quickly :)
[03:16] <StevenK> Heh
[03:24] <Hobbsee> motu meeting
[03:24] <zakame> heya
[03:24] <Hobbsee> hiya zakame!
[03:25] <zakame> meeting?
[03:28] <TheMuso> Ok. The orig tarball does have another tarball inside, but when I unpack both the sid and gutsy versions, even though both orig tarballs have a different MD5, there is no difference in their contents. Turns out the last change was added as a patch...
[03:28] <TheMuso> Just bloody great.
[03:29] <zakame> bmm: "initial release" tends to get buried below more recent changelog entries (and hence, future (and eventual) package updates.)  Documenting every sensible change that you made against the original sources from the start is good practice, because you never know who will be looking at your package, 2 days or 2 months from now.
[03:30] <bmm> zakame: so you would be willing to advocate the package if I change the changelog? Do you have any other comments?
[03:31] <zakame> bmm: and if it builds cleanly, yes :)
[03:31] <bmm> zakame: doesn't it??
[03:33] <bmm> zakame: if you have/find problems with building, please post a comment. I'll do an upload with the new changelog somewhere this weekend (can'
[03:33] <bmm> (can't do it right now)
[03:37] <zakame> bmm: it's ok now, but that doesn't mean the next upload will be; verification (hopefully) is made at every iteration :)
[03:38] <TheMuso> Night folks.
[03:39] <bmm> zakame: sure, well, I'll ping everybody when I've got the new changelog entry in.
[03:40] <zakame> bmm: cool :D
[03:40] <zakame> gn8 TheMuso
[03:41] <soc> i have a question about packaging gimp ... should i wait until the meeting is over?
[03:42] <Hobbsee> shoot
[03:42] <soc> ok
[03:42] <soc> sudo debuild:
[03:42] <soc> dpkg-checkbuilddeps: Build conflicts: libgimp2.0
[03:42] <StevenK> You shouldn't need to run debuild as root.
[03:42] <soc> i don't really understand the error message ...
[03:43] <soc> without sudo i get:
[03:43] <StevenK> A Build-Conflict is something that must not be installed for the package to build.
[03:43] <soc> problem running fakeroot
[03:43] <StevenK> Is fakeroot installed?
[03:43] <soc> stevenk: so i can't have gimp installed if i want to build a newer version?
[03:43] <StevenK> It seems you can't have libgimp2.0 installed.
[03:43] <soc> i thought i wouldn't need fakeroot ...
[03:44] <DarkSun88> Hi all
[03:44] <StevenK> You need fakeroot. You like fakeroot. You must have fakeroot.
[03:44] <StevenK> Or something.
[03:44] <soc> ok :-)
[03:44] <zakame> lolfakeroot
[03:44] <BlueDevil> is gaim compiled without sasl support intentionally?
[03:44] <soc> so do i need to set something up with pbuilder or will fakeroot be enough?
[03:45] <man-di> soc: if you dont wanna deinstall libgimp2.0 go with pbuilder
[03:45] <man-di> soc: fakeroot is just a way to fake root,
[03:45] <soc> omg ... pbuilder is such a mess ...
[03:45] <geser> soc: fakeroot will be enough but pbuilder has the advantage that you don't have to install the build-depends
[03:46] <man-di> soc: pbuilder is soooo easy
[03:46] <soc> it wants do download packages i already have on the system and it takes ages to run the first time+
[03:46] <man-di> geser: fakeroot is only enough when he deinstalls libgimp2.0
[03:46] <soc> i already gave up 4 times because i wanted to go to bed an pbuilder ran the whole day ...
[03:47] <geser> in this case you are right, I was more general
[03:47] <soc> mh ok
[03:47] <soc> i will try once again ...
[03:48] <soc> why does pbuilder want to download things i have already installed?
[03:48] <soc> it downloads things like adduser, alsa-base, alsa-utils, apt, etc ...
[03:48] <soc> i already have that
[03:49] <geser> it needs those packages to create a chroot
[03:49] <man-di> soc: it more or less installs its own system
[03:49] <man-di> soc: so you are completely independant from your work system
[03:50] <man-di> soc: its a pretty minimal system
[03:50] <soc> but why doesn't it use already available debs for that?
[03:50] <man-di> soc: just for building packages
[03:50] <soc> it wouldn't even need root to access them
[03:50] <soc> yes i understand that
[03:50] <soc> but why does it download things twice?
[03:51] <soc> another question:
[03:51] <soc> i have a amd64 and a i386 machine
[03:51] <man-di> so because it needs a ubuntu mirror to get the debs and /var/cache/apt/archives is no mirror
[03:51] <soc> should i setup both
[03:52] <soc> or is there a possibilty to use the amd64 for both?
[03:52] <man-di> soc: its possible to do both on amd64
[03:52] <soc> mh ok
[03:52] <soc> is there anything special about that?
[03:52] <soc> or can i just say pbuilder create?
[03:53] <man-di> soc: never did that with pbuilder, just with normal chroots
[03:54] <soc> what about building packages with dh_make?
[03:54] <soc> is this different?
[03:54] <StevenK> dh_make doesn't build packages
[03:55] <geser> soc: https://wiki.ubuntu.com/PbuilderHowto has an item how to create a i386 pbuilder on amd64
[03:55] <man-di> soc: dh_make creates only some template files
[03:55] <soc> ok it converts source archives into debian package souces ...
[03:56] <man-di> soc: if you do all right zou can build the debian package on both (and more) archs
[03:56] <man-di> from the same debian package source
[03:58] <soc> ok ...
[03:59] <infinito> anyone to review this? http://revu.tauware.de/details.py?upid=5532
[04:12] <statik> anyone feel like re-reviewing python-coverage package? Just added debian/README.Debian-source this time http://revu.tauware.de/details.py?upid=5545
[04:18] <zakame> statik: cool, lemme check
[04:20] <zakame> statik: 'Fixes from REVU' in your debian/changelog may mean anything; document your initial changes as much as you can, so anyone else looking at your pkg (or you, 2 months from now, and updating this to a new version) will understand at a glance what changes happened
[04:21] <statik> zakame: this is a new package I made
[04:21] <statik> zakame: there is no previous version
[04:22] <zakame> statik: nevertheless, there are initial changes, like the addition of setup.py
[04:23] <statik> zakame: I see. so there should be one changelog entry for the initial release, but it should explain that I added setup.py.
[04:23] <zakame> yes
[04:25] <statik> zakame: thanks for your help. anything else it needs to say besides "added setup.py" ?
[04:25] <soc> hi
[04:25] <soc> one question:
[04:26] <soc> how can i change the install directory with debuild
[04:26] <soc> i want a package currently installing tu /usr/bin to install to /opt or something ..
[04:26] <zakame> statik: mention the README.Debian-source note as well
[04:26] <soc> problem is, debuild runs configure for me, i have no idea how to pass arguments ..
[04:27] <statik> zakame: ok, done. uploading now
[04:27] <zakame> soc: look into your debian/rules
[04:27] <Hobbsee> soc: you want to pass the arguments inside the package - ie, in debian/rules.  not in debuild.
[04:28] <soc> ok that seems to be quite complicated
[04:29] <soc> what do i have to change?
[04:29] <soc> www.ubuntuusers.de/paste/11772
[04:32] <soc> this is the bim package
[04:32] <soc> i updated it to 2.3.18 ...
[04:32] <soc> now i want to:
[04:32] <soc> - rename the hole packages to gimp-2.3
[04:32] <man-di> soc: DEB_CONFIGURE_PREFIX := /opt
[04:32] <man-di> vim debian/control
[04:32] <soc> - install them to /osr/local or something ...
[04:33] <soc> do i have to add or change that=
[04:33] <soc> what about line 87
[04:33] <soc> the path is hardcoded there ...
[04:33] <Riddell> stgraber: ipng
[04:33] <Riddell> ping
[04:34] <Riddell> stgraber: for miniracer I see binary files (pak0.pak, maps/*bsp), what are those file types and are those the prefered modified form?
[04:35] <infinito> is there any problem with a FreeBSD license?
[04:36] <raphink> anyone knows what apt-mark is for?
[04:36] <man-di> infinito: depends on what FreeBSD license, 3 or 4 clauses
[04:38] <infinito> man-di: it's not exactly freebsd, but freebsd like... http://pastebin.ca/568395
[04:38] <soc> man-di?
[04:38] <soc> do i have to add that?
[04:38] <soc> beginning, end?
[04:38] <soc> and what about line 87
[04:40] <man-di> soc: add it
[04:40] <man-di> soc: you should really read the maintainer guide instead of asking so questions here
[04:41] <geser> raphink: it's looks like to tool to mark packages as auto-installed or not
[04:41] <raphink> ah
[04:41] <raphink> thanks geser
[04:41] <soc> is there a guideline how to rename libgimp2.0?
[04:42] <soc> libgim2.0-2.3?
[04:42] <soc> someting like that?
[04:46] <soc> man-di: where is the maintainer guide?
[04:46] <man-di> soc: http://www.debian.org/devel/ has many infos
[04:46] <man-di> policy, maintainer-guide, etc.
[04:48] <soc> ok thx
[04:49] <soc> is there a way to rename a package with a script?
[04:49] <man-di> soc: no
[04:49] <man-di> soc: use your favorite text editor
[04:50] <azeem> soc: for libraries, see http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html
[04:50] <soc> hwatever i do, i get dpkg-source: cannot represent change to debian/foobar: binary file contents have changed
[04:50] <soc> i have renamed everything in debian/control and the files in debian/
[05:01] <soc> i just wonder ...
[05:02] <soc> comparing it to the loved/hated checkinstall ... it's possible with checkinstall to change the package name through the ui without any problems, which program does it use for that?
[05:03] <soc> there has somewhere to be some code for renaming packages ...
[05:03] <Hobbsee> ew, ew, ew, wtf are you trying to do?
[05:03] <soc> i just try to change the name of a package
[05:03] <Hobbsee> in debian/control
[05:03] <soc> yeah i already had that ...
[05:03] <soc> nothing worked after that
[05:03] <Hobbsee> because...?
[05:03] <Hobbsee> !doesnt work
[05:04] <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:04] <man-di> soc: you need to delete debian/OLDPACKAGENAMES
[05:04] <geser> Hobbsee: he tries to create a gimp-2.3 package which is coinstallable with gimp from the archive
[05:04] <man-di> soc: or do the renaming from a clean package
[05:04] <Hobbsee> ahhh....
[05:04] <soc> dpkg-source: cannot represent change to debian/foobar: binary file contents have changed
[05:04] <Hobbsee> have you chagned things outside the debian/ dir?
[05:05] <man-di> soc: you need to delete debian/OLDPACKAGENAMES
[05:06] <zakame> gn8 all :)
[05:06] <soc> ok, i just killed the hole gimp-2.3.18 dir
[05:07] <soc> i have the gimp.2.3.16 dir, should i run uupdate again to create a new 2.3.18 directory?
[05:08] <AndyP> i'm just looking at the music-applet merge on MoM - there was a 2.1.0-0ubuntu1 package made for ubuntu which hasn't been updated since it was created and now 2.2.0-1 is in debian, i'm tempted to just request a sync because according to the changelog there aren't any changes in ubuntu that aren't in debian, does a sync request sound appropriate?
[05:08] <man-di> soc: why did you delete everything?
[05:08] <man-di> soc: I told you what to do
[05:08] <soc> because i'm frustrated ...
[05:08] <soc> sorry
[05:08] <soc>  i thought it would be cleaner to start over
[05:08] <soc> i messed too much withit
[05:08] <soc> sudo debuild
[05:08] <soc> debuild with fakeroot
[05:08] <soc> pbuilder
[05:09] <soc> checkinstall ...
[05:09] <Hobbsee> well, if you used checkinstall, no wonder it died....
[05:09] <Hobbsee> debuild is just a wrapper aroudn pbuilder nad such.
[05:09] <Hobbsee> er, no it's not
[05:09] <soc> no this was after everything went wrong
[05:09] <Hobbsee> around dpkg-buildpackage, i meant
[05:09] <Hobbsee> did you modify outside debian/ ?
[05:09] <soc> ok i have a fresh gimp-2.3.18
[05:09] <soc> no
[05:10] <soc> www.ubuntuusers.de/paste/11773
[05:10] <soc> that's the original file
[05:10] <soc> should line 1 stay as it is?
[05:14] <Hobbsee> soc: are you trying to get it into the ubuntu repository?
[05:15] <soc> no
[05:15] <Hobbsee> right
[05:15] <Hobbsee> is this a private package, or what?
[05:15] <soc> just want to package it for myself and some frinds
[05:15] <Hobbsee> right
[05:15] <Hobbsee> soc: does it need to be coinstallable?
[05:16] <soc> yes, because i don't want to cause breakage if something gets updated
[05:16] <soc> for instance hole xsane seems to depend on the right version
[05:16] <Hobbsee> "right version"?
[05:16] <soc> don't no ...
[05:17] <soc> i got it to build without the name change but that broke xsane
[05:17] <soc> xsane wants gimp <= 2.3.17 or something like that
[05:17] <soc> some people just want to try out gimp 2.3, they don't want to have gimp 2.2 replaced by it
[05:17] <Hobbsee> libgimp2.0 (>= 2.3.16)
[05:18] <azeem> libgimp2.0 (<< 2.3.17)
[05:18] <Hobbsee> oh i see
[05:18] <azeem> you'd need to recompile the reverse-deps, I guess
[05:18] <soc> so it exactly wants 2.3.17
[05:18] <azeem> .16
[05:18] <Hobbsee> it wants exactly 2.3.16
[05:18] <soc> sorry, xyes
[05:18] <soc> i meant that :-)
[05:19] <soc> i just want to name it different so that dpkg doesn't want to upgrade the old package to it
[05:19] <soc> and put it in another directory
[05:20] <Hobbsee> ahhh
[05:20] <Hobbsee> azeem: i doubt the current version fo xsane will cope with the older version of gimp anyway?
[05:22] <Hobbsee> soc: basically, you need to rename the source and binary packages in debian/rules to $oldname-2.2 or soemthing, update all the references inside debian/ to be version 2.2, where they say 2.3, and try it.  and add conflicts/replaces to the standard gimp packages
[05:24] <Hobbsee> persia: oh, point. 
[05:24] <Hobbsee> okay, ditch the conflicts/replaces
[05:25] <Hobbsee> i guess if it's a different source package, it would stay indefinetly
[05:25] <persia> soc: You might want to add something extra to the soname as well, just to make sure regular GIMP works properly at the same time.
[05:27] <soc> why 2.2?
[05:28] <soc> i want to build packages of gimp 2.3 for feisty, feisty has gimp 2.2, so i don't want to overwrite that -> i thought i rename the gimp 2.3.18 package to gimp-2.3 so it can coexist
[05:29] <Hobbsee> oh right...
[05:29] <Hobbsee> s/2.3/2.2/ and s/2.2/2.3/ for what i said
[05:29] <soc> :-)
[05:29] <Hobbsee> seeing as i thought you were going the other way
[05:29] <Hobbsee> woudl have thought there would have been a backport for the later gimp
[05:30] <Hobbsee> which you could then just remove, and force install the older one.
[05:30] <soc> no, i just want to have an easy to install/update package of gimp-2.3 for feisty
[05:31] <soc> so i thought using the package manager is the right way instead of distributing compiled archives
[05:31] <bluekuja> Hobbsee, I used to add a dpatch system to add patches to fix some bugs. If the package doesnt have a patch system already, is bad to *add* it?
[05:32] <AndyP> seems that debian is waiting for 2.4 to be released before they package a newer gimp http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322568
[05:32] <ubotu> Debian bug 322568 in gimp "Please package gimp 2.3/2.4" [Wishlist,Open]  
[05:32] <Hobbsee> bluekuja: no, it's good - often the package will need more bugs fixed via patches, etc.
[05:32] <Hobbsee> AndyP: that doesnt help feisty and coinstallable packages, though
[05:32] <AndyP> Hobbsee: i know, just a point of interest
[05:32] <azeem> 2.3 packages are in experimental I think
[05:32] <Hobbsee> :)
[05:33] <bluekuja> Hobbsee, so it's ok to add dpatch system (also if package did not have it already)
[05:33] <Hobbsee> bluekuja: yep
[05:33] <bluekuja> Hobbsee, thanks ;)
[05:34] <AndyP> i was told not to add a patch system if there wasn't already one, to reduce the debian delta (yet another point of information :) )
[05:34] <AndyP> s/reduce/minimise/
[05:34] <azeem> bluekuja: are there patches already in the .diff.gz directly?
[05:34] <bluekuja> azeem, if I add them, of course they will appear in the diff
[05:35] <azeem> bluekuja: "already"
[05:35] <bluekuja> azeem, nope
[05:35] <azeem> ok
[05:35] <bluekuja> azeem, ;)
[05:47] <statik> dholbach: could I convince you to take another quick glance at http://revu.tauware.de/details.py?upid=5545? your initial review was quite helpful, I've also addressed comments from a couple of other people
[05:49] <soc> i'm trying dh_make at the moment ...
[05:50] <Hobbsee> soc: with [01:31]  <soc> so i thought using the package manager is the right way instead of distributing compiled archives <-- do i want to know how you were goign to create those compiled archives?
[05:51] <pochu> statik: you might want to add '  Homepage:' to the description in debian/control...
[05:52] <soc> hobbsee: compile them, and put them in a tar.bz
[05:52] <soc> but dh_make at least creates a working control file for me ...
[05:52] <Hobbsee> so apt would have complained, and tried to update them
[05:52] <statik> pochu: ok, I will do that
[05:53] <pochu> statik: if you add it, note that it's indented with 2 spaces, rather than one.
[05:55] <statik> pochu: ah, thank you. yes, I agree this should be added, then it will show up in the package description, right?
[05:55] <pochu> right.
[05:57] <statik> pochu: done, built a new source package, and uploaded
[05:58] <soc> how can i tell debuild to install the package to a different directory if DEB_CONFIGURE_PREFIX := /opt doesn't do anything?
[05:59] <pochu> statik: you can put a blank line between the description and the homepage, ' .'
[05:59] <pochu> So the Description is clearer :)
[05:59] <pochu> (Sorry for not mentioning it before)
[05:59] <azeem> soc: did you check that DEB_CONFIGURE_PREFIX is honored by the build system?
[06:00] <soc> no, how do i do that=
[06:00] <statik> pochu: I tried that at first, agree it looks nicer. If I have a blank line, then dpkg-source complains about a syntax error in the control file: continued value line not in field
[06:00] <pochu> Hmm
[06:01] <pochu> statik: the blank line in the control file should be an space and a dot: ' .'
[06:01] <statik> aha
[06:01] <soc> is there maybe a chace to tell debuild NOT to run configure?
[06:01] <pochu> It will become a blank line in apt, though :)
[06:01] <azeem> soc: debuild doesn't run configure, the debian/rules rules do 
[06:02] <infinito> hey MOTUs, easy to review here ;) http://revu.tauware.de/details.py?upid=5532
[06:02] <statik> pochu: perfect. that did the trick. built and uploaded
[06:02] <soc> yes so how tell i debian/rules that it should install it to /usr/local or something?
[06:02] <pochu> Cool :)
[06:02] <statik> pochu: thanks for your help :)
[06:02] <azeem> soc: you don't tell it, you modify it to your taste
[06:03] <soc> in rules there is a line with ./configure
[06:03] <pochu> statik: btw, I'm not a MOTU, so I can't advocate it, sorry :)
[06:03] <soc> would it be enough to modify that?
[06:03] <statik> pochu: it's ok, this is my first package so I'm just glad for everyone who is helping me get it right
[06:04] <pochu> :)
[06:05] <pochu> statik: Maybe remove 'The original version was written by Gareth
[06:05] <pochu> + Rees. Ned Batchelder has updated it to determine executable statements
[06:05] <pochu> + more accurately.
[06:05] <pochu> From the description?
[06:05] <pochu> I don't think that's useful at all to know what the module is for...
[06:07] <statik> pochu: ok, removed those
[06:07] <soc> ok, now it compiles ...
[06:07] <soc> one big fat package named gimp-2.3 installing to /usr/local
[06:08] <dholbach> statik: sure
[06:08] <soc> i just wonder if there is maybe a plugin for netbeans or eclipse which would help with the configuration and packaging ...
[06:09] <azeem> soc: doubt it
[06:09] <statik> dholbach: awesome. I just did an upload about 2 minutes ago removing those lines that pochu suggested
[06:09] <soc> hm
[06:10] <dholbach> rock on
[06:10] <soc> i think it's quite bad if there are so many different ways to create a package ...
[06:10] <pochu> statik: I think you can move the python build-dependency to 'Build-Depends-Indep'
[06:11] <soc> checkinstall, from scratch, dh_make, normal ./configure && make, pbuilder fakeroot, etc. ... many things with overlapping areas of responsibility
[06:11] <azeem> soc: all that matters is policy
[06:11] <soc> everything above in my opinion of course
[06:12] <pochu> statik: lintian output: W: python-coverage: script-not-executable ./usr/share/python-support/python-coverage/coverage.py
[06:12] <soc> so maybe we need a normative implematation ...
[06:12] <azeem> soc: people have their personal preferences
[06:12] <pochu> statik: so either chmod +x it, or remove the hashbang :)
[06:13] <statik> pochu: hmm, I thought I had silenced that one
[06:13] <soc> sometimes the documentation is not useful ...
[06:13] <pochu> statik: you can chmod +x it in debian/rules, so don't miss that again in any future repackaging
[06:14] <soc> there are nice explainations what individual tools do, but no chance to get an overview over your possibilities ...
[06:14] <soc> and i was acustomed that one program does just ONE thing
[06:14] <soc> i expected to do a ./configure && make and then soemthing to package it
[06:15] <soc> but instead debuild does all 3 things
[06:15] <statik> pochu: forgive my ignorance, but I am using a very simple debian/rules, just using cdbs. Do you know how I could hook in a chmod +x in debian/rules?
[06:15] <soc> so i didn't really understand how things worked
[06:15] <azeem> soc: debuild is a front-end
[06:15] <azeem> pbuilder does even more than debuild
[06:16] <dholbach> statik: I'm happy with it
[06:17] <soc> azeem: yes, but how should i know it?
[06:17] <soc> there is absolutely no documentation that says:
[06:17] <azeem> soc: I don't know.
[06:17] <soc> pbuilder doesn't adhere to UNIX' principle of one job, one program
[06:18] <soc> that would have helped significantly
[06:18] <statik> dholbach: thanks! what about moving python build-dependency to 'Build-Depends-Indep', and the script-not-executable warning, are those important?
[06:18] <dholbach> you need it as a Build-Depend
[06:18] <soc> you have to know all tools before you even learned them
[06:18] <statik> ok
[06:18] <pochu> statik: I know with debhelper, not with CDBS :)
[06:19] <statik> soc: I found that there is a steep learning curve at first, but later on the tools are extremely efficient
[06:19] <soc> yes, but imo it would be nice to write in the documentation right at the beginning:
[06:20] <azeem> soc: send patches, I guess
[06:20] <soc> debuild runs configure and make by itself, you don't need to run it manually
[06:20] <soc> that would have saved me approx. 4 hours
[06:20] <dholbach> statik: you could patch out the hashbang line
[06:20] <dholbach> from what I saw it doesn't seem to be needed
[06:20] <azeem> soc: as I said, debuild doesn't run configure
[06:20] <dholbach> so you could ask upstream to remove it
[06:21] <azeem> soc: it just happens that configure gets run by the gimp source package's debian/rules, this has nothing to do with debuild
[06:21] <soc> azeem: ok, but practically you type in debuild and you see that configure runs in your terminal, then make
[06:22] <azeem> soc: are you sure this is true for every package?
[06:22] <azeem> because otherwise it would not make sense to write it into the documentation
[06:22] <soc> i have yet to see a package whixh works different
[06:22] <soc> but ok
[06:22] <azeem> packages which don't include a configure might work different
[06:22] <statik> dholbach: it seems like upstream has tried to make this work as both a module and a directly executable script, as they have option parsing, etc. in there
[06:22] <soc> i don't no how those kde do that
[06:22] <soc> cmake etc
[06:22] <dholbach> ah ok
[06:22] <dholbach> statik: no problem to patch it out then
[06:23] <statik> cool
[06:24] <soc> maybe: debuild will run commands in debian/rules, often configure and make (YMMV), so usually you should not run them manually.
[06:24] <soc> damn ... 
[06:24] <soc> compilation fails ...
[06:25] <soc> collect2: ld returned 1 exit staus
[06:25] <soc> status
[06:26] <statik> dholbach: ok, now patching out hashbang. uploaded the new one.
[06:27] <dholbach> rock and roll
[06:27] <statik> dholbach: oh, I accidentally typed 'dput blah.changes' instead of 'dput revu blah.changes', and it uploaded to upload.ubuntu.com. Will that cause a problem?
[06:27] <dholbach> no it will be just rejected
[06:28] <statik> yay for safety belts
[06:28] <soc> www.ubuntuusers.de/paste/11775
[06:28] <dholbach> :-)
[06:28] <soc> someone has an idea why it fails?
[06:28] <statik> I've never been so happy to be rejected
[06:28] <dholbach> hehe :)
[06:29] <dholbach> statik: did you re-upload to revu?
[06:29] <statik> this whole motu channel rocks, it's great to get such good help from people
[06:29] <statik> dholbach: yes
[06:29] <dholbach> any second to approve http://revu.tauware.de/details.py?upid=5545 so we can get it uploaded?
[06:32] <pochu> I would, but I can't ;)
[06:33] <Hobbsee> dholbach: you've checked building, installability, licencing, python stuff on it?
[06:33] <Hobbsee> codewise looks fine to me - but python is not my strong point
[06:34] <dholbach> yes, but best if you look at it too :-)
[06:35] <dholbach> *nod*
[06:35] <Hobbsee> dholbach: i'm happy to ack if you've checked for all the other bits, as mentioned above
[06:35] <dholbach> ok
[06:35] <Hobbsee> it'll sit in NEW forever, though
[06:35] <dholbach> let's see about that ;-)
[06:35] <soc> azeem: do you have an idea why it fails?
[06:36] <azeem> because there are unresolved symbols
[06:36] <azeem> why that is, no idea
[06:37] <Hobbsee> dholbach: ack'd.
[06:37] <Hobbsee> dholbach: unless you sweet talk them.
[06:38] <dholbach> sweet talk?
[06:38] <Hobbsee> persuade them
[06:38] <statik> Hobbsee, dholbach: thank you!
[06:38] <Hobbsee> dholbach: please upload, send mail, etc
[06:40] <dholbach> statik: congratulations to your first uploaded package to the archive!
[06:40] <soc> azeem: maybe i'm missing a dependency?
[06:40] <azeem> maybe
[06:40] <soc> but that should told me configure before ...
[06:40] <soc> wierd ...
[06:41] <azeem> no, not if configure has a bug
[06:41] <soc> is there a special way to handle python things?
[06:43] <soc> azeem: it seems that creating the right configuration files in debian/ is hard, but updating with new sources is easy ...
[06:43] <azeem> that's correct
[06:46] <infinito> anybody wanna help me?? http://revu.tauware.de/details.py?upid=5532
[06:53] <ceros> is it ok to upload packages to REVU while you wait for them to get accepted in Debian?
[06:56] <Hobbsee> ceros: yes, but it's easier just to request a sync for them, before the new package freeze
[06:57] <ceros> ok
[06:57] <Hobbsee> ceros: as it'll take ages thru our NEW queue too - but will take less time to go thru the NEW queue ifit's straight from debian
[06:58] <ceros> ok
[07:00] <soc> dh_make generates a debian/rules with deprecated things in it ... is that wanted?
[07:00] <soc> dh_python
[07:11] <soc> is dh_pysupport /usr/local/lib/gimp recursive?
[07:12] <soc> or will it just lokk in gimp, but not in gimp/*?
[07:22] <soc> someone=
[07:24] <azeem> did you check the documentation or looked in the implementation?
[07:26] <soc> yes
[07:27] <soc> www.ubuntuusers.de/paste/11776
[07:27] <soc> these are my rules (dh_make)
[07:28] <soc> and this is the original:
[07:28] <soc> www.ubuntuusers.de/paste/11777
[07:32] <shawarma> soc: You should never install anything in /usr/local from a .deb.
[08:30] <leonel> I have a  tar.gz   
[08:31] <leonel> is there a  ubuntu  howto   to make  a  new deb  for that  tar.gz
[08:31] <leonel> found it  
[08:35] <xxxxx1> leonel: check packagingguide
[08:35] <pochu> !packagingguide
[08:35] <ubotu> The packaging guide is at http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html - See https://wiki.ubuntu.com/MOTU/Packages/New for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/DeveloperResources - See also !backports
[08:36] <leonel> great !  
[09:35] <man-di> lionel: ping
[09:35] <lionel> pong man-di
[09:37] <man-di> lionel: do you want to sync libapache-mod-jk from debian unstable now?
[09:38] <man-di> lionel: I wanna do a new upload removing apache1 support for debian
[09:39] <lionel> hum... I can't sync myself, but we should sync from Debian yes (I think we don't need anymore to switch from gcj to kaffe)
[09:40] <lionel> concerning droping apache1 modules, I would like to discuss for a Ubuntu consensus
[09:40] <lionel> I'll send a mail on -devel
[09:40] <lionel> I should have take care of it this week. my bad
[09:48] <man-di> lionel: my idea was that ubuntu syncs now, debian goes forward and then ubuntu can decide if it wants to follow or not
[09:49] <lionel> man-di: ubuntu-archive won't sync before monday now...
[09:50] <lionel> or I merge it with this change now (gcj -> kaffe) and we'll see next week what to do with apache1 package
[09:50] <man-di> lionel: -2 in debian uses gcj
[09:50] <man-di> lionel: the only difference should be the changelog to ubuntu
[09:51] <lionel> man-di: in Ubuntu we use kaffe
[09:52] <man-di> lionel: huh?
[09:52] <man-di> debian used kaffe in the past
[09:52] <lionel>   * Merge from Debian unstable. Remaining Ubuntu changes:
[09:52] <lionel>     - Change workers.tomcat_home to tomcat5, and point java_home to kaffe in
[09:52] <lionel>       debian/workers.properties. 
[09:52] <lionel>     - debian/control: Change Maintainer/XSBC-Original-Maintainer field.
[09:52] <lionel> the last changelog for gutsy
[09:52] <man-di> oh
[09:52] <man-di> lionel: Why?
[09:54] <lionel> man-di: because it works  (tm) :)
[09:54] <man-di> gcj doesnt?
[09:54] <man-di> after all gcj is the standard jvm in ubuntu currently
[09:54] <lionel> we had a problem in the past and kept this change
[09:55] <man-di> what was the problem?
[09:55] <lionel> I don't remember :(
[09:55] <man-di> in debian it works with gcj just great
[09:56] <lionel> https://bugs.launchpad.net/ubuntu/+source/libapache-mod-jk/+bug/34863
[09:56] <ubotu> Launchpad bug 34863 in libapache-mod-jk "Dapper: libapache2-mod-jk refers to tomcat4 and j2sdk1.4-sun" [Medium,Fix released]  
[09:56] <lionel> that leads to this change
[09:56] <lionel> yeah
[09:57] <man-di> so there was never a reason not to use gcj
[09:57] <lionel> man-di: upload you package, i'll fill a sync request once it's uploaded
[09:58] <man-di> its in debian since some days
[09:58] <lionel> yeah, I know, but the release withour apache1 modules
[09:58] <man-di> so you dont care about syncing -2?
[09:58] <lionel> no, we can jump this release
[09:59] <man-di> okay
[09:59] <man-di> I'm fine, I just wanted to make sure I dont uploaded new stuff before we spoke about the old stuff
[09:59] <lionel> yes, again, sorry, I should have take care of this this week
[10:00] <lionel> hi bashelier :)
[10:00] <bashelier> hey lionel!
[10:00] <bashelier> sup? :)
[10:01] <lionel> sup?
[10:03] <bashelier> lionel: what's up if you prefer ;)
[10:04] <lionel> oh. Week-end is there, so, it's fine :)
[10:05] <SlimG> Is it possible to make    dpkg-deb --build   automatically chown the files it archives to root ?
[10:06] <man-di> SlimG: dpkg-buildpackage does that for you
[10:07] <man-di> SlimG: when building debian packages from source, dont use dpkg-deb --build
[10:08] <SlimG> man-di: I'm using dpkg-deb -b for closed source apps, thanks for your help!
[10:08] <bashelier> hey man-di :)
[10:08] <bashelier> thanks a lot for the upload ;)
[10:11] <man-di> SlimG: then you are on your own, dpkg-deb --build just puts some existing files into a deb, nothing else
[10:11] <man-di> SlimG: perhaps you can get this to work with using fakeroot
[10:14] <dmb> can someone tell me why this is happening?
[10:14] <dmb> in lintian, it is saying this:
[10:14] <dmb> E: inspircd: file-in-etc-not-marked-as-conffile /etc/init.d/inspircd
[10:14] <dmb> and in debian/conffiles
[10:14] <dmb> etc/init.d/inspircd
[10:14] <dmb> is in it
[10:14] <SlimG> man-di: fakeroot chown root:root <package> -R didn't work
[10:16] <man-di> SlimG: fakeroot bash
[10:16] <man-di> SlimG: then chown root:root ... ; dpkg-deb -b .... inside 
[10:16] <man-di> then exit
[10:17] <man-di> and you should have got a deb with the right owners of the files inside
[10:17] <man-di> SlimG: the issue is that you loose the infos about chowned files when exiting fakeroot
[10:18] <dmb> its debian/conffiles that lists the configuration files right?
[10:21] <SlimG> man-di: I'm writing this into a script, won't the "fakeroot bash" put the script off?
[10:22] <Bassetts> if i can reproduce a bug should i mark it confirmed?
[10:23] <SlimG> man-di: figured it out using bash -c "command" param, thanks for all your help
[10:24] <DktrKranz> Bassetts, yes
[10:24] <DktrKranz> if you can, add as much informations as you can
[10:25] <Bassetts> ok
[10:26] <DktrKranz> which bug are you after?
[10:28] <Bassetts> 107370
[10:28] <Bassetts> someone in ubuntu-bugs is helping me out =)
[10:29] <DktrKranz> good :)
[10:52] <tsmithe> any motus about?
[10:52] <tsmithe> anyone wanna sponsor an update to a package of mine?
[10:53] <tsmithe> the url on revu is http://revu.tauware.de/details.py?upid=5558
[10:55] <tsmithe> i hope to include the functionality into asoundconf-ui <https://launchpad.net/asoundconf-ui/>
[10:55] <tsmithe> but i want this update to test the current functionality (which, to be honest, is quite minimal)
[11:14] <xxxxx1> bye all
[11:15] <geser> tsmithe: looking now at the debdiff
[11:16] <tsmithe> cool thanks
[11:16] <geser> your changelog is missing the entry for asoundconf-gtk (1.5.1-0ubuntu2)
[11:16] <tsmithe> it is?
[11:17] <geser> I'm just curious: is there a reason why you removed the first blank line from each entry?
[11:17] <geser> http://revu.tauware.de/revu1-incoming/asoundconf-gtk-0706151545/asoundconf-gtk-1.6/debian/changelog has 1.5.1-0ubuntu1 an then directly 1.6-0ubuntu1
[11:18] <geser> doesn't it need python-gtk2 anymore?
[11:19] <tsmithe> i didn't realise i was removing lines :)
[11:19] <tsmithe> (i'm not using dch)
[11:19] <tsmithe> and did i remove python-gtk2?
[11:20] <tsmithe> and, well, the first uploaded version was 1.5-1ubuntu5, i'm pretty sure, so i'm not sure the earlier ones are even necessary...
[11:21] <geser> http://members.ping.de/~mb/debdiff is the debdiff between the version in the archive and the version from revu
[11:22] <tsmithe> hmm that's really weird
[11:22] <tsmithe> i guess i'll put that back...
[11:31] <bmm> zakame: About the package that need another changelog line, would "Added a dpatch to make some tools/ shell scripts to use bash because of bashisms" be a good enough changelog line?
[11:31] <bmm> zakame: Oh, package I mean ccbuild http://revu.tauware.de/details.py?upid=5511
[11:33] <crimsun> bmm: "debian/patches/foo.dpatch: Use /bin/bash explicitly" would suffice
[11:33] <bmm> crimsun: thanks!
[11:33] <crimsun> (replacing "foo" as appropriate, of course ;)
[11:34] <bmm> hehe, sure
[11:34] <tsmithe> geser, http://revu.tauware.de/details.py?upid=5559
[11:35] <tsmithe> (thanks)
[11:40] <bmm> crimsun: If you have time, I've made the change and it's uploaded as http://revu.tauware.de/details.py?upid=5560
[11:42] <tsmithe> geser, scratch that :) got stuff to do yet ;)
[11:43] <bmm> Any MOTU: ccbuild is looking for advocates again after adding extra information to the changelog, please see http://revu.tauware.de/details.py?upid=5560
[11:46] <geser> tsmithe: so I shouldn't upload it?
[11:47] <crimsun> (we're discussing UI issues in query)
[11:47] <geser> ok
[11:47] <tsmithe> what he said :)
[11:48] <tobiasschulz> MOTUs: i'm lokking for advocated for my package: http://revu.tauware.de/details.py?upid=5552
[11:51] <geser> tsmithe: you stopped me 1 minute before I'd upload it
[11:51] <tsmithe> :)
[12:03] <tsmithe> do i need to use Build-Depends-Indep?
[12:04] <tsmithe> for my python applet which is arch-independent
[12:05] <tsmithe> geser, ^ ?
[12:05] <crimsun> yes
[12:05] <tsmithe> crimsun, ?
[12:05] <tsmithe> oops ok
[12:05] <crimsun> Build-Depends-Indep: python-all-dev, python-central (>= 0.5)
[12:06] <crimsun> e.g., ^
[12:06] <tsmithe> yep yep
[12:07] <geser> wouldn't python-all be enough if no python headers are needed?
[12:07] <crimsun> oh, in that case he wouldn't need B-D-I
[12:08] <tsmithe> hang on - do i need it then?
[12:08] <tsmithe> if i don't, then someone can upload http://revu.tauware.de/details.py?upid=5561
[12:09] <tsmithe> lintian seems to think i do...
[12:10] <tsmithe> this is the B-D line, "Build-Depends: debhelper (>=5.0), cdbs, python (>= 2.4), python-support (>=0.3), intltool, gettext"
[12:10] <crimsun> and you don't have b-a-i in debian/rules?
[12:11] <geser> cdbs
[12:11] <tsmithe> mm