[03:09] when are the mythbuntu autobuilds for 0.24-fixes ran each day or night? [03:35] wouldn't that depend? [03:35] on how long they take to build, how many things are queued before them [03:35] and what timezone your in [03:41] as I recall, unless there is a backlog, early evening us central time [03:41] I dunno, I was hoping a dev would know what time it started [03:42] mrand: thanks! [03:42] just committed a fix and was wondering when it'd be ready for users [03:46] hey.. i see on the site the mythbuntu-control-centre should have an area to switch repositories forward for mythtv 0.25. anyone want to tell me where that is? I'm not seeing it [15:44] taylorr: looks like your change was a bit too late to be picked up in last nights build. Should be in there tonight (lately builds have been completing around 0300 UTC) [15:49] mrand: thanks! [15:49] you're welcome [17:09] anyone know how to enable optical audio passthru on the hd-pvr? [17:49] quentusrex_: did you look on the mythtv HD-PVR page? I don't know if it applies, but you might look on that and read about "default_audio_input" [17:50] mythtv wiki page, I meant [17:51] mrand, I was able to figure it out. Turns out that when you add the capture source what ever input you set there is the only input the device will listen to. [17:51] so optical passthru is disabled if you set to RCA input [20:53] is there a "how to rebuilt your ubuntu package with a patch applied" guide for mythtv around? I'd like to take a peak at #10054 but have never built mythtv [20:56] dekarl: I don't know if it is up-to-date, but yes. let me see if I can find it... [21:02] dekarl: yep, http://mythbunut.org/wiki/recipes. Oh wait, I suspect that's old (pre-git). Here's a brief thing on git-based builds: http://mythbuntu.org/wiki/developer-cheatsheet#Building (you may have to click "building" in the index). If you need help or run into anything, don't hesitate to ask (so that the guide can be improved) [21:04] so it's not as simple a https://wiki.ubuntu.com/PackagingGuide/Complete#Applying_a_patch + https://wiki.ubuntu.com/PackagingGuide/Complete#Building_the_Package_Locally_.28Binary_Only.29 ? [21:05] [wiki.ubuntu.com] PackagingGuide/Complete - Ubuntu Wiki [21:14] dekarl: I've not done a manual build recently, so I can't say for certain. superm1 might be able to. [21:17] I'll try the one from the ubuntu guide as it talks about patches explicitly [21:28] adding "apt-src" in addition to "apt" statements to the mythbuntu sources.list makes getting the source of the packages lots easier :) [21:29] heh [21:36] hmm, there isn't a "debuild --meet-unmet-dependencies" by chance? [21:41] dekarl, 'apt-get build-dep mythtv' [21:41] that would install build dependencies [21:41] is that what you are looking for? [21:43] yes, thats it! thanks [22:18] ah we do need to update that recipes page [22:18] forgot about it [22:18] http://www.mythtv.org/wiki/User:Dekarl/Testing_patches_on_Mythbuntu [22:18] [www.mythtv.org] User:Dekarl/Testing patches on Mythbuntu - MythTV Official Wiki [22:19] yeah that's a pretty straightforward way to go about it [22:19] thought it might come in handy to have a "dude, please test, it's easy" guide at hand for the next patch :) [22:20] we had talked about a way to deploy a web based GUI that you give it a patch and it gives you a PPA with it [22:20] but it doesn't come up enough that it's worth the effort [22:21] that sounds like a cool idea... it avoids seeding ccache and downloading lots [22:21] escepically for people that are afraid of compilers and all that voodoo stuff [22:22] yeah it's perfect for that scenario [22:23] but i feel like mythtv (and mythbuntu) are still fairly techy oriented [22:23] so most the people can follow a set of commands [22:24] over here in DVB land theres lots of patches that don't get tested because the patch and someone who can test it *and* has the development skills don't come together :( I hope a simple checklist (or premade ppas per ticket) can help with that [22:26] i'll clean up the recipe page, i think i can get it down to a few things to follow and you let me know if it looks good [22:26] Ahh, I just commited because it's build and packaging now [22:26] but feel free to edit it as you like [22:27] no i mean i'll update the recipes page at mythbuntu.org [22:27] not right this moment, but i'll try to in the next day or two [22:27] the one that mrand spat at you [22:28] ahh, I see. it's missing the apt/sources change [22:31] I get heaps of these messages, is that normal or is it me? [22:31] dpkg-shlibdeps: warning: dependency on .so.0 could be avoided if "debian/mythbrowser/usr/lib/mythtv/plugins/.so" were not uselessly linked against it (they use none of its symbols). [22:32] those are normal [22:32] it's because mythtv's linking is using the same link command on everything [22:32] i've raised it in #mythtv previously, but no one seems to mind [22:32] hmm, then I'll just life with it. [22:39] superm1: the guide at my user space is good for getting packages built, I can test them in ~50 minutes (or more likely tomorrow) [22:40] dekarl: cool, ideally i'd like to factor it around using https://github.com/MythTV/packaging/blob/master/deb/build-debs.sh though [22:40] [github.com] deb/build-debs.sh at master from MythTV/packaging - GitHub [22:40] because that gets the latest upstream code (either fixes or master) as well as the latest packaging (fixes or master) [22:40] maybe it's best to add an additional optional argument to that script to include a patch [22:40] that would make it super easy for people [22:40] I didn't go that route because I couldn't figure out where to apply the patch [22:41] yeah the script would need a little bit of work to do that automatically (basically automate a few commands about testing applying the patch and where it would have to go as you say) [22:43] on the other hand the way I used is the generic ubuntu way if I understood it correctly, might come in handy, too [22:43] yeah the way you did it is a fairly generic ubuntu way to do it [22:43] btw, does it make sense to include xmltv in the mythbuntu ppas? [22:44] after all mythtv is pretty much useless without guide data :) [22:44] i get the sense that some upstream folk don't want to know anything about how packaging works, so it's nice to abstract it in build scripts when possible [22:44] no one has came clamoring for it, but that might be a good idea too [22:45] Well, once we move from good old cvs to git I'd like to shuffle the build around a bit anyway to conform to modern standards [22:47] for xmltv? [22:48] * dekarl nods [23:07] i'm not sure how the xmltv code is currently packaged, so it might require some other finagling, but will certainly be easier when upstream moves to git [23:25] I think the packaging scripts are all over here http://git.crustynet.org.uk/?p=xmltv.git;a=tree , not in the main repo [23:25] [git.crustynet.org.uk] git.crustynet.org.uk Git - xmltv.git/tree [23:29] dekarl: can you link me a sample patch that was in a bug that a user would generally be asked to apply? [23:29] i need to see if i can get the patch levels matched up [23:31] I'm currently testing this one http://code.mythtv.org/trac/ticket/10054 [23:31] it's a one liner, but with all devs that have spare time in ATSC it's never going to be applied without user testing [23:33] if you want one that's bigger, see http://code.mythtv.org/trac/ticket/9726 without user testing that's likely going nowhere either [23:34] great, that's perfect for adding the functionality to the deb builder sh script [23:34] thanks