[00:34] <ScottK> kklimonda: Probably not terribly hard, but it'd take some time to look at the code differences in python-defaults.  Addtion the ability to build against dh_python2 doesn't scare me since nothting that's not backported would ever use it.
[02:28] <jasono> Hello.
[07:31] <dholbach> good morning
[07:56] <micahg> udienz: make sure you forward the patch from fische to Debian, can you also add a request to add a build-dep for that lib as well (I forgot to add it before I sponsored and don't see the point of adding it in Ubuntu now)
[10:47] <udienz> micahg, okay done
[10:47] <micahg> udienz: thansk
[10:47] <micahg> *thanks
[10:53] <gnomefreak> is there anyway of findout out if a nvidia card is supported? apt-cache show used to list the supported cards but no longer does
[10:53] <gnomefreak> s/findout/finding
[10:57]  * gnomefreak checking /usr/share/doc/nvidia-current/README.txt.gz
[12:47] <hyperair> say, my MOTU membership seems to be due to expire pretty soon
[12:47] <hyperair> how do i go about renewing it?
[12:47] <geser> hyperair: click on the button
[12:48] <hyperair> geser: where?
[12:48] <geser> didn't the mail you got have a link for renewal?
[12:48] <hyperair> i just see a 'leave the team' button
[12:48] <hyperair> geser: er no, i only got the uus expiry notification, but i noticed MOTU membership is also expiring
[12:49] <geser> then wait till you get the mail with the expire warning. There is a link for renewal your MOTUship
[12:49] <geser> I don't know a way to renew it before that
[12:49] <hyperair> hmm
[12:50] <hyperair> but it's expiring in two weeks. when am i supposed to receive the notification?
[12:50] <geser> in 1 week (7 day warning)
[12:50] <hyperair> the uus notification says to ping persia or TheMuso
[12:50] <geser> because that's how the team is set up
[12:50] <hyperair> ah okay
[12:50] <geser> uus is going away anyways
[12:51] <hyperair> right
[12:51] <hyperair> ubuntu-sponsors, right?
[12:51] <geser> yes
[12:51] <hyperair> okay
[12:59] <ari-tczew> hyperair: check spambox for mail with the expire warning
[12:59] <hyperair> ari-tczew: nah, it's not there.
[12:59] <hyperair> ari-tczew: like geser said, it's a 7-day before warning. i still have 16 days
[13:00] <ari-tczew> aha ok
[13:36] <highvoltage> good morning
[13:41] <paultag> morgen there highvoltage
[13:41] <tumbleweed> highvoltage: hi, you pinged last night?
[14:58] <alexM> hi everybody, quick question to which I don't expect an elaborate answer:
[14:59] <alexM> Is "packaging" the process you transform an application from source code to something that can be installed?
[14:59] <alexM> I didn't manage to clarify this issue.
[15:01] <highvoltage> hey tumbleweed, I wondered if you were up for reviewing a package: http://revu.ubuntuwire.com/p/librecad
[15:01] <highvoltage> if you're busy then np
[15:02] <tumbleweed> highvoltage: sure
[15:51] <highvoltage> tumbleweed: nice, you found a few things I would've missed, thanks!
[15:52] <guspur> good nite all
[15:53] <guspur> i from indonesia
[15:53] <guspur> i fans for ubuntu
[15:53] <tumbleweed> highvoltage: np
[15:56] <highvoltage> hi guspur
[15:57] <guspur> hi highvoltage
[15:57] <guspur> sorry my english is dirty
[15:57] <guspur> i use google translate
[15:58] <guspur> how to begin to develop for ubuntu
[16:02] <highvoltage> guspur: there are many ways to get involved, http://www.ubuntu.com/community has quite a few links that links to even more pages that should tell you everything you'd like to know
[16:03] <guspur> oke thanx brother i hope i can packaging paket for ubuntu
[16:03] <highvoltage> guspur: the best way to start out is probably by getting to know some people who contribute to Ubuntu in your own country. That way you can get some help in your own language/timezone easily which should help you at least get over the initial parts of getting involved
[16:04] <highvoltage> guspur: https://wiki.ubuntu.com/MOTU has lots of information and links for packaging stuff, bookmark it :)
[16:06] <guspur> highvoltage, thx i join in blankon linux indoenesia as documentation division. i like learning to ubuntu
[16:07] <guspur> i is friend mahyudin susanto
[16:08] <guspur> my launcpad is http://launchpad.net/~goesspoerr
[18:23] <scott-work> jdong: do you have a minute to talk about backports ubuntustudio will be working on?
[18:26] <ScottK> scott-work: Probably better to talk to me about it.  jdong isn't that active in backports anymore.
[18:27] <scott-work> ScottK: right, thank you
[18:27] <scott-work> ScottK: i had talked to john a few months back about getting audio applications backported
[18:27] <ScottK> OK.
[18:28] <scott-work> ScottK: a group of ubuntu studio devs would backport them for lucid and would test them in our own ppa
[18:28] <ScottK> OK
[18:28] <scott-work> ScottK: but we would like to get them into the official backport repos
[18:28] <ScottK> Are you backporting from Natty or Maverick?
[18:28] <scott-work> ScottK: from maverick to lucid
[18:29] <scott-work> ScottK: the goals was to keep support for LTS currently
[18:29] <ScottK> scott-work: As long as you test related rdepends that should be fine.
[18:29] <ScottK> Just file bugs againsts lucid-backports and ping me when they are ready for approval.
[18:29] <scott-work> ScottK: our rough plan was to build for lucid, test in ppa, file bug report, post two positive tests, and hopefully the official backport team would push into the repos
[18:30] <scott-work> ScottK: heh, good deal
[18:30] <scott-work> ScottK: and we don't plan on trying to push libraries (like jackd) because that would be ntus
[18:30] <ScottK> Yes.  I just need the test report to say that it builds, installs, and runs.
[18:30] <scott-work> s/ntus/nuts
[18:30] <ScottK> For libraries I insist on a lot of testing and a good reason so good.
[18:31] <scott-work> ScottK:  without assistence i do not believe we have the experience/knowledge to adequately test libraries so i have advocating avoiding them currently
[18:31] <paultag> yeah, libs can break abi very easily
[18:31] <scott-work> hi paultag  :)
[18:31] <ScottK> Fine with me.
[18:31] <paultag> afternoon scott-work, ScottK :)
[18:33] <scott-work> ScottK:  so, now that other issues with natty have been resolved i plan to get back into the backporting groove and you should begin to see bug reports around mid-february
[18:33] <scott-work> thanks :)
[18:33] <ScottK> OK.  Just ping me when you've got something.
[18:51] <scott-work> cjwatson:  can you reply here as my home computer is also logged into this channel and will note your reply
[18:51] <scott-work> cjwatson: if you affirm this i will post my questions, if not i will log into the other channel and then post my question there
[18:53] <cjwatson> 18:46 <cjwatson> scott-work: it's the end of my day so I'm only intermittently around; it would be best if you described the problem such that I can reply asynchronously
[18:54] <scott-work> cjwatson: thank you, trying to work this in before i go into meetings for the afternoon as well
[18:55] <scott-work> cjwatson: the problem appears to be when we updated the ubuntu studio seeds and created some new tasks that the tasks within tasksel got a bit muzzed
[18:55] <scott-work> cjwatson: we should have five (5) selections:  generation, recording, video, graphics, ladspa/lv2/dssi
[18:56] <scott-work> cjwatson: the problem appears that the last task is now parsed into three (3) separate tasks
[18:56] <scott-work> cjwatson:  the intriguing aspect is that we didn't really update that seed very much other than to include "lv2" in the description and remove a few items from the seeds proper
[18:58] <scott-work> cjwatson: i should correct msyelf:  the last task which i called "ladpsa/lv2/dssi" is should really be referred to as "audio-plugins" i believe
[18:59] <cjwatson> scott-work: do you have a screenshot or something demonstrating the problem?
[19:00] <cjwatson> it looks OK to me in the tasksel source
[19:00] <cjwatson> oh, although I can make a guess, it's probably mishandling of the comma-space separator
[19:01] <cjwatson> in fact it probably generates a warning, it's just that nobody sees it :-)
[19:01] <cjwatson>                 if ($desc=~/, /) {
[19:01] <cjwatson>                         warning("task ".$_->{task}." contains a comma in its short description: \"$desc\"");
[19:01] <cjwatson>                 }
[19:01] <cjwatson> I recommend you rephrase the Task-Description line in your audio-plugins seed file to avoid containing commas
[19:01] <cjwatson> e.g. "LADSPA/LV2/DSSI audio plugins"
[19:02] <cjwatson> it probably is basically a tasksel bug though
[19:02] <cjwatson> but that's how to avoid it
[19:10] <ari-tczew> cjwatson: hugs for merging :)
[20:26] <scott-work> cjwatson: thank you!  :)
[20:57] <mdeslaur> geser: did you find someone to review subversion?
[20:58] <geser> not yet, didn't try. Should I look for someone else?
[20:58] <mdeslaur> geser: no, I was about to upload it, but it said "pending", so wasn't sure
[20:58] <mdeslaur> geser: I'll upload it as soon as it finishes building
[20:59] <geser> mdeslaur: I had one problem with a ruby test in my pbuilder but it build fine in my PPA
[20:59] <mdeslaur> ok