[00:50] I'm going to start a Ubuntu Studio ppa where we have fixed packages that yet haven't been SRUd [01:48] zequence: can I ask what you're trying to accomplish with the PPA? [01:53] micahg: Give users the possibility to use packages that have been fixed but yet not been SRUd [01:53] zequence: yes, but why are they not being SRUd (I'm wondering if there's some breakdown somewhere we can fix) [01:54] micahg: The SRU process takes a bit of time [01:54] months as it seems [01:56] zequence: should take about 2 weeks if everything is ready from upload to get to -updates, 8-10 days if the SRU queue isn't backed up [01:56] bug #956438 [01:56] bug 956438 in jackd2 (Ubuntu Quantal) "qjackctl unable to stop jackd2" [Undecided,New] https://launchpad.net/bugs/956438 [01:57] if you'd like people to test the fixes without -proposed, that's fine, but I'd like to see more stuff pushed through SRU if it's needed (I was thinking of joining the -sru team at some point, but stopped having time) [01:57] I haven't prepared packages for 12.10 and 12.04 though [01:57] there's nothing there indicating it's ready for SRU aside from the bug tasks [01:57] right :) [01:58] something like that can go into the sponsorship queue and you can ping a patch pilot in -devel if it [01:58] But no one has informed me of anything not being right [01:58] s not addressed in a timely fashion [01:59] bug tasks means someone that wants to fix it, can, and they then submit it through the sponsorship process [01:59] so, nothing wrong per se, just that you shouldn't be shocked that nothing has been done with it [02:00] I pinged someone in -bugs [02:00] That got the process started [02:00] well, that'll get you bug tasks, not much more [02:01] I was following the instructions written on the wiki page [02:01] the SRU pagE? [02:01] https://wiki.ubuntu.com/StableReleaseUpdates [02:02] you're at step 5.2 :) [02:05] Well, I wasn't clear on the the details of the process [02:05] I'll have a go tomorrow [02:07] ok, I'm here to help if I can [02:09] micahg: thanks [02:54] Len-nb: i use jamin on the way out of ardour.. as an insert [02:54] Len-nb: sometimes, i use it sandalone on the way out of other things [03:23] holstein, where would it make the most sense to have it in the menu? [03:24] Would it be hard to find in an effects sub menu? [03:24] Len-nb: i think that would be fine [03:24] i always add a flag anyways. so it doesnt auto connect to outputs [03:25] Should we do that to more of the standalone stuff? [03:25] We can request changes to the desktop files upstream holstein [03:26] I would thnk it doesn't make sense for JAMin to auto connect anyway. [03:27] depends [03:28] It doesn't make sense to auto connect for one use out of four [15:39] Len-nb: I think applications should all have a setting for disabling auto connect. For one thing, not everyone wants apps to connect to 1-2 [15:40] and there are ways to make custom auto connects [15:40] Probably people want auto connect by default, but have the ability to disable it [15:40] ..for a lot of apps, not all [15:45] I agree [15:46] I use inputs 9-10 ... auto connecting to 1-2 is not very useful [15:47] zequence, from what I have heard from jack devs, auto connect is considered "rude" (not their words, but my paraphrase) [15:50] zequence, is there any way of renaming jack ports? not just in qjackctl, but so that all apps see the new names. [15:55] zequence, re backdrops: While we have asked for backdrop submissions, we have not given any guidance. [15:56] I would suggest a paragraph or two that gives the backdrop artist an idea of what we are looking for. [15:56] Len-nb: This time around, I don't think we can get much further on the artwork. And I will make a point about this tomorrow [15:56] The idea of getting out of the way and not distracting while looking good. [15:57] I would suggest just including anything properly licensed to look [15:58] For the next release, we need to have rules for this. Because of the shot time period, I felt putting up a unorganized wallpaper submission thing would be a bad idea on anything else than our -devel mail lsit [15:59] short* [15:59] Ya. [15:59] I have started working on a list for 13.04+1 [16:00] I will post it later today... or should I wait? [16:00] Let's wait until this release is out [16:00] I think our stuff for 13.04 is done though [16:00] Soome of it is just defining work flows. [16:01] Some is ongoing. [16:01] I would still rather wait at least for a while, and then start a periof of organized planning, which we also announce [16:01] good. I will work on it in private then. [16:02] The binary I was referring to yesterday was an image. [16:02] the diff seems to have subtracted one image line by line and then added the other the same way. [16:03] Maybe that is how it works. [16:03] The diff is only text, AFAIK, so probably not helpful when binaries are involved [16:03] Better to create a bzr branch [16:04] Do they use those in debian? [16:04] No, probably mostly git [16:04] In which case, you could create a tar ball, but better ask the Debian guys [16:04] Neither the debian or the ubuntu package have a bzr branch [16:05] This is for hexter, it looks like they have just taken the original src and added a debian directory [16:06] That's usually how it works [16:06] debian/rules has instructions for some things, including how to build it [16:07] the debian dir really has all of the package info in it [16:07] How do I know who to talk to? There is a list , does Alessio Treglia sound right? [16:07] pkg-multimedia is a good list [16:07] There's also a irc channel, but it's not on freenode [16:08] OFTC [16:08] I made a patch but don't know how to submit. [16:08] channel #debian-multimedia [16:08] I try those things [16:13] Len-nb: usually when you get the source to a package, using "apt-get source", you can see where the git tree for the package is [16:13] In the case of hexter git://anonscm.debian.org/pkg-multimedia/hexter.git [16:14] Becoming a debian multimedia member gives you upload rights [16:14] Not the same as getting Debian upload rights [16:14] Or, I should say, you get the right to push code [16:16] I think the one most important thing to learn, in order to be really helpful, is probably learning about Debian packagin, the policy and the tools [16:18] Len-nb: Another source for info is http://packages.debian.org/source/sid/hexter [16:19] You can find the adress to the git tree at the bottom [16:26] Well, learning git might be a good idea too :) [16:26] Ya it would.. there are some apps that use it for backup and versioning. [16:27] NAMA, some people use it for ardour too [16:28] I did already DL the debian hexter src packages. [16:28] That is what i was using to diff against [16:30] git is very useful to make diffs too [16:30] But, not sure if you can make a usable binary diff. Should be possible. I just don't know how [16:35] anyways, better ask the MM team