[00:27] <maco> both authors and artists go in debian/copyright, right?
[00:29] <RAOF> maco: Anyone with copyright on files that you're distributing goes in debian/copyright.
[00:29] <maco> ok
[00:30] <RAOF> maco: There are quite frequently non-code files for which artists have copyright in packages we distribute; those files are treated no differently to code files.
[00:30] <maco> alright
[00:30] <dtchen> generally, if it's distributed, it needs to be documented.
[01:34] <jdong> oh audio gods, any hints on skype spinning a 2.4GHz core 2 duo and glitching sound in Jaunty?
[01:34] <jdong> in fact even totem seems to induce high CPU usage
[01:34] <jdong> I'd like to point my finger at pulseaudio?
[01:40] <mrooney> jdong: yeah, I have similar problems with skype :)
[01:42] <jdong> mrooney: yeah, it's kinda absurd a 2.4GHz modern CPU can't do videoconferencing without dying :)
[02:28] <vadi2> Hi. I have a question semi-related to packaging. Are configure.ac scripts in bash?
[02:28] <Snova> No.
[02:28] <Snova> They are technically M4, the macro language that Autoconf uses. (At least I'm 99% sure)
[02:29] <Snova> Autoconf basically runs M4 on configure.ac to produce configure.
[02:29] <vadi2> I see
[02:29] <vadi2> is the `which file` equivalent available in them?
[02:29] <Snova> Yes. You can write shell script in them directly.
[02:30] <vadi2> I need to fix a script to detect where a file path is hardcoded to instead locate it
[02:30] <vadi2> Alright, thanks
[02:30] <cjwatson> you should read 'info autoconf'
[02:30] <cjwatson> it's in the autoconf-doc package
[02:30] <lifeless> Snova: writing shell directly is usually the wrong thing to do though
[02:30] <cjwatson> there are macros specifically for finding programs
[02:31] <Snova> lifeless: Probably, but I don't use Autoconf, I just remember how it works. :)
[02:31] <cjwatson> for example, AC_CHECK_PROG
[02:31] <cjwatson> (or AC_PATH_PROG, or various others depending on exactly what you're doing)
[02:32] <vadi2> where can I find a list of AC_CHECK's?
[02:32] <vadi2> I need to find out where is dh_make on the system
[02:32] <cjwatson> 02:30 <cjwatson> you should read 'info autoconf'
[02:32] <cjwatson> 02:30 <cjwatson> it's in the autoconf-doc package
[02:32] <vadi2> Reading..
[02:34] <cjwatson> you might want to spend a bit of time figuring out how to use info if you aren't used to it; or the manual is on the web at http://www.gnu.org/software/autoconf/manual/index.html
[02:35] <vadi2> it's ok just want to fix one thing
[02:35] <cjwatson> autoconf is not easy to dip into unless you know it well; I really do strongly recommend familiarising yourself with it rather than trying to monkey-patch
[02:36] <cjwatson> you don't have to read it cover-to-cover, but you do need more of the basics than can be guessed
[02:36] <cjwatson> it's worth learning about for packaging purposes anyway
[02:37] <vadi2> well, fine, since this is for an app that makes packages I suppose that is necessary knowledge then
[02:38] <RAOF> You will undoubtedly at some point be required to patch someone's broken configure, so... ;)
[03:50] <mistya> I just installed ubuntu. it's fantastic! Thank's dev. Good Job
[04:04] <jdong> mistya: always great to hear happy users :)
[06:40] <dholbach> good morning
[07:08] <iulian> Good morning dholbach.
[07:10] <dholbach> hi iulian
[08:43] <Toadstool> good morning
[09:57] <verwilst> hellow!
[09:59] <verwilst> i've compiled the zabbix-1.6.3-1 deb, but it seems like the debconf zabbix-frontend-php/zabbix-server doesn't exist
[09:59] <verwilst> how can i check/add it?
[10:00] <verwilst> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522076 for more info
[10:01] <verwilst> i want to PPA it, so :)
[10:52] <goshawk> what is the command to generate manpages from program --help?
[10:53] <maxb> help2man? :-)
[10:54] <goshawk> maxb: thanks
[12:27] <directhex> hm. mythbuntu april fool's is a bit mean
[12:44] <Elbrus> directhex: does the deb do anything?
[12:44]  * Elbrus not living in the states and not on 64bits.
[12:44]  * Elbrus doesn't even have a tv
[13:06] <theseinfeld> did you see the bugmenot april's fool! Hilarious!!!
[13:06] <theseinfeld> directhex
[13:07] <directhex> no
[13:33] <bddebian> Heya gang
[13:47] <jpds> 729
[13:47] <jpds> Grrr.
[13:48] <white> hi, anyone here knows how I could make a kmail template that invokes a shell script to parse the body of an email?
[13:56] <jpds> http://tuxradar.com/content/ubuntu-rewrite-linux-kernel-using-mono
[14:02] <directhex> jpds, awesome. now let sabdfl know about it in #ubuntu-devel ;)
[14:05] <directhex> jpds, i can offer you a statement from Novell
[14:05] <directhex> "that t-shirt is ugly"
[14:08] <jpds> directhex: Heh. :)
[14:09] <sistpoty|work> hm... can someone sponsor me an upload of faumachine? (got my signing key not around at work) http://spooky.informatik.uni-erlangen.de/~sistpoty/faumachine/faumachine_20090302-0ubuntu1_to_0ubuntu2.debdiff
[14:10] <fidji> didrocks: hi, didier, have you some times for me ?
[14:10] <sistpoty|work> OTOH I could wait until I get home, of course *g*
[14:11] <jpds> sistpoty|work: Sure.
[14:11] <sistpoty|work> jpds: oh, thanks :) (/me is a little bit embarrased to not have seen the missing dependency on the -data package earlier on *g*)
[14:14] <jpds> sistpoty|work: All done.
[14:18] <sistpoty|work> jpds: thanks a lot :)
[14:18] <jpds> Machts nicht.
[14:19] <sistpoty|work> heh
[14:36] <DktrKranz> sistpoty|work: re bug 329042, we're catching each other :)
[14:37] <sistpoty|work> DktrKranz: heh
[16:01] <quentusrex> Does anyone know how to program a listener for /dev/input/* devices?
[16:02] <ScottK> DktrKranz and sistpoty|work: I think the answer for 1.38 is no.
[16:02] <ScottK> We'll get it from Debian in Karmic and no need to sweat it.
[16:02] <sistpoty|work> ScottK: yes, agreed... and we can backport it then
[16:02] <ScottK> Yes.
[16:03]  * DktrKranz agrees
[16:03] <sistpoty|work> (which I think we *should* do, to allow porting of applications in case the api changed)
[16:03] <ScottK> Yes.  It's boost.  The API changed.
[16:03] <sistpoty|work> heh
[16:04] <ScottK> 1.38 will be the boost for squeeze, so we'll get most of that from Debian anyway.
[16:04] <sistpoty|work> ah, cool :)
[16:08] <DktrKranz> ScottK: sistpoty|work, we have only eight packages remaining to finish python 2.6 transition (wrt uninstallability), is it fine to file bug reports (if not already present) and milestoning them for RC or Release?
[16:09] <sistpoty|work> DktrKranz: makes sense to me
[16:09] <ScottK> DktrKranz: Just put them as Medium priority since we aren't proposing the release be delayed for them.
[16:10] <DktrKranz> ok. I'll have a round at them to see if I can fix some this evening and eventually mark the other ones accordingly, thanks.
[16:11] <vadi2> Is it possible to make dh_make not ask for a confirmation?
[16:47] <kees> ScottK, nhandler, DktrKranz, sistpoty|work: anyone around to approve a feature-freeze-exception?  (bug 352801)
[16:48] <sistpoty|work> kees: already looking at it ;)
[16:48] <ScottK> kees: You've got an archive-admin lined up to review it?
[16:49]  * kees hugs sistpoty|work
[16:49] <sistpoty|work> kees: well, that's only 50% of a granted FFe :P
[16:49] <kees> ScottK: yeah, I was poking slangasek about it earlier.
[16:49] <kees> sistpoty|work: heh.
[16:50] <kees> (this should also solve 345801)
[16:50] <ScottK> kees: Isn't jdstrand one now?
[16:50] <kees> ScottK: he is, yes.
[16:51] <ScottK> You're probably in a better position to convince him.... ;-)
[16:51] <ScottK> kees: Approved.
[16:52] <kees> \o/
[16:52] <kees> though I need 2 +1's, is that right?
[16:52] <sistpoty|work> kees: yep
[16:53] <sistpoty|work> kees: unless a delegate handles it
[16:53] <ScottK> kees: Yes and I was the 2nd.
[16:53] <kees> oooh, and there it is.  *reload*  *dance*
[17:13] <vadi2> How would one go about packaging an app that uses the waf build system instead of autotools? update the 'rules' file by hand?
[17:16] <azeem> vadi2: you'll have to change your rules for it, yes
[17:17] <vadi2> is there a programmatic way available for changing it?
[17:17] <azeem> I don't think so
[17:20] <vadi2> alright
[17:23] <DktrKranz> ScottK: is your syncs processed with syncpackage script?
[17:23] <DktrKranz> s/is/are/
[17:23] <ScottK> DktrKranz: yes.
[17:24] <DktrKranz> you're archive-admin, are other MOTUs entitled to use it (if in a hurry)?
[17:33] <nixternal> the time has come for me to step down from the MC and MOTU, thank you everyone for all of the fish. My reasoning is in my last email concerning the MC Meeting today that went to the motu-council mailing list...enjoy and best wishes
[17:34] <DktrKranz> nixternal: from MOTU too?
[17:34] <ScottK> DktrKranz: We aren't supposed to.
[17:35] <DktrKranz> ScottK: good, thanks.
[17:39] <maxb> Looking at the ubuntu-docs postinst... why does it need to dpkg --compare-versions at all? (Asking -motu not -devel because I'm asking in a "packaging technique" context and -devel is full of a debate at the moment)
[17:40] <nixternal> maxb: can you pastebin the postinst?
[17:41] <nixternal> DktrKranz: nah man, having fun with april foolz
[17:41] <maxb>         if [ -d "$link" ] && ! [ -L "$link" ] && dpkg --compare-versions "$2" lt-nl 9.04.6; then
[17:41] <maxb>                 rmdir "$link"; ln -s ../../ubuntu-docs/libs "$link"
[17:41] <maxb> is the interesting bit
[17:42] <maxb> oh, and that is in a case block for "configure" invocation of the postinst
[17:43] <maxb> The point being, if you're configuring a version of a package that ships $link as a symlink, and you want to clear out empty directories that might be stale on the system, why do you care about the previous version?
[17:47] <nixternal> you are not lying, that is an interesting bit
[17:48] <nixternal> maxb: in #ubuntu-doc there is a fellow by the name of mdke, he could probably answer that best for you
[17:58] <james_w> congratulations bdmurray
[17:59] <bdmurray> thanks james_w!
[17:59] <bobbo> congrats bdmurray!
[18:08]  * dholbach hugs bdmurray
[18:14] <nxvl> where was the MC meeting? a call?
[18:15]  * sebner waves at dholbach and nxvl :)
[18:16] <ivoks> alert: broken python-pastescript in jaunty
[18:16]  * ivoks is testing solution
[18:20] <geser> nxvl: it was in #ubuntu-meeting, an impromptu MC meeting to process bdmurray's application due to bad scheduling the last time
[18:21] <nxvl> mm, it should by the time my internet was down, i don't have the logs
[18:21]  * nxvl opens irclogs.ubuntu.com
[18:21]  * sebner waves at dholbach and nxvl and geser of course :D
[18:22]  * geser waves back to sebner
[18:22] <ivoks> yep, works
[18:24]  * nxvl waves with no aparent reason
[18:24] <ivoks> who do i have to surbscribe to allow ffe for universe package? :)
[18:26] <sebner> nxvl: waving back is the reason :P
[18:26] <nxvl> motu-sru
[18:26] <LucidFox> http://www.google.com/search?hl=en&q=latest+ubuntu+release <-- o_O
[18:26] <LucidFox> (probably common knowledge here already, though)
[18:29] <ivoks> nxvl: motu-sru is for stable releases, right?
[18:29] <ivoks> nxvl: jaunty isn't stable yet, but requires a sync from debian
[18:29]  * ivoks goes to wiki
[18:29] <nxvl> MM
[18:29] <nxvl> IIRC it does the exceptions too
[18:29] <nxvl> let me re-check
[18:30] <ivoks> motu-release
[18:33] <nxvl> ivoks: yup, motu-release
[18:33] <nxvl> ivoks: https://wiki.ubuntu.com/FreezeExceptionProcess
[18:33] <ivoks> nxvl: thanks', i'm already at it :)
[18:37] <ivoks> there
[18:49] <jdong> any sound gods around with experience on why skype in particular acts badly with jaunty pulse?
[18:49] <jdong> the two combined spin a core when playing sound, even the ringtone, about 25% user and 25% system time on a core 2 duo
[18:50] <jdong> (it used to use 20% combined CPU on intrepid but in jaunty it causes stuttering and is more or less unusable)
[18:53]  * hyperair never knew that cores spin
[18:58] <_ruben> hyperair: nowadays the fans are fixed, and the cores spin
[18:58] <hyperair> _ruben: interesting eh
[19:13] <mbana> hi, who packs adobe reader for intrepid?
[19:14] <sebner> mbana: nobondy?
[19:14] <mbana> no there's a channel
[19:16] <sebner> mbana: channel? adobe reader is not available in the official sources and it won't be in future
[19:16] <mbana> no it's available in a repo, i forget which
[19:17] <sebner> mbana: this is the channel for *official* ubuntu packages ;) not for someone's repo with someone's packages
[19:17] <mbana> no it's an official ubuntu repo
[19:18] <sebner> mbana: I even can think of partner?!
[19:18] <mbana> never mind i found it; http://www.medibuntu.org/
[19:18] <sebner> mbana: medibuntu != official ubuntu
[19:19] <cody-somerville> Canonical might provide it via the Partner repository
[19:19] <sebner> cody-somerville: but it isn't available *for now* IIRC, right?
[19:19]  * cody-somerville isn't sure.
[19:19] <cody-somerville> But I wonder where the correct place to ask question about the partner repository is
[19:20] <sebner> cody-somerville: -devel?
[19:21] <cody-somerville> Probably but I don't think thats really the right place
[19:21] <sebner> cody-somerville: well, there isn't something like ubuntu-partner yet AFAIK ^^
[19:21] <Amaranth> That is not the right place
[19:21] <sebner> I refer to a channel
[19:22] <Amaranth> the guys working on partner are completely separate
[19:22] <Amaranth> I don't think there is a place, honestly
[19:22] <cody-somerville> AFAIK, partner is powered by contractors from the community for the most part
[19:24] <cjwatson> cody-somerville: I don't think that's true, no
[19:24] <cjwatson> Brian Thomason does most of it, I believe (though often in conjunction with the partner in question); he's "iamfuzz" on IRC
[19:24] <cjwatson> I think generally you can file bugs in Ubuntu about packages in the partner repository, though
[19:25] <cody-somerville> Thats probably the case now
[19:25] <cody-somerville> but I think ScottK did some work on it at one time
[19:26] <mbana> what are you guys talking about
[19:26] <cjwatson> cody-somerville: yes, ScottK helped out with a review at one point (I was the manager for that contract ...)
[19:26]  * cody-somerville nods.
[19:26] <cjwatson> cody-somerville: but I think he would be the first to deny that he powered the partner repository :-) I don't know of any other similar instances
[19:27] <cody-somerville> lol
[19:27] <cody-somerville> Maybe "powered" was a bit strong
[20:37] <vadi2>  Is it possible to make dh_make not ask for a confirmation?
[20:38] <hyperair> vadi2: why would you want to do that?
[20:38] <vadi2> I need to call it from a script
[20:38] <vadi2> where I do the confirmation already on my own
[20:40] <Elbrus> vadi2: I am not sure, but why would you want to run dh_make from script.
[20:40] <vadi2> that is a different topic :)
[20:41] <Elbrus> it needs manual attention afterwards anyway
[20:41] <Elbrus> IIRC
[20:41] <vadi2> no, I provide it all the arguments it needs, so it doesn't need attention.
[21:31] <quadrispro> savvas: ping
[21:31] <savvas> quadrispro: hey :)
[21:32] <quadrispro> savvas: nice to meet you :) i'm taking a look at bug 341258
[21:32] <savvas> same here hehe
[21:32]  * savvas refreshes his memory :P
[21:33] <quadrispro> savvas: I have some questions
[21:33] <savvas> sure :)
[21:33] <savvas> ask away!
[21:33] <quadrispro> I think there's 2 way to follow to make the package ready for python 2.6: 1) by fixing the makefile 2) by using setup.py script
[21:34] <quadrispro> is it right, isn'it?
[21:34] <quadrispro> looking at your patch it seems you're trying to follow both those ways! :D
[21:35] <savvas> oops, let me check
[21:36] <quadrispro> savvas: perhaps I'm wrong eh :)
[21:36] <quadrispro> but you touched both the Makefile and debian/rules
[21:37] <quadrispro> by disabling the use of make in debian/rules (it could be ok) and, in the same time, tuning the Makefile :P
[21:37] <savvas> um hold a sec
[21:37] <savvas> I think I removed the direct changes and made patches instead
[21:38] <savvas> hm..
[21:38] <savvas> is this package from debian? I'll check
[21:39] <savvas> wheow no :p
[21:40] <quadrispro> no no, -0ubuntuX
[21:40] <savvas> quadrispro: ok, the direct changes in http://launchpadlibrarian.net/23813555/gpixpod_0.6.2-0ubuntu6_fixed.debdiff revert to the original files, that are in orig.tar.gz
[21:40] <quadrispro> (sometime I could go away for some moment, Italy's playing :))
[21:40] <savvas> ok :)
[21:41] <quadrispro> savvas: ah! ok, now I understand but... why??
[21:41] <quadrispro> :)
[21:41] <savvas> lintian-happy
[21:41] <savvas> it had dpatch in its build-depends
[21:42] <quadrispro> yes, savvas but it may be good only rebuild (by patching all the necessary things), then submitting all other changes to debian
[21:42] <quadrispro> in this way we'll sync them later
[21:43] <savvas> but.. gpixpod is not in Debian :\ http://packages.qa.debian.org/g/gpixpod.html
[21:43] <quadrispro> savvas: sorry LOL
[21:43] <quadrispro> ok
[21:43] <quadrispro> then ok
[21:43] <quadrispro> lol
[21:43] <savvas> but wait!!
[21:43] <didrocks> hyperair: around?
[21:43] <savvas> I think I didn't check the Standards-Version update
[21:45] <savvas> quadrispro: I made it 3.7.3 -> 3.8.0 without going through the checklist, give me 5 minutes and I'll let you know :)
[21:45] <quadrispro> ok, perfect
[21:59] <savvas> quadrispro: ok, I think no changes required for standards-version changed, except for "Homepage:" inclusion in debian/control :P
[22:00] <quadrispro> ok
[22:00] <quadrispro> savvas: could you prepare new patch?
[22:00] <savvas> sure
[22:01] <savvas> a few seconds :)
[22:04] <savvas> quadrispro: http://paste.ubuntu.com/142339/
[22:05] <savvas> ( this the difference between the old _fixed.debdiff and new.debdiff patch: http://paste.ubuntu.com/142339/ )
[22:05] <savvas> er sorry
[22:05] <savvas> ( the difference between the patches is: http://paste.ubuntu.com/142341/ )
[22:06] <quadrispro> looks good
[22:06] <quadrispro> building
[22:07]  * savvas crosses fingers :)
[22:10] <quadrispro> savvas: http://paste.ubuntu.com/142347/
[22:10] <quadrispro> ciao tseliot
[22:11] <savvas> in pbuilder?
[22:11] <savvas> applying patch 01_about-window to ./ ... ok.
[22:11] <savvas> applying patch 02_new-album to ./ ... ok.
[22:11] <savvas> applying patch 10_gpixpod_python to ./ ... ok.
[22:11] <savvas> applying patch 20_imgconvert_Makefile_fix to ./ ... ok.
[22:12] <tseliot> quadrispro: ciao ;)
[22:12] <savvas> aaaaah
[22:12] <savvas> got it
[22:12] <savvas> hold a sec
[22:12] <quadrispro> savvas: no no, it happens before giving the package to pbuilder, anyway I'm working on it by getting your previous patch and tuning it
[22:13] <savvas> quadrispro: try this one: wget http://paste.ubuntu.com/142349/plain -O plain
[22:14] <savvas> (must be an extra line or something?)
[22:14] <quadrispro> savvas: just working :)
[22:14] <savvas> oki doki :)
[22:18] <quadrispro> savvas: in debian/changelog would be better using *. - and + as shown here: http://paste.ubuntu.com/142351/
[22:22] <quadrispro> savvas: building in progress -> http://localhost/jaunty/pool/gpixpod_0.6.2-0ubuntu6/gpixpod_0.6.2-0ubuntu6.buildlog
[22:22] <quadrispro> eh, savvas, sorry -> http://home.alessiotreglia.com/jaunty/pool/gpixpod_0.6.2-0ubuntu6/gpixpod_0.6.2-0ubuntu6.buildlog
[22:31] <savvas> quadrispro: oops, sorry, is it too late? should I change the - and + in changelog?
[22:32] <quadrispro> savvas: just done
[22:32] <quadrispro> * already
[22:32] <quadrispro> and uploaded too :)
[22:32] <savvas> I didn't know we had a policy about changelog and -/+, good to know :)
[22:35] <quadrispro> savvas: only style-guidelines :)
[22:36] <savvas> ok, still, good to know :P
[22:37] <savvas> damn this cough is killing me, brb
[22:53] <quadrispro> bye guys
[22:54] <quadrispro> savvas: bye!
[22:57] <savvas> bye !
[22:57] <savvas> oh left :\
[22:57] <savvas> FYI: Launchpad will be going offline for maintenance in three minutes.  :)
[23:15] <savvas> this is weird.. my memory card reader stopped working
[23:16]  * savvas wrong channel, ubuntu+1 :P
[23:41] <savvas> why does openoffice.org-math have NoDisplay=true ?
[23:42] <jpds> savvas: Best talk to calc about that.
[23:44] <savvas> jpds: ok, thanks - I guess they're not online currently :)