[00:06] <ryanakca> Could someone please ack bug 538283 ?
[01:29] <Laibsch> I'm seeing the symptoms described in bug 385139 in a karmic pbuilder.  I believe it is preventing pbuilder from successfully setting up the build environment.  Does the bug speak to anyone around here?
[07:17] <fabrice_sp> jayvee, np ;-) And you'd better get used to quilt: source 3.0(quilt) uses ... :-)
[07:17] <fabrice_sp> quilt
[07:21] <Rhonda> fabrice_sp: No, it doesn't. It is a completely unrelated (and in parts also different) implementation of the same idea.
[07:21] <Rhonda> It's one of the bad misnamers in software history, unfortunately.
[07:22] <Rhonda> Said that, it should though hopefully work well together when one wants to use quilt directly instead of the dpkg internal approach.
[07:23]  * Rhonda . o O ( in the meantime) )
[07:55] <RainCT> morning dholbach :)
[07:55] <dholbach> good morning
[07:55] <dholbach> hey RainCT!
[08:22] <happyaron> hi, is there any document introducting dh7 features and usages?
[08:33] <\sh> moins
[08:37] <RainCT> happyaron: http://joey.kitenet.net/talks/debhelper/debhelper-slides.pdf
[08:38] <happyaron> RainCT: thanks
[08:38] <RainCT> hey \sh
[08:39] <RainCT> happyaron: You're welcome. Those are slides from a DebConf talk (so not really explained) but I found them helpful nevertheless.
[08:41] <\sh> hey RainCT
[09:20] <Rhonda> fabrice_sp: Did you see my paste to your query?
[10:54] <christoph_debian> is that launchpad mailgateway time-sensitive as well or just still broken in 0.93
[10:57] <christoph_debian> anyway if anyone wants to second -> #540838
[13:34] <nigelb> Rhonda: you about?
[13:46] <Rhonda> nigelb: Never. Usually It's better to just ask your question - maybe even someone else could answer. :)
[13:47] <nigelb> Rhonda: I think I fixed the foolishness I was doing ;)
[13:47] <Rhonda> \o/
[13:47] <nigelb> no wonder they say debian has a bit of a barrier
[13:47] <nigelb> its so tough ;)
[13:50] <hyperair> debian is tough?
[13:50] <Laney> hard as nails
[13:51] <nigelb> hyperair: finding documentation for stuff is
[13:51] <hyperair> imo centos is tougher. it's busy screwing you over even while you're not making mistakes.
[13:51] <hyperair> nigelb: isn't debian well documented?
[13:51] <hyperair> like manpages and such
[13:51] <nigelb> hyperair: for packaging stuff?
[13:51] <hyperair> sure it is!
[13:51] <Laney> policy and devref
[13:51] <Laney> job done
[13:52] <hyperair> man dh_stuff
[13:52]  * hyperair nods
[13:52] <Laney> naaahhh dh is optional
[13:52] <Laney> cf manoj packages
[13:52] <nigelb> or may be I'm just baaad at packaging
[13:52] <nigelb> I seem to make all sorts of mistakes
[13:52] <Laney> it's called learning
[13:52] <Laney> you'll get better
[13:53] <nigelb> its embarassing, but I'm swallowign my pride for infinity
[13:55] <hyperair> Laney: manoj packages?
[13:59] <nigelb> oh joy! gwibber depends on python-wnck, not in debian yet
[14:00] <Laney> hyperair: packages maintained by manoj
[14:01] <hyperair> Laney: no dh? that sounds scary.
[14:01] <Laney> depends how good you are at make...
[14:04] <hyperair> Laney: well... i imagine something on the level of cdbs's source..
[14:04] <Laney> they're quite clean actually, at least ucf which I looked at
[14:04] <Laney> anyway bbiab
[14:06] <dupondje> Its prolly way to late to get a new package version into Lucid ? :)
[14:08] <nigelb> dupondje: very late I think
[14:09] <dupondje> its not even in debian sid neither, so would not even be a sync request. Better package it myself and put on my ppa :P
[14:10] <nigelb> dupondje: better get it into debian
[14:10] <nigelb> will by synced for lucid+1
[14:11] <nigelb> dupondje: what package anyway?
[14:11] <dupondje> audacious :)
[14:12] <dupondje> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559055
[14:12] <dupondje> There is a new upstream version available since Nov 22. => lazy asses :)
[14:13] <nigelb> I think you can do an NMU, but a DD could give better opinion on that
[14:14] <dupondje> eh ? :)
[14:17] <nigelb> non-maintainer upload
[14:19] <dupondje> anyway, is there a quick/easy way to package new upstream version? or its just fetch source, copy debian dir, adjust it & package ?
[14:34] <\sh> bdrung: ping eclipse ;) do you know how to solve Exception in thread "main" java.lang.UnsatisfiedLinkError: no swt-gtk-3555 or swt-gtk in swt.library.path, java.library.path or the jar file
[14:37] <bdrung> \sh: you have to set LD_LIBRARY_PATH to the xulrunner path
[14:38] <\sh> bdrung: hmmm? on x86_64 with openjdk-6?
[14:39] <bdrung> \sh: export LD_LIBRARY_PATH=/usr/lib/xulrunner-1.9.2 (or similar) -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=291758
[14:59] <DktrKranz> dholbach: ubuntu-dev-tools 0.96 uploaded in Debian
[15:00] <mok0> DktrKranz: impressive. ubuntu-dev-tools has a wickedly long chain of dependencies
[15:00] <mok0> DktrKranz: many of which were -0ubuntu1 AFAIR
[15:01] <DktrKranz> mok0: well, it's not the first upload in Debian, I already did many
[15:01] <dholbach> DktrKranz: awesome!
[15:01] <DktrKranz> (and yes, there are four rdeps)
[15:01] <mok0> DktrKranz: I tried backporting ubuntu-dev-tools to jaunty, but had to give up
[15:01] <DktrKranz> hehe
[15:02] <mok0> DktrKranz: many new dependencies were introduced since then
[15:02] <DktrKranz> yeah, with LP integration and API, you need several lazr* and launchpadlib
[15:02] <mok0> DktrKranz: exactly
[15:02] <mok0> DktrKranz: well done!
[15:02] <DktrKranz> but I packaged them already ;)
[15:02] <c_korn> an Ubuntu package in Debian ? what secret conspiracy is this ? .)
[15:02] <DktrKranz> thanks ;)
[15:02] <mok0> DktrKranz: I have my notes on my laptop, so I can't exactly remember where I gave up
[15:03] <Laney> we should really move stuff to devscripts
[15:03] <DktrKranz> +0,9
[15:03] <mok0> DktrKranz: ... but it was on the 10th or 12th package in the chain...
[15:03] <DktrKranz> (missing 0.1 is for some scripts really Ubuntu-specific)
[15:03] <Laney> but they don't have python scripts there afaik
[15:03] <Rhonda> hyperair: Actually, it isn't scary at all. Just take a look at the rules file of netris, the package is small enough to do a quick apt-get. (and it's not manoj)
[15:04] <Rhonda> apt-get source of course. :)
[15:05] <Rhonda> And it helps to find out what's actually going on behind the curtain of dh.
[15:06] <mok0> You don't want to look at dh... it is explosive and is likely to cover you with scraps of incomprehensible chunks of perl goo
[15:06] <DktrKranz> Laney: exactly, just perl (IIRC)
[15:06] <Laney> I find joeyh's perl pretty readable tbh
[15:07] <mok0> I wrote a perl program once... about 2 hours after I wrote it, it was already impossible to figure out what it was doing
[15:07] <mok0> :-)
[15:08] <DktrKranz> mok0: it's not your fault, it happens :)
[15:08] <mok0> Heh
[15:08] <Rhonda> mok0: That's why there is no dh in netris packaging.
[15:08] <DktrKranz> I once wrote a Python program, but it self-exploed because of my bad PEP-8
[15:08] <mok0> Rhonda: Ah, respect!
[15:09]  * mok0 forgets the python urbanities... PEP-8?
[15:09] <DktrKranz> coding style
[15:10] <DktrKranz> URLly http://www.python.org/dev/peps/pep-0008/
[15:10] <mok0> Ah... white space
[15:11] <mok0> DktrKranz: The only really sucky thing about python... otherwise I love it
[15:11]  * mok0 wonders, since Python has an opening brace, why can't it have a closing one?
[15:11]  * DktrKranz doesn't like parenthesis
[15:12]  * Rhonda throws scheme at DktrKranz 
[15:12]  * mok0 is hoping for a ';' as the ending brace
[15:12] <DktrKranz> Rhonda: LISP also
[15:13]  * mok0 looks a ((((((DktrKranz))))))
[15:13]  * DktrKranz hides
[15:13] <Rhonda> DktrKranz: lisp is a scheme dialect.
[15:13] <mok0> Rhonda: ... hmmm
[15:13] <Rhonda> The other way round?
[15:14] <Laney> yes, the other way around
[15:14] <mok0> Rhonda: that would be my guess
[15:14] <mok0> :)
[15:14] <dyfet> lisp is the mother tongue
[15:14] <DktrKranz> no
[15:14] <DktrKranz> mother tongue are butterflies
[15:14] <mok0> scheme is GNU's version of common lisp afaik
[15:14]  * Rhonda prefers script-fu anyway when such a thing is needed.
[15:15] <mok0> Rhonda: you a bash man?
[15:15] <mok0> :-)
[15:16]  * Rhonda bashes bash
[15:16] <Rhonda> mok0: perlmonk :)
[15:16] <mok0> Rhonda: Oh dear
[15:16] <nigelb> how does multiple binary packages work?
[15:17] <nigelb> I need to have a separate install file for each package?
[15:17] <nigelb> err.. binary
[15:17] <mok0> nigelb: no, just create a section in control for each of them
[15:17] <nigelb> thats it?
[15:17] <mok0> nigelb: yes
[15:18] <nigelb> so the intallation and stuff/
[15:18] <mok0> nigelb: then you use debian/install and friends to put files in their respective packages
[15:18] <nigelb> It was intially debianized as single binary
[15:18] <nigelb> now, I get to know that it should be split to work properly
[15:18] <mok0> nigelb: you need files debian/install.<packagname> for each package
[15:19] <nigelb> aha :) thank you
[15:19] <Rhonda> nigelb: Yes, debian/$package.install is the way to go for multiple binaries (and the control file snippet, but that part hopefully is the obvious part)
[15:19] <mok0> nigelb: you're welcome :-)
[15:19] <Rhonda> mok0: Erm …  Your approach isn't the best one. :)
[15:20] <nigelb> NM's are discouraged from working with multiple binaries, should that be a problem as long as my sponsor is willing?
[15:20] <Rhonda> debian/$binpackage.$foo is used by debhelper for the different parts.
[15:20] <mok0> Rhonda: educate me
[15:20] <dupondje> nigelb: seems it wasn't packaged because it needs a new lib, that isn't in debian/ubuntu yet :(
[15:20] <Rhonda> So one can has debian/package1.install, debian/package2.menu, and so on
[15:21] <nigelb> dupondje: ah, well, so you cant get into debian either
[15:21] <mok0> Ah, yes, package.install not install.package.. my bad
[15:21]  * mok0 needs coffeine now
[15:21] <Rhonda> nigelb, mok0: Some example, see the filelist here: http://git.debian.org/?p=pkg-games/wesnoth.git;a=tree;f=debian;h=29cd8f81facdf1dc38f9bd7abe14701b9a6f442c;hb=8eebb4
[15:21] <dupondje> nigelb: well the lib is in debian exp, just needs some time it seems :(
[15:22] <mok0> Rhonda: right
[15:22] <nigelb> Rhonda: ah, thats great.  examples were what I needed.  ty :)
[15:22]  * Rhonda . o O ( and that file list will be getting extremely more confusing with the next commit.  %-) )
[15:25]  * Rhonda . o O ( thinking of, I guess I should leave off the "generated" files out of that repository. )
[17:02] <mok0> ScottK: ping
[17:03] <ScottK> mok0: Pong
[17:03] <mok0> ScottK, hi, I'm looking at an important bug in Atlas, that may have been resolved
[17:03] <mok0> bug 363510
[17:04] <mok0> ScottK, I need an FFE for that
[17:04] <ScottK> Looking
[17:05] <mok0> ScottK, It means a jump in version from 3.8.0 to 3.8.3
[17:06] <mok0> ScottK, OTOH, we wont need to backport the fix
[17:06] <mok0> ScottK, and maintain this outdated library for 3 years
[17:06] <ScottK> OK.  Still reading the bug.
[17:09] <ScottK> mok0: I think you mean 3.6.0 -> 3.8.3.
[17:09] <mok0> ScottK, uhm yes
[17:09] <mok0> ScottK, I am building the package now, if the test program works, I propose to sync it
[17:10] <ScottK> mok0: Do you know why Debian has it in Experimental?
[17:11] <mok0> ScottK, No... the last comment on the LP page is from the maintainer, so I suppose he thinks it's ok for ubuntu
[17:12] <mok0> ScottK, the whole 3.8.3 series is in exp.
[17:12] <ScottK> mok0: libatlas-base-dev has 13 reverse build-depends.  You'd need to deal with the entire transition.
[17:12] <mok0> ScottK, hm
[17:13] <ScottK> mok0: Generally, if the newer atlas is mature, I do think it makes sense to move forward, but you need to look at the entire atlas stack and make sure we aren't fixing one thing and breaking 5 others.
[17:13] <mok0> ScottK, of course... it's more rdepends that I thought
[17:14] <Laney> I think I saw talk of an atlas transition for Squeeze
[17:14] <mok0> Laney: and... ?
[17:14] <Laney> you should ask if the Debian people know of any issues
[17:14] <ScottK> mok0: I'd suggest do test rebuilds and lay out a complete plan for one FFe.
[17:14] <ScottK> As long as it tests out OK, I think we should probably go ahead.
[17:14] <mok0> ScottK, OK, sounds reasonable
[17:14] <Laney> they might be willing to hear your bugs so that their transition goes easier
[17:15] <Laney> etc
[17:15] <mok0> Laney: sure
[17:18] <mok0> ScottK, several important packages are in the list of rdepends, R for one; perhaps that is why the package is still in experimental
[17:27] <mok0> ScottK, it's worse, you need to look at the rdepends of package libatlas3gf-base
[17:28] <ScottK> Oh my.
[17:29] <mok0> ScottK, I think libatlas-base-dev is the old version of libatlas
[17:29] <mok0> ScottK, doesn't look realistic for Lucid, huh?
[17:29] <ScottK> Yes, I was looking at current reverse-build-depends in Ubuntu, not Debian experimental.
[17:30] <ScottK> mok0: For the ones that are run time depends (and not build depends), I suspect testing a sub-set of them would be sufficient if it goes well.
[17:30] <ScottK> You might ask upstream about 3.6 -> 3.8 binary compatibility.
[17:31] <mok0> ScottK, ok, I will investigate it
[18:02] <siretart`> mok0: ScottK: is the backporters meeting scheduled for now or in 1h?
[18:02] <mok0> siretart`: heh
[18:02]  * ScottK looks at mok0.
[18:02] <mok0> siretart`: It's actually 18:00 UTC now, but I think I made a mistake when scheduling the meeting
[18:03] <siretart`> so, what do we do now?
[18:03] <mok0> On the fridge, it says 19:00 UTC, so perhaps we should wait
[18:03] <siretart`> TBH, that would suit me better, I could then have dinner right now :-)
[18:04] <mok0> siretart`: great
[18:04] <mok0> I will stick around #ubuntu-meeting in case anyone else shows up
[18:04] <siretart`> excellent. thanks
[18:04] <mok0> siretart`: enjoy you meal :-)
[18:06] <siretart`> thanks :-)
[19:33] <duanedesign> reviewing RC bugs Debian has closed I have found one that affects Lucid and it hasnt been merged.
[19:35] <duanedesign> i am still learning the motu processes so I am unsure about what I should do next?
[19:36] <geser> Have both Ubuntu and Debian the same upstream version?
[19:51] <micahg> duanedesign: have you seen this: http://qa.ubuntuwire.org/bugs/rcbugs/lucid/
[19:52] <duanedesign> micahg: yes. That is where I found the bug :)
[19:52] <micahg> duanedesign: k, I thought it was cool and just saw it today, so thought I'd mention it :)
[19:54] <duanedesign> micahg: sure. I just found it a couple of days ago. Well I didnt find it p_ersia told me about it
[19:56] <duanedesign> geser: ubuntu has 0.5-2.2 and Debian unstable has 0.5-2.3 . I opened a bug report on it. bug 541446
[19:58] <geser> duanedesign: have you verified that it builds in a lucid environment (a lucid pbuilder)?
[19:59] <duanedesign> geser:heh, I only verified the bug. Ill verify the fix as well..
[20:02] <geser> please subscribe "ubuntu-sponsors" when you are done to add it to the sponsoring queue
[20:02] <Fersure> debuild is saying that it can't find my 'secret key'. how would I sort this out? can't see anything in the docs
[20:04] <Fersure> (totally new to packaging for ubuntu. following the PackagingGuide on the wiki)
[20:04] <BlackZ> Fersure: are you used the same name in export DEBFULLNAME ?
[20:04] <BlackZ> have*
[20:04] <Fersure> yep
[20:04] <BlackZ> Fersure: gpg --list-keys
[20:04] <BlackZ> is it in the list?
[20:04] <geser> either use the same name, comment and email address in debian/changelog matching one of your key uid or tell debsign which key to use
[20:05] <Fersure> BlackZ: yes
[20:05] <ChogyDan> Fersure: did you put a comment in your key?  I made the mistake of not having a blank comment
[20:05] <Fersure> oh um yes I did
[20:05] <Fersure> so I should create the key again leaving a blank comment?
[20:05] <Fersure> how would I delete the key I currently have then? o.o
[20:06] <ChogyDan> then as geser said, you have to write the comment out in the changelogs also, or just remake the key without the comment.  I think there are other tricks
[20:06] <BlackZ> Fersure: yes, or you can modify it instead
[20:06] <Fersure> how? I'm a total noob when it comes to gpg.
[20:07] <BlackZ> Fersure: however I suggest you to re-create it and then re-try
[20:08] <Fersure> okay.
[20:08] <porthose> Fersure, or for a quick fix you can just use the -k<keyid> option with debuild
[20:08] <BlackZ> Fersure: for more information, you can read https://help.ubuntu.com/community/GnuPrivacyGuardHowto
[20:09] <Fersure> Ah excellent. Thanks. :)
[20:37] <duanedesign> geser: i verified it builds in a Lucid pbuilder and the fix works. is there anything else I need to do other than subscribing "ubuntu-sponsors" to the bug?
[20:38] <geser> no (perhaps be patient :)
[20:52] <duanedesign> geser: thank you very much. Just happy to be helping and learning more about packaging/MOTU
[23:13] <Anzenketh> I am trying to learn how to create a debian package from scratch is there a newer version of https://wiki.ubuntu.com/PackagingGuide/Complete
[23:57] <diwic> Hmm...I've done "apt-src install pulseaudio", "apt-src build pulseaudio", then made a change to src/modules/alsa/alsa-source.c, then ran "make", then trying to run the pulseaudio wrapper script (src/pulseaudio), but the change wasn't there. What did I do wrong?
[23:59] <sladen_> diwic: 'debuild -b -uc -us' && dpkg -i ../pulseaudio.*