/srv/irclogs.ubuntu.com/2010/02/12/#ubuntustudio-devel.txt

ScottL!packaging00:28
ubottuThe packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports00:28
ScottLpersia: a couple of points about celtx - the version in REVU apparently has appreciable changes to the source code that aren't documented in the change file00:33
ScottLi'd already started talking to the original packager about getting it into ubuntu but his hard drive had broken and wasn't available to help at that time00:33
ScottLthe version in REVU is 2.0 and 2.7 is out (9 months old) but I realize that it's important to just get it accepted and then we can update it00:34
persiaUm, no.00:34
persiaBetter to update it and then get it accepted.00:35
persiaNo new upstream versions after feature freeze.00:35
persiaIf we miss feature freeze, it would be good to work with Debian Multimedia to get it into Debian, and we'd sync next time.00:35
ScottLspeaking of Debian Multimedia, that reminds me to send an email about Hydrogen 0.9.400:36
persia:)00:39
ScottL_persia: i see that JACK in the main bug is "triaged"...what exactly does that mean?  someone has loooked at it?00:42
persiaThat person was me, but that wasn't the MIR bug.00:43
persiaThat's just an extra bug about jack-in-main.  We undrestand the issue very well, hence "triaged".00:43
ScottL_gotcha00:46
ScottL_if the proper course is to get the new version of celtx into ubuntu then I really doubt it will happen before the FF00:47
ScottL_unless someone really experienced looks at it...it's build on mozilla build00:48
ScottL_but as you suggested I can try talking to debian multimedia about it also00:49
persiaThat's probably the best path.  You might also look for help from the folks in #ubuntu-mozillateam, but they tend to be fairly busy.00:50
persiaScottL_: s/Ubuntu Developers/Ubuntu Studio Developers/ for next time :)01:01
ScottL_doh, yeah sorry, trying to get things done with kids interrupting me01:06
persiaHeh.  Understood.  I just don't like to say "Ubuntu Developers want to do X" because it's rarely true that there is sufficient consensus for that to be the case :)01:09
persiaOK.  All JACK bugs triaged except the crashes, and I don't feel like digging through those right now.  Maybe later in the cycle.01:09
persiaWith luck, having everything triaged will help demonstrate support for the MIR>01:10
ScottLwife is an RN and doesn't leave work until at least 7:30pm so I'm keeping up with kids, cooking dinner, helping with homework...keeps me moving around for several hours ;P01:10
* persia has already poked one MIR person, and may poke another soon01:10
persiaExercise is good :)01:10
ScottLre; ubuntu developer, should I send another email to clarify or think most people won't even notice?01:11
persiaI'd not send clarification unless someone asks.01:11
ScottLafter my wife gets home tonight (if she doesn't do it too late) i'm going to spend an hour working on the copyright for zynjacku01:12
persiaCool.01:12
ScottLso working on bugs = fixing the problem, creating debdiff and then submitting patch to bug ?01:13
persiaSometimes.01:13
persiaSometimes it's just triage.01:13
persiaSometimes it's sending patches upstream.01:13
persiaDepends on the nature of the issue, etc.01:14
ScottLafter lucid is released I might try to do some bug work01:18
ScottLi figured to be successful (or actually helpful) took experience that I didn't have and decided that packaging was like working in a void (a good one) because noone was "depending" on me01:19
persiaheh, and now you7re being depended upon for packaging :)01:19
persiaBut after Feature Freeze, most of the development work is bugwork, so I hope you'll help get the software in shape for release.01:20
ScottLwell, yeah, but my own initiative did that ;P    i could have quitely worked on packages without committing01:20
persiaLots of bugs are already fixed, or have fixes submitted by the bug submitters.01:20
persiaOr fixes available upstream.01:20
persiaso it's sometimes just a matter of reading the bug, finding the patch, testing the patch, preparing a package including the patch, and getting it uploaded.01:21
persiaactually writing patches happens sometimes, but don't let concern over writing patches block you from looking at bugs.01:21
ScottL_hydrogen:  not only did I email but I'm in #debian-multimedia (OFTC) channel also, if no response in a few days I'll try to contact Free or someone directly01:24
persiaMakes sense.01:25
persiafree used to hang out in this channel, but I suspect the lack of time got to him.01:25
ScottLit would be considerably awesome to establish a substantial and sustainable working relationship with them :)01:27
ScottLmaybe even dividing up work if we get more or more able packagers01:28
persiaNo reason to do that.01:29
persiaInstead of thinking of "group working with group", consider "people working as part of groups".01:29
persiaSo one person can be active in both areas.01:29
persiaExcept for the special packages needed for branding, etc., nearly all packaging should be done in Debian Multimedia.01:30
persiaWell, there's some patches we need to carry because some bits are a little different, but those are really very minor.01:30
persiaSo, if you're interested in packaging and package maintenance, and interested in helping Studio, working in Debian Multimedia is a good way to do that.01:31
ScottL_i've considered also joining Debian Multimedia but thought I should gain more experience and knowledge first01:32
persiaSure.  No reason not to do that.01:32
persiaI'm just saying that the model of having individuals working as members of multiple (often cooperative) teams tends to be easier than the model of individuals working exclusively within teams and building relationships between teams.01:33
persiaAvoids most of the potential "us vs. them" distinctions.01:33
ScottL_well that certainly makes sense01:34
persiaScottL_: I'm having browser issues: neither of the browsers I typically use seems to be able to get a good patch from http://trac.jackaudio.org/changeset/3848 ; do you think you could extract one?02:08
persiaIf not, I'll go find someone else.02:08
ScottL_sure, i'll try02:10
ScottL_i see a changelog and a jackalsadriver.cpp file, which do you want? or both?02:11
ScottL_persia: i can also download the unified diff or a zip file02:13
persiaunified diff please :)02:14
ScottL_can I use pastebin to get it to you? or how else?02:15
persiaIf you could attach it to https://bugs.launchpad.net/ubuntu/+source/jack-audio-connection-kit/+bug/494223 , it would be best.02:17
ubottuUbuntu bug 494223 in jack-audio-connection-kit "jack alsa driver unable to initialize capture-only mode" [Low,Triaged]02:17
persia(that's the bug it fixes)02:17
TheMusowhat patch are we trying to fetch?02:18
persiahttp://trac.jackaudio.org/changeset/384802:18
ScottL_I wasn't able to download an actual file, but rather text (i fear this was the problem you were having)02:18
ScottL_well, text in the browser02:19
persiaI want to read it.  It's *supposed* to handle resampling inside jack somehow.02:19
persiaBut I haven't read it yet, because I can7t load that page in my browsers.02:19
TheMusooh02:19
persiaScottL_: If you got a bunch of text that claimed to be a unified diff, that's precisely what I'd prefer.02:20
ScottL_i have the text, how do you want it?02:20
persiaattach it to the bug :)02:22
persiaOr stick it in a pastebin, and I'll do that.02:22
ScottL_http://paste.ubuntu.com/374377/02:23
persiaThank you :)02:23
ScottL_sorry i wasn't quicker, two year old is being needy02:23
persiaNo worries.  You've made possible what was previously difficult.02:24
ScottL_i'll see how you attached it to the bug later as i'm guessing you are going to save the file as a patch and attach it but I don't know how you would name it02:24
TheMusopersia: If its not useful, I have an svn checkout of jack2 here and I can pull the diff right from it if thats easier/better/cleaner.02:25
ScottL_away for a bit with son02:25
persiaTheMuso: The pastebin is very readable for me: I'm just trying to understand it.02:25
persiaTheMuso: If you understand the code, it's the only bug against jack that has a potential solution indicated in LP that isn't fixed.02:26
* persia was trying to trim the bug list to look nice for the MIR.02:26
persiaTheMuso: I don't expect you'd have a lot of time for it for the next 4-5 hours at least, but let me know if you think it would be easy to review (as I've never before looked at the JACK code)02:27
TheMusopersia: I have never looked at jack code either, and no I'm busy for the next few hours.02:28
TheMusoSpeaking of jack2, I was talking to Conor at the sprint about how we need to sort out package names with Debian. If I was to kick that discussion off, would people here be interested in participating?02:30
persiaTheMuso: Ah, I thought you might have because of the checkout :)  No worries, I'll leave you to work, and see if I can use the patch to cause a noticeable behaviour change that makes things better.02:30
TheMusopersia: No I had it lying around for another reason, probably packaging related from some time back.02:31
* persia doesn't really have enough background02:31
persiaWere I trying to push jack2, I'd probably start by asking for free's opinion/02:31
TheMusoAgreed.02:32
persiapity we didn't catch him at UDS :(02:32
TheMusoYeah.02:33
persiahansfbaier: Hey.02:42
hansfbaierpersia: Yes?02:42
persiahansfbaier: Just hadn't seen your nick recently, but had been trying to get someone to review libprolooks102:43
hansfbaierAh, thanks.02:43
hansfbaierpersia: ^02:43
hansfbaierpersia: It probably would need a performance fix for the buttons, but I am pretty short of time ATM02:44
persiahansfbaier: No worries.  My hope is to just get it *in* Ubuntu for now.02:45
persiaOnce it's in, we can get more testers, and some bugs, and look at how to make it better.02:45
persia(and maybe then you'll have time again)02:45
hansfbaierpersia: I hope I corrected all major packaging errors.... Yes, I know, the READMEs are a bit sparse....02:45
hansfbaierpersia: My next big thing for libprolooks will be a patcher widget.02:46
hansfbaierpersia: To make jackpanel be able to do patching also.02:46
persiasomething like patchage, but from the panel?02:47
hansfbaierpersia: Yes, but it will be visually more like a real studio patchbay.02:47
hansfbaierWith jacks and cables02:47
hansfbaierpersia: Well like wiring real equipment together.02:48
persiaRight.  I'll be curious to see it, although I'll admit to liking a sparse interface for lots of things :)02:48
hansfbaierpersia: I hope I can make it simple and very usable though....02:49
hansfbaierpersia: patchage looks nice, but isn't as useable as I'd like to have.02:50
hansfbaierpersia: One of the main features is that it will group multiple channel connections from one device to another together and thus making02:50
hansfbaierpersia: it visually much more tidy and informative02:51
hansfbaierpersia: that would appear like a multicore cable02:51
persiatidiness sounds excellent.02:51
persiaI worried that the graphics for the draped cables might obscure the jacks, but it sounds like you have a plan for that already.02:52
hansfbaierpersia: both qjackctl and patchage look a bit messy with a lot of channels and connections.02:53
persiaI can't use the qjackctl patchbay at all.  It gets too messy too quickly.02:56
persiaWith patchage, I can usually come up with a sane map, but it requires it's own virtual desktop.02:57
persiaSomething in the panel that appears and disappears is very appealing.02:57
hansfbaierpersia: Yes, that's what I had i mind.03:18
aboganiI'm on the outside, I'm looking in, I can see through you, See your true colors, Cause inside you're ugly, You're Ugly like me, I can see through you, See to the real you (Staind - Outside) 07:07
aboganistochastic: Are you around?10:48
stochasticonly for a few minutes10:48
aboganiOk so next time :-)10:49
stochasticwhy? complex issue?10:51
aboganistochastic: No issue at all10:52
aboganistochastic: I just discovered by chance that you are a processing user. 10:52
aboganiProcessing10:52
stochasticsort of.10:52
stochasticI've done very little with the language, but have read up on it10:53
aboganiAh Ok. I supposed that you are interested on it.10:53
aboganimore10:53
stochasticyeah, interactive art programming is kinda where I love to geek out the most10:54
stochasticChucK is my favorite language right now.10:55
aboganiJust curious (only because I'm an Arduino user).... ChucK's URL? 10:56
stochastichttp://chuck.cs.princeton.edu10:56
* stochastic has yet to dive into Arduino...10:56
stochasticAnyways, I should probably be off to bed now. Big day tomorrow.10:57
aboganiOk! Ciao10:57
aboganiGood night!10:57
stochasticnight.10:58
aboganiTheMuso: Are you around?17:03
* abogani is stupid never remember the Luke's TZ! :-(17:04
persia4:00 there17:05
aboganiindeed17:06
aboganiScottL ScottL_ ScottL__: Please don't forget the email17:19
aboganiNo way Tim Gardner don't want release a i386 preempt kernel...17:22
ScottL__abogani: i am taking lunch from work in thirty minutes and was planning on replying to the email during that time :)17:28
aboganiScottL__: Ok sorry to bother you.17:30
ScottL__abogani:  it's okay, you're not bothering me :)17:34
ScottL__abogani:  and sorry that you had to use three of my names!  LOL17:37
ScottL__hmmm, was going to tell abogani that the email was sent, but it appears that he isn't here (which explains why auto-complete tab didn't work now or earlier)18:25

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!