[00:04] <KasimirGabert> !page
[00:04] <ubotu> Sorry, I don't know anything about page - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[00:18] <InsClusoe> pdebuild seems to have hanged at last step. It says cleaning the build env and then started taking rest. ;-)
[00:19] <mok0> InsClusoe: it is probably packaging everything back into base.tgz
[00:20] <InsClusoe> mok0: Yeah.. probably. /var/cache/pbuilder/result has many .deb files, but no base.tgz
[00:21] <mok0> base.tgz is probably in /var/cache/pbuilder
[00:21] <mok0> InsClusoe: aren't those debs the ones you've built?
[00:21] <InsClusoe> mok0: Yes
[00:22] <mok0> When it's done, pbuilder re-packs base.tgz, it can take a while
[00:22] <InsClusoe> base.tgz is present in /var/cache/pbuilder as you said.
[00:23] <mok0> sounds like everything is ok
[00:23] <KasimirGabert> my program is built using Qt4, and pbuilder fails because the dev files aren't present
[00:24] <KasimirGabert> how should I include them?
[00:24] <KasimirGabert> because they aren't required to run the program, right?
[00:24] <mok0> KasimirGabert: put them in debian/control, in the Build-Depends: line
[00:24] <emgent> debian #464058
[00:24] <KasimirGabert> ah
[00:24] <KasimirGabert> thanks :)
[00:24] <emgent> Debian #464058
[00:24] <emgent> uhm..
[00:24] <ubotu> Debian bug 464058 in turba2 "turba2: Access rights not checked properly" [Grave,Fixed] http://bugs.debian.org/464058
[00:24] <emgent> lag...
[00:25] <mok0> ubotu, you are soooo slow
[00:25] <InsClusoe> mok0: Will pdebuild succeed even if there is an older base.tgz present in /var/cache/pbuilder? Should I delete the older file? 2 hrs go, I created one base.tgz and that's what I see now..
[00:26] <mok0> InsClusoe: no it keeps working on that one. If you do pbuilder update, for example
[00:26] <InsClusoe> mok0: am surprised at how it seems to have hung for the last 30 minutes. getting iffy.
[00:27] <mok0> InsClusoe: hmm, yes
[00:28] <InsClusoe> mok0: do you still want me wait?
[00:28] <mok0> InsClusoe: no, it is not _that_ slow.  Will that resume from where it left off earlier?
[00:32] <mok0> InsClusoe: that should unpack base.tgz and update it with the latest packages
[00:33] <mok0> InsClusoe: and then pack it back into base.tgz
[00:34] <InsClusoe> mok0: ok.. just killed the older process with ^c.
[00:34] <InsClusoe> mok0: Pbuilder, then, printed this... removing directory /var/cache/pbuilder/build//14502 and its subdirectories
[00:34] <InsClusoe> mok0: notice two /'s in the file pth
[00:34] <mok0> InsClusoe: that's fine
[00:35] <InsClusoe> pbuilder update needs to be run as su?
[00:36] <mok0> InsClusoe: yep
[00:36] <mok0> InsClusoe: sudo pbuilder update
[00:37] <InsClusoe> mok0: its creating the base tarball...
[00:37] <InsClusoe> oh.. it's already done.
[00:38] <mok0> InsClusoe: shouldn't take more than 10-20 seconds
[00:38] <InsClusoe> mok0: oh... I was so stupid I wasted 30 MINUTES on it.
[00:38] <InsClusoe> :-)
[00:38] <mok0> InsClusoe: heh
[00:39] <mok0> InsClusoe: experience comes at a price
[00:39] <InsClusoe> mok0: now I know wise men are always shown to have long grey beards!
[00:39] <mok0> InsClusoe: :-)
[00:40] <mok0> InsClusoe: now you have a pbuilder...
[00:42] <InsClusoe> mok0: Wise men must have started compiling in Fortran or Cobol and waited ages... for the beard to grow.
[00:43] <mok0> InsClusoe: ... or waiting for their pbuilders to finish, when actually just hung...
[00:43] <InsClusoe> mok0: :-D Now I can upload source.changes to the bug and start my next waiting session?
[00:44] <mok0> InsClusoe: you need to create a debdiff
[00:44] <mok0> debdiff old.dsc new.dsc
[00:47] <InsClusoe> Alright.. Done.
[00:47] <InsClusoe> Jeez... so many steps...
[00:47]  * InsClusoe pants and catches his breath
[00:47] <InsClusoe> Pls tell me it'
[00:48] <InsClusoe> Pls tell me it's over...
[00:48] <InsClusoe> :-)
[00:48] <mok0> InsClusoe: It's over
[00:49]  * InsClusoe hugs mok0
[00:49]  * mok0 hugs back
[00:50] <mok0> Launchpad is down for maintenance :-(
[00:50] <InsClusoe> mok0: Thanks for being there.
[00:50] <mok0> InsClusoe: glad to help
[00:50] <InsClusoe> What? :-(
[00:50] <InsClusoe> I cant upload my first ever debdiff to the bug?
[00:50] <mok0> It says it's back soon
[00:51] <InsClusoe> It's sun rise time here... I have to sleep soon or I won't make it to work today..
[00:52] <mok0> InsClusoe: heh, well upload it tomorrow, then...
[00:52] <slangasek> it's a 3-hour outage and we're only 50 minutes in; I don't recommend staying up
[00:52] <InsClusoe> Guess I don't have a choice then...
[00:53] <mok0> slangasek: ah, so 3 hours is "soon" now? :-)
[00:53] <slangasek> mok0: it's a generic message, of course...
[00:53] <TheMuso> There is every possibility that the downtime could be longer.
[00:53] <slangasek> the maintenance schedule was posted well in advance though (c.f /topic #ubuntu-devel)
[00:54] <InsClusoe> mok0: They must have waited longer for pdebuild... They are used to it.
[00:54] <mok0> Well, time for bed, then.
[00:54] <InsClusoe> ok.. Thank you all MOTUs for helping out..
[00:55]  * InsClusoe tries hard to muster energy to wave his hand to say goodbye..
[00:55]  * mok0 waves
[00:56] <mok0> Goodnight, folks'
[00:56] <InsClusoe> See you all tomorrow at #ubuntu-classroom
[01:23] <slicer> You know, some times you really can get far by just asking nice (and it helps that you ask nice people). The patent I had problems with is about to be licensed freely to all opensource programs (and not just GPL), and in the meantime I've gotten an explicit permission to publish my program under BSD :) *Warm fuzzy feeling*
[01:26] <slicer> Which nicely solves all my debian/copyright headaches.
[01:49] <TheMuso> slicer: What program?
[01:54] <bddebian> Heya gang
[01:55] <LaserJock> hiya bddebian
[01:55] <bddebian> Heya LaserJock
[01:58] <nixternal> boo
[01:59] <bddebian> ahh
[01:59] <bddebian> Hi nixternal
[01:59] <LaserJock> hi nixternal
[01:59] <ScottK> Heya bddebian, nixternal, and LaserJock
[02:00] <LaserJock> evening ScottK
[02:00] <bddebian> Heya ScottK
[02:00] <ScottK> Let me tell you, don't ever move a conffile in a Debian package.  It's a PITA to get right.
[02:01] <LaserJock> interesting
[02:01] <StevenK> Oh yes. But the sense of accomplishment you feel afterwards.
[02:01] <bddebian> heh
[02:02] <slangasek> ScottK: in the absence of LP, do you happen to remember offhand the status of the libconvert-tnef-perl and libmime-perl MIRs?
[02:02] <nixternal> wasabi!
[02:02] <slangasek> ScottK: hmm, moving conffiles - the recipe didn't help, or you didn't know about it?
[02:02] <ScottK> slangasek: All the ones I asked for for amavisd-new were approved.
[02:02] <ScottK> I just found it.
[02:03] <ScottK> With my limited shell ability the recipe takes it from impossible to PITA.
[02:03] <slangasek> ah :)
[02:03] <ScottK> slangasek: I'm pretty sure those were both on my MIR list as approved.  Let me see if I saved any bugmail on them.
[02:04] <soto> Why does my .changes file have distribution FOO when I ran pdebuild with DIST=BAR?
[02:04] <slangasek> ScottK: ok; libmime-perl is still in universe
[02:04] <ScottK> slangasek: For libmime-perl I have bugmail from pitti saying approved
[02:04] <slangasek> ok
[02:04] <StevenK> soto: Because your debian/changelog mentions FOO, not BAR?
[02:04] <ScottK> slangasek: Same for libconvert-tnef-perl
[02:04] <slangasek> once LP is back up then, I'll get it promoted properly
[02:05] <ScottK> slangasek: Thanks.
[02:05] <slangasek> ScottK: yeah, libconvert-tnef-perl is in main after all, it just also depends on libmime-perl
[02:05]  * bddebian never knows whether or not to say hi to StevenK and slangasek ;-P
[02:05] <soto> StevenK: How are packages built for multiple releases?
[02:05] <Nafallo> hi bddebian
[02:05] <StevenK> soto: They aren't.
[02:06] <bddebian> Heya Nafallo
[02:06] <soto> StevenK: I don't follow. I want to build a package on say, Hardy, Gutsy and Feisty. I have to edit the changelog each time?
[02:07] <soto> Maybe I watch too much Ron Popeil, but I like to "Set it and forget it"
[02:07] <slangasek> bddebian: ...hi?
[02:07] <bddebian> slangasek: :)
[02:07] <StevenK> soto: You can build it unmodified on each release. The .changes files will have what the debian/changelog says
[02:08] <StevenK> bddebian: You've confused me ...
[02:08] <bddebian> StevenK: How so?
[02:08] <StevenK> bddebian: Whether or not to say hi? Hrrm?
[02:08] <bddebian> StevenK: Well I seem to annoy you two more than most ;-P
[02:09] <bddebian> Maybe annoy isn't the right word...
[02:10] <soto> StevenK: Isn't the correct distribution expected to be put in the changes file? I don't believe that package maintainers are manually editing the changelogs for release over 4-5 distributions.
[02:11] <jdong> soto: as a developer, I do :)
[02:11] <jdong> if you can't be bothered to specify what release you are targeting, it implies quite a bit about how carefully you are conducting your QA too
[02:11] <jdong> (IMO)
[02:12] <jdong> dch -r can help a bit if you choose to script things like this
[02:12] <soto> Oh common. This screams "there must be a better way to do this".
[02:14] <TheMuso> soto: IMO, whenver you edit a package, and set the changelog appropriately, it is something tat should be done manually. At least for me, it makes me check what I've changed, and why.
[02:14] <soto> It's a feature!
[02:14]  * ScottK agrees with TheMuso
[02:15] <soto> TheMuso: I'm not changing anything, just building a source package (bleeding edge, not available in repositories), not for upload, for 2 different distributions.
[02:16] <TheMuso> soto: If you don't intend to upload anywhere, thats fine. Just build the package against the releases you want.
[02:16] <jdong> soto: then you just need two different pbuilder base.tgz's
[02:16] <jdong> if you build for personal reasons, the changelog sections mean basically nothing
[02:16] <jdong> that's only useful if you're dputting
[02:19] <soto> jdong: Yes, my package depends on a library which I have to build also. Pbuilder instructions on the wiki say I should dput my package into a local repo. Except dput decides where it goes based on .changes file distribution entry.
[02:19] <jdong> did it say to dput into a local repo? Just a flat-structure apt repo should work just fine
[02:19] <jdong> i.e. one generated with dpkg-scanpackages
[02:20] <soto> jdong: mini-dinstall
[02:20] <jdong> soto: IMO that's a bit overkill...
[02:20] <bddebian> apt-ftparchive
[02:20] <jdong> When I wrote prevu I just used a simple directory like "gutsy-debs" and ran dpkg-scanpackages inside it
[02:20] <jdong> apt-ftparchive probably is a smarter idea
[02:21] <TheMuso> apt-ftparchive is actually quite easy to use, and the configs make sense.
[02:21]  * TheMuso has written some as yet unfinished shell scripts around apt-ftparchive.
[02:21] <soto> Okay thanks. I guess I'll do apt-ftparchive.
[02:21] <TheMuso> And they work reallywell.
[02:22] <soto> I really wish this wasn't nearly so painful. It seems needlessly difficult to build your own packages.
[02:23] <jdong> soto: well it's more of an initial learning curve, but these tools are more the "proper " way to do it. I mean if you wanted easy just hit "debuild -B" and call it a day
[02:23] <jdong> but that's irresponsible to those who will use your package
[02:24]  * TheMuso remembers his slackware packaging days. I'd never heard of a chroot, or building in a chroot environment. And its not something the slackware packaging community does either so...
[02:24] <soto> jdong: But debuild won't build for another distribution. And I don't think works out build dependencies for you
[02:25] <jdong> soto: you can use a debootstrapped chroot, virtual machine / dual-boot with different releases, etc
[02:25] <soto> jdong: That's simpler than pbilder?
[02:25] <jdong> I guess all of those things "make more sense" than a pbuilder at first
[02:25] <LaserJock> well, throwing in a script to munge the changelog is trivial
[02:25] <jdong> soto: well... IMO it is simpler in that those are techniques already familiar while pbuilder is a new tool to learn
[02:25] <soto> jdong: It's not "not making sense". It's just too much work.
[02:26] <jdong> soto: the work is mostly in setting up the initial build infrastructure
[02:26] <jdong> afterwards, using it is a snap
[02:27] <soto> jdong: It's not as much a snap as it should be (c.f. portage)
[02:27] <jdong> DIST=gutsy prevu
[02:27] <jdong> that's all I type to build a package on my gutsy box
[02:27] <jdong> I'm sure pbuilder-dist is similar
[02:27] <jdong> I've got my infrastructure set up the way I like it
[02:28] <jdong> and portage is not all that simple when beginning either, you've got to set up your portage overlay and directory structure, and so on
[02:28] <soto> jdong: That imagine that still won't deal with the library issue I was describing
[02:28] <jdong> well, I don't know about pbuilder-dist, but prevu certainly does
[02:28] <soto> I imagine
[02:28] <jdong> prevu builds against itself
[02:29] <jdong> i.e. cd libfoo; prevu; sudo prevu-update; cd clientfoo; prevu
[02:29] <jdong> the latter prevu invocation automatically finds the built libfoo from the last run
[02:29] <jdong> but as I said, that's simply a wrapper around a bindmounted apt repo with dpkg-scanpackages
[02:30] <soto> jdong: Okay sound good. Will look into it. Wrappers are fine if they make my life easy (it's not the learning curve that bothers me, it's repetitive work that should be automated)
[02:31] <soto> Is there a way to build automatically from source-control (e.g. svn head)
[02:31] <jdong> soto: bzr-builddeb, I beleive "svn-builddeb" might also exist?
[02:31] <ScottK> svn-buildpackage I think
[02:31] <Nafallo> bzr-svn :-)
[02:32] <jdong> soto: but once you understand your own workflow, IMO scripting is a trivial thing to do. I'm sure 90% of us here have scripts we use in our daily workflow
[02:32] <jdong> Nafallo: LOL *hands him KDE svn*
[02:32] <RAOF> jdong: It's only terribly slow once :P
[02:32] <Nafallo> :-)
[02:32] <ScottK2> Nafallo: Only if I want to expend time learning tools I encounter no where outside Ubuntu.
[02:33] <soto> jdong: I don't mind scripting. I mind scripting when obviously many people must have already scripted what I wanted to do.
[02:33] <Nafallo> ScottK2: I only wanted to learn bzr.
[02:33] <jdong> soto: learning someone else's scripts sometimes is not as efficient as writing one's own
[02:33] <ScottK2> Nafallo: I already deal with cvs, svn, and git elsewhere.  N+1 VCS just isn't high on my list.
[02:34] <Nafallo> ScottK2: :-P
[02:34] <Nafallo> ScottK2: well, I only deal with bzr. learn svn isn't high on my list :-)
[02:34] <soto> jdong: I'm from the school of "Don't reinvent the wheel"
[02:35] <ScottK2> Sure.
[02:35] <jdong> soto: well this isn't reinventing the wheel. This is like reinventing the half-sheet of paper. Just make your own (tm)
[02:35] <Nafallo> but now I'm going to brush my teeth and go to bed. sure is about time...
[02:35] <Nafallo> Thu Feb 21 02:35:31 GMT 2008
[02:35] <jdong> Nafallo: bzr-toothbrush.
[02:35] <jdong> *ducks*
[02:35] <Nafallo> lol
[03:02] <LaserJock> oh heah, LP is back up
[03:02] <RAOF> Indeed it is.
[03:04] <ScottK2> Fresh with brand new misfeatures.
[03:04] <bddebian> hehe
[03:05]  * RAOF suddenly gets why bddebian is bdefreese in debian channels :)
[03:05] <LaserJock> I'm pretty sure it's still fixing more bugs than creating
[03:05] <bddebian> RAOF: Why, because they all hate me? :-)
[03:06] <LaserJock> hmm
[03:06]  * LaserJock suddenly wonders if there is a certain wiki page on wiki.debian.org :-)
[03:07] <bddebian> LaserJock: Hah, not hardly.  Unless it's bdefreese is a **** ;-P
[03:07] <LaserJock> sure not
[03:09] <LaserJock> hmm
[03:17] <LaserJock> what the heck, why is Mark sub'd to these .desktop bugs :/
[03:20] <LaserJock> man bug #1 is a mess
[03:20] <ubotu> Launchpad bug 1 in ubuntu "Microsoft has a majority market share" [Critical,Confirmed] https://launchpad.net/bugs/1
[03:22] <ScottK2> So now you they have the wonderful new feature of being able to subscribe for all the bug reports for a package.  This is somehow different than being a bug contact.
[03:22] <ScottK2> LaserJock: Personally, I wish they'd spend time fixing bugs instead of inventing two names for the same thing.
[03:23] <LaserJock> oh really?
[03:23] <LaserJock> I haven't seen this
[03:24] <lifeless> ScottK2: yes, it is different
[03:24] <lifeless> ScottK2: because its been done more consistently over a larger scope
[03:25] <LaserJock> I can't see the diff
[03:27] <ScottK2> lifeless: It's different for projects, distros, and milestones, but not for packages (which is not what the LP description claims).
[03:29] <LaserJock> hmm
[03:30] <LaserJock> they didn't really change anything for packages did they?
[03:32] <emgent> doko, ping
[03:32] <LaserJock> it's just "subscribe to bug mail" instead of the "Bug Contacts" or whatever it was
[03:33] <emgent> coredev here, there are an important merge to upload (with security fix) in hardy
[03:33] <emgent> malone #193869
[03:33] <ubotu> Launchpad bug 193869 in moin "Please merge moin-1.5.8 (main) from Debian unstable (Security FIX)" [Medium,In progress] https://launchpad.net/bugs/193869
[03:33] <LaserJock> you're asking in -motu? :-)
[03:34] <emgent> yep because in this chan there are more core-dev :P
[03:34] <LaserJock> I doubt that
[03:35] <LaserJock> why is that ubuntu2?
[03:35] <emgent> ups..
[03:44] <bddebian> persia: w00t, survex fixed in Debian!!
[03:46] <mneptok> who broke Debian's cervix?
[03:46] <bddebian> hehe
[03:48] <LaserJock> emgent: btw, since we're in an Alpha freeze you might ask slangasek if it's worth uploading now
[03:50] <emgent> LaserJock, i talked with geser
[03:50] <emgent> i know alpa freeze, but it's security upload.
[03:50] <LaserJock> well, think about it
[03:50] <LaserJock> how many people are running public hardy Moin servers?
[03:50] <LaserJock> and how many of those people *actually* use our packages?
[03:51] <emgent> small target
[03:51] <emgent> but, geser say to me that it's important fix and open bug about moins.
[03:51] <ScottK> emgent: You want to talk to someone in RM before uploading right now.
[03:52] <ScottK> emgent: Important, yes, but it can wait a day.
[03:53] <emgent> ScottK, uhm ok thanks for suggestions :P
[04:03] <ScottK2> Dear CDBS what magic incantation do I need to give you to actually stuff the preinst I made for you into the package?
[04:04] <TheMuso> ScottK2: Name the file correctly?
[04:04] <ScottK2> TheMuso: postfix-policyd-spf-python.preinst for package postfix-policyd-spf-python, right?
[04:04] <ScottK2> That's what I thought too, but not so far.
[04:06] <TheMuso> ScottK2: yeah, weird.
[04:07]  * ScottK2 checks for bugs ...
[04:14] <ScottK2> Even better.  The preinst is in the .deb, but doesn't get installed for some reason.
[04:14]  * ScottK2 tries again....
[04:14] <LaserJock> eww
[04:24] <StevenK> ScottK2: Does dpkg -I see it?
[04:30] <ScottK2> StevenK: Checking
[04:32] <ScottK2> StevenK: Is the a big i or a little l?
[04:33] <StevenK> Big I
[04:33] <StevenK> -i is install, -I is information
[04:33] <ScottK2> L says not installed
[04:34] <StevenK> minus captial indigo <.deb>
[04:36] <ScottK2> Using -D2 when installing produces http://pastebin.com/d51c22434
[04:36] <ScottK2> I'll get that now
[04:37] <ScottK2> StevenK: http://pastebin.com/d27629fc6
[04:38] <StevenK> dpkg (subprocess): unable to execute new pre-installation script: Exec format error
[04:38] <StevenK> Way cool
[04:38] <ScottK2> Does dpkg run the script before it installs it?
[04:38] <ScottK2> Cause it's not where I'd expect to find it.
[04:39] <StevenK> ScottK2: It worries me that it doesn't list a shebang line for preinst
[04:39] <AnAnt> can anyone help me with debconf ?
[04:39] <StevenK> ScottK2: It runs the preinst from a temporary location
[04:39] <ScottK2> It may be that some maintainer is an idiot and forgot to put it in
[04:39] <ScottK2> Ah
[04:39] <ScottK2> StevenK: Thanks.    Good night all.
[04:42] <LaserJock> heh
[04:42] <LaserJock> night ScottK
[04:46] <bddebian> Gnight ScottK2
[04:46] <bddebian> Grr GNUSTEP stuff is a PITA
[05:00] <LucidFox> bddebian> PITA?
[05:14] <bddebian> LucidFox: Pain In The Ass :)
[05:29] <LaserJock> yikes, I'm about to expire
[05:30] <jsgotangco> hey LaserJock long time no chat
[05:30] <nixternal> come on, you are to young to expire
[05:30] <nixternal> whoa, it is Jerome!
[05:30] <nixternal> wasabi jsgotangco
[05:30] <jsgotangco> hello true believers!
[05:30] <nixternal> hehe
[05:30] <LaserJock> hmm, must be the old-timers club
[05:30] <jsgotangco> nixternal: yeah ive been very very busy lately
[05:30] <nixternal> no doubt
[05:30] <nixternal> I hear you there with the very very busy
[05:31] <jsgotangco> nixternal: 2 product releases this quarter :/
[05:31] <nixternal> LaserJock: you and jsgotangco are older than I, I am still a n00b compared to you two legends :)
[05:31] <jsgotangco> doh
[05:31] <nixternal> you know, I do not miss product releases at all
[05:31] <LaserJock> hah
[05:32] <nixternal> I just play like I know what I am doing, and somehow, people keep falling for it
[05:32] <nixternal> it has worked great thus far, but now the secret is out, I am sure I am doomed
[05:32] <jsgotangco> that you use OS X to develop KDE?
[05:32]  * jsgotangco hides
[05:33] <LaserJock> jsgotangco: no, he's a Vista fanboi
[05:33] <Hobbsee> vista, actually.
[05:33] <LaserJock> hah
[05:33] <jsgotangco> more evil than i thought
[05:33] <nixternal> !nixternal
[05:33] <ubotu> Oh no!  The pointy-clicky Vista lover has arrived!  He's rumoured to be giving out free money, too!
[05:33] <nixternal> see what Hobbsee started
[05:34] <jsgotangco> i must admit though, that most of my desktop work is done in osx now but all the server is ubuntu
[05:34] <jsgotangco> i have to catch up with these rails cultists
[05:34] <nixternal> I have OS X here too, brand new, and I absolutely hate it
[05:35] <LaserJock> boooo
[05:35] <LaserJock> OS X is the bomb
[05:35] <nixternal> my buddy gave me a Mac Pro with all of the bells and whistles
[05:35] <StevenK> LaserJock: Only a Steve Jobs fanboi would say that.
[05:35] <nixternal> the nicest thing about the entire rig is the 23" Cinemedia or whatever they call it
[05:35] <jsgotangco> i just like the fact that whatever i do in OS X in rails just works when i cap deploy to ubuntu
[05:35] <LaserJock> StevenK: crap, you found me out
[05:36] <nixternal> hahaha
[05:36] <nixternal> Steve Jobs is a hell of a lot better Ballmer
[05:36] <nixternal> Jobs at least makes sense when he talks
[05:59] <StevenK> Oh, I found nixternal's heroes.
[05:59] <StevenK> http://msdn.microsoft.com/events/hero/sfbio/
[06:00] <LaserJock> StevenK: lol!
[06:03] <nixternal> that's great stuff, where can I get one of those? :p
[06:03] <StevenK> nixternal: And here I was thinking you came up with them.
[06:05] <LaserJock> StevenK: probably for one of those fancy MBA classes
[06:06] <nixternal> haha
[06:06] <nixternal> my MBA classes are on hold right now until the school opens back up
[06:20] <InsClusoe> Hi to everyone.. I have created debdiff for bitesize bug#181860. I am uploading it to the bug.
[06:21] <InsClusoe> After that, whom should I subscribe to the bug?
[06:24] <InsClusoe> anybody's got a minute to spare?
[06:29] <pooli1> hi
[06:29] <poolie> can anyone give me a clue about this error
[06:29] <LaserJock> InsClusoe: it's a Universe package?
[06:29] <poolie> cp: cannot stat `./debian/overrides/bzrtools': No such file or directory
[06:29] <poolie> so, obviously that file is missing
[06:29] <poolie> but i'm not sure why it would be expected to be there
[06:31] <InsClusoe> LaserJock: how do I find that?
[06:31] <LaserJock> InsClusoe: apt-cache policy <packagename>
[06:32] <InsClusoe> it's from main.
[06:33] <InsClusoe> LaserJock: Apt reports that it's from feisty/main on my pc.
[06:37] <LaserJock> InsClusoe: so then you need to subscribe ubuntu-main-sponsors
[06:38] <InsClusoe> LaserJock: ok.. Thank you.
[06:40] <InsClusoe> ok..... Got to go now. Have a nice day.
[06:49] <superm1> TheMuso, i just wanted to remind you about pulseaudio + mplayer, making it start on pulse and fallback to alsa (didn't see a fix committed on hardy-changes or LP)
[06:56] <TheMuso> superm1: Its in bzr.
[06:56] <superm1> TheMuso, were you going to hold off pushing it then?
[06:56] <TheMuso> superm1: I thought there may have been more work people wanted to do. If not, I'll upload.
[06:56] <superm1> TheMuso, well i see one bug
[06:56] <superm1> that might be worthwhile to add as well
[06:57] <superm1> https://bugs.edge.launchpad.net/ubuntu/+source/mplayer/+bug/191488
[06:57] <ubotu> Launchpad bug 191488 in mplayer "[mplayer] [DSA-1496-1] several buffer overflows" [High,Confirmed]
[06:57] <TheMuso> ok will have a look in a bit.
[06:57] <superm1> that bug might actually even be worth adding nominations for other releases too
[06:57] <superm1> since it's got some CVE's on it
[06:59] <TheMuso> Yeah, anyway, will look later.
[06:59] <superm1> okay :)
[07:11] <warp10> hi all!
[07:14] <Unksi> hi
[07:26] <dholbach> good morning
[07:31] <AstralJava> Morning dholbach.
[07:31] <dholbach> hi AstralJava
[07:45] <\sh> moins
[07:46] <\sh> does anybody has problems with ff3 + adobe flash plugin and sound?
[07:47]  * Hobbsee was viewing youtube earlier with it, without problems
[07:47] <\sh> hmm...then it's the combination: usb headset + ff3 + flash
[07:47] <\sh> the headset works under gnome without a problem...but only flash sound is not played
[07:48] <\sh> and that's a problem when you need it for your companies product ,-)
[07:50] <uniscript> this is probably a FAQ but I can't seem to get debmirror to get past NO_PUBKEY 40976EAF437D05B5
[07:51] <\sh> uniscript: feed --ignore-release-gpg to debmirror or add the key with apt-key
[07:51] <uniscript> gpg is only interested in the last 32-bits
[07:51] <uniscript> of the keyid
[07:53] <uniscript> --ignore-release-gpg is working but seems far from ideal and I've jumped through all the hoops but still no joy
[07:54] <\sh> uniscript: what mirror is it, the maintainer of the mirror has a pubkey to add eventually...
[07:54] <\sh> uniscript: I'm using it for my complete ubuntu mirror at home
[07:55] <uniscript> archive.ubuntu.com
[07:55] <\sh> then add the ftpmaster key to your root gpg keyring...just try that
[07:55] <\sh> pub   1024D/437D05B5 2004-09-12
[07:55] <\sh> pub   1024D/FBB75451 2004-12-30
[07:55] <\sh> both
[07:55] <\sh> I have them added to /root/.gpg/
[07:56] <uniscript> I have the former but not the latter
[07:56] <\sh> gpg --recv 0xFBB75451 :)
[07:57] <uniscript> no joy
[07:57] <uniscript> not running debmirror as root
[07:57] <uniscript> so added to my keyring
[07:58] <uniscript> I've been happily mirror gutsy and feisty and friends in the past
[08:08] <slytherin> hello team. :-)
[08:23] <TheMuso> c/
[08:40] <slytherin> Does a MIR bug needs to be marked confirmed?
[09:30] <geser> good morning
[09:56] <Laibsch> Is there some kind soul to review http://revu.tauware.de/details.py?package=anki
[09:56] <Laibsch> ?
[09:58] <Hobbsee> does it have an exception?
[09:58] <hellboy195> Laibsch: does debian has this programm + version?
[09:59] <Laibsch> hellboy195: no
[09:59] <Laibsch> Hobbsee: you mean an exception to enter hardy?  that is not what I am looking for.
[09:59] <hellboy195> Laibsch: I'm not MOTU but then it should be anki_0.9.3-0ubuntu1.dsc  ;)
[09:59] <Hobbsee> Laibsch: correct.
[09:59] <Laibsch> hellboy195: upstream source is anki_0.9.3-1
[09:59] <Hobbsee> why do you want the review then?
[10:00] <Fujitsu> To get in early for intrepid.
[10:00] <Laibsch> Hobbsee: so it gets into ubuntu eventually, I thought that was the whole reason for revu
[10:00] <Fujitsu> It's not unheard of.
[10:00] <Fujitsu> But things do get forgotten after a while.
[10:00] <Fujitsu> So it's probably not a great idea to do it two months early.
[10:00] <Laibsch> I have had a "needs-packaging" for months if not years now
[10:00] <Laibsch> "needs-packaging" bug open
[10:00] <Fujitsu> I'm not sure I see the relevance.
[10:01] <Laibsch> Fujitsu: the relevance of anki?
[10:01] <Fujitsu> The relevance of the length of time that the bug has been open.
[10:01] <Laibsch> well, I don't see the relevance of quite a lot of packages for me personally, but I can see that it might be a great deal to others ;-)
[10:02] <Hobbsee> Laibsch: ok.  but you do realise that various of the build-deps might change between now and intrepid, and that certainly debian/changelog will change?
[10:02] <Laibsch> Fujitsu: OK, I want to make sure this eventually gets in so I did some work
[10:02] <hellboy195> Laibsch: but it has to be 0ubuntu1. Hobbsee agree?
[10:02] <Fujitsu> hellboy195: I think it should be -1, but only because it might as well go to Debian first at this stage.
[10:03] <Laibsch> hellboy195: I went with what dch -i gave me.  But thanks for your review.  This is the kind of stuff I am looking for
[10:03] <hellboy195> Laibsch: not when it's wrong xD
[10:03] <Laibsch> sure
[10:03] <Laibsch> I want to hear about what is wrong
[10:03] <hellboy195> Laibsch: I mean when I'm wrong ;)
[10:04] <hellboy195> Fujitsu: and if it doesn't go to Debian first?
[10:04] <Fujitsu> hellboy195: Then -0ubuntu1 is necessary.
[10:05] <hellboy195> :)
[10:05] <Laibsch> Well, I don't object to it going to debian first
[10:05] <uniscript> so why are so many packages -1ubuntu1?
[10:05] <hellboy195> uniscript: merges from debian
[10:05] <Laibsch> But I am not a debian dev
[10:06] <uniscript> got it, ta
[10:06] <hellboy195> :)
[10:06] <Laibsch> If anyone is willing to make an effort to get this into debian, I am all for it
[10:06] <Laibsch> I'll support as much as I can
[10:07] <hellboy195> Laibsch: well as you bring it to REVU to get it into Ubuntu there is also a site for uploading it to debian
[10:07] <Laibsch> But as I said yesterday, the package is usually in good shape and easy to maintain (look at how small the necessary changes were)
[10:07] <Laibsch> hellboy195: Is there?
[10:07] <hellboy195> Laibsch: http://mentors.debian.net/cgi-bin/welcome
[10:07] <Laibsch> where?
[10:08] <Laibsch> hellboy195: Ah, nice.  I was totally unaware of that
[10:08] <Laibsch> That will be a better route, then, I guess
[10:08] <hellboy195> Laibsch: if it will be in debian the next months it will also be in ubuntu :O
[10:09] <Laibsch> Aha, I thought that debian still did not carry the whole list of packages from debian
[10:09] <Laibsch> hellboy195: The site makes it appear that it is targetted for the original author of the software
[10:10] <Laibsch> which I am not
[10:10] <Fujitsu> We carry everything that's in Debian main, except for packages that are explicitly blacklisted.
[10:10] <Laibsch> I am just a packager trying to get it into debian
[10:10] <Laibsch> and ubuntu
[10:10] <hellboy195> Laibsch: AFAIK everybody can package and upload it. It's like REVU
[10:10] <Fujitsu> Laibsch: What gives you that idea?
[10:10] <Laibsch> OK
[10:10] <Laibsch> Will do
[10:11] <Laibsch> Fujitsu: "Still a large number of packages is       maintained by non-official developers. How do they get their work into       Debian ..." and the whole first paragraph
[10:11] <Laibsch> "I want to have my package uploaded to Debian"
[10:11] <Laibsch> *my*
[10:11] <Laibsch> It is not my package
[10:11] <Fujitsu> Package != piece of software
[10:11] <Laibsch> or at least not my software
[10:11] <Fujitsu> You've made the package
[10:12] <Laibsch> yeah, but the wording does not sound like revu initially
[10:12] <Laibsch> I hesitated
[10:13] <hellboy195> Laibsch: do you believe every programmer packages their software at there own? NO. If you hestiate contact upstream
[10:16] <Laibsch> I am in contact of upstream
[10:16] <Laibsch> Of course I know that not every programmer packages their stuff
[10:17] <hellboy195> Laibsch: just ask him if you are allowed ;=)
[10:17] <Laibsch> But that does not automatically mean that mentors.debian.net is open to contributions from just any old fart who comes around
[10:17] <hellboy195> Laibsch: if upstream allows you, yes
[10:18] <Laibsch> I mean the reasoning could be that "if you have written the stuff yourself the chances are higher you will stick around and not abandon the package after initial upload"
[10:18] <Laibsch> so such a policy could make sense
[10:18] <Laibsch> and the wording was at least ambivalent
[10:18] <Fujitsu> That's more of a problem in Ubuntu, unfortunately.
[10:18] <Laibsch> 'tis all i am saying
[10:19] <Laibsch> hellboy195: the software is of course FOSS, otherwise, it would not get into debian or ubuntu anyway
[10:19] <Laibsch> So I can do as I please with the software and upload it to any distribution I like
[10:19] <Laibsch> ;-)
[10:20] <hellboy195> Laibsch: yeah but it sounds better when upstream *allowed* it. Hmm I don't know anybody who refused it ^^
[10:21] <Laibsch> The darn mentos.debian.net won't accept my GPG key
[10:21] <Fujitsu> Mmm... Mentos...
[10:21] <Laibsch> the fresh-maker?
[10:21] <Laibsch> ;-)
[10:21] <hellboy195> lol
[10:21] <Fujitsu> Laibsch: What's the error?
[10:22] <Laibsch> Error: Please check that the PGP public key you uploaded is in             the correct format. You need to run "gpg --export --armor             your-email-address > public-key-file" to create a proper             file.
[10:22] <Laibsch> which is of course what I did
[10:22] <Fujitsu> Hmm.
[10:22] <Laibsch> #mentors.debian.net does not seem to exist
[10:23] <azeem> it's #debian-mentors on oftc
[10:23] <Laibsch> Aha
[10:23] <Laibsch> Let's see
[10:24] <azeem> Laibsch: it's more general than just mentors.debian.net discussions, it's like #ubuntu-motu for Debian really
[10:27] <persia> bddebian: Thanks for the heads up.  Any further refinement of the newpki-client patch?
[10:31] <azeem> persia: bddebian isn't up yet
[10:32] <slicer> TheMuso: (re: 9 hours ago:) Mumble
[10:32] <TheMuso> slicer: Ah ok.
[10:32] <persia> azeem: Yes, but as I do, he tends to notice things said hours previously.
[10:33] <azeem> persia: he's not online when he's sleeping
[10:33] <azeem> 11:32 [OPN] -!- There is no such nick bddebian
[10:33] <azeem> persia: otherwise, I wouldn't notify you, of course
[10:34] <azeem> or are you saying he's reading channel logs?
[10:34] <persia> So, I use irclogs.ubuntu.com to follow discussion for 14-16 hours of each day, rather than actually checking backscroll for these channels.
[10:34] <azeem> ah
[10:34] <azeem> he never does that for the other channels we're on together, so I assume he wasn't here either
[10:34] <azeem> sorry
[10:34] <persia> Maybe he doesn't :)
[10:35] <azeem> well you'll find out when he magically knows about our conversation
[11:07] <nuthark> ubuntu-motu
[11:16] <Laney> Where are the files which are removed by --purge defined?
[11:17] <persia> Laney: /var/lib/dpkg/
[11:19] <Laney> persia: I mean for a particular package. I'm working on a bug where I want to prevent a particular which was created by a package being deleted with --purge if the user wishes.
[11:19] <nuthark> why
[11:21] <persia> Laney: Right.  /var/lib/dpkg contains several directories.  ./info is likely the one you will find most interesting, containing per-package information about the maintainer scripts, included files, configuration files, etc.
[11:21] <Laney> nuthark: bug #162426
[11:21] <ubotu> Launchpad bug 162426 in mrtg "Purging MRTG removes data from /var/www/mrtg" [Undecided,Confirmed] https://launchpad.net/bugs/162426
[11:21] <nuthark> why
[11:22] <persia> The solution to bugs of this class are often to not ship the affected file or directory in the package, and create it if it does not previously exist in the postinst (which means removing it in the postrm if it is empty: only preserve things that actually have user-generated data).
[11:22] <nuthark> why
[11:22] <Laney> Are you trolling?
[11:22] <nuthark> yes
[11:22] <persia> nuthark: Are you trolling for results, or just for fun?
[11:22] <nuthark> poor persia
[11:23] <persia> (in other words, would you actually like a lecture on the rationale for preserving user-generated data and removing auto-generated files)
[11:23] <nuthark> poor persia
[11:25] <Laney> persia: The package puts some images in that directory though. Would that make a difference?
[11:26] <nuthark> poor Laney
[11:26] <hellboy195> nuthark: kickban :)
[11:26] <persia> Laney: Yes.  If the package populates the directory, it needs to ship the directory in the package.  In that case, you need to inspect the purge behaviour carefully to see at what point the user-generated data is being removed.
[11:26] <nuthark> poor persia
[11:26] <hellboy195> lol
[11:27] <persia> It may be that the postrm is too agressive, or that there is something else involved.  I recommend reviewing http://women.debian.org/wiki/English/MaintainerScripts for an overview before digging in too deeply, as other sources of documentation tend to be somewhat sparse in the description of how a purge actually works.
[11:32] <Laney> persia: That's a good page!
[11:33] <persia> Laney: Indeed it is.  It's the only explanation of maintainer scripts that ever really made sense to me.  The others all seem either too vague or too focused on details of policy rather than providing an overview.
[11:35] <Laney> persia: I managed to identify in the postrm where the directory was being forcibly removed, but the reviewer asked for a debconf prompt to be used. Can you take a look at this script and tell me if it looks OK to you? http://paste.ubuntu-nl.org/56831/
[11:36] <Laney> So remove the directory if the user wants, otherwise let dpkg work as it usually would.
[11:44] <persia> Laney: Sorry, but I really don't know anything about debconf use.  I couldn't tell you if that worked without testing, and don7t have time now for proper review.
[11:44] <Laney> Ah OK never mind.
[11:44] <Laney> Someone raised doubts anyway. It seems to work for me so I might just attach it to the bug and let others decide which way is best ;)
[11:45] <mok0> heh, the new version of gcc issues compiler warnings for xpm files
[11:45] <mok0> warning: deprecated conversion from string constant to ‘char*’
[11:45] <persia> Um.  Should .xpm files be compiled?
[11:45] <mok0> persia: they are sometimes included
[11:46] <mok0> persia: an xpm is  C code
[11:46] <persia> Ah.  I suppose.
[11:46]  * mok0 thinks we need an xpm corrector for the millions of xpm files out there...
[11:48] <soren> mok0: What's the problem with them exactly?
[11:48] <mok0> soren: it's because they are defined as char * instead of const char *
[11:48] <soren> Ah.
[11:49] <mok0> soren: the new gcc version is stricter on embedded strings
[11:50]  * persia wonders if those parsers that don't compile the .xpm files would break if the .xpm files were mass-updated.
[11:51] <mok0> persia: probably :-)
[11:52] <persia> If anyone wants a fairly code-easy research task: bug #136852 may be interesting.  Lots of scope for possible alternate solutions and general usability improvement.
[11:52] <ubotu> Launchpad bug 136852 in module-assistant "lists madwifi but cannot build the module" [Low,Confirmed] https://launchpad.net/bugs/136852
[11:52] <mok0> for example, one xpm starts: static char * file_new_xpm[] = { ...
[11:53] <mok0> it should be static const char * file_new_xpm[] = { .. to avoid the warning. It is not likely that it would give problems, because you can cast a const char * to a char * without problems. But, there's always ol'e Murphy...
[11:54]  * tsmithe finds it funny that, after the discussion has calmed down on debian-mentors and debian-multimedia, actually pointing this out and requesting sponsorship causes everyone to become silent
[11:54] <persia> tsmithe: context?
[11:54] <tsmithe> wrt to fluid
[11:57]  * persia grumbles at nautilus for preferring to use the name of a file rather than the magic number to determine the file type.
[11:58] <Iulian> Hi
[11:58] <mok0> persia: it should use the mime type
[11:59] <tsmithe> persia, i'm always intrigued as to how nautilus (and other apps) actually determine file type in the first place, without using file extensions. how does it work? (can you point me to a doc?)
[11:59] <mok0> tsmithe: mime types now peek inside the file
[12:00] <tsmithe> ahh, and, say, look at the first few bytes to see what it is?
[12:00] <mok0> tsmithe: they used to be based on extensions but that changed
[12:00] <tsmithe> (like gzip has a recognisable header)
[12:00] <tsmithe> yes, extensions are ugly
[12:00] <mok0> tsmithe: exactly
[12:00] <theseinfeld> TheMuso LucidFree are you up for some revu of http://revu.tauware.de/details.py?package=libdc1394-22 ?
[12:00] <tsmithe> cool, thanks
[12:00] <persia> tsmithe: Depends on the application.  There are at least four systems in place: magic numbers, Debian MIME definitions, KDE MIME definitions, and GNOME MIME definitions.  Freedesktop.org has gone a long way towards integrating the latter two, and there are efforts in Debian to get along with that, but it's not quite there yet.
[12:01] <tsmithe> hmm. so what's a "magic number"?
[12:01] <persia> mok0: Not always: it depends on how the MIME-type is defined in the MIME database for the desktop environment.  Some use magic, some use extensions, some use a mix.  Take a look at your .desktop files to see the wide variance of definitions.
[12:01] <persia> tsmithe: man magic
[12:02] <mok0> tsmithe: that's what "file" uses
[12:02] <tsmithe> aha
[12:02] <mok0> tsmithe: old unix stuff
[12:02] <persia> (and other tools, with various degrees of compatibility to file)
[12:02] <tsmithe> (file is very impressive to me)
[12:02] <mok0> tsmithe: cool indeed
[12:03] <tsmithe> and, well, it all seems quite simple, really
[12:04] <theseinfeld> superm1 are you there?
[12:05] <mok0> for mime discussion, look here http://wiki.debian.org/MimeTypesSupport
[12:07] <persia> tsmithe: Please poke me when fluid hits the archives: it may benefit from a merge between the most recent Ubuntu upload and whatever is on mentors or Debian at that point.  Also, I forgot to set lzma compression.
[12:08] <mok0> I am working on pgadmin3, that has around 5Mb i18n files. Lintian complains about it. What is standard procedure in such a case? There is another "all" package pgadmin-data, which is required, so I could put the i18n stuff in there w/o probs.
[12:08] <tsmithe> persia, of course. and, do we want to fix the mime type for sf2 files somehow? according to d-multimedia, they appear as video/x-msvideo
[12:10] <persia> Erm.  That would be great.  man dh_installmime for some hints for the debian MIME helper, create a .desktop file to define the MIME type for fdo compliant DEs, and we should be mostly good.  Extra points for defining the right magic, but that's a little harder.
[12:11] <tsmithe> right. but is defining the mime type of the soundfont really down to the soundfont package? something else seems to have determined it previously; what if we have more than one soundfont installed?
[12:13] <persia> Generally, MIME types are defined by either a common provider or a common consumer.    As we only have one provider, it seems a good place to start for now.  As the scope of free soundfonts grows, maybe somewhere else will seem more appropriate (e.g. timidity or gstreamer-midi, or whatever).
[12:14] <tsmithe> makes sense, and it is important to have it done correctly.
[12:38] <slytherin> persia: Have you seen the the mail regarding 'glassfishv2ur1' sent to motu list?
[12:39] <persia> slytherin: Yes.  Personally, I'd like to see a "glassfish" package and documentation of the upgrade process in the release notes, but I'm not sure how much cultural shift can be accomplished before it is too late for hardy.
[12:41] <persia> slytherin: If you have time, would you mind inspecting the package on REVU, and helping Nitya get it them little more compliant with policy?  I think they're still multiverse, but they need help.
[12:41] <slytherin> persia: What I am not able to understand is whether it is really different form the existing glassfish packages or just an upgrade.
[12:42] <persia> That's why I would prefer a "glassfish" package.  It's a new major upstream version, which may be able to be installed in parallel if collected from the upstream site (although I don't know if it is completely clean within Ubuntu).
[12:44] <slytherin> let me have a look
[12:44] <slytherin> I will also ask question in the bug.
[12:45] <persia> There are also parallel version upgrades to other parts of the application cluster (e.g. sunwderby) which makes it annoyingly invasive.  On the other hand, it's a far-edge multiverse app, and so the potential for regression or breakage is low: I am taking the assumption that if Nitya (and others) can get it clean and compatible in the next couple weeks, it has at least a 50% chance of getting FFe approval.
[12:45] <persia> slytherin: Thanks :)
[12:46] <slytherin> If there aren't many rdepends then I would prefer an upgrade instead of a parallel install
[12:50] <hellboy195> Debian has a "SHELL = /bin/bash" in their rules file. should I delete it?
[12:52] <DktrKranz> gpocentek, your fix in bug 41491 is not sufficient since a packages won't install. Mind looking at it when you have time?
[12:52] <ubotu> Launchpad bug 41491 in wzdftpd "Dapper: Broken dependencies for some wzdftpd modules" [Medium,Fix released] https://launchpad.net/bugs/41491
[12:54]  * bigon is wondering if empathy (telepathy based IM application) could be considered as a gnome app and thus get the general FF gnome exception
[12:54] <persia> hellboy195: Only if it builds cleanly with dash (with that in place, it likely doesn't)
[12:54] <persia> bigon: Possibly, but it never hurts to file a bug.
[12:54] <hellboy195> persia: k, thx :)
[12:57] <hellboy195> persia: whats the difference between sed -e "s/=PY/$(python_ver)/g;  and  sed -e "s/=PY/$(PYVER)/g; ?
[12:57] <gpocentek> DktrKranz: it works for me
[12:58] <gpocentek> just tested from the -proposed repo
[12:58] <persia> hellboy195: s/python_ver/PYVER/1 ?
[12:58] <persia> Less flippantly, it uses a different variable (and no, I have no idea where those variables are defined)
[12:59] <DktrKranz> gpocentek, I'll have a better look, then. Probably my VM is not clean.
[12:59] <hellboy195> persia: hmm I'll keep the debian ones for now
[12:59] <gpocentek> DktrKranz: what was the error, wrong deps again?
[13:00] <DktrKranz> gpocentek, so it seems, but I'll try with a fresh Dapper, probably it's something wrong by my side
[13:00] <gpocentek> ok
[13:00] <DktrKranz> It's a weird error.
[13:01] <slytherin> persia: Initial observations. We are carrying glassfish-bin from feisty (1.0.1). Current source in Ubuntu is some pre release of 2.1 but there is no glassfish-bin package and glassfish metapackage is commented in debian/control. Let me check what is state in Debian so that I can add comments accordingly.
[13:02] <persia> slytherin: Best to coordinate with Nitya, rather than me: I haven't even looked into the packages deeply, beyond getting a little disturbed at the possibility of having four different copies of Derby in the archives.
[13:02] <slytherin> :-)
[13:11] <hellboy195> persia: the merge of wxwidgets is not yet too difficult. I'm happy debian applied already a lot :)
[13:20] <norsetto> peace everybody
[13:23] <zul> dholbach: ping #181690
[13:25] <slomo> is Emmet Hikory sometimes here? what's his nickname? :)
[13:26] <norsetto> slomo: persia, be kind to him ....
[13:26] <slomo> ah
[13:26] <slomo> hi persia :) i'm looking at your wildmidi package now... but why did you choose that and not timidity? (afaik both are "sleeping" upstream but working well)
[13:28] <slomo> persia: if you're there i'd also like to tell you some things i would like to see changed
[13:30] <persia> slomo: Because timidity launches a daemon and doesn't have an easily extracted library.
[13:31] <persia> Also, yes, the package needs some work.  There's a couple improvements already in the Ubuntu version, and more would be welcome.  The mentors version was mostly to spike interest in case someone watching the Debian bug wanted to get libgstwildmidi.so working before I could.
[13:32] <slomo> persia: oh, i'll merge in the ubnutu changes then... would you like me as Uploaders? in that case i'll get the package ready for upload, fix gstreamer and get it uploaded ;)
[13:33] <slytherin> persia: Can you check the dialog I have added to the bug and see if it makes sense?
[13:33] <slomo> persia: hm, the ubuntu version has no changes?
[13:33] <persia> slomo: That would be great.  I'm not especially attached to the package, although I am willing to track upstream (if it revives).  I more wanted to gfix the gstreamer-midi bug.  Depending on the volume of your changes, and the degree of your interest, feel free to be Maintainer (with me as Uploader).
[13:34] <persia> No changes?  I thought sistpoty made a couple.  Perhaps the mentors version was after that.  My apologies for the confusion.
[13:34] <slomo> persia: i'd prefer you as maintainer and me as uploader if that's no problem for you :) and i'll upload the version i upload to debian to ubuntu too, as -1~hardy1 or something, ok?
[13:36] <persia> slomo: Given that upstream hasn't been active in years, it's no problem for me to be maintainer, and I'll try to respond to bugs.  Regarding the Ubuntu version, it's MOTU maintained, so your improved upload would be appreciated.  I'd suggest -0ubuntu2 rather than -1~hardy1 just in case there is some other issue that makes a sync hard, and someone wants to backport.
[13:38] <persia> Thanks a lot for chasing this.  I think the issue is that libwildmidi requires there to be some configuration definition to initialise, which might require creating a timidity.cfg (or alternative) for embedded use, and possibly using fluid-soundfont, but I've not gotten far enough to be sure.
[13:38] <slomo> persia: ok, i'll try to get it working :)
[13:39] <persia> Thanks.  I'll be taking another look at MIDI this weekend (assuming the soundfont gets through NEW), and would be happy to test or track things down if you've run into something and would like a hand.
[13:40] <emgent> heya people
[13:45] <LucidFox> hello emgent
[13:45] <LucidFox> (a bit late, though :))
[13:46] <emgent> heya
[13:47] <slomo> persia: got it working (i guess), still have to find a midi file to try it on ;)
[13:47] <mok0> Does someone here know about locale catalogs?
[13:47] <slomo> persia: want to give me an url to one?
[13:47] <slytherin> anyone handling sugar packages here?
[13:49] <persia> slomo: http://www.buzzwood.com/midtest.htm is supposedly a good way to torture test.  You may find ftp://ftp.personalcopy.net/pub/miditest.zip a valid compressed archive of them, but I've not inspected that personally.
[13:51] <persia> slytherin: re: bug comment, looks reasonable.
[13:52] <slomo> persia: and found a big in wildmidi and the gst plugin *fixing* :)
[13:52] <slytherin> persia: ok
[13:53] <persia> slomo: Excellent :)  Thanks again for running with it.  Is there somewhere on alioth it might make sense to put the wildmidi source?
[13:54] <slomo> persia: not for a single package i guess
[13:54] <slomo> persia: oh, collab-maint maybe
[13:57] <persia> slomo: Hmm.  I'll look into that, but I think "maybe" has considerable weight for collab-maint.  In-archive works as well.
[13:57] <slomo> persia: do you prefer dpatch, quilt or simple-patch-system?
[13:58] <tsmithe> persia, regarding fluid and timidity, i had the idea of patching timidity to look in /etc/timidity/cfg.d for configs, and having fluid install a "fluid.cfg" file describing the correct configuration there
[14:00] <dholbach> zul: what about it?
[14:00] <zul> dholbach: I included it with the upload Im about to do
[14:00] <persia> slomo: Whichever is your favorite, as you are making the first patch.  I mostly chase QA stuff, and so have used them all often.  Given the inactivity upstream, I'd prefer not using inline patches (not planning to merge from VCS).
[14:01] <dholbach> zul: OK, anything I need to do?
[14:01] <zul> no you were mentioned in the bug report so I thought I would give you a heads up
[14:02] <slomo> persia: seems to have problems reading the timidity.cfg and freepats.cfg (maybe only supports an older format?) i'm trying to get it working now
[14:02] <persia> tsmithe: Given how badly freepats works for the default install, I'm thinking of just swapping the dependency for now, rather than something so complicated for hardy.  using a cfg.d for hardy+1 would be a great feature.
[14:02] <norsetto> heya dholbach, thx for the invitation :-)
[14:03] <persia> slomo: That sounds familiar.
[14:03] <tsmithe> persia, but swapping the dependency would incur an extra 60MiB of required downloading
[14:03] <slomo> persia: yay, i have sound ;)
[14:03] <persia> tsmithe: For an optional universe package (not on the CD).
[14:03] <tsmithe> true
[14:03] <slomo> persia: you're right, freepats sounds very bad :)
[14:03] <persia> slomo: Excellent!  Thanks again.
[14:04] <persia> slomo: fluid-soundfont is also on mentors (thanks tsmithe) if you want better sound :)
[14:04] <slomo> persia: license ok? do you have a sponsor already?
[14:04] <tsmithe> (or to upload it ;) )
[14:04] <tsmithe> i'm also interested in the work involving wildmidi. do i fathom that slomo is uploading to debian?
[14:05] <slomo> tsmithe: that's the plan
[14:05] <tsmithe> excellent. then does that mean that gst-midi should be enabled? i'm not currently up to speed with its current status
[14:07] <slomo> tsmithe: yes
[14:07] <persia> slomo: It's MIT license, and it's tsmithe's package.  I've seen correspondance with upstream, and am fairly confident it's about as close to a free soundfont as we're likely to get before someone writes a script to generate one from free algorithmic synthesizers.
[14:08]  * persia goes to sleep
[14:08] <slomo> persia: uploading
[14:09] <tsmithe> slomo, all sounding good.
[14:09] <tsmithe> would you be willing to sponsor fluid-soundfont, too?
[14:11] <slomo> tsmithe: url? :)
[14:13] <tsmithe> slomo, hang on
[14:13] <tsmithe> slomo, http://mentors.debian.net/debian/pool/main/f/fluid-soundfont/fluid-soundfont_3-1.dsc
[14:14] <slomo> tsmithe: ok
[14:15] <tsmithe> slomo, excellent!
[14:46] <slomo> tsmithe: 127 MB?!
[14:46] <slomo> omg
[14:50] <tsmithe> slomo, er, yeah. it's hefty, that's for sure
[14:50] <tsmithe> but it's as complete as they get
[14:50] <tsmithe> (and it sounds nice, too)
[14:52] <RainCT> persia: will you have a moment to test if a package builds on amd64 later today?
[14:52] <geser> RainCT: [15:08:16]             -*- persia goes to sleep
[14:53] <slomo> tsmithe: that's too large for my taste, sorry :/
[14:53] <slomo> tsmithe: i doubt it will be accepted
[14:54] <geser> RainCT: will an amd64 pbuilder suffice?
[14:54] <tsmithe> slomo, why do you doubt that?
[14:54] <RainCT> geser: I think yes :)
[14:55] <geser> RainCT: have you a link to the .dsc?
[14:55] <slomo> tsmithe: because it's large, the largest debian package ever (afaik) and it won't make mirrors happy ;)
[14:55] <slomo> tsmithe: if you find a larger debian package i'll sponsor and review it ;)
[14:56] <RainCT> geser: I said later, it's not ready yet ;)
[14:56] <_MMA_> slomo: Arent some of the games that large? Tremulous, Warsow, Open Arena or the like?
[14:56] <geser> RainCT: ah, I parsed the later in the context of persia sleeping now
[14:57] <geser> _MMA_: you forgot urbanterror-data
[14:57] <_MMA_> "or the like"
[14:57] <tsmithe> _MMA_, slomo, and openoffice.org
[14:57] <tsmithe> which ways in at 279MB
[14:57] <tsmithe> *weighs
[14:58] <slomo> tsmithe: good point
[14:58] <tsmithe> ;)
[14:58] <slomo> persia: ok, wildmidi finally uploaded
[14:58] <slomo> persia: many many patches ;)
[15:06] <mok0> ScottK: pgadmin3 almost ready
[15:10] <slomo> tsmithe: looks good
[15:10] <tsmithe> slomo, :)
[15:10] <slomo> tsmithe: shouldn't there be a timidity config file or something?
[15:11] <tsmithe> slomo, as i said to persia, i'm going to (for a later revision) look at updating timidity to search a cfg.d directory for configs
[15:11] <tsmithe> once i've done that, i'll include a config
[15:11] <tsmithe> atm, i'm keeping the first release simple
[15:11] <slomo> tsmithe: a sample config in /usr/share/doc would be nice though
[15:11] <slomo> tsmithe: so users like me can actually use it ;)
[15:11] <slomo> tsmithe: would be nice if you could add it before i upload
[15:11] <tsmithe> slomo, okey
[15:12] <slomo> tsmithe: ping me when you're done and uploaded the new version :)
[15:13] <tsmithe> slomo, will do
[15:16] <bddebian> Heya gang
[15:17] <\sh> grmpf
[15:17] <bddebian> Well hello to you too \sh :-)
[15:17] <geser> bddebian: Hi
[15:17] <bddebian> Heya geser
[15:19] <norsetto> heya bddebian
[15:20] <bddebian> Hi norsetto
[15:20] <emgent> heya people
[15:21] <bddebian> Hi emgent
[15:21] <hellboy195> \sh: don't worry. next wine release is soon ;)
[15:30] <\sh> hellboy195: well, it doesn't help...when the problem is raised by the compiler
[15:31] <hellboy195> \sh: I just wanted to cheer you up ^
[16:07] <tsmithe> slomo, new version uploaded. sorry it took so long.
[16:08] <slomo> tsmithe: no wonder, 128 mb take some time ;)
[16:08] <slomo> tsmithe: can you give me the url again please? :)
[16:08] <tsmithe> slomo, well, that wasn't the delay (just me being slow). i did a orig-source-free upload, tbh. the url is http://mentors.debian.net/debian/pool/main/f/fluid-soundfont/fluid-soundfont_3-1.dschttp://mentors.debian.net/debian/pool/main/f/fluid-soundfont/fluid-soundfont_3-1.dsc
[16:09] <tsmithe> woops
[16:09] <tsmithe> http://mentors.debian.net/debian/pool/main/f/fluid-soundfont/fluid-soundfont_3-1.dsc
[16:09] <slomo> ok :)
[16:10] <tsmithe> (i ended up having to split up the config file i had to fit with the two binary packages)
[16:11] <\sh> siretart: pingeling you old sysadmin ;) do you know any open/free alternative to netzoom datacenter designer?
[16:12] <sistpoty|work> hi folks
[16:13] <tsmithe> hiya sistpoty|work
[16:13] <sistpoty|work> hi tsmithe
[16:14] <geser> Hi sistpoty|work
[16:14] <sistpoty|work> hi geser
[16:14] <slomo> tsmithe: ok, building now... then testing and if it works for me i'll upload ;)
[16:14] <LucidFox> Gah! http://paste.ubuntu.com/4841/
[16:14] <slomo> tsmithe: i hope we never ever get a new upstream version :P
[16:15] <RainC1> uhm.. is there some way I could have disabled all my tty's? :P
[16:15] <LucidFox> Christian Marillat is a responsive maintainer, but his English... eck.
[16:15] <tsmithe> slomo, well, frank alluded to some "enhancements", but i don't think we will. it's stable.
[16:16] <slomo> LucidFox: he's french, that explains it i guess :)    seems he changed his attitude to ubuntu to be much more positive than a year or two ago :)
[16:16] <slomo> tsmithe: no need to call dh_shlibdeps btw
[16:16] <LucidFox> slomo> he used to hate Ubuntu?
[16:16] <tsmithe> slomo, no you're right. i really don't know why that's there...
[16:16] <slomo> tsmithe: i'll remove it ;)
[16:16] <\sh> RainCT: /etc/default/console-setup ?
[16:16] <tsmithe> does it warrant a new upload? (it's not harming anyone)
[16:16] <tsmithe> ahh thanks :D
[16:16] <LucidFox> I didn't get such an impression, he readily merges changes from Ubuntu at my request
[16:17] <\sh> RainCT: the entry # Setup these consoles.  Most people do not need to change this.
[16:17] <\sh> ACTIVE_CONSOLES="/dev/tty[1-6]"
[16:17] <slomo> LucidFox: well, at least he was a bit unfriendly when i sent a mail to him long ago :) well, nevermind, makes me happy that everything is better now
[16:17] <RainCT> \sh: it's enabled there.. strange
[16:18] <RainCT> \sh: well, thx anyway
[16:20] <HighNo> hi guys. i'd like to change a package that already made it into hardy. it is a dependency thing that stopps it from being installed on feisty and gutsy. just upload it to revu?
[16:20] <LucidFox> HighNo> no, file a bug in Launchpad and upload a debdiff
[16:20] <eddyMul> I'm having trouble with "pbuilder-dist hardy": http://paste.ubuntu.com/4842/
[16:21] <sistpoty|work> HighNo: you want to change a hardy package to be installable in gutsy/feisty?
[16:21] <HighNo> thx lucidfox
[16:21] <slomo> tsmithe: maybe bzip2 compression makes sense here for the .deb, not sure
[16:22] <HighNo> sistpoty yes
[16:22] <tsmithe> slomo, well, we were wondering about lzma, but we weren't sure whether debian supported it
[16:22] <norsetto> eddyMul: seems like you have a problem with your chroot sources.list
[16:22] <sistpoty|work> HighNo: urgh... don't do this please... the right thing would be a backport then
[16:22] <slomo> tsmithe: afaik yes, let me check
[16:23] <sistpoty|work> HighNo: jdong should be able to help you further, I guess
[16:23] <tsmithe> slomo, excellent. if so, can you teach me how to use it?
[16:23] <slomo> tsmithe: yes, since jan 2008
[16:23] <slomo> tsmithe: erm... no :)
[16:23] <tsmithe> right; i thought i heard some sort of announcement back then
[16:23] <slomo> tsmithe: i have no idea how to use it
[16:23] <tsmithe> oh ok haha
[16:24] <sistpoty|work> slomo, tsmithe: iirc it's a dh_bulddep option (getting passed down to dpkg, so you might want to look in the man page there)
[16:24] <slomo> yes, i'm looking atm
[16:24] <HighNo> sistpoty it only takes one change in the control file...
[16:24] <tsmithe> sistpoty|work, ah; thanks :)
[16:24] <eddyMul> norsetto: hm... I'll try leaving out the --othermirror then...
[16:24] <slomo> dh_builddep -u "-Z lzma" or soemthing
[16:25] <slomo> HighNo: which?
[16:25] <tsmithe> slomo, yeah, that looks right
[16:25] <sistpoty|work> HighNo: still, I don't recommend installing (binary) packages of hardy into an older distribution, but rather have these *build* on the older distribution, which is easily done by a backport
[16:25] <eddyMul> btw, is it normal for pbuilder-dist (under gutsy) to warn me "Warning: Unknown distribution «hardy»."?
[16:26] <HighNo> slomo Python-Support >= 0.5.4 instead of 0.7.1
[16:26] <slomo> tsmithe: let me try it, if it does something good i'll upload it as such
[16:27] <geser> eddyMul: yes, as only debootstrap from gutsy-backports knows about hardy
[16:27] <tsmithe> slomo, yeah, i'm just testing it. let's see who wins :p
[16:27] <norsetto> eddyMul: instead of removing--other-mirror try adding --override-config
[16:28] <HighNo> sistpoty it is all python
[16:28] <slomo> tsmithe: *compressing*
[16:28] <tsmithe> yeah, it looks good :)
[16:28] <slomo> i wonder how much space is saved by this
[16:28] <slomo> if it's less than 1 MB it probably doesn't matter
[16:29] <slomo> hm, needs very long
[16:29] <slomo> tsmithe: btw, we have to Depend on a newer dpkg for this
[16:29] <tsmithe> yeah, lzma is a slow compressor...
[16:29] <sistpoty|work> HighNo: is the python-support dep versioned as a build-dependency or as a dependency?
[16:29] <slomo> and Build-Depend
[16:29] <eddyMul> norsetto: I'll try to add --override-config, then. Thanks.
[16:29] <tsmithe> slomo, oh really?
[16:29] <emgent`work> packages.ubuntu.com is down?
[16:29] <tsmithe> ok.
[16:30] <slomo> tsmithe: 1.14.0
[16:30] <tsmithe> slomo, cheers :)
[16:30] <dholbach> Ubuntu Developer Week is going on, join #ubuntu-classroom
[16:31] <slomo> tsmithe: i'll change all that then and upload if it makes sense
[16:31] <slomo> tsmithe: if it ever finishes compressing
[16:32] <tsmithe> fun for the buildd :p
[16:32] <HighNo> sistpoty i think it is in normal depends though i am not sure if it even needs it
[16:32] <slomo> tsmithe: debian needs binary (and source) uploads ;)
[16:33] <tsmithe> oh really? aren't binary uploads a bit of a security risk?, as someone could send the correct source, but change the binary.
[16:34] <slomo> tsmithe: 114 mb vs 129 mb for the large deb
[16:34] <tsmithe> that's a reasonable difference
[16:34] <tsmithe> but is the time worth it, you think?
[16:34] <slomo> tsmithe: debian developers are trusted ;) but sure, you're right
[16:34] <slomo> yes
[16:34] <tsmithe> hehe, mine only just finished
[16:35] <slomo> tsmithe: ok, final build and upload now... *phew*
[16:35] <bddebian> slomo: !!!
[16:35] <slomo> hi bddebian :)
[16:36] <LucidFox> Is there a more user-friendly alternative to dpkg --compare-versions?
[16:36] <bddebian> slomo: Hey, any chance you would have time to look at an updated muine package I made?  I get some weird shit with dh_makeclilibs and I'm not overly familiar with the mono stuff :-(
[16:36] <sistpoty|work> hi bddebian
[16:36] <bddebian> LucidFox: Unfortunately not that I've found :-(
[16:36] <slomo> bddebian: output to pastebin please :)
[16:36] <bddebian> Heya sistpoty|work
[16:37] <norsetto> bddebian: ask LucidFox, he is the Mono expert
[16:37] <LucidFox> bddebian> maybe I could write one and get it included into devscripts
[16:37] <tsmithe`> ok that was weird
[16:37] <LucidFox> norsetto> I'm not really a Mono expert :)
[16:37] <norsetto> LucidFox: ops, sorry, a Multi expert ;-)
[16:38] <bddebian> slomo: http://paste.debian.net/49623
[16:40] <slomo> tsmithe: nice, wildmidi does not support this .sf2 files
[16:41] <slomo> tsmithe: if you want to add support for it... :)
[16:41] <tsmithe> slomo, wildmidi doesn't support sf2 last i checked; it uses timidity if sf2s are required
[16:41] <slomo> bddebian: you need .exe.config or .dll.config for the dlls and/or exe files
[16:41] <slomo> bddebian: see debian cli policy
[16:42] <bddebian> Gah, that sounds too much like work
[16:43] <slomo> tsmithe: if you have some time it'd be nice to have support for this added to wildmidi ;)
[16:44] <tsmithe> slomo, it would make an interesting project. i'll take a look.
[16:44] <slomo> tsmithe: most other annoying bugs are fixed by the current ubuntu package it seems
[16:45] <pochu> sistpoty|work, ScottK: will you consider adding enabling a plugin in gst-plugins-bad a new feature? It fixes bug 111555
[16:45] <ubotu> Launchpad bug 111555 in timidity "package gstreamer sw midi playback plugin" [Low,Confirmed] https://launchpad.net/bugs/111555
[16:45] <pochu> (as in, do I need to request an exception from motu-release?)
[16:46] <slomo> pochu: you have to do some work to get it working out of the box though, you need pats and a valid config file at a position where the plugin looks by default
[16:46] <tsmithe> slomo, right. where can i get your debian sources, with all the respective patches? (or are they all counted under the ubuntu package?)
[16:46] <slomo> tsmithe: 0.2.2-1~hardy1 has all the patches
[16:47] <tsmithe> that's a non-standard version... dsc?
[16:47] <pochu> slomo: pats isn't a problem. the config... will you create it? (or will you guide me?)
[16:47] <tsmithe> slomo, pochu, and with fluid, pats is even less of a problem! :p
[16:47] <pochu> slomo: I already have -bad ready for upload... perhaps I should upload it now and get the midi bits later?
[16:47] <slomo> pochu: for now, recommend freepats and chaneg the wildmidi plugin to look at /usr/share/gstreamer-0.10/wildmidi.cfg or something as fallback
[16:48] <sistpoty|work> pochu: do I read it right, that you'd only need to tweak a few bits in the source package?
[16:48] <pochu> sistpoty|work: yeah
[16:48] <slomo> sistpoty|work: yes
[16:48] <pochu> sistpoty|work: and it won't break other plugins :)
[16:49] <sistpoty|work> pochu: while it's a feature, it's not one you need an exception for (if stuff breaks, we can easily disable it again)
[16:49] <pochu> sistpoty|work: alright, thanks
[16:49] <sistpoty|work> np
[16:50] <slomo> pochu: well, look at gstwildmidi.c... first of all add  and then in 181 do a check for path == NULL and use the path i gave you above then...this config file should be shipped by the package then and should simply be a copy of the freepats.cfg for now
[16:51] <slomo> pochu: and at line 60 add: #ifndef TIMIDITY_CFG\n#define TIMIDITY_CFG "/etc/timidity/timidity.cfg"\n#endif       (3 lines)
[16:51] <slomo> pochu: if you hve the patch please show it to me for review (and don't forget to recommend freepats and ship the config file :) )
[16:51] <pochu> slomo: ok, doing it right now :)
[16:51] <pochu> thanks
[16:52] <slomo> pochu: and don't do path = "blablabla" but instead path = g_strdup ("blablabla") :)
[16:52] <tristil> I'm confused about dch/debuild settings and version numbering in general. Can someone walk me through them? I have a new package, alexandria-0.6.3, which has never been a Debian package before. Should I start by building alexandria_0.6.3_all.deb?
[16:53] <tristil> For upload?
[16:53] <slomo> pochu: essentially do the same as line 165 to 172 do ;)
[16:54] <slomo> tsmithe: uploading btw... hope it finishes someday ;)
[16:54] <tsmithe> slomo, haha, thanks
[16:54] <sistpoty|work> tristil: for debian packages start with <upstream_version>-1, and succeeding uploads of the same upstream version would be <upstream_version>-2 etc.
[16:55] <sistpoty|work> tristil: in ubuntu, we use <upstream_version>-0ubuntu1 (-0ubuntu2) etc
[16:55] <sistpoty|work> tristil: so that the version is lower than the first debian version (and we can eventually sync a debian version later)
[16:55] <tristil> sistpoty|work, Okay, so should my first upload be alexandria0.6.3-0~ppa1?
[16:55] <tristil> The one with the orig.tar.gz in it?
[16:56] <sistpoty|work> tristil: oh, you're asking for a ppa? sorry, don't know the conventions for that, but that would make sense to me, as it would be lower than the first ubuntu version
[16:56] <slomo> tsmithe: too bad debian wants binary uplaods :) now i have to upload ~260 mb
[16:56] <tsmithe> :s
[17:03] <pochu> slomo: line 181... the one after the if "if (path == NULL) { path = g_build_path (G_DIR_SEPARATOR_S, "/etc", "timidity.cfg", NULL); " ?
[17:04] <slomo> pochu: the one before "if (path == NULL) { /* I've created a symlink to get it playing"
[17:04] <slomo> and simply do the same logic as done in all the other ifs ;)
[17:04] <tristil> sistpoty|work, so this is what I'm confused about. If I use ubuntu as the epoch, or even ubuntu~ppa, and run debuild -S -sd, it complains that I'm not an Ubuntu maintainer, but if I use ~ppa it says "dpkg-genchanges: warning: ignoring -sd option for native Debian package"
[17:05] <tristil> And includes the binary.
[17:05] <eddyMul> norsetto: pbuilder-dist still complained about "Malformed line 1 in source list /etc/apt/sources.list (URI)" even after adding --override-config.
[17:06] <eddyMul> when I give --debug to `pbuilder-dist --create`, where can I find the "chroot"?
[17:06] <sistpoty|work> tristil: the latter sounds like you're building a native package...?
[17:06] <norsetto> eddyMul: try to login and check what is in there
[17:06] <slomo> pochu: would be great to have out of the box midi playback in hardy :)
[17:07] <tristil> sistpoty|work: First I release  alexandria_0.6.3~ppa1_all.deb for Hardy, then I try to bump it and release alexandria_0.6.3~ppa2_all.deb for gutsy, so I don't want the binary anymore, right?
[17:08] <eddyMul> norsetto: there is no base.tgz, though. Will `sudo pbuilder-dist hardy create --login` work? (my box is slow, and pbuilder takes some time. I want to make sure I issue the right command before waiting for ~25 minutes...)
[17:09] <sistpoty|work> tristil: erm, as I wrote... I'm not too sure about the ppa versioning conventions
[17:10] <slomo> pochu: the wildmidi plugin is not perfect yet though, works good for fundamental playback but that's it... i'll probably spend some time on it in the next days
[17:11] <tsmithe> "<slomo> pochu: would be great to have out of the box midi playback in hardy :)" exactly :D
[17:12] <pochu> slomo: should I use g_build_path too?
[17:12] <mok0_> ScottK: pgadmin3 patch in LP (bug 194058)
[17:12] <ubotu> Launchpad bug 194058 in pgadmin3 "[hardy] please upgrade pgadmin3" [Undecided,New] https://launchpad.net/bugs/194058
[17:12] <pochu> slomo: hmm, lines 156 and 174... looks like the same check :)
[17:12] <slomo> pochu: no, we're linux only ;)
[17:13] <slomo> pochu: yes, one of them should go away (or simply change the second of those two to your check :) )
[17:13] <norsetto> eddyMul: ah, but in that case there should'n be any sources.list. Just create it with pbuilder (sudo puilder create --debootstrapopts --variant=buildd)
[17:13] <pochu> I think I'll do the latter ;)
[17:13] <mok0_> pochu: just saw you already uploaded pgadmin3
[17:14] <slomo> pochu: that's what i would do too ;)
[17:15] <slomo> pochu: if there are some upstream changes by me or someone else in the plugin i'll give you diffs (or upload to debian)
[17:15] <pochu> mok0_: hmm, really? what's that? :-)
[17:15] <mok0_> pochu: my mistake, your'e not Lionel Porcheron
[17:15] <pochu> slomo: great, or let me know if you are busy and I'll try to backport them
[17:16] <slomo> pochu: :)
[17:16] <pochu> mok0_: heh, I'm not. "lionel" in this channel is the one you're looking for ;)
[17:16] <mok0_> pochu: thx :-)
[17:16] <lionel> mok0_: yes ?
[17:17] <mok0_> lionel: I just noticed you already uploaded pgadmin3
[17:17] <pochu> anytime
[17:17] <mok0_> lionel: I spent most of the day revising the package :-(
[17:17] <lionel> mok0_: yes... arf. I uploaded it some week ago
[17:18] <mok0_> hm. ScottK asked me to upgrade it yesterday
[17:19] <slomo> tsmithe: still uploading the tarball.... :)
[17:19] <mok0_> lionel: I didnt think to check
[17:19] <lionel> mok0_: cheching is always a good thing. Things tend to gost fast here :). Sorry for your most of the day :(
[17:20] <mok0_> lionel: I did make some useful changes IMO. I moved -data package to -doc (which it is) and I split off the i18n stuff in a separate "all" package
[17:21] <lionel> mok0_: I wanted to keep delta with debian as small as possible
[17:21] <mok0_> lionel: the debian package is bad, though
[17:21] <lionel> mok0_: :)
[17:22] <norsetto> mok0: ok, I will mark it as invalid it then (unless you did it yourself that is)
[17:22] <mok0_> norsetto: not yet
[17:22] <mok0_> norsetto: I want to grill ScottK  first
[17:23] <lionel> mok0_: Debian maintainer is open to contributions, so I think we can try to make the changes you made in Debian package (well, actually, there are publiched on pgadmin website)
[17:23] <norsetto> mok0: I see, just be aware that he is an ex-marine ;-)
[17:24] <mok0_> norsetto: I have the brown belt in shotkokan karate :-)
[17:24] <mok0_> shotokan
[17:24] <norsetto> mok0: yes, but he might have an m46 still handy .....
[17:25] <lionel> I'm not sure this is covered by CoC :-D
[17:25] <pochu> ScottK: re -0ubuntu1 vs -1~hardy1... where's the policy which says that? -1~hardy1 makes more sense to me, although if policy enforces the first one...
[17:26] <norsetto> pochu: where is 1~hardy1 coming from?
[17:27] <pochu> norsetto: debian new
[17:27] <pochu> norsetto: as in backports from debian new without any changes
[17:27] <slomo> norsetto: lool and me used it a few times and iirc seb128 asked lool once to upload something as -1~hardy1 that was waiting on the NEW queue in debian
[17:27] <pochu> that also means that it will be synced in the next release
[17:28] <pochu> whereas 0ubuntu1 won't
[17:28] <norsetto> pochu: oh, ok, its a backport of a sync
[17:28] <pochu> right
[17:28] <pochu> but ScottK once told me policy enforced ubuntuX, but as I don't know where that is mentioned...
[17:29] <norsetto> pochu: well, I for one would like to see an Ubuntu policy at least once
[17:29] <pochu> heh
[17:30] <pochu> Hmm, is tomorrow the MOTU meeting?
[17:31] <pochu> no, it's next week
[17:31] <norsetto> pochu: according to this page what you say is correct: https://help.ubuntu.com/community/UbuntuBackports
[17:32] <pochu> norsetto: what is incorrect?
[17:32] <norsetto> pochu: nothing, I said "correct" not incorrect
[17:33] <pochu> norsetto: hmm, I was unclear (as usual...). This isn't a backport at all...
[17:33] <pochu> norsetto: it's a sync of a package sitting in NEW
[17:33] <slomo> more like a "forwardport" :)
[17:33] <pochu> but as we don't sync from NEW, then we do a fake-sync ;)
[17:33] <norsetto> pochu: so its a fake-sync?
[17:33] <pochu> yeah :-)
[17:34] <pochu> norsetto: sorry for being unclear, my English isn't very good...
[17:34] <norsetto> pochu: np
[17:34] <mario_limonciell> oh i've wondered what fakesync means
[17:34] <mario_limonciell> neat :)
[17:34] <norsetto> pochu: I like slomo wording, a "forwardport" ehehe
[17:35] <pochu> heh
[17:35] <slomo> mario_limonciell: hi :) i'd like to have gmyth-upnp and things packaged too, at least totem will require gmyth-upnp soonish ;)
[17:35] <slomo> mario_limonciell: do you have some plans already?
[17:35] <mario_limonciell> slomo, yeah i'll get it together in the next night or two
[17:36] <slomo> mario_limonciell: perfect, just write me a mail with the url when you're done, ok? :)
[17:36] <mario_limonciell> slomo, will do, or IRC if i catch you on when it's ready :)
[17:36] <slomo> mario_limonciell: i know the reason for the broken seeking now btw... what did you play? :)
[17:36] <norsetto> mario_limonciell: Any idea why I can't install any of your fglrx packages?
[17:37] <mario_limonciell> slomo, it was an mpeg2 recording
[17:37] <slomo> mario_limonciell: at least mpeg-ts is unseekable (as the fluendo mpeg-ts demuxer doesn't support it yet)
[17:37] <slomo> mario_limonciell: mpeg ts or ps?
[17:37] <slomo> mario_limonciell: apart from that there's a fix now in 0.10.6 (which pochu will upload soonish) that makes seeking a bit more likely to work
[17:37] <mario_limonciell> slomo, well hm i've got both, but i'm not sure which one I did
[17:37] <mario_limonciell> slomo, ah that's spectacular news
[17:37] <mario_limonciell> norsetto, on hardy?
[17:38] <norsetto> mario_limonciell: gutsy or hardy doesn't matter
[17:38] <eddyMul> how do I tell `pbuilder-dist create` to not clean the build env? --debug isn't doing it for me...
[17:38] <mario_limonciell> norsetto, generated on hardy though?
[17:38] <slomo> mario_limonciell: please retry with 0.10.6 on a non-mpeg-ts file :) and if it still doesn't work remove gstreamer0.10-fluendo-mpegdemux for testing... and then report your results please ;)
[17:38] <mario_limonciell> norsetto, there are some issues with the last public release's hardy scripts
[17:38] <RainCT> geser: if you still have time to test it, http://mentors.debian.net/debian/pool/main/o/open-invaders/open-invaders_0.3-1.dsc
[17:38] <mario_limonciell> slomo, alrighty will let you know how that turns out after work
[17:38] <norsetto> mario_limonciell: the old ones with m-a are fine
[17:39] <slomo> mario_limonciell: perfect, thanks
[17:39] <mario_limonciell> norsetto, can you PM, this discussion is more appropriate for it
[17:42] <geser> RainCT: http://paste.ubuntu.com/4854/
[17:46] <tristil> Does the message from the build server, "MD5 sum of uploaded file does not match existing file in archive" mean that there is another orig.tar.gz file in the repository archive?
[17:48] <pochu> slomo: the timidity.cfg is a workaround, right? will we ship it with wildmidi or libwildmidi0 later?
[17:49] <RainCT> geser: what does config.log say?
[17:49] <geser> tristil: yes
[17:50] <tristil> geser: Thanks.
[17:52] <ScottK> pochu and mok0_: About -0ubuntu1 version numbering: If you look at the lintian code that checks to see if something is an Ubuntu revision, it's there.
[17:52] <ScottK> Dunno about formal policy documentation, but that's where it appears in running code.
[17:52] <RainCT> geser: ah right, pbuilder. hm.. this doesn't do any difference, or? http://paste.ubuntu.com/4856
[17:54] <geser> RainCT: http://members.ping.de/~mb/tmp/config.log
[17:55] <geser> RainCT: after install pkg-config I get: checking for ALLEGRO... configure: error: Package requirements (alsa) were not met:
[17:58] <geser> RainCT: and after also installing libasound2-dev it complete configure and starts building
[17:59] <geser> RainCT: but only to fail with http://paste.ubuntu.com/4858/
[18:04] <RainCT> geser: ok, now I don't understand anything ;)
[18:06] <geser> RainCT: at first you seem to be missing two build-depends: pkg-config and libasound2-dev
[18:06] <geser> and there seem to be a second bug when I tries to actually build it
[18:08] <RainCT> geser: ok I found this http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=311840
[18:08] <ubotu> Debian bug 311840 in kraptor "kraptor: FTBFS on 64 bit arches." [Important,Fixed]
[18:11] <RainCT> geser: does it build with this? http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=kraptor-64bit.diff;att=1;bug=311840
[18:13] <tsmithe> slomo, how's the upload?
[18:14] <geser> RainCT: after appling this change to headers/pmask.h it builds
[18:14]  * sistpoty|work heads home
[18:14] <sistpoty|work> cya
[18:15] <RainCT> geser: with or without the other patch?
[18:15] <slomo> pochu: not sure yet
[18:15] <slomo> tsmithe: finished... you should have mail
[18:15] <geser> RainCT: only the second patch. should I also apply the first one?
[18:16] <slomo> RainCT: new gbrainy or something to upload? :)
[18:16] <tsmithe> slomo, i got an "incomplete upload" message..
[18:16] <tsmithe> (no .changes file)
[18:17] <slomo> tsmithe: that's bad... probably took too long :)
[18:17] <tsmithe> hmm
[18:17] <slomo> tsmithe: i'll try it from my server again
[18:17] <RainCT> geser: no, better if it works without it :)
[18:17] <tsmithe> slomo, are you able to upload the .changes file separately?
[18:17] <slomo> tsmithe: it was uploaded
[18:17] <tsmithe> (wouldn't want you to do the whole thing over)
[18:17] <tsmithe> hmm
[18:18] <RainCT> slomo: heh, not yet :)
[18:18] <slomo> tsmithe: i'll upload to my server and do it frmo there... 100 mbit connection should make things possible ;)
[18:19] <slomo> RainCT: ok :)
[18:19] <tsmithe> slomo, are you sure 100mbit will be enough? :p
[18:20] <slomo> tsmithe: if not i won't sponsor it :P
[18:21] <tsmithe> damn!
[18:37] <LucidFox> ScottK> Regarding bug #192774, ack #2? Where's the first one? :)
[18:37] <ubotu> Launchpad bug 192774 in avidemux "[FFe request] Avidemux 2.4.1" [Wishlist,Confirmed] https://launchpad.net/bugs/192774
[18:38] <RainCT> geser: can you do a last build to see if I got the patch right please? http://mentors.debian.net/debian/pool/main/o/open-invaders/open-invaders_0.3-1.dsc
[18:38] <zul> what is the process for feature freeze exception for ubuntu these days?
[18:38] <ScottK> LucidFox: Thanks.  I put it back.
[18:39] <LucidFox> zul> https://wiki.ubuntu.com/FreezeExceptionProcess
[18:39] <RainCT> zul: if it's a bug fix only release, just upload it; else, subscribe motu-release to the bug report (which should contain information on why, what changed and regression risk) and wait for 2 ack's
[18:39] <ScottK> zul: https://wiki.ubuntu.com/FreezeExceptionProcess
[18:41] <zul> okies thanks
[18:42] <tsmithe> slomo, got a processing notification: thanks for the upload :)
[18:43] <slomo> tsmithe: oh? successfully?
[18:43] <slomo> tsmithe: great
[18:43] <slomo> tsmithe: i didn't reupload yet ;)
[18:44] <tsmithe> hah, well, it looks good. although being told that it was uploaded to localhost was a bit weird
[18:46] <geser> RainCT: it builds now without a problem
[18:46] <jdong> slomo: what do you think about monodevelop RC1 for Hardy?
[18:46] <slomo> jdong: nothing
[18:46] <slomo> :)
[18:46] <slomo> jdong: i don't plan anything
[18:47] <jdong> slomo: mmmkay
[19:04] <tsmithe> slomo, debian doesn't like lzma it seems: Rejected: fluid-soundfont-gs_3-1_all.deb: deb contents timestamp check failed [exceptions.SystemError: E:This is not a valid DEB archive, it has no 'data.tar.gz' or 'data.tar.bz2' member]
[19:04] <tsmithe> Rejected: fluid-soundfont-gm_3-1_all.deb: deb contents timestamp check failed [exceptions.SystemError: E:This is not a valid DEB archive, it has no 'data.tar.gz' or 'data.tar.bz2' member]
[19:05] <slomo> tsmithe: oh no
[19:05] <slomo> tsmithe: i'll reupload with bz2 tomorrow
[19:05] <tsmithe> :)
[19:07] <norsetto> mario_limonciell: I have attached all info to bug 194090
[19:07] <ubotu> Launchpad bug 194090 in linux-restricted-modules-2.6.24 "fglrx restricted driver doesn't work on hardy" [Undecided,New] https://launchpad.net/bugs/194090
[19:17] <slangasek> slomo: hrm, why does fluid-soundfont-gs warrant lzma?
[19:18] <slangasek> the performance tradeoffs make it inadvisable to use lzma for any but the largest packages...
[19:18] <slomo> slangasek: because it saves about 15 mb in the generated binary packages
[19:18] <slangasek> ok, 15MB is good savings :-)
[19:19] <mario_limonciell> norsetto, can you verify if fglrx module is loaded at that time?
[19:20] <slomo> slangasek: too bad it isn't support but dak or whatever rejected it here ;)
[19:21] <slangasek> slomo: heh, it's only been supported in Ubuntu for about a week or two
[19:21] <slangasek> if even that long
[19:22] <mario_limonciell> norsetto, i'd suspect that it is properly loaded (in which case you have unearthed a bug in the more modern releases)
[19:22] <tsmithe> slangasek, did persia upload it to ubuntu with lzma?
[19:23] <slangasek> I don't know, I'd have to dig it out of the NEW queue to see
[19:23] <slangasek> congrats on getting the licensing fixed, btw
[19:23] <tsmithe> ok, don't worry
[19:23] <tsmithe> no problem :) it's definitely worth the small amount of hassle
[19:24] <tsmithe> where can i find the new queue? i looked at people.ubuntu.com/~ubuntu-archive/queue, but that didn't seem up-to-date when i checked
[19:24] <slangasek> well, if that's not being updated then I guess you can't
[19:25] <tsmithe> heh ok then :)
[19:43] <slomo> slangasek: do you know when debian's dak (or whatever) will get support for lzma? and is orig.tar.bz2 (and data.tar.bz2) supported already?
[19:45] <tsmithe> slomo, looking at the e-mail i got, data.tar.bz2 should work fine
[19:48] <bddebian> slomo: Sorry but even reading the CLI policy, I don't see how to fix those errors on the .exe file.  I see the config.dll stuff but nothing about exes?
[19:49] <slomo> bddebian: it's the same
[19:49] <nxvl_work> ScottK: ping
[19:49] <ScottK2> nxvl_work: Pong
[19:50] <nxvl_work> ScottK2: CC Meeting starts in 10 minutes
[19:50] <ScottK2> nxvl_work: OK.  Looks like I can make it after all then.
[19:50] <bddebian> slomo: So it would be muine.exe.config with dllmap dll="libmuine" target="libmuine.so.X" in it?
[19:50] <slangasek> slomo: I'm not aware of any plans to implement support for lzma in Debian
[19:51] <slomo> bddebian: yes
[19:51] <bddebian> Scary. I'll try that thanks.
[19:51] <bddebian> slomo: What about the foo has no valid signature stuff?
[19:51] <slomo> slangasek: well, dpkg supports it already
[19:51] <slomo> bddebian: ignore
[19:52] <slangasek> slomo: yes, but dak has to support it too, and I'm not aware of any plans in that regard for Debian
[19:52] <bddebian> slomo: OK, thanks
[19:56] <tsmithe> slomo, i'm very appreciative of your patches to wildmidi; having looked at the -0ubuntu1 sources, i must say they do clean things up an awful lot.
[19:57] <slomo> tsmithe: np... do you think sf2 support will be hard?
[19:58] <tsmithe> slomo, well, i'm not sure. i'll have to look at the sf2 spec first :)
[19:59] <tsmithe> i'd very glad to do it: be good practice for my C
[20:01] <bddebian> slomo: Same issue with this file, is it correct? http://paste.debian.net/49679
[20:02] <slomo> bddebian: probably nto... where is libmuine.so?
[20:04] <persia> tsmithe: I failed to remember --lzma when uploading :(
[20:05] <persia> slomo: pochu: Thanks a lot.  That's looking much better :)
[20:05] <bddebian> slomo: /usr/lib/muine/libmuine.so
[20:05] <tsmithe> persia, ah well, don't worry :)
[20:06] <bddebian> slomo: Does target need a specific path?
[20:06] <slomo> bddebian: give the full path
[20:07] <bddebian> I'll try that, thanks
[20:13] <jdstrand> emgent: fyi-- uploaded cacti (thanks!) and replied to motu application
[20:14] <emgent> jdstrand, thanks
[20:17] <emgent> jdstrand, big Thanks ehehehhe
[20:17] <jdstrand> np :)
[20:19] <bddebian> slomo: This isn't working :-(  Should it be the full destination path?  I.E. debian/tmp/usr/lib/muine/foo.so?
[20:20] <slomo> bddebian: no... /usr/lib/muine/libmuine.so (and it will still complain but it will work at least)
[20:20] <nxvl_work> @now berlin
[20:20] <bddebian> slomo: Ah, OK, thanks
[20:23] <tsmithe> slomo, but what if the package is not installed to / ?
[20:23] <tsmithe> hardcoding paths.. urgh
[20:24] <emgent> heya blueyed :P
[20:29] <blueyed> Hi emgent.. you're on your way? :)
[20:29] <emgent> hehe yep
[20:30] <emgent> i go to my girlfriend home, see you later.
[20:43] <norsetto> mario_limonciell: yes, the fglrx module is loaded
[20:43] <mario_limonciell> norsetto, okay i'll bring that upstream then. Thanks
[20:43] <norsetto> mario_limonciell: no problem, let me know if I can do something else
[20:47] <mario_limonciell> norsetto, well it would be useful if you were under NDA to see if a testing driver would resolve it, but that's out of your control :)
[20:47] <norsetto> mario_limonciell: if signing an NDA can help to solve problems I can sign an NDA, no big deal
[20:48] <mario_limonciell> norsetto, well I'll see what AMD says after I bring it up.  I'll keep you in the loop as I hear.
[20:48] <norsetto> mario_limonciell: ok, thanks for that.
[21:04] <geser> are CC meetings always that chaotic? /me didn't attend any since he become MOTU but doesn't remember them as that chaotic in the past
[21:05] <ScottK2> Nearly so I think.
[21:10] <persia> They've become more unwieldly since having agendas that wouldn't fit in two hours.  As a result, there's a lot more fuss from potential new members and teams.
[21:10] <hellboy195> persia: ah you're back :)
[21:12] <geser> did the agenda ever fit into two hours? I remember CC meeting taking 3 hours or more already in the past
[21:12] <persia> The last CC meeting I attended took ~90 minutes, but that was a while back.  Lately, I've just been reading the logs.
[21:17] <hellboy195> persia: Why are build_options.py  config.py  __init__.py
[21:17] <hellboy195>  wxwidgets2.6-<IP_ADDRESS>.2/wxPython/wx/build and debian only has __init__.py. It seems that this is not mentioned in changelog!?
[21:17] <norsetto> hellboy: you could have checked with me before merging conky, there was a little hitch that I was waiting to clear
[21:18] <norsetto> hellboy195 that is
[21:18] <ScottK2> FYI folks, this is why I advocate checking with whoever touched the package last.
[21:19] <persia> hellboy195: I'm not entirely sure about that (the python part of wxwidgets isn't the part I've investigated).  I remember something about those files being autogenerated, but I don't remember the details.
[21:19]  * persia advocates people working on bugs, rather than chasing merges.  Merges are fine and good, but pointless if they aren't closing bugs.
[21:20] <hellboy195> persia: autogenerated? great :) either I'm doing a lot of crap or there will be only 2 or 3 remaining changes left
[21:20] <hellboy195> norsetto: what hitch?
[21:20] <persia> hellboy195: Don't trust me 100% on the python bits: check the code to see what it needs.
[21:22] <hellboy195> persia: I have to trust you because nevertheless I am 10000000 times less good than you ;)
[21:22] <norsetto> configure does enable some of the options by defualt, so there is no need to have those in rules, but thats not the point, the point is that it is good practice to check with the previous uploader (just for cases like this)
[21:23] <persia> hellboy195: Better to not merge than blindly trust me about wxpython
[21:23] <hellboy195> norsetto: yeah. debian folks told me already. sry for that :(
[21:23] <hellboy195> persia: k, we'll see
[21:23] <norsetto> hellboy195: np, but please keep this in mind for the future
[21:24] <hellboy195> norsetto: yep :) btw. there will be a new debian revision soon. I'm helping debian folks with that battery patch which isn't working in the right way
[21:24] <norsetto> hellboy195: thats very good
[21:29] <hellboy195> persia: hmm I'll do this merge good so I'll ask the previous merger. no problem if this take some days?
[21:30] <persia> hellboy195: No big rush.  What issue is fixed by the new version?  Also, you may want to backtrack uploaders until you find a python person, just to be sure.
[21:32] <hellboy195> persia: debian applied a lot of the remaining ubuntu changes but really *new* things are only 2-3 as far as I see
[21:32] <rexbron> RainCT, hey, I am just reviewing the current trunk of ubuntu-dev-tools and you make reference to python-ubuntu-utils, a package which does not exist. Currently we are installing the python modules in python-ubuntutools to reflect the namespace. Shall I change the references to match python-ubuntutools?
[21:33] <hellboy195> norsetto: btw, on tuesday I wrote a mail to Andrea Veri, no answer yet. If he doesn't reply by the end of this week you have to decide what to do ..
[21:33] <tsmithe> slomo, thanks for the re-upload
[21:33] <norsetto> hellboy195: about?
[21:33] <hellboy195> norsetto: I haven't seen him since 3 weeks
[21:34] <norsetto> hellboy195: did you ask DktrKranz?
[21:34] <hellboy195> norsetto: about? he also hasn't seen him for a while
[21:35] <norsetto> hellboy195: and he didn tell you anything before?
[21:36] <hellboy195> norsetto: well he said that he will enjoy real life a little bit and will be more often offline for 1 or 2 weeks. now I haven't seen him since 3 weeks and I'm a little bit worried
[21:37] <persia> hellboy195: Which wxwidgets2.6 are you working on?  I just got an update for <IP_ADDRESS>.2-1ubuntu1
[21:37] <hellboy195> persia: <IP_ADDRESS>.2--2
[21:38] <hellboy195> persia: hardy actually has <IP_ADDRESS>.2-1ubuntu2
[21:38] <persia> heh.  OK.  I'm oddly behind, perhaps due to the FTBFS fix in -1ubuntu2.  Sorry for the confusion.
[21:39] <hellboy195> persia: np
[21:39] <norsetto> hellboy195: well, give him some more time, perhaps he is just on a skying holiday
[21:39] <hellboy195> norsetto: k
[21:52] <emgent> heya
[22:08] <jetsaredim> if I have a code branch in my bzr area on launchpad - how can I get the thing built and into my ppa?
[22:08] <ScottK2> jetsaredim: Ask in #launchpada
[22:08] <ScottK2> #launchpad even
[22:09] <warp10> ScottK2, persia: rather surprising and really, really appreciated... thank you so much
[22:09] <ScottK2> warp10: You're welcome.
[22:10] <jetsaredim> thx both
[22:17] <norsetto> congrats warp10!
[22:18] <warp10> thank you norsetto! :)
[22:25] <LaserJock> when was the CC meeting?
[22:27] <persia> LaserJock: Currently underway (but ending soon)
[22:27] <LaserJock> oh
[22:35] <tsmithe> persia, slangasek, interested parties, do you think i should wait until fluid-soundfont in ubuntu is passed new before filing a sync from debian [new - if appropriate], or would it just be easier to do so now?
[22:36] <slangasek> tsmithe: well, you should wait until it passes /Debian/ new, because the Debian new queue isn't world-accessible
[22:38] <ScottK2> tsmithe: You might also consider a -0ubuntu1 upload in the mean time.
[22:38] <ScottK2> nxvl_work: Congratulations.
[22:38] <slangasek> ScottK2: I believe that's what's already in Ubuntu new
[22:38] <tsmithe> slangasek, ah, right, i must have been confused by https://launchpad.net/ubuntu/+source/wildmidi (the wildmidi changelog reads "Sync of the Debian package that currently waits on NEW.")
[22:38] <nxvl_work> ScottK2: thanks!
[22:39] <tsmithe> ScottK2, yes; I have done that.
[22:39] <norsetto> congrats nxvl
[22:39] <nxvl_work> ScottK2: not only for the support, but for the help on all my way until here!
[22:39] <ScottK2> tsmithe: OK.  Then wait for it to get out of New before you ask.
[22:39]  * nxvl_work gives a BIG HUG to norsetto and ScottK2
[22:39] <ScottK2> nxvl_work: You earned it.
[22:39]  * tsmithe presumes that nxvl_work has become a MOTU, and thus gives his congratulations also
[22:40] <ScottK2> tsmithe: Ubuntu Member
[22:40] <tsmithe> ok, well, still; no less a milestone
[22:40] <ScottK2> Yes
[22:41] <LaserJock> congrats nxvl_work
[22:41] <tsmithe> ScottK2, could you clarify which "New" you refer to: debian or ubuntu? if i'm already waiting for it to pass debian new, are you also suggesting i wait for ubuntu new?
[22:43] <nxvl_work> LaserJock: thanx!
[22:44] <ScottK2> tsmithe: I meant Debian (as in keep on doing what you are doing then).
[22:44] <ScottK2> tsmithe: Sorry for the confusion.
[22:47] <tsmithe> ScottK2, heh, don't worry :)
[23:05] <norsetto> g'night all
[23:17] <StevenK> Eeek, three ScottK's
[23:28] <steveire> Hi. Before it got backported I put libxine in my ppa. I'd intended that the ppa version would be overriden when the official version was backported. I named it 1.1.10-1ubuntu1~ppa1. However, that version name does not get overriden by the backported version. http://rafb.net/p/bN6WYA12.html. What should I have named it in this case and how can I anticipate the version of the backported package in the future?
[23:37] <LaserJock> steveire: it looks like the problem is the ubuntu1 part
[23:39] <mok0_> steveire: dpkg --compare-versions 1.1.10-1ubuntu1~ppa1 gt 1.1.10-1~gutsy1  && echo greater
[23:39] <mok0_> steveire: there's nothing you could have done to anticipate this
[23:39] <LaserJock> I'm not sure that's right
[23:40] <LaserJock> if the version in Ubuntu is 1.1.10-1 then a backport isn't going to have an ubuntuX version
[23:41] <LaserJock> I think the backporting versioning is just adding ~<release>1 to the current Ubuntu version
[23:43] <mok0_> LaserJock: that means anything you put in your ppa should have a release that always start with 0, if you want it to be overridden
[23:44] <LaserJock> that's a bit of a tough case
[23:45] <mok0_> He should've named it -0ubuntu1~ppa1
[23:45] <LaserJock> well
[23:45] <LaserJock> that's not right though
[23:46] <mok0_> LaserJock: example?
[23:46] <LaserJock> the version is already -1
[23:46] <LaserJock> so going to -0 seems wrong when it's based on -1
[23:47] <LaserJock> I'm more thinking the backports version being changed would be better
[23:47] <mok0_>  dpkg --compare-versions 1.1.10-0ubuntu1~ppa1 lt 1.1.10-1~gutsy1  && echo true
[23:47] <mok0_> gives true
[23:47] <LaserJock> of course
[23:48] <LaserJock> I'm just saying that -0 is wrong to do because it's not -0 it's -1
[23:49] <RainCT> rexbron: if you are still here, about your previous question, yes, please change any reference to python-ubuntu-utils to python-ubuntutools if there is any
[23:50] <RainCT> geser: thanks again for the testing before
[23:51] <rexbron> RainCT: I went a head and did that, should be pushed to LP. I also updated ppaput to reflect the change in namespace (the lazy way though)
[23:52] <mok0_> LaserJock: In that case, perhaps:  1.1.10-1~gutsy1~ppa1
[23:53] <LaserJock> yeah, I was thinking that
[23:53] <LaserJock> but that presupposes that the backport will exist
[23:53] <mok0_> LaserJock: you never can know, of course
[23:53] <LaserJock> yeah
[23:53] <LaserJock> it's a race between PPAs and -backports to see who goes lower ;-)
[23:54] <mok0_> LaserJock: hehe
[23:54] <mok0_> LaserJock: if think ~0ppa1 is lower than anything
[23:55] <LaserJock> kinda yeah
[23:55] <LaserJock> but it's wrong if a -1 is what it's based on
[23:55] <mok0_> LaserJock: I was thinking -1~0ppa1
[23:55] <LaserJock> it's not a great idea to munge the version if it's gonna misrepresent the "heritage" of the package
[23:56] <LaserJock> oh
[23:56] <LaserJock> hmm
[23:56] <LaserJock> I do use something like that for my PPA
[23:57] <mok0_> LaserJock: I actually like that best